Public report of ManageIQ/manageiq-ui-classic, published 16 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, 16 November 2026, 20:07 UTC · Survey ID cd_2f0d0f9f9c8e479792193b341285a40f

ManageIQ/manageiq-ui-classic

Measured 16 November 2026, 20:05 UTC, at code version 120b5c3

First survey, so nothing to compare with yet
CAI score 42.2out of 100 Weak
CriticalWeakAdequateStrongExemplary

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: 97,729 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Code Health, 37.3

Findings by how serious they are

222 critical 1533 serious 324 minor

13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 20:05 UTC

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

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

69of 69 dimensions measured by tools.
2066of 2079 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
69dimensions across 7 lenses, read from 97,729 lines of product code in 2 projects.
Chapters

Executive summary

ManageIQ/manageiq-ui-classic falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 42.2 out of 100 and is rated Weak, and 162 of its 222 critical findings are security problems in its code and in the build pipeline.

Code Health, at 37.3, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 3.3 points. Adopting a type checker comes next, worth about 2.7 points. Raising Code Health to 70 would lift the score to about 46.3.

153 weaknesses in the code could be used by an attacker. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fixing the weaknesses the scanner points to and pinning each tool to an exact version would close both risks. The 37 labels or groups of fields with no name need connecting to their fields or naming.

The product code is 97,729 lines, about €120,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 37.3 · counts for 46%Accessibility 40.1 · counts for 25%Maturity 47.2 · counts for 14%Security and Compliance 47.4 · counts for 8%Production Readiness 52.0 · counts for 4%Architecture 64.4 · counts for 2%Performance 100.0 · counts for 1%

If Code Health rose from 37.3 to 70, the lowest score rated Strong, the score would rise from 42.2 to about 46.3.

Code composition: what the lines of code are
Product code 68%Tests 32%
Rebuild cost: about €120,000 · Estimate
Cost to rebuild€41,000 to €210,000, for 684 to 2,170 hours of work, about 0.8 person-years for 1 to 2 engineers
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 42. 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: 97,729 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
Resolve the 1 finding(s) in Type Safety.
Raises the score by about 3.3 points · Medium effort · Type Safety
2
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`.
Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Raises the score by about 2.7 points · Medium effort · Nullable reference types
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with rails.
Raises the score by about 1.3 points · Low effort · ADR Quality

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Code Health, at 37.3 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 finding(s) in Type Safety. Of all the actions in this report, it raises the score most for the work it takes: about 3.3 points for medium effort, because it clears the 1 Type Safety findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 16% on every change. The history of the code shows how much it changes: about 84,554 lines over the last 90 days, which is about 342,913 lines a year. At that pace, the extra work comes to an estimated 59.3 to 356.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

348 modules, with 181 dependencies between them. 2 loops run through 9 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 308 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 ApplicationHelper.Toolbar2 ApplicationHelper.Toolbar.Mixins3 TextualMixins4 AnsibleCredentialHelper5 AnsiblePlaybookHelper6 AnsibleRepositoryHelper7 ApplicationController8 ApplicationHelper9 AuthKeyPairCloudHelper10 AvailabilityZoneHelper11 CloudDatabaseHelper12 CloudNetworkHelper13 CloudObjectStoreContainerHelper14 CloudObjectStoreObjectHelper15 CloudSubnetHelper16 CloudTenantHelper17 CloudVolumeBackupHelper18 CloudVolumeHelper19 CloudVolumeSnapshotHelper20 CloudVolumeTypeHelper21 ConfigurationJobHelper22 ConfiguredSystemHelper23 ContainerBuildHelper24 ContainerGroupHelper25 ContainerImageHelper26 ContainerNodeHelper27 ContainerProjectHelper28 ContainerTemplateHelper29 EmsCloudHelper30 EmsClusterHelper31 EmsConfigurationHelper32 EmsContainerHelper33 GenericObjectHelper34 Mixins35 ReportController36 ServiceHelper37 (global)38 ApplicationHelper.Button39 OpsController.Settings40 TreeNode
1 ApplicationHelper.Toolbar
2 ApplicationHelper.Toolbar.Mixins
3 TextualMixins
4 AnsibleCredentialHelper1
5 AnsiblePlaybookHelper3
6 AnsibleRepositoryHelper2
7 ApplicationController5
8 ApplicationHelper13
9 AuthKeyPairCloudHelper2
10 AvailabilityZoneHelper3
11 CloudDatabaseHelper4
12 CloudNetworkHelper5
13 CloudObjectStoreContainerHelper3
14 CloudObjectStoreObjectHelper1
15 CloudSubnetHelper4
16 CloudTenantHelper3
17 CloudVolumeBackupHelper3
18 CloudVolumeHelper4
19 CloudVolumeSnapshotHelper3
20 CloudVolumeTypeHelper3
21 ConfigurationJobHelper3
22 ConfiguredSystemHelper1
23 ContainerBuildHelper1
24 ContainerGroupHelper1
25 ContainerImageHelper1
26 ContainerNodeHelper1
27 ContainerProjectHelper1
28 ContainerTemplateHelper1
29 EmsCloudHelper4
30 EmsClusterHelper2
31 EmsConfigurationHelper2
32 EmsContainerHelper7
33 GenericObjectHelper2
34 Mixins1
35 ReportController2
36 ServiceHelper41
37 (global)18111248111111111111111111111111148961
38 ApplicationHelper.Button2
39 OpsController.Settings14
40 TreeNode1
Uses a module listed above itPart of a loopThe module itself
1 ApplicationHelper.Toolbar2 ApplicationHelper.Toolbar.Mixins3 TextualMixins4 AnsibleCredentialHelper5 AnsiblePlaybookHelper6 AnsibleRepositoryHelper7 ApplicationController8 ApplicationHelper9 AuthKeyPairCloudHelper10 AvailabilityZoneHelper11 CloudDatabaseHelper12 CloudNetworkHelper13 CloudObjectStoreContainerHelper14 CloudObjectStoreObjectHelper15 CloudSubnetHelper16 CloudTenantHelper17 CloudVolumeBackupHelper18 CloudVolumeHelper19 CloudVolumeSnapshotHelper20 CloudVolumeTypeHelper21 ConfigurationJobHelper22 ConfiguredSystemHelper23 ContainerBuildHelper24 ContainerGroupHelper25 ContainerImageHelper26 ContainerNodeHelper27 ContainerProjectHelper28 ContainerTemplateHelper29 EmsCloudHelper30 EmsClusterHelper31 EmsConfigurationHelper32 EmsContainerHelper33 GenericObjectHelper34 Mixins35 ReportController36 ServiceHelper37 (global)38 ApplicationHelper.Button39 OpsController.Settings40 TreeNodeApplicationHelper.Toolbar1ApplicationHelper.Toolbar.Mixins2TextualMixins3AnsibleCredentialHelper4AnsiblePlaybookHelper5AnsibleRepositoryHelper6ApplicationController7ApplicationHelper8AuthKeyPairCloudHelper9AvailabilityZoneHelper10CloudDatabaseHelper11CloudNetworkHelper12CloudObjectStoreContainerHelper13CloudObjectStoreObjectHelper14CloudSubnetHelper15CloudTenantHelper16CloudVolumeBackupHelper17CloudVolumeHelper18CloudVolumeSnapshotHelper19CloudVolumeTypeHelper20ConfigurationJobHelper21ConfiguredSystemHelper22ContainerBuildHelper23ContainerGroupHelper24ContainerImageHelper25ContainerNodeHelper26ContainerProjectHelper27ContainerTemplateHelper28EmsCloudHelper29EmsClusterHelper30EmsConfigurationHelper31EmsContainerHelper32GenericObjectHelper33Mixins34ReportController35ServiceHelper36(global)37ApplicationHelper.Button38OpsController.Settings39TreeNode4013251323453143343331111111422721241181112481111111111111111111111111489612141+308 more modules (most-connected shown)

At a glance — Code Health · 37.3 · Weak · gated by R1, R10, X5 ·

At a glance — Architecture · 64.4 · Adequate · gated by D6, R9 ·

At a glance — Maturity · 47.2 · Weak · gated by D34, M2 ·

At a glance — Readiness · 52.0 · Adequate · gated by P3, P7 ·

At a glance — Security · 47.4 · Checked 4 of 9 · gated by D29, C2 ·

At a glance — Accessibility · 40.1 · Weak · gated by AC2, AC4 ·

At a glance — Performance · 100.0 · Exemplary ·

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 — Injection250High / Critical
A03:2025 — Software Supply Chain Failures4Medium

Roadmap

Top priorities: Resolve the 1 finding(s) in Type Safety; Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive; Resolve the 72 FunctionTooLong finding(s) in God Classes — start with index.jsx (22), schema.js (2), action-form.schema.js.

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

Do thisHelpsEffortDimension
Resolve the 1 finding(s) in Type Safety.+3.3 ptsMediumType Safety
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.+2.7 ptsMediumNullable reference types
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with rails.+1.3 ptsLowADR Quality
Resolve the 72 FunctionTooLong finding(s) in God Classes — start with index.jsx (22), schema.js (2), action-form.schema.js.+2.5 ptsHighGod Classes
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.+2.1 ptsMediumCode Duplication
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+2.1 ptsMediumForms & labels
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.0 ptsMediumKeyboard semantics
Resolve the 94 TodoComment finding(s) in Explicit Debt — start with REDACTED (11), textual_summary.rb (7), REDACTED (4).+0.9 ptsMediumExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 481 files carrying findings, judged against the Production bar: 9% slop · 47% mixed · 44% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.0SlopStatic Analysis (SAST): High: REDACTED

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

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

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

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

Could not be resolved — 13

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 69 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 — 69 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D16D17D19D20D24D28D29D30D34D35D43D44AC1AC2AC3AC4AC5AC6AX10AX2AX3AX4C2GD1IC1M1M2M3P1P10P3P6P7PF3R1R10R11R2R3R4R6R7R8R9X1X12X16X17X21X23X24X25X27X28X29X3X30X5

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, 2066 of 2079 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 01a1e5f7-5b73-79a7-ad9b-331494692d87.

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.

  • 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: this repository's production source spans .ts, .tsx, .rb, and our analyzer cannot run the .rb test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 66.3% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2,311 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 691 test source file(s) (.rb) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .rb, and the ruby executor ran against the .rb half and never executed — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `yarn install --immutable --mode=skip-build` in the repository root (1916 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (156007 LoC, 2141 module-visible types across 358 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A filesystem error ended D28's config-credential walk (FileNotFoundException: Could not find file 'app/javascript/oldjs/components/.eslintrc.json'.); configs after that point were not read for credential bindings.
  • AC2 Forms & labels — 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. 318 further occurrence(s) are not listed individually; the score already reflects all 358.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 871 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • 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. 'ActiveRecord::Base' is imported (REDACTED:1223), 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.
  • C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • 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. 'ActiveRecord::Base' is imported (REDACTED:1223), 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. 'ActiveRecord::Base' is imported (REDACTED:1223), 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. 'ActiveRecord::Base' is imported (REDACTED:1223), 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
  • P8 Schema migrations — 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 schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
  • 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. The filesystem refused the listing or the read of: app/javascript/oldjs/components/.eslintrc.json, app/javascript/oldjs/directives/.eslintrc.json, app/javascript/oldjs/services/.eslintrc.json. Every other path was read.
  • 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. 212 further occurrence(s) are not listed individually; the score already reflects all 252.
  • 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
  • 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. 154 further occurrence(s) are not listed individually; the score already reflects all 194.
  • 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. 155 further occurrence(s) are not listed individually; the score already reflects all 195.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 1237 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 24 further occurrence(s) are not listed individually; the score already reflects all 64.
  • X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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 Complexity5.8 / 10Adequate✓ 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 5.8 / 10 · rule-coverage 100% · ceiling Prevented

206 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EmsCommon.button at 120. A further 7 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being CiProcessing.process_vm_buttons at 39 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/helpers/application_helper/title.rb (Title.title_from_layout at 39), app/helpers/miq_ae_class_helper.rb (MiqAeClassHelper.ae_field_fonticon at 27), app/helpers/shared_helper/ab_show_helper.rb (AbShowHelper.shared_button_basic_info at 23). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

EmsCommon.button (cyclomatic 120)REDACTED:193
index.ChargebackAssignmentsForm (cyclomatic 99)app/javascript/components/chargeback-assignments-form/index.jsx:14
ReportController.replace_right_cell (cyclomatic 85)REDACTED:636
CatalogController.replace_right_cell (cyclomatic 72)REDACTED:2299
Common.settings_get_form_vars (cyclomatic 72)app/controllers/ops_controller/settings/common.rb:493

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

What to do

  1. Bring the 6 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with EmsCommon.button (cyclomatic 120), index.ChargebackAssignmentsForm (cyclomatic 99), ReportController.replace_right_cell (cyclomatic 85). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity5.0 / 10Adequate✓ 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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

263 method(s) exceeded the cognitive complexity threshold of 15; the worst was ReportController.replace_right_cell at 153.

ReportController.replace_right_cell (cognitive 153)REDACTED:636
index.ChargebackAssignmentsForm (cognitive 125)app/javascript/components/chargeback-assignments-form/index.jsx:14
Common.settings_get_form_vars (cognitive 113)app/controllers/ops_controller/settings/common.rb:493
CatalogController.replace_right_cell (cognitive 106)REDACTED:2299
MiqRequestMethods.prov_get_form_vars (cognitive 91)REDACTED:725

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

What to do

  1. Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with ReportController.replace_right_cell (cognitive 153), index.ChargebackAssignmentsForm (cognitive 125). — 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 2 together lifts Cognitive Complexity from 5.0 to about 5.3/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

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

D3 · God Classes4.2 / 10Weak✓ 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 4.2 / 10 · rule-coverage 100% · ceiling Prevented

137 god class(es) detected.

FunctionTooLong: index.ChargebackAssignmentsForm · ×72app/javascript/components/chargeback-assignments-form/index.jsx:14
TooManyMethods: MiqAeClassController · ×38REDACTED:2
FileTooLong: REDACTED · ×27REDACTED

What to do

  1. Resolve the 72 FunctionTooLong finding(s) in God Classes — start with index.jsx (22), schema.js (2), action-form.schema.js. — One of this dimension's main actionable groups (72 warning-level).
  2. Resolve the 38 TooManyMethods finding(s) in God Classes — start with textual_summary.rb (6), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (38 warning-level).
  3. Resolve the 27 FileTooLong finding(s) in God Classes — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (27 warning-level).

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

D4 · Code Duplication7.8 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

103 duplicated block group(s) detected. 5.6 % of the production lines (5,439 of 97,729) are in a reported copy. A further 119 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (7 lines × 2) · ×11app/controllers/mixins/ems_common/core.rb:5
Duplicated block (9 lines × 2) · ×9app/controllers/ems_cluster_controller.rb:49
Duplicated block (8 lines × 2) · ×8REDACTED:189
Edited copy of a member (9 corresponding lines) · ×7app/helpers/generic_object_definition_helper.rb:5
Duplicated block (6 lines × 2) · ×7REDACTED:2188

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

What to do

  1. Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with textual_summary.rb (6), core.rb, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with menus.rb (2), ems_cluster_controller.rb, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with REDACTED, ems_cluster_controller.rb, REDACTED. — One of this dimension's main actionable groups (8 warning-level).

Detailed fixes: d4_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+RubyGems), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)2.3 / 10Critical✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

111 of 173 classes have LCOM4 above 3.

Low cohesion: ApplicationController (LCOM4 91) · ×111REDACTED:4

What to do

  1. Resolve the 111 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED, REDACTED, explorer_presenter.rb. — One of this dimension's main actionable groups (111 warning-level).

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

D10 · Test Quality9.5 / 10Stronggated by 70 serious findings✓ Tool-verified

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

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

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

0 skipped, 70 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2311 tests. Measured on the JavaScript/TypeScript suite only — at least 691 test source file(s) (.rb) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: Login page · ×70cypress/e2e/ui/login.cy.js:7
Mock-dominated test: passes the intercepted action to next · ×9app/javascript/spec/miq-redux/middleware.spec.js:22

What to do

  1. Resolve the 70 No assertions finding(s) in Test Quality — start with menu.cy.js (13), searchbox.cy.js (5), rates.cy.js (4). — One of this dimension's main actionable groups (70 warning-level).
  2. Resolve the 9 Mock-dominated test finding(s) in Test Quality — start with date-value-editor.spec.js (5), middleware.spec.js, label-selection.spec.js. — One of this dimension's main actionable groups (9 recommendation-level).

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

D12 · Dependency Hygiene10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 outdated direct gem(s), 0 pinning defect(s). 15 declaration(s) graded against rubygems.org, none of them against a committed Gemfile.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. 5 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.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. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 8 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 8 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. This repository publishes itself under Apache 2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 31 serious findings✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: app/javascript/components/group-form/index.jsx (6×63=378); app/javascript/components/chargeback-assignments-form/index.jsx (3×99=297); REDACTED (10×26=260) Repeated repair below the complexity floor: app/javascript/components/automate-simulation-form/index.jsx (4 of 5 changes were fixes); app/javascript/components/automate-simulation-form/automate-simulation-form.schema.js (3 of 5 changes were fixes); app/javascript/notifications/init.js (3 of 4 changes were fixes)

Hotspot: app/javascript/components/group-form/index.jsx · ×27app/javascript/components/group-form/index.jsx:42
Repeated repair: app/javascript/components/automate-simulation-form/index.jsx · ×4app/javascript/components/automate-simulation-form/index.jsx:9

What to do

  1. Resolve the 27 Hotspot finding(s) in Churn × Complexity Hotspots — start with index.jsx (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (27 warning-level).
  2. Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.jsx, automate-simulation-form.schema.js, init.js. — One of this dimension's main actionable groups (4 warning-level).

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

D16 · Bus Factor9.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 251 of the 1282 production source files in this repository: 967 are under the ~2,400-byte size floor this dimension measures over, and the remaining 64 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.7 / 10Stronggated by 160 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

169 deducted task-comment markers across 97729 LoC (0.2/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×94spec/spec_helper.rb:16
FixmeComment · ×65spec/support/controller_helper.rb:85
TodoComment repeated across 10 filesapp/helpers/application_helper/toolbar/miq_templates_center.rb:80

What to do

  1. Resolve the 94 TodoComment finding(s) in Explicit Debt — start with REDACTED (11), textual_summary.rb (7), REDACTED (4). — One of this dimension's main actionable groups (94 warning-level).
  2. Resolve the 65 FixmeComment finding(s) in Explicit Debt — start with navbar.rb (4), tree_builder.rb (3), REDACTED (3). — One of this dimension's main actionable groups (65 warning-level).
  3. Resolve the 1 TodoComment repeated across 10 files finding(s) in Explicit Debt — start with miq_templates_center.rb. — One of this dimension's main actionable groups (1 warning-level).

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

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. 3 document(s) read across 1 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 foundbin/rails:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with rails. — 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.

D24 · Comment Value7.2 7.1 / 10Strong✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 7.1 / 10 · rule-coverage 99% · ceiling Documented

53 of 1864 judged comments only repeat the code they sit on (2.8 %). 30 comment(s) in another language or script were not judged.

redundant comment · ×42app/javascript/components/automate-import-export-form/review-import-form.jsx:28
doc comments repeat the namesapp/javascript/components/schedule-form/schedule-form-types.ts:75

What to do

  1. Resolve the 42 redundant comment finding(s) in Comment Value — start with expect_dual_list.js (4), zone.cy.js (3), index.jsx (2). — One of this dimension's main actionable groups (42 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.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

254 finding(s): 0 critical, 162 high, 92 medium, 0 low. 9 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 1 file(s) — `bin/before_install` (line 12) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities9.3 / 10Stronggated by 4 serious findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

What to do

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

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

D34 · Knowledge Freshness3.5 / 10Weak✓ 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 3.5 / 10 · rule-coverage 100% · ceiling Documented

195 of 315 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 315 of the 1282 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×192REDACTED:1
Most significant orphaned file · ×3app/presenters/menu/default_menu.rb:1
Concentrated knowledge decay

What to do

  1. Resolve the 192 Orphaned file finding(s) in Knowledge Freshness — start with textual_summary.rb (35), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (192 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with default_menu.rb, textual_summary.rb, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: TagSelector.js↔ValueSelector.js 71%; default_menu.rb↔routes.rb 50%; taggingWrapper.jsx↔middleware.js 50%

Boundary-crossing change coupling: default_menu.rb ↔ routes.rbapp/presenters/menu/default_menu.rb:1
Change coupling: TagSelector.js ↔ ValueSelector.js · ×2app/javascript/tagging/components/InnerComponents/TagSelector.js:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with default_menu.rb. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 Change coupling finding(s) in Change Coupling — start with TagSelector.js, taggingWrapper.jsx. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d35_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.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 74 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.2 / 10Adequate✓ Tool-verified

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

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

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

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — app/views/dashboard/login.html.haml:4, app/views/generic_object_definition/_show_god.html.haml:13, app/views/vm_common/_config.html.haml:31

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 & labels2.3 / 10Critical✓ 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 <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — app/javascript/components/file-upload/index.jsx:12, app/javascript/components/selected-groups-list/index.jsx:26
  • This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — app/javascript/components/miq-structured-list/miq-structured-list-body/value-tags/miq-structured-list-inputs.jsx:9
  • A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×2) — app/javascript/menu/search.tsx:54, app/javascript/menu/search.tsx:110
  • 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. (×35) — app/views/catalog/_confirmation_modal.html.haml:22, app/views/catalog/_form_basic_info.html.haml:9, app/views/catalog/_form_basic_info.html.haml:21, …

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 structure5.8 / 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.

  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×15) — app/views/chargeback_rate/_form.html.haml:55, app/views/ems_infra/scaledown.html.haml:36, app/views/generic_mailer/policy_action_email.html.haml:5, …
  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — app/views/dashboard/iframe.html.haml:2
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — app/views/layouts/_policy_sim.html.haml:10, app/views/vm_common/_policy_options.html.haml:8
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×6) — app/views/layouts/application.html.haml:2, app/views/layouts/login.html.haml:2, app/views/layouts/print.html.haml:2, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — app/views/vm_common/console_vmrc.html.haml:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics2.7 / 10Weak✓ 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. (×9) — app/views/configuration/_ui_3.html.haml:10, app/views/layouts/_edit_to_email.html.haml:58, app/views/layouts/_perf_options.html.haml:3, …
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×7) — app/views/layouts/_compare.html.haml:11, app/views/layouts/_empty.html.haml:10, app/views/layouts/_tabs.html.haml:11, …
  • An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — app/views/shared/_compare_header_expanded.html.haml:7

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness6.2 / 10Adequate✓ Tool-verified

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.

  • aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. (×2) — app/javascript/components/miq_debug/toast-item.jsx:45, app/views/static/edit_alert_dialog.html.haml:3

What to do

  • Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety6.4 / 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.

  • `i` sets color: #fff on background-color: #0088ce — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — app/stylesheet/legacy/fonticon_picker.scss:19
  • `.ae-namespace-tree-scroll .tree-branch-wrapper` 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. — app/stylesheet/miq-ae-class.scss:71
  • `.reconfigure-form .reconfigure-form-table .miq-data-table .cell .cds--btn--ghost` 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. — app/stylesheet/miq-data-table.scss:362
  • `.overflow-menu-disabled` 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. — app/stylesheet/toolbar.scss:225
  • `.about-modal .cds--modal-container .about-modal-body .plugins-button` 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. — app/stylesheet/legacy/about_modal_background.scss:69
  • `.vm-snapshot-tree .tree-branch-wrapper` 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. — app/javascript/components/vm-snapshot-tree-select/styles.scss:77
  • `.automate_entry_points .tree-branch-wrapper` 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. — app/javascript/components/automate-entry-points/styles.scss:32
  • `.cds--modal-content:focus` 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. — app/javascript/components/automate-entry-points/styles.scss:77

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 composition6.7 / 10Adequate✓ 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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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 Controls3.3 / 10Weak✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
  • Only 2 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.

What to do

  • Name the access rules — Pundit or Action Policy classes (a PostPolicy), a CanCanCan Ability, or rolify roles — and consult them where access is checked (authorize @record, load_and_authorize_resource, authorize!), so the rule set is reviewable and testable on its own.
  • Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Ruby: methods whose whole body still raises NotImplementedError where nothing overrides them, or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings 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 & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Ruby: methods that only raise NotImplementedError or a "not implemented" error where nothing overrides them, methods that take inputs and return a constant or do nothing, 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.

M1 · Documentation (README)6.0 / 10Adequate✓ 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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • 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 documentation0.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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.

P1 · CI/CD gates8.0 / 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.

  • A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.

What to do

  • Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
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.

P3 · Security & performance tooling3.0 / 10Weak✓ 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 brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3

What to do

  • Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.

  • `Net::HTTP.start` 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. — REDACTED:17

What to do

  • Set `open_timeout` and `read_timeout` explicitly on every client (Net::HTTP, Faraday `request: { timeout: }`, HTTParty `timeout:`), add Faraday's `:retry` middleware (faraday-retry) or `retriable`, and a breaker (`circuitbox`, `stoplight`) around dependencies that fail.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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.

R1 · Type Safety0.4 / 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.

  • 45 typed · 1075 plain JS — the untyped files are app/javascript/angular/index.js, app/javascript/angular/miq_ae_class/ae_method_form_controller.js, app/javascript/components/AeInlineMethod/FilterNamespace.jsx, app/javascript/components/AeInlineMethod/NamespaceSelector.jsx, app/javascript/components/AeInlineMethod/helper.js, app/javascript/components/AeInlineMethod/index.jsx (+1069 more).
R10 · Code Duplication3.1 / 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.

  • 138 duplicated blocks under app/javascript/components/ have copies in at least two of the sibling directories ab-form, action-form, ansible-credentials-form, ansible-playbook-edit-catalog-form, ansible-playbook-workflow, ansible-repository-form (+98 more sibling(s) not listed) — 100 of them are reported below, and 38 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 138 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 138 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 138 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. — app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:51
  • 16 duplicated blocks under app/javascript/components/provider-dashboard-charts/ have copies in at least two of the sibling directories events-bar-chart, heat-map-chart, pod-trend-charts, provider-dashboard-utilization-chart, recent-host-chart, recent-vm-chart (+2 more sibling(s) not listed) — 11 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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. — app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.js:9
  • 15 duplicated blocks under app/javascript/ have copies in at least two of the sibling directories components, helpers, oldjs, tagging — 13 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app/javascript/components/miq-about-modal/helper.js:26
  • 12 duplicated blocks under app/javascript/components/data-tables/ have copies in at least two of the sibling directories button-group-list, button-list, catalog-items-table, datastore, iso-datastore-table, object-types-list (+6 more sibling(s) not listed) — 9 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app/javascript/components/data-tables/datastore/index.jsx:27
  • app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:51 · app/javascript/components/terraform-template-catalog-form/index.jsx:43 — the two spans are one implementation copied and then locally edited — 862 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. — app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:51
  • app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:1 · app/javascript/components/workflow-credential-mapping-form/workflow-credential-mapping-form.schema.js:1 — these 2 files are line-for-line copies of one another — 124 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:1
  • app/javascript/components/miq-ae-class/index.jsx:12 · app/javascript/components/miq-ae-customization/index.jsx:10 — the two spans are one implementation copied and then locally edited — 646 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. — app/javascript/components/miq-ae-class/index.jsx:12
  • app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js:8 · app/javascript/components/storage-service-form/storage-service-form.schema.js:6 — the two spans are one implementation copied and then locally edited — 750 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. — app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js:8
  • app/javascript/components/async-action-button.jsx:13 · app/javascript/components/async-credentials/async-credentials.jsx:13 — the two spans are one implementation copied and then locally edited — 686 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. — app/javascript/components/async-action-button.jsx:13
  • app/javascript/components/ansible-repository-form/index.jsx:1 · app/javascript/components/embedded-terraform-repository-form/index.jsx:1 · app/javascript/components/workflow-repository-form/index.jsx:1 — these 3 files are line-for-line copies of one another — 88 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — app/javascript/components/ansible-repository-form/index.jsx:1
  • app/javascript/components/utilization/utilization-report.tsx:17 · app/javascript/components/utilization/utilization-summary.tsx:13 — the two spans are one implementation copied and then locally edited — 524 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. — app/javascript/components/utilization/utilization-report.tsx:17
  • app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:13 · app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:13
  • app/javascript/components/ansible-credentials-form/index.jsx:9 · app/javascript/components/embedded-terraform-credentials-form/index.jsx:9 · app/javascript/components/workflow-credentials-form/index.jsx:9 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — app/javascript/components/ansible-credentials-form/index.jsx:9
  • app/javascript/components/container-projects/helper.jsx:107 · app/javascript/components/container-projects/helper.jsx:186 · app/javascript/components/container-projects/helper.jsx:267 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — app/javascript/components/container-projects/helper.jsx:107
  • app/javascript/components/embedded-automate-entry-point/index.jsx:8 · app/javascript/components/embedded-workflow-entry-point/index.jsx:8 — the two spans are one implementation copied and then locally edited — 451 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. — app/javascript/components/embedded-automate-entry-point/index.jsx:8
  • app/javascript/components/miq-about-modal/helper.js:26 · app/javascript/oldjs/miq_browser_detect.js:32 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — app/javascript/components/miq-about-modal/helper.js:26
  • app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:7 · app/javascript/components/terraform-template-catalog-form/helper.js:7 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:7
  • app/javascript/components/remove-catalog-item-modal.jsx:30 · app/javascript/components/remove-generic-item-modal.jsx:68 — the two spans are one implementation copied and then locally edited — 463 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. — app/javascript/components/remove-catalog-item-modal.jsx:30
  • app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx:9 · app/javascript/components/workflow-credential-mapping-form/index.jsx:11 — the two spans are one implementation copied and then locally edited — 448 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. — app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx:9
  • app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationDonutChart.js:1 · app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationMemoryDonutChart.js:1 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationDonutChart.js:1
  • app/javascript/components/ansible-repository-form/ansible-repository-form.schema.js:1 · app/javascript/components/embedded-terraform-repository-form/embedded-terraform-repository-form.schema.js:1 · app/javascript/components/workflow-repository-form/workflow-repository-form.schema.js:1 — these 3 files are line-for-line copies of one another — 64 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — app/javascript/components/ansible-repository-form/ansible-repository-form.schema.js:1
  • app/javascript/components/network-security-groups-form/index.jsx:19 · app/javascript/components/routers-form/index.jsx:77 — the two spans are one implementation copied and then locally edited — 320 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. — app/javascript/components/network-security-groups-form/index.jsx:19
  • app/javascript/components/cloud-volume-form/index.jsx:34 · app/javascript/components/storage-service-form/index.jsx:41 — the two spans are one implementation copied and then locally edited — 384 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. — app/javascript/components/cloud-volume-form/index.jsx:34
  • app/javascript/components/host-initiator-group-form/index.jsx:18 · app/javascript/components/physical-storage-form/index.jsx:41 — the two spans are one implementation copied and then locally edited — 373 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. — app/javascript/components/host-initiator-group-form/index.jsx:18
  • app/javascript/components/ansible-credentials-form/ansible-credentials-form.schema.js:3 · app/javascript/components/embedded-terraform-credentials-form/embedded-terraform-credentials-form.schema.js:3 · app/javascript/components/workflow-credentials-form/workflow-credentials-form.schema.js:3 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/javascript/components/ansible-credentials-form/ansible-credentials-form.schema.js:3
  • app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:108 · app/javascript/components/terraform-template-catalog-form/helper.js:91 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:108
  • app/javascript/components/ap-form/event-log-tab.jsx:39 · app/javascript/components/ap-form/file-tab.jsx:33 — 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. — app/javascript/components/ap-form/event-log-tab.jsx:39
  • app/javascript/components/chargeback-assignments-form/simple-list.jsx:25 · app/javascript/components/chargeback-assignments-form/tenant-tree.jsx:44 — the two spans are one implementation copied and then locally edited — 389 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. — app/javascript/components/chargeback-assignments-form/simple-list.jsx:25
  • app/javascript/components/data-tables/datastore/index.jsx:27 · app/javascript/components/data-tables/time-profile-table/index.jsx:16 — the two spans are one implementation copied and then locally edited — 415 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. — app/javascript/components/data-tables/datastore/index.jsx:27
  • app/javascript/components/ansible-playbook-edit-catalog-form/schemaHelper.js:2 · app/javascript/components/terraform-template-catalog-form/schemaHelper.js:2 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — app/javascript/components/ansible-playbook-edit-catalog-form/schemaHelper.js:2
  • app/javascript/components/button-group/index.jsx:150 · app/javascript/components/generic-objects-form/custom-button-form/index.jsx:110 — the two spans are one implementation copied and then locally edited — 387 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. — app/javascript/components/button-group/index.jsx:150
  • app/javascript/components/host-initiator-form/index.jsx:11 · app/javascript/components/volume-mapping-form/index.jsx:16 — the two spans are one implementation copied and then locally edited — 286 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. — app/javascript/components/host-initiator-form/index.jsx:11
  • app/javascript/components/cloud-database-form/cloud-database-form.jsx:38 · app/javascript/components/cloud-tenant-form/index.jsx:14 — the two spans are one implementation copied and then locally edited — 255 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. — app/javascript/components/cloud-database-form/cloud-database-form.jsx:38
  • app/javascript/components/reconfigure-vm-form/helpers/disk.js:59 · app/javascript/components/reconfigure-vm-form/helpers/network.js:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — app/javascript/components/reconfigure-vm-form/helpers/disk.js:59
  • app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:259 · app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.js:199 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:259
  • app/javascript/components/ab-form/ab-form.schema.js:38 · app/javascript/components/generic-objects-form/custom-button-form/custom-button-form.schema.js:27 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — app/javascript/components/ab-form/ab-form.schema.js:38
  • app/javascript/components/pxe-image-edit-form/index.jsx:13 · app/javascript/components/pxe-windows-image-edit-form/index.jsx:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — app/javascript/components/pxe-image-edit-form/index.jsx:13
  • app/javascript/components/tagging-editor/tag.jsx:9 · app/javascript/tagging/components/InnerComponents/Tag.js:9 — the two spans are one implementation copied and then locally edited — 202 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. — app/javascript/components/tagging-editor/tag.jsx:9
  • app/javascript/components/ab-form/ab-form.schema.js:85 · app/javascript/components/generic-objects-form/custom-button-form/custom-button-form.schema.js:79 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/javascript/components/ab-form/ab-form.schema.js:85
  • app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.js:9 · app/javascript/components/provider-dashboard-charts/servers-pie-chart/index.js:9 — the two spans are one implementation copied and then locally edited — 237 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. — app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.js:9

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 Boundaries8.4 / 10Strong✓ 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.

  • app/javascript/packs/globals.js:24 imports patternfly/dist/js/patternfly-settings.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:24
  • app/javascript/packs/globals.js:25 imports patternfly/dist/js/patternfly-functions-base.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:25
  • app/javascript/packs/globals.js:26 imports patternfly/dist/js/patternfly-functions-list.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:26
  • app/javascript/packs/globals.js:27 imports patternfly/dist/js/patternfly-functions-sidebar.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:27
  • app/javascript/packs/globals.js:28 imports patternfly/dist/js/patternfly-functions-popovers.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:28
  • app/javascript/packs/globals.js:29 imports patternfly/dist/js/patternfly-functions-data-tables.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:29
  • app/javascript/packs/globals.js:30 imports patternfly/dist/js/patternfly-functions-navigation.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:30
  • app/javascript/packs/globals.js:31 imports patternfly/dist/js/patternfly-functions-count-chars.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:31
  • app/javascript/packs/globals.js:32 imports patternfly/dist/js/patternfly-functions-colors.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:32
  • app/javascript/packs/globals.js:33 imports patternfly/dist/js/patternfly-functions-charts.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:33
  • app/javascript/packs/globals.js:34 imports patternfly/dist/js/patternfly-functions-fixed-heights.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:34
  • app/javascript/packs/globals.js:35 imports patternfly/dist/js/patternfly-functions-tree-grid.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/globals.js:35
  • app/javascript/packs/jasmine-assets.js:4 imports jasmine-jquery/lib/jasmine-jquery.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — app/javascript/packs/jasmine-assets.js:4
  • config/webpack/RailsEnginesPlugin.js:3 imports enhanced-resolve/lib/getPaths, 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. — config/webpack/RailsEnginesPlugin.js:3
  • config/webpack/RailsEnginesPlugin.js:4 imports enhanced-resolve/lib/forEachBail, 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. — config/webpack/RailsEnginesPlugin.js:4

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 Complexity8.4 / 10Strong✓ 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.

  • CarbonValueEditor has cyclomatic complexity 53 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/expression-editor/carbon-value-editor.jsx:273
  • (anonymous) has cyclomatic complexity 50 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. — app/javascript/components/report-editor/validation.ts:7
  • ChargebackFilter has cyclomatic complexity 45 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:112
  • atomToHuman has cyclomatic complexity 41 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/expression-editor/expression-human.js:89
  • (anonymous) has cyclomatic complexity 40 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/report-editor/report-form-values.ts:73
  • processReplaceRightCell has cyclomatic complexity 33 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/oldjs/miq_explorer.js:183
  • miqAtomToRule has cyclomatic complexity 33 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/expression-editor/expression-adapter.js:20
  • FindValueEditor has cyclomatic complexity 33 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/expression-editor/find-value-editor.jsx:115
  • InstanceForm has cyclomatic complexity 30 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/components/miq-ae-class/instance-form.jsx:12
  • ruleToMiqAtom has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/expression-editor/expression-adapter.js:161
  • SummaryTab has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/components/report-editor/tabs/summary-tab.tsx:112
  • validateRule has cyclomatic complexity 24 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/expression-editor/expression-validator.js:82
  • ChargebackAssignmentsForm has cyclomatic complexity 24 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/chargeback-assignments-form/index.jsx:14
  • (anonymous) has cyclomatic complexity 23 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/chargeback-assignments-form/index.jsx:86
  • (anonymous) has cyclomatic complexity 23 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/group-form/index.jsx:93
  • (anonymous) has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/components/workers-form/workers-form.jsx:21
  • DashboardWidget has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/dashboard-widgets/dashboard-charts/index.jsx:9
  • ReviewImportForm has cyclomatic complexity 20 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/automate-import-export-form/review-import-form.jsx:10
  • buildSubmitData has cyclomatic complexity 19 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/ab-form/helper.js:100
  • onSubmit has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/ap-form/index.jsx:146
  • ChartsTab has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/report-editor/tabs/charts-tab.tsx:48
  • getInitialValue has cyclomatic complexity 18 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/data-tables/datastore/schema/modal-form.schema.js:43
  • onItemClick has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/gtl-view.jsx:433
  • formatFieldValues has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx:76
  • CheckboxTreeComponent has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/tree-view/checkbox_tree.jsx:8
  • onSubmit has cyclomatic complexity 17 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/group-form/index.jsx:213
  • ApForm has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — app/javascript/components/ap-form/index.jsx:15
  • LabelSelection has cyclomatic complexity 16 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/chargeback-assignments-form/label-selection.jsx:16
  • onClick has cyclomatic complexity 15 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/miq-toolbar.jsx:37
  • ExpressionEditorInner has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/condition-form/expression-editor-field.jsx:10
  • (anonymous) has cyclomatic complexity 15 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/async-credentials/async-credentials.jsx:89
  • fetchResources has cyclomatic complexity 15 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/chargeback-assignments-form/index.jsx:233
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/network-security-groups-form/helper.js:9
  • buildErrorDetails has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/miq-error-modal/miq-error-modal.jsx:24
  • DateValueEditor has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/expression-editor/date-value-editor.jsx:178
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — cypress/support/commands/provider_helper_commands.js:180
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — app/javascript/components/expression-editor/field-config.js:82, app/javascript/components/role-form/index.jsx:125
  • fetchSavedTagCategory has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — app/javascript/components/chargeback-assignments-form/tag-selection.jsx:65
  • prepareSubmitData has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/javascript/components/generic-objects-form/custom-button-form/helper.js:82
R3 · Large Files9.5 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • REDACTED has 1231 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
  • app/javascript/components/ansible-playbook-edit-catalog-form/schema.js has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:1
  • app/javascript/components/action-form/action-form.schema.js has 545 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/action-form/action-form.schema.js:1
  • app/javascript/components/expression-editor/carbon-value-editor.jsx has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/expression-editor/carbon-value-editor.jsx:1
  • app/javascript/components/chargeback-assignments-form/index.jsx has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/chargeback-assignments-form/index.jsx:1
  • app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:1
  • app/javascript/components/gtl-view.jsx has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/gtl-view.jsx:1
  • app/javascript/components/schedule-form/helper.ts has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/schedule-form/helper.ts:1
  • app/javascript/packs/component-definitions-common.js has 432 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/packs/component-definitions-common.js:1
  • app/javascript/components/container-projects/helper.jsx has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/javascript/components/container-projects/helper.jsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage7.4 / 10Strong✓ 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) — app/javascript/components/gtl-view.jsx:1, app/javascript/packs/component-definitions-common.js:1, app/javascript/oldjs/miq_explorer.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling6.7 / 10Adequate✓ Tool-verified

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

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

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
  • The root package declares the lint script `lint` (`eslint .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `.` (or the workspace's task runner). — package.json:22
  • This stylelint config makes every finding a warning, and stylelint exits 0 on warnings: the lint step passes however many fire, so it gates nothing. Set the rules the team enforces to `error`, or run stylelint with `--max-warnings 0` where CI runs it. — .stylelintrc:2

What to do

  • Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code5.3 / 10Adequate✓ Tool-verified

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

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

  • Unreachable from the 25 application, 12 tooling and 391 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `yarn test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (×12) — app/javascript/components/gtl-view.jsx, app/javascript/components/provider-form/index.jsx, app/javascript/components/settings-company-tags/index.jsx, …
  • no import path from any entry point (25 application, 12 tooling, 391 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 — app/javascript/packs/component-definitions-common.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (×6) — app/javascript/oldjs/miq_explorer.js, app/javascript/oldjs/miq_qe.js, app/javascript/oldjs/miq_c3.js, …
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/angular/index.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 — app/javascript/angular/miq_ae_class/ae_method_form_controller.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/terraform-template-catalog-form/index.jsx) — 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) — app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.js, app/javascript/components/terraform-template-catalog-form/helper.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/host-initiator-form/index.jsx) — 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 — app/javascript/components/host-initiator-form/host-initiator-form.schema.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/controllers/index.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 (×3) — app/javascript/oldjs/controllers/playbook-reusable-code-mixin.js, app/javascript/oldjs/controllers/dialog_editor/dialog_editor_controller.js, app/javascript/oldjs/controllers/dialog_user/dialog_user_controller.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/volume-mapping-form/index.jsx) — 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 — app/javascript/components/volume-mapping-form/volume-mapping-form.schema.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/cloud-volume-form/index.jsx) — 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 — app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx) — 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 — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/provider-dashboard-charts/heat-map-chart/index.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 — app/javascript/components/provider-dashboard-charts/heat-map-chart/HeatMapChartGraph.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/request-workflow-status/index.jsx) — 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 — app/javascript/components/request-workflow-status/request-workflow-status-item.jsx
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/storage-service-form/index.jsx) — 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 — app/javascript/components/storage-service-form/storage-service-form.schema.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/storage-service-form/get-compliant-resources.jsx) — 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 — app/javascript/components/async-action-button.jsx
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/miq-about-modal/miq-about-modal.jsx) — 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 — app/javascript/components/miq-about-modal/helper.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.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) — app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationDonutChart.js, app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationMemoryDonutChart.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/components/data-tables/gtl/StaticGTLView.jsx, app/javascript/components/data-tables/gtl/index.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 — app/javascript/components/data-tables/gtl/DataTable.jsx
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/request-workflow-status/request-workflow-status-item.jsx) — 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 — app/javascript/components/request-workflow-status/data.js
  • no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/AeInlineMethod/index.jsx) — 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 — app/javascript/components/AeInlineMethod/NamespaceSelector.jsx

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 Hygiene4.0 / 10Weak✓ 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.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — app/javascript/spec/toolbar-actions/toolbar-actions-delete.spec.js:6, eslint.config.js:1, app/javascript/spec/helpers/old_js_file_require_helper.js:6

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports2.9 / 10Weak✓ 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.

  • app/javascript/components/ap-form/category-tab.jsx → app/javascript/forms/data-driven-form.jsx → app/javascript/forms/mappers/componentMapper.jsx → app/javascript/components/ap-form/category-tab.jsx (one verified cycle inside a mutually-dependent group of 22 files) — app/javascript/components/ap-form/category-tab.jsx:1
  • app/javascript/components/cloud-volume-actions-form/helper.js → app/javascript/components/cloud-volume-actions-form/restore-from-backup.schema.js → app/javascript/components/cloud-volume-actions-form/helper.js — app/javascript/components/cloud-volume-actions-form/helper.js:2
  • app/javascript/miq-component/helpers.js → app/javascript/miq-component/registry.js → app/javascript/miq-component/helpers.js — app/javascript/miq-component/helpers.js:1

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
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.

X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `emptyChildren` is exported and takes `parent: object` from its caller, and it calls itself at line 33 (`emptyChildren`) with a piece of `parent` — and nowhere in `emptyChildren` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `emptyChildren` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — app/javascript/components/workers-form/helpers.jsx:33
  • `buildPatch` is exported and takes `parent: object` from its caller, and it calls itself at line 48 (`buildPatch`) with a piece of `parent` — and nowhere in `buildPatch` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `buildPatch` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — app/javascript/components/workers-form/helpers.jsx:48

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped4.6 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `node.text` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:57
  • `taskContent` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — app/javascript/controllers/reloadable_controller.js:30
  • `pid` is text this program did not author, and it is written into the text of an element through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:443, REDACTED:483
  • `menu_id` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:450
  • `menu_title` is text this program did not author, and it is written into the text of an element through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:451
  • `pid` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:484
  • `btoa(JSON.stringify(row_col_chart_index))` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:490
  • `options.legend` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — app/javascript/oldjs/miq_explorer.js:7
  • `content` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — app/javascript/oldjs/miq_explorer.js:114, app/javascript/oldjs/miq_explorer.js:286
  • `data.rightCellText` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — app/javascript/oldjs/miq_explorer.js:165
  • `__('The appliance has no access to the assets required to run the WebMKS console. For more info please see the docume…` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — app/javascript/packs/remote_consoles_webmks.js:76

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob7.4 / 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.

  • `transformSaved` accepts `report_id` from the caller and keeps it in `report_id` on line 30, where only it can read the value — but nothing ever reads `report_id`. Setting `report_id` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `report_id` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `report_id` from the accepted options so callers stop setting a knob that does nothing. — app/javascript/components/data-tables/optimization/transform.js:30
  • `transformReport` accepts `action` from the caller and keeps it in `action` on line 42, where only it can read the value — but nothing ever reads `action`. Setting `action` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `action` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `action` from the accepted options so callers stop setting a knob that does nothing. — app/javascript/components/data-tables/optimization/transform.js:42

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.
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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 handling6.7 / 10Adequate✓ 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. (×2) — REDACTED:48, app/javascript/components/expression-editor/date-value-editor.jsx:50
  • `.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. (×2) — app/javascript/components/expression-editor/date-value-editor.jsx:199, app/javascript/components/automate-import-export-form/review-import-form.jsx:97
  • `… rescue false` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:111
  • `rescue StandardError => _err` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:976
  • `rescue` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — REDACTED:1276, app/helpers/number_helper.rb:28, app/helpers/number_helper.rb:48, …
  • `rescue StandardError` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — REDACTED:139, app/controllers/mixins/actions/vm_actions/evacuate.rb:63, app/controllers/mixins/actions/vm_actions/live_migrate.rb:48
  • `… rescue nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — REDACTED:692, REDACTED:1738, app/controllers/ops_controller/settings/common.rb:505
  • `… rescue []` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:41

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1237 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.

What to do

  • Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.

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 Health37.3Weak — gated by R1, R10, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture64.4Adequate — gated by D6, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity47.2Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness52.0Adequate — gated by P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security47.4Checked 4 of 9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility40.1Weak — gated by AC2, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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 'ActiveRecord::Base' (REDACTED:1223) but declares no persisted model this check reads (ActiveRecord and Sequel migration columns, db/schema.rb, Mongoid document fields). 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 'ActiveRecord::Base' (REDACTED:1223) but declares no persisted model this check reads (ActiveRecord/Sequel migration and db/schema.rb columns, Mongoid document fields). 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 'ActiveRecord::Base' (REDACTED:1223) but declares no persisted model this check reads (ActiveRecord migration and db/schema.rb columns, Sequel migration columns, Mongoid fields). 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.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 53 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; this repository's Ruby 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; this repository's TypeScript 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.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no exported interface declares behaviour
  • 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
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: this repository stores data through 'ActiveRecord::Base' (REDACTED:1223) but declares no persisted model this check reads (ActiveRecord migration and db/schema.rb columns, Sequel migration columns, Mongoid fields). 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 scored — polyglot repository, one half's runner produced no measurement
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — N/A — too few peers to establish a naming convention (14884 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Ruby surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • 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.
  • D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 value object(s); a Domain/Aggregates/ValueObjects layer
  • 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
  • M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
  • 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'.
  • P2 Observability — This repository's JavaScript/TypeScript, Ruby source (2 module(s), 1987 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • P8 Schema migrations — ActiveRecord is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
  • P9 Domain vs controller coverage — coverage data present for 579 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • S1 Web-Security Posture — Not assessed: 1237 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for Ruby: this reading covers the code's own cryptography and the TLS connections it opens as a client, and a Rails, Rack or Sinatra application's transport, header and validation settings are not modelled. Their absence here is not a finding about this repository.
  • 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
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
  • 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
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 222 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
  • + 126 more in this group — see findings.md.
AC2 · Forms & labels · <label> that labels no control · ×37
  • <label> that labels no control app/javascript/components/file-upload/index.jsx:12 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/javascript/components/selected-groups-list/index.jsx:26 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/views/catalog/_confirmation_modal.html.haml:22 — 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 app/views/catalog/_form_basic_info.html.haml:9 — 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 app/views/catalog/_form_basic_info.html.haml:21 — 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 app/views/catalog/_form_basic_info.html.haml:31 — 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 app/views/catalog/_form_basic_info.html.haml:38 — 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 app/views/catalog/_form_basic_info.html.haml:50 — 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 app/views/catalog/_form_basic_info.html.haml:64 — 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 app/views/catalog/_form_basic_info.html.haml:76 — 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 app/views/catalog/_form_basic_info.html.haml:90 — 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 app/views/catalog/_form_basic_info.html.haml:103 — 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 app/views/catalog/_form_basic_info.html.haml:120 — 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 app/views/catalog/_form_basic_info.html.haml:132 — 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 app/views/catalog/_form_basic_info.html.haml:144 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control app/views/catalog/_form_basic_info.html.haml:155 — 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 app/views/catalog/_form_basic_info.html.haml:172 — 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 app/views/catalog/_form_basic_info.html.haml:181 — 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 app/views/catalog/_form_basic_info.html.haml:189 — 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 app/views/catalog/_form_ovf_template_options.html.haml:7 — 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 app/views/catalog/_form_ovf_template_options.html.haml:18 — 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 app/views/catalog/_form_ovf_template_options.html.haml:28 — 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 app/views/catalog/_form_ovf_template_options.html.haml:37 — 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 app/views/catalog/_form_ovf_template_options.html.haml:49 — 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 app/views/catalog/_form_ovf_template_options.html.haml:61 — 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.
  • + 12 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×6
  • Click handler on a non-interactive <div> app/views/configuration/_ui_3.html.haml:10 — 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> app/views/layouts/_edit_to_email.html.haml:58 — 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> app/views/layouts/_perf_options.html.haml:3 — 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> app/views/miq_policy_rsop/_rsop_results.html.haml:44 — 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> app/views/shared/views/_compliance_history.html.haml:3 — 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> app/views/vm_common/_policies.html.haml:8 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC1 · Text alternatives · <img> without a text alternative · ×3
  • <img> without a text alternative app/views/dashboard/login.html.haml:4 — 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 app/views/generic_object_definition/_show_god.html.haml:13 — 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 app/views/vm_common/_config.html.haml:31 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC4 · Keyboard semantics · Click handler on a non-interactive <td> · ×2
  • Click handler on a non-interactive <td> app/views/ops/_classification_entry.html.haml:49 — 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 <td> app/views/ops/_classification_entry.html.haml:51 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC5 · ARIA correctness · aria-hidden on a focusable element · ×2
  • aria-hidden on a focusable element app/javascript/components/miq_debug/toast-item.jsx:45 — aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
  • aria-hidden on a focusable element app/views/static/edit_alert_dialog.html.haml:3 — aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) app/javascript/components/cloud-volume-actions-form/helper.js:2 — app/javascript/components/cloud-volume-actions-form/helper.js → app/javascript/components/cloud-volume-actions-form/restore-from-backup.schema.js → app/javascript/components/cloud-volume-actions-form/helper.js
  • Import cycle (2 files) app/javascript/miq-component/helpers.js:1 — app/javascript/miq-component/helpers.js → app/javascript/miq-component/registry.js → app/javascript/miq-component/helpers.js
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title app/views/dashboard/iframe.html.haml:2 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> app/views/vm_common/console_vmrc.html.haml:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Click handler on a non-interactive <tr> · ×1
  • Click handler on a non-interactive <tr> app/views/shared/summary/_textual_listview.html.haml:14 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: default_menu.rb ↔ routes.rb app/presenters/menu/default_menu.rb:1 — `app/presenters/menu/default_menu.rb` (context presenters) and `config/routes.rb` (context config) sit in DIFFERENT parts of the tree yet change together 50% of the time (41 of the 82 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 41 shared commits counted here, the most recent 3 are `48170eea` Convert Help Menu Form to React; `1cc6e746` Added Embedded Workflows / Credentials Page; `2b8f6c50` Remove workflow_credential_controller — run `git show` on any of them.
R8 · Dependency Hygiene · Unlisted import 'angular-mocks' · ×1
  • Unlisted import 'angular-mocks' app/javascript/spec/toolbar-actions/toolbar-actions-delete.spec.js:6 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'globals' · ×1
  • Unlisted import 'globals' eslint.config.js:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'patternfly-bootstrap-treeview' · ×1
  • Unlisted import 'patternfly-bootstrap-treeview' app/javascript/spec/helpers/old_js_file_require_helper.js:6 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) app/javascript/components/ap-form/category-tab.jsx:1 — app/javascript/components/ap-form/category-tab.jsx → app/javascript/forms/data-driven-form.jsx → app/javascript/forms/mappers/componentMapper.jsx → app/javascript/components/ap-form/category-tab.jsx (one verified cycle inside a mutually-dependent group of 22 files)
Serious — 1533 finding(s)
D6 · Cohesion (LCOM4) · Low cohesion · ×111
  • Low cohesion: ApplicationController (LCOM4 91) REDACTED:4 — ApplicationController's methods fall into 91 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 91 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: OpsController (LCOM4 71) REDACTED:1 — OpsController's methods fall into 71 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 71 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ExplorerPresenter (LCOM4 58) app/presenters/explorer_presenter.rb:1 — ExplorerPresenter's methods fall into 58 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 58 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TreeBuilderVandt (LCOM4 58) app/presenters/tree_builder_vandt.rb:1 — TreeBuilderVandt's methods fall into 58 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 58 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: GenericFeatureButton (LCOM4 57) app/helpers/application_helper/button/generic_feature_button.rb:1 — GenericFeatureButton's methods fall into 57 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 57 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TreeBuilderImages (LCOM4 57) app/presenters/tree_builder_images.rb:1 — TreeBuilderImages's methods fall into 57 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 57 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TreeBuilderInstances (LCOM4 57) app/presenters/tree_builder_instances.rb:1 — TreeBuilderInstances's methods fall into 57 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 57 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WidgetPresenter (LCOM4 56) app/presenters/widget_presenter.rb:1 — WidgetPresenter's methods fall into 56 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 56 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ReportController (LCOM4 32) REDACTED:3 — ReportController's methods fall into 32 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 32 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MiqAeClassController (LCOM4 18) REDACTED:2 — MiqAeClassController's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: StorageController (LCOM4 16) REDACTED:1 — StorageController's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ToolbarBuilder (LCOM4 13) app/helpers/application_helper/toolbar_builder.rb:1 — ToolbarBuilder's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TreeBuilderAutomateSimulationResults (LCOM4 13) app/presenters/tree_builder_automate_simulation_results.rb:1 — TreeBuilderAutomateSimulationResults's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ChargebackRateController (LCOM4 12) REDACTED:1 — ChargebackRateController's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NetworkRouterController (LCOM4 12) REDACTED:1 — NetworkRouterController's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WorkflowController (LCOM4 12) app/controllers/workflow_controller.rb:1 — WorkflowController's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WorkflowCredentialController (LCOM4 12) app/controllers/workflow_credential_controller.rb:1 — WorkflowCredentialController's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AnsibleCredentialController (LCOM4 11) REDACTED:1 — AnsibleCredentialController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CloudDatabaseController (LCOM4 11) app/controllers/cloud_database_controller.rb:1 — CloudDatabaseController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CloudSubnetController (LCOM4 11) app/controllers/cloud_subnet_controller.rb:1 — CloudSubnetController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CloudTenantController (LCOM4 11) app/controllers/cloud_tenant_controller.rb:1 — CloudTenantController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EmsStorageController (LCOM4 11) app/controllers/ems_storage_controller.rb:1 — EmsStorageController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: FloatingIpController (LCOM4 11) REDACTED:1 — FloatingIpController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: HostController (LCOM4 11) REDACTED:1 — HostController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: HostInitiatorController (LCOM4 11) app/controllers/host_initiator_controller.rb:1 — HostInitiatorController's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • + 86 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×94
  • TodoComment spec/spec_helper.rb:16 — # TODO: isolate the helpers we need for UI specs instead of general Dir glob — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_cloud_network_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_cloud_subnet_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_ems_network_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_ems_storage_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_floating_ip_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_network_port_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_network_router_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/shared/controllers/shared_examples_for_security_group_controller.rb:22 — # TODO(lsmola) figure out why I have to mock pdf available here, but not in other Manager's lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/product/reports_spec.rb:36 — # TODO: ApplicationController::Performance::CHARTS_REPORTS_FOLDER — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment spec/controllers/dashboard_controller_spec.rb:531 — # TODO: figure out why flash messages are not in result.body — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment lib/gtl_formatter.rb:4 — # TODO: make sure we can autoload this properly without loading core first — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment cypress/e2e/e2e_helper.rb:31 — # TODO: By default, Factory bot sets definition_file_paths to directories to search for factories: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment config/routes.rb:609 — # TODO: routes for new/edit/copy buttons need to be revisited — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment config/routes.rb:610 — # TODO: so they can be changed to send up POST request instead of GET — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/presenters/tree_builder.rb:309 — ## Timelines (TODO) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/presenters/tree_builder_vandt.rb:29 — # TODO: Do more to pre-prune the tree. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/presenters/tree_kids.rb:16 — # TODO: Perhaps push the object sorting down to SQL, if possible -- no point where there are few items. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/presenters/tree_node/ext_management_system.rb:4 — # # TODO: This should really leverage .base_model on an EMS — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:83 — # TODO: Remove this old open-tag-only way in favor of block style — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/helpers/gtl_helper.rb:67 — # TODO: the "what happens on nil" logic should probably live here, not in ReportDataController.prototype.initObjects — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/helpers/vm_helper.rb:6 — # TODO: These methods can be removed once the Summary and ListNav data layer is consolidated. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/helpers/vm_helper/textual_summary.rb:19 — # TODO: Determine if DoNav + url_for + :title is the right way to do links, or should it be link_to with :title — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/helpers/vm_cloud_helper/textual_summary.rb:16 — # TODO: Determine if DoNav + url_for + :title is the right way to do links, or should it be link_to with :title — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/helpers/host_helper/textual_summary.rb:8 — # TODO: Determine if DoNav + url_for + :title is the right way to do links, or should it be link_to with :title — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 69 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×72
  • FunctionTooLong: index.ChargebackAssignmentsForm app/javascript/components/chargeback-assignments-form/index.jsx:14 — FunctionTooLong — ChargebackAssignmentsForm runs 397 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 297 over it, 3.97× 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: action-form.schema.createSchema app/javascript/components/action-form/action-form.schema.js:8 — FunctionTooLong — createSchema runs 377 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 277 over it, 3.77× 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: chargeback-filter.ChargebackFilter app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:112 — FunctionTooLong — ChargebackFilter runs 337 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 237 over it, 3.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: instance-form.InstanceForm app/javascript/components/miq-ae-class/instance-form.jsx:12 — FunctionTooLong — InstanceForm runs 288 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 188 over it, 2.88× 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: label-selection.LabelSelection app/javascript/components/chargeback-assignments-form/label-selection.jsx:16 — FunctionTooLong — LabelSelection runs 258 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 158 over it, 2.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.GroupForm app/javascript/components/group-form/index.jsx:42 — FunctionTooLong — GroupForm runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ae_method_form_controller.aeMethodFormController app/javascript/angular/miq_ae_class/ae_method_form_controller.js:4 — FunctionTooLong — aeMethodFormController runs 224 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: carbon-value-editor.CarbonValueEditor app/javascript/components/expression-editor/carbon-value-editor.jsx:273 — FunctionTooLong — CarbonValueEditor runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.ApForm app/javascript/components/ap-form/index.jsx:15 — FunctionTooLong — ApForm runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: summary-tab.SummaryTab app/javascript/components/report-editor/tabs/summary-tab.tsx:112 — FunctionTooLong — SummaryTab runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.SettingsReplicationForm app/javascript/components/settings-replication-form/index.jsx:15 — FunctionTooLong — SettingsReplicationForm runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.RoleForm app/javascript/components/role-form/index.jsx:14 — FunctionTooLong — RoleForm 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: tag-selection.TagSelection app/javascript/components/chargeback-assignments-form/tag-selection.jsx:16 — FunctionTooLong — TagSelection runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ab-form.schema.createSchema app/javascript/components/ab-form/ab-form.schema.js:26 — FunctionTooLong — createSchema runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: playbook-reusable-code-mixin.playbookReusableCodeMixin app/javascript/oldjs/controllers/playbook-reusable-code-mixin.js:4 — FunctionTooLong — playbookReusableCodeMixin runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: main-menu.MainMenu app/javascript/menu/main-menu.tsx:27 — FunctionTooLong — MainMenu 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: index.AutomateEntryPoints app/javascript/components/automate-entry-points/index.jsx:23 — FunctionTooLong — AutomateEntryPoints runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.SettingsCUCollectionTab app/javascript/components/settings-cu-collection/index.jsx:13 — FunctionTooLong — SettingsCUCollectionTab runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: host-initiator-form.schema.createSchema app/javascript/components/host-initiator-form/host-initiator-form.schema.js:53 — FunctionTooLong — createSchema runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: field-picker.FieldPicker app/javascript/components/report-editor/field-picker.tsx:17 — FunctionTooLong — FieldPicker runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: workers.schema.addSchema app/javascript/components/workers-form/workers.schema.js:6 — FunctionTooLong — addSchema 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: miq-table-cell.MiqTableCell app/javascript/components/miq-data-table/miq-table-cell.jsx:15 — FunctionTooLong — MiqTableCell runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: namespace-tree-modal.NamespaceTreeModal app/javascript/components/miq-ae-class/namespace-tree-modal.jsx:42 — FunctionTooLong — NamespaceTreeModal runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: charts_config.chartConfig app/javascript/components/provider-dashboard-charts/charts_config.js:41 — FunctionTooLong — chartConfig runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: import-datastore-via-git-modal.ImportDatastoreViaGitModal app/javascript/components/automate-import-export-form/import-datastore-via-git-modal.jsx:9 — FunctionTooLong — ImportDatastoreViaGitModal runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 47 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×70
  • No assertions: Login page cypress/e2e/ui/login.cy.js:7 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Overview > cypress/e2e/ui/menu.cy.js:16 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Services > cypress/e2e/ui/menu.cy.js:26 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Clouds > cypress/e2e/ui/menu.cy.js:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Infrastructure > cypress/e2e/ui/menu.cy.js:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Physical Infrastructure > cypress/e2e/ui/menu.cy.js:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Containers > cypress/e2e/ui/menu.cy.js:69 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Network > cypress/e2e/ui/menu.cy.js:87 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Storage > cypress/e2e/ui/menu.cy.js:99 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Automation > cypress/e2e/ui/menu.cy.js:115 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Control > cypress/e2e/ui/menu.cy.js:139 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Settings > cypress/e2e/ui/menu.cy.js:152 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Documentation cypress/e2e/ui/menu.cy.js:167 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ManageIQ.org cypress/e2e/ui/menu.cy.js:180 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Menu search cypress/e2e/ui/searchbox.cy.js:6 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Is present on list view page cypress/e2e/ui/searchbox.cy.js:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Is present on explorer page cypress/e2e/ui/searchbox.cy.js:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Is not present on non-list page cypress/e2e/ui/searchbox.cy.js:23 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Is present on list view page cypress/e2e/ui/searchbox.cy.js:28 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should search nodes only within expanded tree cypress/e2e/ui/validate-select-accordion-item.cy.js:9 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should support path arrays containing both exact strings and regex patterns cypress/e2e/ui/validate-select-accordion-item.cy.js:51 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should not collapse already expanded node cypress/e2e/ui/validate-select-accordion-item.cy.js:61 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: can delete an analysis profile cypress/e2e/ui/Settings/Application-Settings/analysis-profiles.cy.js:280 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Should fail if start date is greater than end date cypress/e2e/ui/Settings/Application-Settings/c_and_u_gap_collection.cy.js:121 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: Validate gap collection initiation cypress/e2e/ui/Settings/Application-Settings/c_and_u_gap_collection.cy.js:131 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 45 more in this group — see findings.md.
D17 · Explicit Debt · FixmeComment · ×65
  • FixmeComment spec/support/controller_helper.rb:85 — # FIXME: This hash needs cleanups as we clenup the /report_data, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment spec/presenters/tree_node_spec.rb:5 — # FIXME: rewrite this to FactoryBot — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment spec/presenters/tree_node/vm_or_template_spec.rb:4 — # FIXME: make this dynamic somehow by using VmOrTemplate.descendants — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment spec/controllers/host_controller_spec.rb:472 — # FIXME: This should rather be a POST, but it really is a GET. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment spec/controllers/miq_ae_customization_controller_spec.rb:535 — # FIXME: this tree is an exceptional one, it's going to be removed when we replace the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment spec/controllers/optimization_controller_spec.rb:11 — # FIXME: this should go away with #4943
  • FixmeComment spec/controllers/vm_controller_spec.rb:8 — # FIXME: need to render views for now, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment spec/controllers/vm_controller_spec.rb:15 — # FIXME: the espace=false seems unused — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment config/routes.rb:1664 — # FIXME: Change tagging_edit to POST only; We need to remove the redirects — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment config/routes.rb:2180 — # FIXME: Change stamp to POST only; We need to remove the redirect — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/custom_buttons_mixin.rb:12 — # FIXME: don't we have a method for the splits? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/custom_buttons_mixin.rb:13 — # FIXME: cannot we ask for the null parent using Arel? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/explorer_presenter.rb:42 — # element_updates -- update DOM element content or title FIXME: content can be — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_builder.rb:14 — # FIXME: some subclasses still access @sb — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_builder.rb:40 — # FIXME: parent ids should be provided on autoload as well — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_builder.rb:204 — # already a node? FIXME: make a class for node — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_builder_catalog_items.rb:45 — # FIXME: adding gettext here would break the tree_select for languages other than English — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_builder_snapshots.rb:34 — # FIXME: deciding based on the string is not ideal, it should be evaluated on the node object instead — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_node.rb:6 — # FIXME: fill in missing docs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/tree_node/node.rb:28 — # FIXME: this makes problems in tests — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/presenters/menu/default_menu.rb:52 — # FIXME: remove? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment REDACTED:716 — # FIXME: singular vs plural for controller.class.toolbar_singular — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment REDACTED:1029 — # FIXME: a refactoring of identify_record and related is needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/helpers/gtl_helper.rb:61 — # FIXME: fetch_path doesn't work on structs in a hash — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment app/helpers/application_helper/navbar.rb:22 — # FIXME: The 'active' below is an active section not an item. That is wrong. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 40 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED · ×43
  • 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
  • + 18 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file app/javascript/components/gtl-view.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/packs/component-definitions-common.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 app/javascript/oldjs/miq_explorer.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 app/javascript/angular/miq_ae_class/ae_method_form_controller.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 app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.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 app/javascript/components/host-initiator-form/host-initiator-form.schema.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 app/javascript/oldjs/controllers/playbook-reusable-code-mixin.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 app/javascript/oldjs/miq_qe.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 app/javascript/components/terraform-template-catalog-form/helper.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 app/javascript/menu/main-menu.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/oldjs/controllers/dialog_editor/dialog_editor_controller.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 app/javascript/components/provider-form/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/settings-company-tags/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/container-group-console/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/volume-mapping-form/volume-mapping-form.schema.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 app/javascript/components/terraform-template-catalog-form/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/report-editor/report-editor-types.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/miq-about-modal/miq-about-modal.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/AeInlineMethod/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/oldjs/miq_c3.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 app/javascript/oldjs/miq_c3_config.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 app/javascript/components/cloud-volume-form/cloud-volume-form.schema.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 app/javascript/oldjs/miq_ujs_bindings.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 app/javascript/components/data-tables/requests-table/index.jsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.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.
D3 · God Classes · TooManyMethods · ×38
  • TooManyMethods: MiqAeClassController REDACTED:2 — TooManyMethods — 140 methods. The bar is 30 methods; this is 110 over it, 4.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CatalogController REDACTED:1 — TooManyMethods — 133 methods. The bar is 30 methods; this is 103 over it, 4.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Compare REDACTED:1 — TooManyMethods — 125 methods. The bar is 30 methods; this is 95 over it, 4.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ApplicationController REDACTED:4 — TooManyMethods — 116 methods. The bar is 30 methods; this is 86 over it, 3.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ApplicationHelper REDACTED:1 — TooManyMethods — 98 methods. The bar is 30 methods; this is 68 over it, 3.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextualSummary app/helpers/host_helper/textual_summary.rb:1 — TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextualSummary app/helpers/vm_helper/textual_summary.rb:1 — TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CiProcessing REDACTED:1 — TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: VmCommon REDACTED:1 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: OpsRbac REDACTED:2 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextualSummary app/helpers/service_helper/textual_summary.rb:1 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Performance REDACTED:1 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MiqRequestMethods REDACTED:1 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: StorageController REDACTED:1 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: InfraNetworkingController app/controllers/infra_networking_controller.rb:1 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextualSummary app/helpers/physical_server_helper/textual_summary.rb:1 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DashboardController REDACTED:1 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MiqRequestController REDACTED:1 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ReportController REDACTED:3 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: OpsController REDACTED:1 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: EditorMapping app/controllers/report_controller/reports/editor_mapping.rb:15 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ContainerSummaryHelper app/helpers/container_summary_helper.rb:1 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextualSummary app/helpers/pxe_helper/textual_summary.rb:1 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GenericObjectDefinitionController REDACTED:1 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MiqAeCustomizationController REDACTED:1 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 13 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×27
  • Hotspot: app/javascript/components/group-form/index.jsx app/javascript/components/group-form/index.jsx:42 — app/javascript/components/group-form/index.jsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in index.GroupForm at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/group-form/index.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/chargeback-assignments-form/index.jsx app/javascript/components/chargeback-assignments-form/index.jsx:14 — app/javascript/components/chargeback-assignments-form/index.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 99 in index.ChargebackAssignmentsForm at line 14. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/chargeback-assignments-form/index.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:278 — REDACTED changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in MiqAeClassController.replace_right_cell at line 278. 3 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:515 — REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in Compare.prepare_data_for_compare_or_drift_report at line 515. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/group-form/customer-tags-tab.jsx app/javascript/components/group-form/customer-tags-tab.jsx:28 — app/javascript/components/group-form/customer-tags-tab.jsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in customer-tags-tab.CustomerTagsTab at line 28. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/group-form/customer-tags-tab.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/report-editor/tabs/summary-tab.tsx app/javascript/components/report-editor/tabs/summary-tab.tsx:112 — app/javascript/components/report-editor/tabs/summary-tab.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in summary-tab.SummaryTab at line 112. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/tabs/summary-tab.tsx`: 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: app/javascript/components/automate-import-export-form/review-import-form.jsx app/javascript/components/automate-import-export-form/review-import-form.jsx:10 — app/javascript/components/automate-import-export-form/review-import-form.jsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in review-import-form.ReviewImportForm at line 10. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/automate-import-export-form/review-import-form.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/chargeback-assignments-form/label-selection.jsx app/javascript/components/chargeback-assignments-form/label-selection.jsx:16 — app/javascript/components/chargeback-assignments-form/label-selection.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in label-selection.LabelSelection at line 16. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/chargeback-assignments-form/label-selection.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/report-editor/index.tsx app/javascript/components/report-editor/index.tsx:61 — app/javascript/components/report-editor/index.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in index.ReportEditor at line 61. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/index.tsx`: 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: app/javascript/components/sortable-list/index.jsx app/javascript/components/sortable-list/index.jsx:22 — app/javascript/components/sortable-list/index.jsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in index.SortableList at line 22. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/sortable-list/index.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/ab-form/index.jsx app/javascript/components/ab-form/index.jsx:13 — app/javascript/components/ab-form/index.jsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in index.AbForm at line 13. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/ab-form/index.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:587 — REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in OpsRbac.rbac_edit_reset at line 587. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/chargeback-assignments-form/tag-selection.jsx app/javascript/components/chargeback-assignments-form/tag-selection.jsx:16 — app/javascript/components/chargeback-assignments-form/tag-selection.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in tag-selection.TagSelection at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/chargeback-assignments-form/tag-selection.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx:18 — app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in class-fields-editor.ClassFieldsEditor at line 18. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/report-editor/field-picker.tsx app/javascript/components/report-editor/field-picker.tsx:17 — app/javascript/components/report-editor/field-picker.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in field-picker.FieldPicker at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/field-picker.tsx`: 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: app/javascript/components/miq-data-table/miq-table-cell.jsx app/javascript/components/miq-data-table/miq-table-cell.jsx:15 — app/javascript/components/miq-data-table/miq-table-cell.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in miq-table-cell.MiqTableCell at line 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/miq-data-table/miq-table-cell.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/report-editor/tabs/preview-tab.tsx app/javascript/components/report-editor/tabs/preview-tab.tsx:40 — app/javascript/components/report-editor/tabs/preview-tab.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in preview-tab.PreviewTab at line 40. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/tabs/preview-tab.tsx`: 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: app/javascript/components/ab-form/helper.js app/javascript/components/ab-form/helper.js:100 — app/javascript/components/ab-form/helper.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in helper.buildSubmitData at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/ab-form/helper.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: app/javascript/components/report-editor/tabs/charts-tab.tsx app/javascript/components/report-editor/tabs/charts-tab.tsx:48 — app/javascript/components/report-editor/tabs/charts-tab.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in charts-tab.ChartsTab at line 48. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/tabs/charts-tab.tsx`: 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: app/javascript/components/report-editor/tabs/trend-columns-tab.tsx app/javascript/components/report-editor/tabs/trend-columns-tab.tsx:19 — app/javascript/components/report-editor/tabs/trend-columns-tab.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in trend-columns-tab.TrendColumnsTab at line 19. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/tabs/trend-columns-tab.tsx`: 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: app/javascript/components/expression-editor/index.jsx app/javascript/components/expression-editor/index.jsx:36 — app/javascript/components/expression-editor/index.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in index.ExpressionEditor at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/expression-editor/index.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/expression-editor/find-value-editor.jsx app/javascript/components/expression-editor/find-value-editor.jsx:115 — app/javascript/components/expression-editor/find-value-editor.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in find-value-editor.FindValueEditor at line 115. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/expression-editor/find-value-editor.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/miq-ae-class/namespace-tree-modal.jsx app/javascript/components/miq-ae-class/namespace-tree-modal.jsx:42 — app/javascript/components/miq-ae-class/namespace-tree-modal.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in namespace-tree-modal.NamespaceTreeModal at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/miq-ae-class/namespace-tree-modal.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/tree-view/checkbox_tree.jsx app/javascript/components/tree-view/checkbox_tree.jsx:8 — app/javascript/components/tree-view/checkbox_tree.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in checkbox_tree.CheckboxTreeComponent at line 8. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/tree-view/checkbox_tree.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: app/javascript/components/report-editor/tabs/filter/standard-filter.tsx app/javascript/components/report-editor/tabs/filter/standard-filter.tsx:16 — app/javascript/components/report-editor/tabs/filter/standard-filter.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in standard-filter.StandardFilter at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/report-editor/tabs/filter/standard-filter.tsx`: 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.
  • + 2 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×27
  • FileTooLong: REDACTED REDACTED — FileTooLong — 2230 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1730 over it, 4.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 2126 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1626 over it, 4.25× 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 — 1604 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1104 over it, 3.21× 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 — 1426 significant lines (blank, comment-only and punctuation-only lines excluded). 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: REDACTED REDACTED — FileTooLong — 1201 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 701 over it, 2.40× 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 — 1181 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 681 over it, 2.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1138 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 638 over it, 2.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: REDACTED REDACTED — FileTooLong — 952 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 452 over it, 1.90× 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 — 852 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 352 over it, 1.70× 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 — 787 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 287 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 781 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 281 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: settings/common.rb app/controllers/ops_controller/settings/common.rb — FileTooLong — 740 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 240 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 689 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 189 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 181 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 148 over it, 1.30× 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 — 626 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 126 over it, 1.25× 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 — 622 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 122 over it, 1.24× 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: report_controller/menus.rb app/controllers/report_controller/menus.rb — FileTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded). 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: REDACTED REDACTED — FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 42 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 35 over it, 1.07× 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 — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× 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 — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× 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 — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: reports/editor_mapping.rb app/controllers/report_controller/reports/editor_mapping.rb — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • + 2 more in this group — see findings.md.
AC3 · Page structure · Data table has no header cells · ×15
  • Data table has no header cells app/views/chargeback_rate/_form.html.haml:55 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/ems_infra/scaledown.html.haml:36 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/generic_mailer/policy_action_email.html.haml:5 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/host/_form.html.haml:7 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/layouts/_policy_sim.html.haml:56 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/layouts/_role_visibility.html.haml:22 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/layouts/_role_visibility.html.haml:41 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/layouts/listnav/_compare_sections.html.haml:9 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/miq_ae_class/_angular_inputs_form.html.haml:6 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/miq_ae_customization/_dialog_sample_buttons.html.haml:4 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/miq_alert/_form.html.haml:126 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/miq_request/_request.html.haml:92 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/report/_menu_form1.html.haml:7 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/report/_menu_form2.html.haml:8 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells app/views/shared/buttons/_group_order_form.html.haml:6 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
R11 · Import Boundaries · Boundary violation [package · ×15
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:24 — app/javascript/packs/globals.js:24 imports patternfly/dist/js/patternfly-settings.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:25 — app/javascript/packs/globals.js:25 imports patternfly/dist/js/patternfly-functions-base.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:26 — app/javascript/packs/globals.js:26 imports patternfly/dist/js/patternfly-functions-list.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:27 — app/javascript/packs/globals.js:27 imports patternfly/dist/js/patternfly-functions-sidebar.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:28 — app/javascript/packs/globals.js:28 imports patternfly/dist/js/patternfly-functions-popovers.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:29 — app/javascript/packs/globals.js:29 imports patternfly/dist/js/patternfly-functions-data-tables.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:30 — app/javascript/packs/globals.js:30 imports patternfly/dist/js/patternfly-functions-navigation.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:31 — app/javascript/packs/globals.js:31 imports patternfly/dist/js/patternfly-functions-count-chars.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:32 — app/javascript/packs/globals.js:32 imports patternfly/dist/js/patternfly-functions-colors.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:33 — app/javascript/packs/globals.js:33 imports patternfly/dist/js/patternfly-functions-charts.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:34 — app/javascript/packs/globals.js:34 imports patternfly/dist/js/patternfly-functions-fixed-heights.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/globals.js:35 — app/javascript/packs/globals.js:35 imports patternfly/dist/js/patternfly-functions-tree-grid.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] app/javascript/packs/jasmine-assets.js:4 — app/javascript/packs/jasmine-assets.js:4 imports jasmine-jquery/lib/jasmine-jquery.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] config/webpack/RailsEnginesPlugin.js:3 — config/webpack/RailsEnginesPlugin.js:3 imports enhanced-resolve/lib/getPaths, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] config/webpack/RailsEnginesPlugin.js:4 — config/webpack/RailsEnginesPlugin.js:4 imports enhanced-resolve/lib/forEachBail, 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.
D29 · Static Analysis (SAST) · REDACTED · ×14
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×14
  • Swallowed exception (caught, then discarded) REDACTED:111 — `… rescue false` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:976 — `rescue StandardError => _err` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:1276 — `rescue` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/helpers/number_helper.rb:28 — `rescue` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/helpers/number_helper.rb:48 — `rescue` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/helpers/cloud_volume_helper/textual_summary.rb:60 — `rescue` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/helpers/cloud_volume_helper/textual_summary.rb:66 — `rescue` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:139 — `rescue StandardError` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:692 — `… rescue nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:1738 — `… rescue nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/controllers/ops_controller/settings/common.rb:505 — `… rescue nil` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/controllers/mixins/actions/vm_actions/evacuate.rb:63 — `rescue StandardError` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) app/controllers/mixins/actions/vm_actions/live_migrate.rb:48 — `rescue StandardError` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:41 — `… rescue []` 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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×13
  • Untrusted text written into markup unescaped REDACTED:57 — `node.text` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped app/javascript/controllers/reloadable_controller.js:30 — `taskContent` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:443 — `pid` is text this program did not author, and it is written into the text of an element through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:450 — `menu_id` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:451 — `menu_title` is text this program did not author, and it is written into the text of an element through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:483 — `pid` is text this program did not author, and it is written into the text of an element through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:484 — `pid` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:490 — `btoa(JSON.stringify(row_col_chart_index))` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped app/javascript/oldjs/miq_explorer.js:7 — `options.legend` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped app/javascript/oldjs/miq_explorer.js:114 — `content` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped app/javascript/oldjs/miq_explorer.js:165 — `data.rightCellText` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped app/javascript/oldjs/miq_explorer.js:286 — `content` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped app/javascript/packs/remote_consoles_webmks.js:76 — `__('The appliance has no access to the assets required to run the WebMKS console. For more info please see the docume…` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×11
  • Duplicated block (7 lines × 2) app/controllers/mixins/ems_common/core.rb:5 — app/controllers/mixins/ems_common/core.rb:5-11 | app/controllers/mixins/ems_common/core.rb:26-32 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) REDACTED:480 — REDACTED:480-488 | app/controllers/ops_controller/settings/common.rb:815-821 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) REDACTED:70 — REDACTED:70-76 | app/controllers/report_controller/saved_reports.rb:139-145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) app/helpers/configuration_job_helper/textual_summary.rb:33 — app/helpers/configuration_job_helper/textual_summary.rb:33-39 | app/helpers/vm_helper/textual_summary.rb:348-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) app/helpers/ansible_credential_helper/textual_summary.rb:54 — app/helpers/ansible_credential_helper/textual_summary.rb:54-60 | app/helpers/workflow_credential_helper/textual_summary.rb:54-60 — `app/helpers/ansible_credential_helper/textual_summary.rb` and `app/helpers/workflow_credential_helper/textual_summary.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 7 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (7 lines × 2) app/helpers/condition_helper.rb:68 — app/helpers/condition_helper.rb:68-74 | app/helpers/miq_alert_set_helper.rb:45-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) app/helpers/generic_object_definition_helper/textual_summary.rb:25 — app/helpers/generic_object_definition_helper/textual_summary.rb:25-31 | app/helpers/service_helper/textual_summary.rb:285-291 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) app/helpers/cloud_object_store_container_helper/textual_summary.rb:31 — app/helpers/cloud_object_store_container_helper/textual_summary.rb:31-37 | app/helpers/cloud_object_store_object_helper/textual_summary.rb:37-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) app/helpers/configuration_profile_helper/textual_summary.rb:59 — app/helpers/configuration_profile_helper/textual_summary.rb:59-65 | app/helpers/configured_system_helper/textual_summary.rb:61-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) app/helpers/configuration_profile_helper/textual_summary.rb:69 — app/helpers/configuration_profile_helper/textual_summary.rb:69-75 | app/helpers/ems_configuration_helper/textual_summary.rb:62-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) app/controllers/ems_automation_controller.rb:101 — app/controllers/ems_automation_controller.rb:101-107 | app/controllers/ems_configuration_controller.rb:107-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×9
  • Duplicated block (9 lines × 2) app/controllers/ems_cluster_controller.rb:49 — app/controllers/ems_cluster_controller.rb:49-57 | REDACTED:306-315 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/controllers/ems_cluster_controller.rb:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (9 lines × 2) REDACTED:134 — REDACTED:134-142 | app/controllers/vm_controller.rb:40-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) REDACTED:57 — REDACTED:57-65 | REDACTED:69-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) REDACTED:154 — REDACTED:154-162 | REDACTED:87-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:154` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) app/controllers/report_controller/menus.rb:390 — app/controllers/report_controller/menus.rb:390-398 | app/controllers/report_controller/menus.rb:434-442 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) app/controllers/report_controller/menus.rb:409 — app/controllers/report_controller/menus.rb:409-417 | app/controllers/report_controller/menus.rb:453-461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) app/helpers/application_helper/button/ems_storage_timeline.rb:3 — app/helpers/application_helper/button/ems_storage_timeline.rb:3-11 | app/helpers/application_helper/button/ems_timeline.rb:3-15 — before extracting anything, compare `app/helpers/application_helper/button/ems_storage_timeline.rb` and `app/helpers/application_helper/button/ems_timeline.rb` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) app/controllers/application_controller/explorer.rb:221 — app/controllers/application_controller/explorer.rb:221-229 | app/controllers/application_controller/tags.rb:89-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) app/helpers/host_initiator_group_helper/textual_summary.rb:33 — app/helpers/host_initiator_group_helper/textual_summary.rb:33-41 | app/helpers/host_initiator_helper/textual_summary.rb:23-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×8
  • Duplicated block (8 lines × 2) REDACTED:189 — REDACTED:189-196 | REDACTED:5-12 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) app/controllers/ems_cluster_controller.rb:81 — app/controllers/ems_cluster_controller.rb:81-88 | REDACTED:132-139 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) REDACTED:106 — REDACTED:106-113 | REDACTED:116-123 — 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 (8 lines × 2) app/helpers/request_info_helper.rb:222 — app/helpers/request_info_helper.rb:222-230 | app/helpers/request_info_helper.rb:237-244 — 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 (8 lines × 2) app/services/container_dashboard_service.rb:187 — app/services/container_dashboard_service.rb:187-194 | app/services/ems_infra_dashboard_service.rb:88-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/services/container_dashboard_service.rb:187` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) app/helpers/ansible_playbook_helper/textual_summary.rb:31 — app/helpers/ansible_playbook_helper/textual_summary.rb:31-38 | app/helpers/workflow_helper/textual_summary.rb:31-38 — `app/helpers/ansible_playbook_helper/textual_summary.rb` and `app/helpers/workflow_helper/textual_summary.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 8 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) REDACTED:315 — REDACTED:315-322 | app/controllers/infra_networking_controller.rb:164-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) app/helpers/catalog_helper/orchestration_template_helper.rb:43 — app/helpers/catalog_helper/orchestration_template_helper.rb:43-50 | app/helpers/miq_ae_class_helper.rb:417-424 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
AC4 · Keyboard semantics · Anchor without href · ×7
  • Anchor without href app/views/layouts/_compare.html.haml:11 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href app/views/layouts/_empty.html.haml:10 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href app/views/layouts/_tabs.html.haml:11 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href app/views/layouts/_tabs.html.haml:16 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href app/views/report/_menu_form1.html.haml:18 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href app/views/report/_widget_form_menu.html.haml:19 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href app/views/vm_common/_add_to_service.html.haml:5 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×7
  • Focus outline removed in CSS without a :focus replacement app/stylesheet/miq-ae-class.scss:71 — `.ae-namespace-tree-scroll .tree-branch-wrapper` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement app/stylesheet/miq-data-table.scss:362 — `.reconfigure-form .reconfigure-form-table .miq-data-table .cell .cds--btn--ghost` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement app/stylesheet/toolbar.scss:225 — `.overflow-menu-disabled` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement app/stylesheet/legacy/about_modal_background.scss:69 — `.about-modal .cds--modal-container .about-modal-body .plugins-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement app/javascript/components/vm-snapshot-tree-select/styles.scss:77 — `.vm-snapshot-tree .tree-branch-wrapper` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement app/javascript/components/automate-entry-points/styles.scss:32 — `.automate_entry_points .tree-branch-wrapper` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement app/javascript/components/automate-entry-points/styles.scss:77 — `.cds--modal-content:focus` 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.
D29 · Static Analysis (SAST) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×7
  • Edited copy of a member (9 corresponding lines) app/helpers/generic_object_definition_helper.rb:5 — app/helpers/generic_object_definition_helper.rb:5-13 | app/helpers/shared_helper/ab_list_helper.rb:5-16 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/helpers/storage_resource_helper/textual_summary.rb:75 — app/helpers/storage_resource_helper/textual_summary.rb:75-83 | app/helpers/storage_service_helper/textual_summary.rb:42-50 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/services/automate_import_json_serializer_service.rb:33 — app/services/automate_import_json_serializer_service.rb:33-42 | app/services/automate_import_json_serializer_service.rb:46-54 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:122 — REDACTED:122-130 | app/controllers/vm_controller.rb:28-36 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/services/dashboard_service.rb:61 — app/services/dashboard_service.rb:61-71 | app/services/ems_dashboard_service.rb:65-73 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/helpers/storage_resource_helper/textual_summary.rb:51 — app/helpers/storage_resource_helper/textual_summary.rb:51-59 | app/helpers/storage_service_helper/textual_summary.rb:17-25 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/helpers/ops_helper/settings_label_tag_mapping_helper.rb:22 — app/helpers/ops_helper/settings_label_tag_mapping_helper.rb:22-30 | app/helpers/ops_helper/settings_tab_helper.rb:48-56 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×7
  • Duplicated block (6 lines × 2) REDACTED:2188 — REDACTED:2188-2193 | REDACTED:2224-2229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:2185` calls `fetch_name_from_object` and `REDACTED:2222` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) app/helpers/service_helper/textual_summary.rb:295 — app/helpers/service_helper/textual_summary.rb:295-300 | app/helpers/storage_helper/textual_summary.rb:232-237 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/helpers/service_helper/textual_summary.rb:295` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) REDACTED:561 — REDACTED:561-566 | REDACTED:650-655 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) REDACTED:290 — REDACTED:290-295 | REDACTED:526-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) REDACTED:176 — REDACTED:176-181 | REDACTED:193-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) REDACTED:1046 — REDACTED:1046-1051 | REDACTED:1060-1065 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) REDACTED:1671 — REDACTED:1671-1676 | REDACTED:2128-2133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC3 · Page structure · Page without a main landmark · ×6
  • Page without a main landmark app/views/layouts/application.html.haml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/layouts/login.html.haml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/layouts/print.html.haml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/layouts/remote_console.html.haml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/layouts/report_only.html.haml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark app/views/vm_common/console_vmrc.html.haml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×6
  • Edited copy of a member (14 corresponding lines) REDACTED:311 — REDACTED:311-324 | REDACTED:329-342 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:524 — REDACTED:524-538 | REDACTED:543-556 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:1564 — REDACTED:1564-1580 | REDACTED:1622-1635 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:88 — REDACTED:88-104 | REDACTED:123-136 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/controllers/infra_networking_controller.rb:85 — app/controllers/infra_networking_controller.rb:85-100 | REDACTED:255-268 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/services/dialog_local_service.rb:3 — app/services/dialog_local_service.rb:3-16 | app/services/dialog_local_service.rb:20-33 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×6
  • Duplicated block (12 lines × 2) REDACTED:74 — REDACTED:74-85 | REDACTED:104-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) REDACTED:882 — REDACTED:882-893 | REDACTED:909-920 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:882` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) REDACTED:1120 — REDACTED:1120-1131 | REDACTED:1148-1159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) REDACTED:482 — REDACTED:482-493 | REDACTED:1114-1125 — 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 (12 lines × 2) app/controllers/mixins/containers_common_mixin.rb:143 — app/controllers/mixins/containers_common_mixin.rb:143-154 | REDACTED:519-530 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) REDACTED:18 — REDACTED:18-29 | app/controllers/miq_policy_log_controller.rb:25-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×5
  • Edited copy of a member (17 corresponding lines) app/controllers/application_controller/sysprep_answer_file.rb:4 — app/controllers/application_controller/sysprep_answer_file.rb:4-23 | app/controllers/application_controller/user_script_file.rb:4-20 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) REDACTED:879 — REDACTED:879-895 | REDACTED:1414-1430 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) app/controllers/infra_networking_controller.rb:495 — app/controllers/infra_networking_controller.rb:495-522 | REDACTED:442-458 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) app/helpers/ansible_credential_helper/textual_summary.rb:13 — app/helpers/ansible_credential_helper/textual_summary.rb:13-29 | app/helpers/workflow_credential_helper/textual_summary.rb:13-29 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) app/controllers/infra_networking_controller.rb:47 — app/controllers/infra_networking_controller.rb:47-63 | REDACTED:195-211 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×5
  • Edited copy of a member (10 corresponding lines) REDACTED:582 — REDACTED:582-591 | REDACTED:595-605 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) app/presenters/tree_builder_policy_simulation.rb:80 — app/presenters/tree_builder_policy_simulation.rb:80-89 | app/presenters/tree_builder_policy_simulation.rb:93-103 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) REDACTED:53 — REDACTED:53-63 | REDACTED:79-88 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) REDACTED:152 — REDACTED:152-161 | REDACTED:166-175 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) app/controllers/miq_event_definition_controller.rb:27 — app/controllers/miq_event_definition_controller.rb:27-36 | app/controllers/mixins/generic_show_mixin.rb:107-116 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) app/helpers/catalog_helper/orchestration_template_helper.rb:14 — app/helpers/catalog_helper/orchestration_template_helper.rb:14-26 | app/helpers/orchestration_stack_helper.rb:5-18 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) REDACTED:232 — REDACTED:232-244 | REDACTED:296-309 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) REDACTED:193 — REDACTED:193-207 | REDACTED:212-224 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) REDACTED:529 — REDACTED:529-541 | app/controllers/report_controller/menus.rb:474-486 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) app/controllers/application_controller/automate.rb:82 — app/controllers/application_controller/automate.rb:82-96 | app/controllers/application_controller/automate.rb:100-112 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×5
  • Edited copy of a member (5 corresponding lines) REDACTED:303 — REDACTED:303-307 | REDACTED:311-315 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/services/container_dashboard_service.rb:264 — app/services/container_dashboard_service.rb:264-268 | app/services/container_service_mixin.rb:213-219 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/services/container_dashboard_service.rb:156 — app/services/container_dashboard_service.rb:156-160 | app/services/container_dashboard_service.rb:165-171 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/helpers/ems_infra_helper/textual_summary.rb:116 — app/helpers/ems_infra_helper/textual_summary.rb:116-120 | app/helpers/ems_physical_infra_helper/textual_summary.rb:93-97 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/services/container_dashboard_service.rb:148 — app/services/container_dashboard_service.rb:148-152 | app/services/dashboard_service.rb:50-57 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D15 · Churn × Complexity Hotspots · Repeated repair · ×4
  • Repeated repair: app/javascript/components/automate-simulation-form/index.jsx app/javascript/components/automate-simulation-form/index.jsx:9 — app/javascript/components/automate-simulation-form/index.jsx changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is index.AutomateSimulationForm at line 9), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix automate simulation target reload on target_class change”; “Memoize schema to fix FieldArray setState-during-render warning”; “Fix FieldArray setState-during-render warning”; “Fix Execute Methods checkbox initial value”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/automate-simulation-form/index.jsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/javascript/components/automate-simulation-form/automate-simulation-form.schema.js app/javascript/components/automate-simulation-form/automate-simulation-form.schema.js:18 — app/javascript/components/automate-simulation-form/automate-simulation-form.schema.js changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is automate-simulation-form.schema.createSchema at line 18), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix automate simulation target reload on target_class change”; “Fix FieldArray setState-during-render warning”; “Fix Execute Methods checkbox initial value”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/automate-simulation-form/automate-simulation-form.schema.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/javascript/notifications/init.js app/javascript/notifications/init.js:18 — app/javascript/notifications/init.js changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is init.init at line 18), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix too many requests error on page back and forward multiple times”; “Fix pr issues”; “Fix browser back/forward button”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/notifications/init.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: app/javascript/components/utilization/utilization-summary.tsx app/javascript/components/utilization/utilization-summary.tsx:24 — app/javascript/components/utilization/utilization-summary.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is utilization-summary.UtilizationSummary at line 24), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix pr problems”; “Fix broken translation”; “Fix bug where rows won't show for non-english”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 12:13:10 -05:00' --until='2026-11-13 12:13:10 -05:00' --full-history --no-merges -- app/javascript/components/utilization/utilization-summary.tsx`: 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 · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:74 — REDACTED:74-87 | REDACTED:104-117 | app/controllers/workflow_credential_controller.rb:76-89 | app/controllers/workflow_repository_controller.rb:119-132 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:47 — REDACTED:47-72 | REDACTED:76-94 | REDACTED:245-268 | REDACTED:279-301 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:125 — REDACTED:125-160 | REDACTED:208-243 | REDACTED:93-128 | REDACTED:186-221 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) app/helpers/vm_helper/textual_summary.rb:557 — app/helpers/vm_helper/textual_summary.rb:557-562 | app/helpers/vm_helper/textual_summary.rb:566-572 | app/helpers/vm_helper/textual_summary.rb:576-582 | app/helpers/vm_helper/textual_summary.rb:586-592 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) REDACTED:167 — REDACTED:167-174 | REDACTED:178-184 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/helpers/miq_alert_helper.rb:175 — app/helpers/miq_alert_helper.rb:175-181 | app/helpers/miq_alert_helper.rb:185-191 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/services/dashboard_service.rb:18 — app/services/dashboard_service.rb:18-24 | app/services/dashboard_service.rb:32-38 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/controllers/mixins/custom_buttons.rb:23 — app/controllers/mixins/custom_buttons.rb:23-29 | REDACTED:668-678 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×4
  • Edited copy of a member (4 corresponding lines) app/helpers/application_helper/button/condition_delete.rb:5 — app/helpers/application_helper/button/condition_delete.rb:5-8 | app/helpers/application_helper/button/policy_delete.rb:5-8 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/helpers/application_helper/button/volume_attach.rb:3 — app/helpers/application_helper/button/volume_attach.rb:3-6 | app/helpers/application_helper/button/volume_clone.rb:3-6 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/helpers/automation_manager_configured_system_helper.rb:30 — app/helpers/automation_manager_configured_system_helper.rb:30-33 | app/helpers/configuration_script_helper.rb:81-84 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/controllers/ems_automation_controller.rb:67 — app/controllers/ems_automation_controller.rb:67-70 | app/controllers/ems_configuration_controller.rb:117-120 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×4
  • Duplicated block (11 lines × 2) REDACTED:429 — REDACTED:429-439 | REDACTED:562-572 — 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 (11 lines × 2) REDACTED:479 — REDACTED:479-489 | REDACTED:503-513 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) app/services/container_dashboard_service.rb:175 — app/services/container_dashboard_service.rb:175-185 | app/services/ems_infra_dashboard_service.rb:76-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/services/container_dashboard_service.rb:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) app/controllers/configuration_profile_controller.rb:41 — app/controllers/configuration_profile_controller.rb:41-51 | app/controllers/configured_system_controller.rb:34-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) REDACTED:106 — REDACTED:106-115 | REDACTED:140-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) app/helpers/catalog_helper.rb:157 — app/helpers/catalog_helper.rb:157-166 | app/helpers/catalog_helper/orchestration_template_helper.rb:30-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) REDACTED:510 — REDACTED:510-519 | app/controllers/miq_ae_customization_controller/custom_buttons.rb:73-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) app/controllers/infra_networking_controller.rb:482 — app/controllers/infra_networking_controller.rb:482-491 | REDACTED:415-424 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) REDACTED:441 — REDACTED:441-445 | REDACTED:371-375 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:369` calls `copy_hash` and `REDACTED:440` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) app/helpers/ansible_repository_helper/textual_summary.rb:30 — app/helpers/ansible_repository_helper/textual_summary.rb:30-34 | app/helpers/workflow_repository_helper/textual_summary.rb:30-34 — `app/helpers/ansible_repository_helper/textual_summary.rb` and `app/helpers/workflow_repository_helper/textual_summary.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 5 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (5 lines × 2) REDACTED:2182 — REDACTED:2182-2186 | REDACTED:2200-2204 — 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 (5 lines × 2) app/helpers/catalog_helper/orchestration_template_helper.rb:14 — app/helpers/catalog_helper/orchestration_template_helper.rb:14-18 | app/helpers/orchestration_stack_helper.rb:5-9 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/helpers/catalog_helper/orchestration_template_helper.rb:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/helpers/orchestration_stack_helper.rb:10` calls `row_data`, `_` and `app/helpers/catalog_helper/orchestration_template_helper.rb:19` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) REDACTED:48 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) app/javascript/components/expression-editor/date-value-editor.jsx:50 — 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) app/javascript/components/expression-editor/date-value-editor.jsx:199 — `.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) app/javascript/components/automate-import-export-form/review-import-form.jsx:97 — `.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.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×3
  • Edited copy of a member (31 corresponding lines) app/services/container_dashboard_service.rb:175 — app/services/container_dashboard_service.rb:175-205 | app/services/ems_infra_dashboard_service.rb:71-106 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) REDACTED:88 — REDACTED:88-121 | REDACTED:125-155 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) REDACTED:1308 — REDACTED:1308-1338 | REDACTED:1347-1384 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×3
  • Edited copy of a member (19 corresponding lines) REDACTED:2519 — REDACTED:2519-2541 | REDACTED:551-569 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) REDACTED:125 — REDACTED:125-145 | REDACTED:52-70 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) REDACTED:1412 — REDACTED:1412-1431 | REDACTED:1436-1454 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) REDACTED:32 — REDACTED:32-49 | app/controllers/workflow_credential_controller.rb:34-51 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) REDACTED:34 — REDACTED:34-51 | REDACTED:92-114 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) app/helpers/application_helper/toolbar/configuration_scripts/policy_mixin.rb:3 — app/helpers/application_helper/toolbar/configuration_scripts/policy_mixin.rb:3-20 | app/helpers/application_helper/toolbar/configured_system/automation/policy_mixin.rb:3-23 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×3
  • Edited copy of a member (12 corresponding lines) REDACTED:173 — REDACTED:173-185 | REDACTED:190-201 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) REDACTED:1952 — REDACTED:1952-1963 | REDACTED:1973-1984 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) REDACTED:1342 — REDACTED:1342-1357 | REDACTED:1394-1405 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) REDACTED:693 — REDACTED:693-708 | REDACTED:713-729 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) REDACTED:514 — REDACTED:514-529 | REDACTED:535-550 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) REDACTED:87 — REDACTED:87-103 | app/controllers/cloud_volume_snapshot_controller.rb:48-63 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×3
  • Edited copy of a member (11 corresponding lines) REDACTED:93 — REDACTED:93-103 | REDACTED:215-226 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) REDACTED:131 — REDACTED:131-141 | REDACTED:108-119 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) app/controllers/infra_networking_controller.rb:538 — app/controllers/infra_networking_controller.rb:538-549 | REDACTED:428-438 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 8+ corresponding lines) app/helpers/cloud_subnet_helper/textual_summary.rb:97 — app/helpers/cloud_subnet_helper/textual_summary.rb:97-104 | app/helpers/ems_infra_helper/textual_summary.rb:82-89 | app/helpers/ems_infra_helper/textual_summary.rb:93-100 | app/helpers/storage_helper/textual_summary.rb:76-83 | app/helpers/storage_helper/textual_summary.rb:87-94 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) app/controllers/mixins/actions/host_actions/misc.rb:52 — app/controllers/mixins/actions/host_actions/misc.rb:52-59 | app/controllers/mixins/actions/host_actions/misc.rb:102-109 | app/controllers/mixins/actions/host_actions/misc.rb:113-120 | app/controllers/mixins/actions/host_actions/misc.rb:124-131 | app/controllers/mixins/actions/host_actions/misc.rb:135-142 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) app/helpers/ems_infra_helper/textual_summary.rb:155 — app/helpers/ems_infra_helper/textual_summary.rb:155-162 | app/helpers/generic_object_helper/textual_summary.rb:76-83 | app/helpers/infra_networking_helper/textual_summary.rb:32-40 | app/helpers/service_helper/textual_summary.rb:295-302 | app/helpers/storage_helper/textual_summary.rb:232-239 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) app/services/ems_dashboard_service.rb:55 — app/services/ems_dashboard_service.rb:55-61 | app/services/cloud_tenant_dashboard_service.rb:104-109 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/helpers/container_helper/textual_summary.rb:136 — app/helpers/container_helper/textual_summary.rb:136-142 | app/helpers/container_image_helper/textual_summary.rb:128-133 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/helpers/textual_mixins/textual_authentications_status.rb:3 — app/helpers/textual_mixins/textual_authentications_status.rb:3-8 | lib/gtl_formatter.rb:278-283 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) REDACTED:143 — REDACTED:143-160 | REDACTED:226-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) REDACTED:111 — REDACTED:111-128 | REDACTED:204-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) app/controllers/container_controller.rb:11 — app/controllers/container_controller.rb:11-28 | app/controllers/container_node_controller.rb:12-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • Duplicated block (16 lines × 2) REDACTED:32 — REDACTED:32-47 | app/controllers/workflow_credential_controller.rb:34-49 — before extracting anything, compare `REDACTED` and `app/controllers/workflow_credential_controller.rb` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) REDACTED:831 — REDACTED:831-846 | REDACTED:1365-1380 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:831` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) REDACTED:177 — REDACTED:177-192 | REDACTED:438-453 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) REDACTED:879 — REDACTED:879-891 | REDACTED:1414-1426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) REDACTED:265 — REDACTED:265-277 | REDACTED:328-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:342` calls `add_flash`, `_` and `REDACTED:278` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) app/helpers/application_helper/button/generic_object_definition_button_button_delete.rb:5 — app/helpers/application_helper/button/generic_object_definition_button_button_delete.rb:5-17 | app/helpers/application_helper/button/generic_object_definition_button_button_group_delete.rb:9-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
AC2 · Forms & labels · <fieldset> without a <legend> · ×2
  • <fieldset> without a <legend> app/javascript/menu/search.tsx:54 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> app/javascript/menu/search.tsx:110 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×2
  • Heading level jumps from h1 to h3 app/views/layouts/_policy_sim.html.haml:10 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 app/views/vm_common/_policy_options.html.haml:8 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: TagSelector.js ↔ ValueSelector.js app/javascript/tagging/components/InnerComponents/TagSelector.js:1 — `app/javascript/tagging/components/InnerComponents/TagSelector.js` and `app/javascript/tagging/components/InnerComponents/ValueSelector.js` change together 71% of the time (10 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `acf4f782` Fix taggings issue while adding or removing assigned filters to user …; `147db9ed` tagging: fix PfSelect import; `15924de7` Make searching through Tag categories and values work — run `git show` on any of them.
  • Change coupling: taggingWrapper.jsx ↔ middleware.js app/javascript/components/taggingWrapper.jsx:1 — `app/javascript/components/taggingWrapper.jsx` and `app/javascript/miq-redux/middleware.js` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 6 shared commits counted here, the most recent 3 are `acf4f782` Fix taggings issue while adding or removing assigned filters to user …; `466c8c9f` Tagging onDelete returns function; `1bd910ac` Fix delete for provision tagging — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) REDACTED:558 — REDACTED:558-583 | REDACTED:588-613 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) REDACTED:420 — REDACTED:420-448 | REDACTED:453-478 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) REDACTED:828 — REDACTED:828-849 | REDACTED:1362-1384 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) app/services/cloud_tenant_dashboard_service.rb:79 — app/services/cloud_tenant_dashboard_service.rb:79-100 | app/services/ems_dashboard_service.rb:14-35 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) REDACTED:367 — REDACTED:367-387 | REDACTED:391-411 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) REDACTED:784 — REDACTED:784-804 | REDACTED:1220-1243 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) REDACTED:36 — REDACTED:36-64 | app/controllers/workflow_repository_controller.rb:39-69 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) app/controllers/infra_networking_controller.rb:427 — app/controllers/infra_networking_controller.rb:427-455 | app/controllers/mixins/explorer_show.rb:186-220 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 14+ corresponding lines) app/helpers/configured_system_helper/textual_summary.rb:82 — app/helpers/configured_system_helper/textual_summary.rb:82-95 | app/helpers/container_group_helper/textual_summary.rb:107-120 | app/helpers/container_node_helper/textual_summary.rb:87-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) REDACTED:149 — REDACTED:149-165 | REDACTED:214-232 | REDACTED:70-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) REDACTED:1177 — REDACTED:1177-1191 | REDACTED:173-187 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:456 — REDACTED:456-471 | REDACTED:493-507 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 7+ corresponding lines) app/helpers/cloud_volume_helper/textual_summary.rb:139 — app/helpers/cloud_volume_helper/textual_summary.rb:139-145 | app/helpers/host_initiator_group_helper/textual_summary.rb:61-67 | app/helpers/host_initiator_helper/textual_summary.rb:55-61 | app/helpers/host_initiator_helper/textual_summary.rb:65-74 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) app/helpers/configuration_job_helper/textual_summary.rb:59 — app/helpers/configuration_job_helper/textual_summary.rb:59-65 | app/helpers/orchestration_stack_helper/textual_summary.rb:111-117 | app/helpers/orchestration_stack_helper/textual_summary.rb:121-127 | app/helpers/orchestration_stack_helper/textual_summary.rb:131-137 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) app/helpers/miq_ae_customization_helper.rb:60 — app/helpers/miq_ae_customization_helper.rb:60-67 | app/helpers/orchestration_stack_helper.rb:22-29 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) app/helpers/application_helper/button/server_demote.rb:5 — app/helpers/application_helper/button/server_demote.rb:5-12 | app/helpers/application_helper/button/server_promote.rb:5-12 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) app/helpers/host_helper/textual_summary.rb:487 — app/helpers/host_helper/textual_summary.rb:487-490 | app/helpers/textual_mixins/vm_common.rb:233-235 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/helpers/orchestration_stack_helper/textual_summary.rb:45 — app/helpers/orchestration_stack_helper/textual_summary.rb:45-47 | app/helpers/service_helper/textual_summary.rb:140-142 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×2
  • Edited copy of a member (1 corresponding lines) app/helpers/container_node_helper/textual_summary.rb:53 — app/helpers/container_node_helper/textual_summary.rb:53-54 | app/helpers/host_helper/textual_summary.rb:249-249 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) app/helpers/ansible_credential_helper/textual_summary.rb:33 — app/helpers/ansible_credential_helper/textual_summary.rb:33-33 | app/helpers/workflow_credential_helper/textual_summary.rb:33-33 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) REDACTED:44 — REDACTED:44-62 | app/controllers/workflow_repository_controller.rb:49-67 — before extracting anything, compare `REDACTED` and `app/controllers/workflow_repository_controller.rb` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/controllers/workflow_repository_controller.rb:48` calls `javascript_redirect` and `REDACTED:43` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (19 lines × 2) REDACTED:71 — REDACTED:71-89 | REDACTED:164-182 — 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) REDACTED:374 — REDACTED:374-387 | REDACTED:398-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:374` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) REDACTED:132 — REDACTED:132-145 | REDACTED:57-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×2
  • Duplicated block (9–11 lines × 2) REDACTED:167 — REDACTED:167-175 | REDACTED:79-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9–11 lines × 2) REDACTED:571 — REDACTED:571-581 | REDACTED:625-633 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2
  • Duplicated block (9 lines × 3) REDACTED:106 — REDACTED:106-114 | REDACTED:118-126 | REDACTED:130-138 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 3) app/presenters/tree_builder_ops_diagnostics.rb:9 — app/presenters/tree_builder_ops_diagnostics.rb:9-17 | app/presenters/tree_builder_ops_rbac.rb:11-19 | app/presenters/tree_builder_ops_settings.rb:9-17 — before extracting anything, compare `app/presenters/tree_builder_ops_diagnostics.rb` and `app/presenters/tree_builder_ops_settings.rb` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×2
  • Duplicated block (17 lines × 3) app/controllers/cloud_volume_type_controller.rb:15 — app/controllers/cloud_volume_type_controller.rb:15-31 | app/controllers/ems_storage_controller.rb:16-89 | app/controllers/storage_resource_controller.rb:16-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (17 lines × 3) app/helpers/application_helper/button/host_initiator_group_new.rb:3 — app/helpers/application_helper/button/host_initiator_group_new.rb:3-19 | app/helpers/application_helper/button/host_initiator_new.rb:3-19 | app/helpers/application_helper/button/volume_mapping_new.rb:3-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
R10 · Code Duplication · Duplicated block (74 lines × 3 locations) · ×2
  • Duplicated block (74 lines × 3 locations) app/javascript/components/ansible-credentials-form/index.jsx:9 — app/javascript/components/ansible-credentials-form/index.jsx:9 · app/javascript/components/embedded-terraform-credentials-form/index.jsx:9 · app/javascript/components/workflow-credentials-form/index.jsx:9 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
  • Duplicated block (74 lines × 3 locations) app/javascript/components/container-projects/helper.jsx:107 — app/javascript/components/container-projects/helper.jsx:107 · app/javascript/components/container-projects/helper.jsx:186 · app/javascript/components/container-projects/helper.jsx:267 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication · Duplicated block (40 lines × 2 locations) · ×2
  • Duplicated block (40 lines × 2 locations) app/javascript/components/ab-form/ab-form.schema.js:38 — app/javascript/components/ab-form/ab-form.schema.js:38 · app/javascript/components/generic-objects-form/custom-button-form/custom-button-form.schema.js:27 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
  • Duplicated block (40 lines × 2 locations) app/javascript/components/pxe-image-edit-form/index.jsx:13 — app/javascript/components/pxe-image-edit-form/index.jsx:13 · app/javascript/components/pxe-windows-image-edit-form/index.jsx:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 12) · ×2
  • Complex function (anonymous) (cyclomatic 14, cognitive 12) app/javascript/components/expression-editor/field-config.js:82 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 14, cognitive 12) app/javascript/components/role-form/index.jsx:125 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R7 · Dead Code · Dead file (~193 LoC) · ×2
  • Dead file (~193 LoC) app/javascript/components/AeInlineMethod/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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
  • Dead file (~193 LoC) app/javascript/oldjs/miq_c3.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (~123 LoC) · ×2
  • Dead file (~123 LoC) app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationMemoryDonutChart.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.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
  • Dead file (~123 LoC) app/javascript/oldjs/miq_browser_detect.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (~118 LoC) · ×2
  • Dead file (~118 LoC) app/javascript/components/data-tables/gtl/DataTable.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (app/javascript/components/data-tables/gtl/StaticGTLView.jsx, app/javascript/components/data-tables/gtl/index.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
  • Dead file (~118 LoC) app/javascript/components/request-workflow-status/data.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/request-workflow-status/request-workflow-status-item.jsx) — 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
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap app/javascript/components/workers-form/helpers.jsx:33 — `emptyChildren` is exported and takes `parent: object` from its caller, and it calls itself at line 33 (`emptyChildren`) with a piece of `parent` — and nowhere in `emptyChildren` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `emptyChildren` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap app/javascript/components/workers-form/helpers.jsx:48 — `buildPatch` is exported and takes `parent: object` from its caller, and it calls itself at line 48 (`buildPatch`) with a piece of `parent` — and nowhere in `buildPatch` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `buildPatch` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X25 · Inert configuration knob · Option is kept and never read · ×2
  • Option is kept and never read app/javascript/components/data-tables/optimization/transform.js:30 — `transformSaved` accepts `report_id` from the caller and keeps it in `report_id` on line 30, where only it can read the value — but nothing ever reads `report_id`. Setting `report_id` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `report_id` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `report_id` from the accepted options so callers stop setting a knob that does nothing.
  • Option is kept and never read app/javascript/components/data-tables/optimization/transform.js:42 — `transformReport` accepts `action` from the caller and keeps it in `action` on line 42, where only it can read the value — but nothing ever reads `action`. Setting `action` therefore changes nothing: every caller gets the same behaviour whatever they pass, and nothing reports that the option was ignored. Read `action` where the behaviour it configures is decided — or, if the behaviour genuinely is fixed, remove `action` from the accepted options so callers stop setting a knob that does nothing.
AC2 · Forms & labels · <TextArea> field component without a label · ×1
  • <TextArea> field component without a label app/javascript/components/miq-structured-list/miq-structured-list-body/value-tags/miq-structured-list-inputs.jsx:9 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×1
  • Link used as a button (placeholder href) app/views/shared/_compare_header_expanded.html.haml:7 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.9 · ×1
  • Low contrast colour pair in CSS (3.9:1) app/stylesheet/legacy/fonticon_picker.scss:19 — `i` sets color: #fff on background-color: #0088ce — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · EmsCommon.button (cyclomatic 120) · ×1
  • EmsCommon.button (cyclomatic 120) REDACTED:193 — EmsCommon.button has cyclomatic complexity 120 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · index.ChargebackAssignmentsForm (cyclomatic 99) · ×1
  • index.ChargebackAssignmentsForm (cyclomatic 99) app/javascript/components/chargeback-assignments-form/index.jsx:14 — index.ChargebackAssignmentsForm has cyclomatic complexity 99 (threshold 15). Of this number, 24 points are the body's own statements and 75 belong to 15 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 · ReportController.replace_right_cell (cyclomatic 85) · ×1
  • ReportController.replace_right_cell (cyclomatic 85) REDACTED:636 — ReportController.replace_right_cell has cyclomatic complexity 85 (threshold 15). To reduce it, separate the cases: extract each independent 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 · CatalogController.replace_right_cell (cyclomatic 72) · ×1
  • CatalogController.replace_right_cell (cyclomatic 72) REDACTED:2299 — CatalogController.replace_right_cell has cyclomatic complexity 72 (threshold 15). To reduce it, separate the cases: extract each independent 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 · Common.settings_get_form_vars (cyclomatic 72) · ×1
  • Common.settings_get_form_vars (cyclomatic 72) app/controllers/ops_controller/settings/common.rb:493 — Common.settings_get_form_vars has cyclomatic complexity 72 (threshold 15). To reduce it, separate the cases: extract each independent 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 · instance-form.InstanceForm (cyclomatic 69) · ×1
  • instance-form.InstanceForm (cyclomatic 69) app/javascript/components/miq-ae-class/instance-form.jsx:12 — instance-form.InstanceForm has cyclomatic complexity 69 (threshold 15). Of this number, 30 points are the body's own statements and 39 belong to 13 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · VmCommon.replace_right_cell (cyclomatic 59) · ×1
  • VmCommon.replace_right_cell (cyclomatic 59) REDACTED:951 — VmCommon.replace_right_cell has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · chargeback-filter.ChargebackFilter (cyclomatic 59) · ×1
  • chargeback-filter.ChargebackFilter (cyclomatic 59) app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:112 — chargeback-filter.ChargebackFilter has cyclomatic complexity 59 (threshold 15). Of this number, 47 points are the body's own statements and 12 belong to 7 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 · ApplicationController.get_view (cyclomatic 58) · ×1
  • ApplicationController.get_view (cyclomatic 58) REDACTED:1050 — ApplicationController.get_view has cyclomatic complexity 58 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · carbon-value-editor.CarbonValueEditor (cyclomatic 58) · ×1
  • carbon-value-editor.CarbonValueEditor (cyclomatic 58) app/javascript/components/expression-editor/carbon-value-editor.jsx:273 — carbon-value-editor.CarbonValueEditor has cyclomatic complexity 58 (threshold 15). Of this number, 48 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · label-selection.LabelSelection (cyclomatic 56) · ×1
  • label-selection.LabelSelection (cyclomatic 56) app/javascript/components/chargeback-assignments-form/label-selection.jsx:16 — label-selection.LabelSelection has cyclomatic complexity 56 (threshold 15). Of this number, 19 points are the body's own statements and 37 belong to 13 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · HostController.button (cyclomatic 51) · ×1
  • HostController.button (cyclomatic 51) REDACTED:178 — HostController.button has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validation.validateReportForm (cyclomatic 51) · ×1
  • validation.validateReportForm (cyclomatic 51) app/javascript/components/report-editor/validation.ts:7 — validation.validateReportForm has cyclomatic complexity 51 (threshold 15). Of this number, 50 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent 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 · CatalogController.atomic_req_submit (cyclomatic 48) · ×1
  • CatalogController.atomic_req_submit (cyclomatic 48) REDACTED:1001 — CatalogController.atomic_req_submit has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent 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 · MiqAlertController.alert_field_changed (cyclomatic 46) · ×1
  • MiqAlertController.alert_field_changed (cyclomatic 46) REDACTED:95 — MiqAlertController.alert_field_changed has cyclomatic complexity 46 (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 · index.RoleForm (cyclomatic 46) · ×1
  • index.RoleForm (cyclomatic 46) app/javascript/components/role-form/index.jsx:14 — index.RoleForm has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 125, transformTree, onSubmit, …). 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.
D1 · Cyclomatic Complexity · MiqAlertController.alert_valid_record? (cyclomatic 45) · ×1
  • MiqAlertController.alert_valid_record? (cyclomatic 45) REDACTED:603 — MiqAlertController.alert_valid_record? 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 · miq-table-cell.MiqTableCell (cyclomatic 45) · ×1
  • miq-table-cell.MiqTableCell (cyclomatic 45) app/javascript/components/miq-data-table/miq-table-cell.jsx:15 — miq-table-cell.MiqTableCell has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 11 of the 45 points are its own statements and the rest belongs to 11 function items inside it that branch (cellComponent, renderIcon, cellIcon, …). 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.
D1 · Cyclomatic Complexity · Compare.prepare_data_for_compare_or_drift_report (cyclomatic 43) · ×1
  • Compare.prepare_data_for_compare_or_drift_report (cyclomatic 43) REDACTED:515 — Compare.prepare_data_for_compare_or_drift_report 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 · BreadcrumbsMixin.data_for_breadcrumbs (cyclomatic 43) · ×1
  • BreadcrumbsMixin.data_for_breadcrumbs (cyclomatic 43) app/controllers/mixins/breadcrumbs_mixin.rb:24 — BreadcrumbsMixin.data_for_breadcrumbs 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 · MiqRequestMethods.prov_get_form_vars (cyclomatic 42) · ×1
  • MiqRequestMethods.prov_get_form_vars (cyclomatic 42) REDACTED:725 — MiqRequestMethods.prov_get_form_vars 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 · VmCommon.show (cyclomatic 42) · ×1
  • VmCommon.show (cyclomatic 42) REDACTED:143 — VmCommon.show 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 · review-import-form.ReviewImportForm (cyclomatic 42) · ×1
  • review-import-form.ReviewImportForm (cyclomatic 42) app/javascript/components/automate-import-export-form/review-import-form.jsx:10 — review-import-form.ReviewImportForm has cyclomatic complexity 42 (threshold 15). Of this number, 20 points are the body's own statements and 22 belong to 9 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 · tag-selection.TagSelection (cyclomatic 42) · ×1
  • tag-selection.TagSelection (cyclomatic 42) app/javascript/components/chargeback-assignments-form/tag-selection.jsx:16 — tag-selection.TagSelection has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 12 of the 42 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 65, a function literal at line 33, a function literal at line 99, …). 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.
D1 · Cyclomatic Complexity · summary-tab.SummaryTab (cyclomatic 42) · ×1
  • summary-tab.SummaryTab (cyclomatic 42) app/javascript/components/report-editor/tabs/summary-tab.tsx:112 — summary-tab.SummaryTab has cyclomatic complexity 42 (threshold 15). Of this number, 35 points are the body's own statements and 7 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 · atomToHuman (cyclomatic 42) · ×1
  • atomToHuman (cyclomatic 42) app/javascript/components/expression-editor/expression-human.js:89 — atomToHuman has cyclomatic complexity 42 (threshold 15). Of this number, 41 points are the body's own statements and 1 belongs 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 · Widgets.widget_set_form_vars (cyclomatic 40) · ×1
  • Widgets.widget_set_form_vars (cyclomatic 40) REDACTED:305 — Widgets.widget_set_form_vars has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ApplicationHelper.view_to_url (cyclomatic 40) · ×1
  • ApplicationHelper.view_to_url (cyclomatic 40) REDACTED:238 — ApplicationHelper.view_to_url has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ApplicationController.set_global_session_data (cyclomatic 39) · ×1
  • ApplicationController.set_global_session_data (cyclomatic 39) REDACTED:1553 — ApplicationController.set_global_session_data 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 · Schedules.schedule_get_form_vars (cyclomatic 39) · ×1
  • Schedules.schedule_get_form_vars (cyclomatic 39) REDACTED:358 — Schedules.schedule_get_form_vars 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 · VmCommon.set_right_cell_vars (cyclomatic 39) · ×1
  • VmCommon.set_right_cell_vars (cyclomatic 39) REDACTED:1203 — VmCommon.set_right_cell_vars has cyclomatic complexity 39 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MiqAlertController.alert_build_edit_screen (cyclomatic 38) · ×1
  • MiqAlertController.alert_build_edit_screen (cyclomatic 38) REDACTED:277 — MiqAlertController.alert_build_edit_screen has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · report-form-values.buildInitialValues (cyclomatic 38) · ×1
  • report-form-values.buildInitialValues (cyclomatic 38) app/javascript/components/report-editor/report-form-values.ts:73 — report-form-values.buildInitialValues 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 · find-value-editor.FindValueEditor (cyclomatic 37) · ×1
  • find-value-editor.FindValueEditor (cyclomatic 37) app/javascript/components/expression-editor/find-value-editor.jsx:115 — find-value-editor.FindValueEditor has cyclomatic complexity 37 (threshold 15). Of this number, 31 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, 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 · index.ExpressionEditor (cyclomatic 37) · ×1
  • index.ExpressionEditor (cyclomatic 37) app/javascript/components/expression-editor/index.jsx:36 — index.ExpressionEditor has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 5 of the 37 points are its own statements and the rest belongs to 18 function literals inside it that branch (lines 182, 154, 46, …). 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 · index.SortableList (cyclomatic 37) · ×1
  • index.SortableList (cyclomatic 37) app/javascript/components/sortable-list/index.jsx:22 — index.SortableList has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 7 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 164, handleDragStart, handleKeyDown, …). 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.
D1 · Cyclomatic Complexity · DashboardController.show (cyclomatic 36) · ×1
  • DashboardController.show (cyclomatic 36) REDACTED:133 — DashboardController.show 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 · ApplicationHelper.db_to_controller (cyclomatic 36) · ×1
  • ApplicationHelper.db_to_controller (cyclomatic 36) REDACTED:356 — ApplicationHelper.db_to_controller has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ToolbarChooser.center_toolbar_filename_classic (cyclomatic 36) · ×1
  • ToolbarChooser.center_toolbar_filename_classic (cyclomatic 36) app/helpers/application_helper/toolbar_chooser.rb:344 — ToolbarChooser.center_toolbar_filename_classic 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 · EmsClusterController.button (cyclomatic 35) · ×1
  • EmsClusterController.button (cyclomatic 35) app/controllers/ems_cluster_controller.rb:27 — EmsClusterController.button 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 · Menus.menu_field_changed (cyclomatic 35) · ×1
  • Menus.menu_field_changed (cyclomatic 35) app/controllers/report_controller/menus.rb:64 — Menus.menu_field_changed 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 · MiqAeClassController.form_method_field_changed (cyclomatic 34) · ×1
  • MiqAeClassController.form_method_field_changed (cyclomatic 34) REDACTED:800 — MiqAeClassController.form_method_field_changed 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 · namespace-tree-modal.NamespaceTreeModal (cyclomatic 34) · ×1
  • namespace-tree-modal.NamespaceTreeModal (cyclomatic 34) app/javascript/components/miq-ae-class/namespace-tree-modal.jsx:42 — namespace-tree-modal.NamespaceTreeModal has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 7 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 194, a function literal at line 182, onLoadData, …). 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.
D1 · Cyclomatic Complexity · miqAtomToRule (cyclomatic 34) · ×1
  • miqAtomToRule (cyclomatic 34) app/javascript/components/expression-editor/expression-adapter.js:20 — miqAtomToRule has cyclomatic complexity 34 (threshold 15). Of this number, 33 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 · OpsController.set_form_locals (cyclomatic 33) · ×1
  • OpsController.set_form_locals (cyclomatic 33) REDACTED:383 — OpsController.set_form_locals has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.SettingsCUCollectionTab (cyclomatic 33) · ×1
  • index.SettingsCUCollectionTab (cyclomatic 33) app/javascript/components/settings-cu-collection/index.jsx:13 — index.SettingsCUCollectionTab has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 10 function items inside it that branch (transformTree, a function literal at line 122, handleSubmit, …). 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.
D1 · Cyclomatic Complexity · miq_explorer.ManageIQ.explorer.processReplaceRightCell (cyclomatic 33) · ×1
  • miq_explorer.ManageIQ.explorer.processReplaceRightCell (cyclomatic 33) app/javascript/oldjs/miq_explorer.js:183 — miq_explorer.ManageIQ.explorer.processReplaceRightCell has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Schedules.build_search_filter_from_params (cyclomatic 32) · ×1
  • Schedules.build_search_filter_from_params (cyclomatic 32) REDACTED:520 — Schedules.build_search_filter_from_params has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · StorageController.button (cyclomatic 32) · ×1
  • StorageController.button (cyclomatic 32) REDACTED:73 — StorageController.button 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 · UtilizationController.chart_chooser (cyclomatic 32) · ×1
  • UtilizationController.chart_chooser (cyclomatic 32) REDACTED:34 — UtilizationController.chart_chooser 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 · CustomButtons.ab_get_node_info (cyclomatic 31) · ×1
  • CustomButtons.ab_get_node_info (cyclomatic 31) app/controllers/miq_ae_customization_controller/custom_buttons.rb:6 — CustomButtons.ab_get_node_info 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 · PolicyMixin.validate_snmp_options (cyclomatic 31) · ×1
  • PolicyMixin.validate_snmp_options (cyclomatic 31) REDACTED:91 — PolicyMixin.validate_snmp_options has cyclomatic complexity 31 (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 · index.SettingsReplicationForm (cyclomatic 31) · ×1
  • index.SettingsReplicationForm (cyclomatic 31) app/javascript/components/settings-replication-form/index.jsx:15 — index.SettingsReplicationForm has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 13 function items inside it that branch (handleConfirmCallback, a function literal at line 70, onModalSubmit, …). 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.
D1 · Cyclomatic Complexity · Diagnostics.diagnostics_set_form_vars (cyclomatic 30) · ×1
  • Diagnostics.diagnostics_set_form_vars (cyclomatic 30) REDACTED:466 — Diagnostics.diagnostics_set_form_vars has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Widgets.widget_get_form_vars (cyclomatic 30) · ×1
  • Widgets.widget_get_form_vars (cyclomatic 30) REDACTED:471 — Widgets.widget_get_form_vars has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · checkbox_tree.CheckboxTreeComponent (cyclomatic 30) · ×1
  • checkbox_tree.CheckboxTreeComponent (cyclomatic 30) app/javascript/components/tree-view/checkbox_tree.jsx:8 — checkbox_tree.CheckboxTreeComponent has cyclomatic complexity 30 (threshold 15). Of this number, 18 points are the body's own statements and 12 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · workflow-entry-points.WorkflowEntryPoints (cyclomatic 30) · ×1
  • workflow-entry-points.WorkflowEntryPoints (cyclomatic 30) app/javascript/components/workflows/workflow-entry-points.jsx:14 — workflow-entry-points.WorkflowEntryPoints has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (onSort, onApply, sortFunction, …). 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.
D1 · Cyclomatic Complexity · customer-tags-tab.CustomerTagsTab (cyclomatic 30) · ×1
  • customer-tags-tab.CustomerTagsTab (cyclomatic 30) app/javascript/components/group-form/customer-tags-tab.jsx:28 — customer-tags-tab.CustomerTagsTab has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 58, handleContextReady, handleQueryChange, …). 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.
D1 · Cyclomatic Complexity · field-picker.FieldPicker (cyclomatic 30) · ×1
  • field-picker.FieldPicker (cyclomatic 30) app/javascript/components/report-editor/field-picker.tsx:17 — field-picker.FieldPicker has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 75, a function literal at line 54, a function literal at line 38, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.ReportEditor (cyclomatic 30) · ×1
  • index.ReportEditor (cyclomatic 30) app/javascript/components/report-editor/index.tsx:61 — index.ReportEditor has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 90, a function literal at line 83, a function literal at line 145, …). 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.
D1 · Cyclomatic Complexity · expression-editor-field.ExpressionEditorInner (cyclomatic 29) · ×1
  • expression-editor-field.ExpressionEditorInner (cyclomatic 29) app/javascript/components/condition-form/expression-editor-field.jsx:10 — expression-editor-field.ExpressionEditorInner has cyclomatic complexity 29 (threshold 15). Of this number, 15 points are the body's own statements and 14 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.AbForm (cyclomatic 29) · ×1
  • index.AbForm (cyclomatic 29) app/javascript/components/ab-form/index.jsx:13 — index.AbForm has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 80, a function literal at line 43, a function literal at line 59, …). 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.
D1 · Cyclomatic Complexity · pf_aggregate_status_card.PfAggregateStatusCard (cyclomatic 29) · ×1
  • pf_aggregate_status_card.PfAggregateStatusCard (cyclomatic 29) app/javascript/components/pf_aggregate_status_card.jsx:4 — pf_aggregate_status_card.PfAggregateStatusCard has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (renderMiniLayout, renderNormalLayout, displayNotification, …). 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.
D1 · Cyclomatic Complexity · import-datastore-via-git-modal.ImportDatastoreViaGitModal (cyclomatic 29) · ×1
  • import-datastore-via-git-modal.ImportDatastoreViaGitModal (cyclomatic 29) app/javascript/components/automate-import-export-form/import-datastore-via-git-modal.jsx:9 — import-datastore-via-git-modal.ImportDatastoreViaGitModal has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 47, a function literal at line 91, a function literal at line 40, …). 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.
D1 · Cyclomatic Complexity · index.ButtonGroupForm (cyclomatic 29) · ×1
  • index.ButtonGroupForm (cyclomatic 29) app/javascript/components/button-group/index.jsx:13 — index.ButtonGroupForm has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 37, onSubmit, a function literal at line 47, …). 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.
D1 · Cyclomatic Complexity · date-value-editor.DateValueEditor (cyclomatic 29) · ×1
  • date-value-editor.DateValueEditor (cyclomatic 29) app/javascript/components/expression-editor/date-value-editor.jsx:178 — date-value-editor.DateValueEditor has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 11 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 208, a function literal at line 214, handleToggle, …). 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.
D1 · Cyclomatic Complexity · index.MiqDataTable (cyclomatic 29) · ×1
  • index.MiqDataTable (cyclomatic 29) app/javascript/components/miq-data-table/index.jsx:19 — index.MiqDataTable has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (classNameRow, a function literal at line 169, headerSortDirection, …). 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.
D1 · Cyclomatic Complexity · MiqActionController.action_field_changed (cyclomatic 28) · ×1
  • MiqActionController.action_field_changed (cyclomatic 28) REDACTED:57 — MiqActionController.action_field_changed 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.RequestsTable (cyclomatic 28) · ×1
  • index.RequestsTable (cyclomatic 28) app/javascript/components/data-tables/requests-table/index.jsx:6 — index.RequestsTable 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 9 function items inside it that branch (onSort, a function literal at line 124, a function literal at line 21, …). 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.
D1 · Cyclomatic Complexity · charts-tab.ChartsTab (cyclomatic 28) · ×1
  • charts-tab.ChartsTab (cyclomatic 28) app/javascript/components/report-editor/tabs/charts-tab.tsx:48 — charts-tab.ChartsTab has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · main-menu.MainMenu (cyclomatic 28) · ×1
  • main-menu.MainMenu (cyclomatic 28) app/javascript/menu/main-menu.tsx:27 — main-menu.MainMenu has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 10 function items inside it that branch (onSelect, a function literal at line 135, a function literal at line 67, …). 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.
D1 · Cyclomatic Complexity · ruleToMiqAtom (cyclomatic 28) · ×1
  • ruleToMiqAtom (cyclomatic 28) app/javascript/components/expression-editor/expression-adapter.js:161 — ruleToMiqAtom 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 · MiqRequestMethods.build_grid (cyclomatic 27) · ×1
  • MiqRequestMethods.build_grid (cyclomatic 27) REDACTED:527 — MiqRequestMethods.build_grid has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CatalogController.atomic_form_field_changed (cyclomatic 27) · ×1
  • CatalogController.atomic_form_field_changed (cyclomatic 27) REDACTED:235 — CatalogController.atomic_form_field_changed has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MiqActionController.action_valid_record? (cyclomatic 27) · ×1
  • MiqActionController.action_valid_record? (cyclomatic 27) REDACTED:333 — MiqActionController.action_valid_record? has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MiqAeClassController.get_method_form_vars (cyclomatic 27) · ×1
  • MiqAeClassController.get_method_form_vars (cyclomatic 27) REDACTED:2176 — MiqAeClassController.get_method_form_vars has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PxeController.replace_right_cell (cyclomatic 27) · ×1
  • PxeController.replace_right_cell (cyclomatic 27) app/controllers/pxe_controller.rb:141 — PxeController.replace_right_cell has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous).link (cyclomatic 27) · ×1
  • (anonymous).link (cyclomatic 27) app/javascript/oldjs/directives/checkchange.js:4 — (anonymous).link has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (viewModelDateComparison, model, modelCopy, …). 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.
D1 · Cyclomatic Complexity · CatalogController.st_get_form_vars (cyclomatic 26) · ×1
  • CatalogController.st_get_form_vars (cyclomatic 26) REDACTED:1692 — CatalogController.st_get_form_vars has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MiqAeClassController.replace_right_cell (cyclomatic 26) · ×1
  • MiqAeClassController.replace_right_cell (cyclomatic 26) REDACTED:278 — MiqAeClassController.replace_right_cell 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 · MiqAeClassController.instance_form_data (cyclomatic 26) · ×1
  • MiqAeClassController.instance_form_data (cyclomatic 26) REDACTED:1222 — MiqAeClassController.instance_form_data 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 · index.AutomateEntryPoints (cyclomatic 26) · ×1
  • index.AutomateEntryPoints (cyclomatic 26) app/javascript/components/automate-entry-points/index.jsx:23 — index.AutomateEntryPoints has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 13 function items inside it that branch (onExpand, onLoadData, a function literal at line 91, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.ReconfigureVmForm (cyclomatic 26) · ×1
  • index.ReconfigureVmForm (cyclomatic 26) app/javascript/components/reconfigure-vm-form/index.jsx:24 — index.ReconfigureVmForm has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 10 function items inside it that branch (setRenderForm, setButtonClick, a function literal at line 117, …). 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.
D1 · Cyclomatic Complexity · MiqRequestMethods.workflow_instance_from_vars (cyclomatic 25) · ×1
  • MiqRequestMethods.workflow_instance_from_vars (cyclomatic 25) REDACTED:1001 — MiqRequestMethods.workflow_instance_from_vars 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 · Common.settings_get_info (cyclomatic 25) · ×1
  • Common.settings_get_info (cyclomatic 25) app/controllers/ops_controller/settings/common.rb:739 — Common.settings_get_info has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · OrchestrationStackController.button (cyclomatic 25) · ×1
  • OrchestrationStackController.button (cyclomatic 25) app/controllers/orchestration_stack_controller.rb:59 — OrchestrationStackController.button has cyclomatic complexity 25 (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 · aeMethodFormController (cyclomatic 25) · ×1
  • aeMethodFormController (cyclomatic 25) app/javascript/angular/miq_ae_class/ae_method_form_controller.js:4 — aeMethodFormController has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 31 function items inside it that branch (a function literal at line 287, setConfigInfo, getConfigInfo, …). 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.
D1 · Cyclomatic Complexity · MiqRequestMethods.prov_field_changed (cyclomatic 24) · ×1
  • MiqRequestMethods.prov_field_changed (cyclomatic 24) REDACTED:9 — MiqRequestMethods.prov_field_changed 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 · AutomateTreeHelper.at_tree_select_toggle (cyclomatic 24) · ×1
  • AutomateTreeHelper.at_tree_select_toggle (cyclomatic 24) app/helpers/automate_tree_helper.rb:67 — AutomateTreeHelper.at_tree_select_toggle 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 · MiqAlertHelper.miq_summary_alert_parameters (cyclomatic 24) · ×1
  • MiqAlertHelper.miq_summary_alert_parameters (cyclomatic 24) app/helpers/miq_alert_helper.rb:46 — MiqAlertHelper.miq_summary_alert_parameters has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · expression-validator.validateRule (cyclomatic 24) · ×1
  • expression-validator.validateRule (cyclomatic 24) app/javascript/components/expression-editor/expression-validator.js:82 — expression-validator.validateRule 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 · index.MiqCustomTab (cyclomatic 24) · ×1
  • index.MiqCustomTab (cyclomatic 24) app/javascript/components/miq-custom-tab/index.jsx:8 — index.MiqCustomTab has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 10 function items inside it that branch (staticContents, a function literal at line 94, onTabSelect, …). 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.
D1 · Cyclomatic Complexity · workers-form.WorkersForm (cyclomatic 24) · ×1
  • workers-form.WorkersForm (cyclomatic 24) app/javascript/components/workers-form/workers-form.jsx:12 — workers-form.WorkersForm has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 21, onSubmit::isDifferent). 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.
D1 · Cyclomatic Complexity · createSchema (cyclomatic 24) · ×1
  • createSchema (cyclomatic 24) app/javascript/components/settings-replication-form/settings-replication-form.schema.js:6 — createSchema has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 17 function items inside it that branch (a function literal at line 114, a function literal at line 81, onCellClick, …). 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.
D1 · Cyclomatic Complexity · Filter.exp_commit_find (cyclomatic 23) · ×1
  • Filter.exp_commit_find (cyclomatic 23) REDACTED:630 — Filter.exp_commit_find has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VmCommon.list_child_vms (cyclomatic 23) · ×1
  • VmCommon.list_child_vms (cyclomatic 23) REDACTED:841 — VmCommon.list_child_vms has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: VmCommon.action_type (cyclomatic 24) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · ToolbarChooser.center_toolbar_filename_ops (cyclomatic 23) · ×1
  • ToolbarChooser.center_toolbar_filename_ops (cyclomatic 23) app/helpers/application_helper/toolbar_chooser.rb:206 — ToolbarChooser.center_toolbar_filename_ops has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CatalogHelper.catalog_basic_information (cyclomatic 23) · ×1
  • CatalogHelper.catalog_basic_information (cyclomatic 23) app/helpers/catalog_helper.rb:98 — CatalogHelper.catalog_basic_information has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MiqActionHelper.miq_summary_action_type (cyclomatic 23) · ×1
  • MiqActionHelper.miq_summary_action_type (cyclomatic 23) app/helpers/miq_action_helper.rb:22 — MiqActionHelper.miq_summary_action_type has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DialogLocalService.determine_api_endpoints (cyclomatic 23) · ×1
  • DialogLocalService.determine_api_endpoints (cyclomatic 23) app/services/dialog_local_service.rb:38 — DialogLocalService.determine_api_endpoints has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · buildSubmitData (cyclomatic 23) · ×1
  • buildSubmitData (cyclomatic 23) app/javascript/components/ab-form/helper.js:100 — buildSubmitData has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 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 · preview-tab.PreviewTab (cyclomatic 22) · ×1
  • preview-tab.PreviewTab (cyclomatic 22) app/javascript/components/report-editor/tabs/preview-tab.tsx:40 — preview-tab.PreviewTab has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 9 function items inside it that branch (renderContent, a function literal at line 77, a function literal at line 65, …). 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.
D1 · Cyclomatic Complexity · index.HelpMenuTab (cyclomatic 22) · ×1
  • index.HelpMenuTab (cyclomatic 22) app/javascript/components/settings-help-menu-form/index.jsx:14 — index.HelpMenuTab has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 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 · ApplicationController.view_to_hash (cyclomatic 21) · ×1
  • ApplicationController.view_to_hash (cyclomatic 21) REDACTED:642 — ApplicationController.view_to_hash 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 · ApplicationController.get_view_process_search_text (cyclomatic 21) · ×1
  • ApplicationController.get_view_process_search_text (cyclomatic 21) REDACTED:971 — ApplicationController.get_view_process_search_text 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 · Explorer.x_button (cyclomatic 21) · ×1
  • Explorer.x_button (cyclomatic 21) app/controllers/application_controller/explorer.rb:71 — Explorer.x_button 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 · MiqRequestMethods.prov_set_form_vars (cyclomatic 21) · ×1
  • MiqRequestMethods.prov_set_form_vars (cyclomatic 21) REDACTED:909 — MiqRequestMethods.prov_set_form_vars 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 · Performance.perf_chart_chooser (cyclomatic 21) · ×1
  • Performance.perf_chart_chooser (cyclomatic 21) REDACTED:9 — Performance.perf_chart_chooser 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 · GenericButtonMixin.button (cyclomatic 21) · ×1
  • GenericButtonMixin.button (cyclomatic 21) app/controllers/mixins/generic_button_mixin.rb:47 — GenericButtonMixin.button 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 · OpsController.settings_replace_right_cell (cyclomatic 21) · ×1
  • OpsController.settings_replace_right_cell (cyclomatic 21) REDACTED:544 — OpsController.settings_replace_right_cell 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 · Common.settings_update_save (cyclomatic 21) · ×1
  • Common.settings_update_save (cyclomatic 21) app/controllers/ops_controller/settings/common.rb:302 — Common.settings_update_save 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 · Schedules.schedule_edit (cyclomatic 21) · ×1
  • Schedules.schedule_edit (cyclomatic 21) REDACTED:191 — Schedules.schedule_edit 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 · UtilizationController.get_node_info (cyclomatic 21) · ×1
  • UtilizationController.get_node_info (cyclomatic 21) REDACTED:129 — UtilizationController.get_node_info 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 · index.ContainerGroupConsole (cyclomatic 21) · ×1
  • index.ContainerGroupConsole (cyclomatic 21) app/javascript/components/container-group-console/index.jsx:8 — index.ContainerGroupConsole has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 10 function items inside it that branch (closeConsole, a function literal at line 52, a function literal at line 81, …). 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.
D1 · Cyclomatic Complexity · helper.getFirewallRules (cyclomatic 21) · ×1
  • helper.getFirewallRules (cyclomatic 21) app/javascript/components/network-security-groups-form/helper.js:2 — helper.getFirewallRules has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 9, 53). 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 · request-workflow-status-item.RequestWorkflowStatusItem (cyclomatic 21) · ×1
  • request-workflow-status-item.RequestWorkflowStatusItem (cyclomatic 21) app/javascript/components/request-workflow-status/request-workflow-status-item.jsx:11 — request-workflow-status-item.RequestWorkflowStatusItem has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 69, a function literal at line 35, renderStatusTag, …). 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.
D1 · Cyclomatic Complexity · index.RoutersForm (cyclomatic 21) · ×1
  • index.RoutersForm (cyclomatic 21) app/javascript/components/routers-form/index.jsx:9 — index.RoutersForm has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (formatInitialData, getSubmitData, a function literal at line 68, …). 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.
D1 · Cyclomatic Complexity · Buttons.buttons_get_node_info (cyclomatic 20) · ×1
  • Buttons.buttons_get_node_info (cyclomatic 20) REDACTED:470 — Buttons.buttons_get_node_info 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 · Performance.perf_util_daily_gen_data (cyclomatic 20) · ×1
  • Performance.perf_util_daily_gen_data (cyclomatic 20) REDACTED:983 — Performance.perf_util_daily_gen_data 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 · EmsConfigurationController.button (cyclomatic 20) · ×1
  • EmsConfigurationController.button (cyclomatic 20) app/controllers/ems_configuration_controller.rb:27 — EmsConfigurationController.button has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MiqAeClassController.method_form_fields (cyclomatic 20) · ×1
  • MiqAeClassController.method_form_fields (cyclomatic 20) REDACTED:914 — MiqAeClassController.method_form_fields 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 · GenericShowMixin.show (cyclomatic 20) · ×1
  • GenericShowMixin.show (cyclomatic 20) app/controllers/mixins/generic_show_mixin.rb:3 — GenericShowMixin.show 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 · LabelTagMapping.label_tag_mapping_edit (cyclomatic 20) · ×1
  • LabelTagMapping.label_tag_mapping_edit (cyclomatic 20) REDACTED:53 — LabelTagMapping.label_tag_mapping_edit 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 · VmCommon.button (cyclomatic 20) · ×1
  • VmCommon.button (cyclomatic 20) REDACTED:29 — VmCommon.button has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: VmCommon.action_type (cyclomatic 24) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · ToolbarBuilder.twostate_button_selected (cyclomatic 20) · ×1
  • ToolbarBuilder.twostate_button_selected (cyclomatic 20) app/helpers/application_helper/toolbar_builder.rb:375 — ToolbarBuilder.twostate_button_selected has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.ConditionForm (cyclomatic 20) · ×1
  • index.ConditionForm (cyclomatic 20) app/javascript/components/condition-form/index.jsx:27 — index.ConditionForm has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (onSubmit, a function literal at line 83, a function literal at line 91, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.DashboardWidget (cyclomatic 20) · ×1
  • index.DashboardWidget (cyclomatic 20) app/javascript/components/dashboard-widgets/dashboard-charts/index.jsx:9 — index.DashboardWidget 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 · field-config.buildFieldConfig (cyclomatic 20) · ×1
  • field-config.buildFieldConfig (cyclomatic 20) app/javascript/components/expression-editor/field-config.js:74 — field-config.buildFieldConfig has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 82). 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 · Dashboards.db_edit (cyclomatic 19) · ×1
  • Dashboards.db_edit (cyclomatic 19) REDACTED:116 — Dashboards.db_edit 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 · Schedules.schedule_set_form_vars (cyclomatic 19) · ×1
  • Schedules.schedule_set_form_vars (cyclomatic 19) REDACTED:296 — Schedules.schedule_set_form_vars 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 · ExplorerPresenter.for_render_default (cyclomatic 19) · ×1
  • ExplorerPresenter.for_render_default (cyclomatic 19) app/presenters/explorer_presenter.rb:236 — ExplorerPresenter.for_render_default 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 · GtlFormatter.format_cols (cyclomatic 19) · ×1
  • GtlFormatter.format_cols (cyclomatic 19) lib/gtl_formatter.rb:67 — GtlFormatter.format_cols 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 · async-credentials.AsyncCredentials (cyclomatic 19) · ×1
  • async-credentials.AsyncCredentials (cyclomatic 19) app/javascript/components/async-credentials/async-credentials.jsx:18 — async-credentials.AsyncCredentials has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 52, 80, …). 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 · redux.TreeView (cyclomatic 19) · ×1
  • redux.TreeView (cyclomatic 19) REDACTED:126 — redux.TreeView has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 249, 184, 258, …). 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 · remove-generic-item-modal.removeItems (cyclomatic 19) · ×1
  • remove-generic-item-modal.removeItems (cyclomatic 19) app/javascript/components/remove-generic-item-modal.jsx:37 — remove-generic-item-modal.removeItems 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 5 function literals inside it that branch (lines 87, 66, 72, …). 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 · trend-columns-tab.TrendColumnsTab (cyclomatic 19) · ×1
  • trend-columns-tab.TrendColumnsTab (cyclomatic 19) app/javascript/components/report-editor/tabs/trend-columns-tab.tsx:19 — trend-columns-tab.TrendColumnsTab has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 78, 48, 68, …). 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 · index.SettingsCompanyTags (cyclomatic 19) · ×1
  • index.SettingsCompanyTags (cyclomatic 19) app/javascript/components/settings-company-tags/index.jsx:15 — index.SettingsCompanyTags has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (formCallback, onButtonCallback, renderList, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 19) · ×1
  • (anonymous) (cyclomatic 19) app/javascript/oldjs/controllers/dialog_editor/dialog_editor_controller.js:1 — (anonymous) has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 27 function items inside it that branch (init, customizer, a function literal at line 203, …). 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.
D1 · Cyclomatic Complexity · Filter.exp_button (cyclomatic 18) · ×1
  • Filter.exp_button (cyclomatic 18) REDACTED:16 — Filter.exp_button 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 · Performance.perf_gen_charts (cyclomatic 18) · ×1
  • Performance.perf_gen_charts (cyclomatic 18) REDACTED:1094 — Performance.perf_gen_charts 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 · Common.settings_form_field_changed (cyclomatic 18) · ×1
  • Common.settings_form_field_changed (cyclomatic 18) app/controllers/ops_controller/settings/common.rb:13 — Common.settings_form_field_changed 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 · EditorMapping.serialize_report_attrs (cyclomatic 18) · ×1
  • EditorMapping.serialize_report_attrs (cyclomatic 18) app/controllers/report_controller/reports/editor_mapping.rb:451 — EditorMapping.serialize_report_attrs 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 · index.ApForm · ×1
  • index.ApForm::onSubmit (cyclomatic 18) app/javascript/components/ap-form/index.jsx:146 — index.ApForm::onSubmit 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 (index.ApForm) 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 · modal-form.schema.createClassFieldsSchema · ×1
  • modal-form.schema.createClassFieldsSchema::getInitialValue (cyclomatic 18) app/javascript/components/data-tables/datastore/schema/modal-form.schema.js:43 — modal-form.schema.createClassFieldsSchema::getInitialValue 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 · class-fields-editor.ClassFieldsEditor · ×1
  • class-fields-editor.ClassFieldsEditor::formatFieldValues (cyclomatic 18) app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx:76 — class-fields-editor.ClassFieldsEditor::formatFieldValues 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 · gtl-view.GtlView · ×1
  • gtl-view.GtlView::onItemClick (cyclomatic 18) app/javascript/components/gtl-view.jsx:433 — gtl-view.GtlView::onItemClick 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 · standard-filter.StandardFilter (cyclomatic 18) · ×1
  • standard-filter.StandardFilter (cyclomatic 18) app/javascript/components/report-editor/tabs/filter/standard-filter.tsx:16 — standard-filter.StandardFilter has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 31, 42, 52, …). 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 · createTreeReducer (cyclomatic 18) · ×1
  • createTreeReducer (cyclomatic 18) app/javascript/components/tree-view/reducers/index.js:63 — createTreeReducer 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 19 function literals inside it that branch (lines 66, 71, 76, …). 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 · MiqRequestMethods.prov_edit (cyclomatic 17) · ×1
  • MiqRequestMethods.prov_edit (cyclomatic 17) REDACTED:219 — MiqRequestMethods.prov_edit 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 · CatalogController.st_edit (cyclomatic 17) · ×1
  • CatalogController.st_edit (cyclomatic 17) REDACTED:437 — CatalogController.st_edit 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 · CatalogController.get_node_info_handle_leaf_node (cyclomatic 17) · ×1
  • CatalogController.get_node_info_handle_leaf_node (cyclomatic 17) REDACTED:1908 — CatalogController.get_node_info_handle_leaf_node 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 · MiqAeClassController.update_instance (cyclomatic 17) · ×1
  • MiqAeClassController.update_instance (cyclomatic 17) REDACTED:599 — MiqAeClassController.update_instance 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 · Reconfigure.build_reconfigure_hash (cyclomatic 17) · ×1
  • Reconfigure.build_reconfigure_hash (cyclomatic 17) app/controllers/mixins/actions/vm_actions/reconfigure.rb:109 — Reconfigure.build_reconfigure_hash 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 · PolicyMixin.send_button_changes (cyclomatic 17) · ×1
  • PolicyMixin.send_button_changes (cyclomatic 17) REDACTED:3 — PolicyMixin.send_button_changes 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 · PolicyMixin.build_snmp_options (cyclomatic 17) · ×1
  • PolicyMixin.build_snmp_options (cyclomatic 17) REDACTED:124 — PolicyMixin.build_snmp_options 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 · OpsRbac.rbac_edit_reset (cyclomatic 17) · ×1
  • OpsRbac.rbac_edit_reset (cyclomatic 17) REDACTED:587 — OpsRbac.rbac_edit_reset 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 · AnalysisProfiles.ap_form_data (cyclomatic 17) · ×1
  • AnalysisProfiles.ap_form_data (cyclomatic 17) REDACTED:87 — AnalysisProfiles.ap_form_data 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 · EditorMapping.chargeback_validation_errors (cyclomatic 17) · ×1
  • EditorMapping.chargeback_validation_errors (cyclomatic 17) app/controllers/report_controller/reports/editor_mapping.rb:400 — EditorMapping.chargeback_validation_errors 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 · ToolbarChooser.center_toolbar_filename_automate_customization (cyclomatic 17) · ×1
  • ToolbarChooser.center_toolbar_filename_automate_customization (cyclomatic 17) app/helpers/application_helper/toolbar_chooser.rb:140 — ToolbarChooser.center_toolbar_filename_automate_customization 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 · index.AeInlineMethod (cyclomatic 17) · ×1
  • index.AeInlineMethod (cyclomatic 17) app/javascript/components/AeInlineMethod/index.jsx:15 — index.AeInlineMethod has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 8 function items inside it that branch (renderModalSelector, onCellClickHandler, renderList, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.AnsibleRepositoryForm (cyclomatic 17) · ×1
  • index.AnsibleRepositoryForm (cyclomatic 17) app/javascript/components/ansible-repository-form/index.jsx:9 — index.AnsibleRepositoryForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (onSubmit, a function literal at line 16, a function literal at line 21, …). 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.
D1 · Cyclomatic Complexity · index.ApForm (cyclomatic 17) · ×1
  • index.ApForm (cyclomatic 17) app/javascript/components/ap-form/index.jsx:15 — index.ApForm 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. This shape REPEATS in the file: one other method here (index.ApForm::onSubmit) 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 · index.ContainerGroupLogs (cyclomatic 17) · ×1
  • index.ContainerGroupLogs (cyclomatic 17) app/javascript/components/container-group-logs/index.jsx:7 — index.ContainerGroupLogs has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 35, 22). 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 · index.EmbeddedTerraformRepositoryForm (cyclomatic 17) · ×1
  • index.EmbeddedTerraformRepositoryForm (cyclomatic 17) app/javascript/components/embedded-terraform-repository-form/index.jsx:9 — index.EmbeddedTerraformRepositoryForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (onSubmit, a function literal at line 16, a function literal at line 21, …). 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.
D1 · Cyclomatic Complexity · field-selector.TwoStepFieldSelector (cyclomatic 17) · ×1
  • field-selector.TwoStepFieldSelector (cyclomatic 17) app/javascript/components/expression-editor/field-selector.jsx:12 — field-selector.TwoStepFieldSelector has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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 · index.WorkflowRepositoryForm (cyclomatic 17) · ×1
  • index.WorkflowRepositoryForm (cyclomatic 17) app/javascript/components/workflow-repository-form/index.jsx:9 — index.WorkflowRepositoryForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (onSubmit, a function literal at line 16, a function literal at line 21, …). 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.
D1 · Cyclomatic Complexity · ApplicationController.drop_breadcrumb (cyclomatic 16) · ×1
  • ApplicationController.drop_breadcrumb (cyclomatic 16) REDACTED:757 — ApplicationController.drop_breadcrumb 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 · ApplicationController.render_or_redirect_partial (cyclomatic 16) · ×1
  • ApplicationController.render_or_redirect_partial (cyclomatic 16) REDACTED:1246 — ApplicationController.render_or_redirect_partial 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 · ApplicationController.get_global_session_data (cyclomatic 16) · ×1
  • ApplicationController.get_global_session_data (cyclomatic 16) REDACTED:1489 — ApplicationController.get_global_session_data 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 · CiProcessing.edit_record (cyclomatic 16) · ×1
  • CiProcessing.edit_record (cyclomatic 16) REDACTED:26 — CiProcessing.edit_record has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: CiProcessing.process_vm_buttons (cyclomatic 39) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · DialogRunner.dialog_get_form_vars (cyclomatic 16) · ×1
  • DialogRunner.dialog_get_form_vars (cyclomatic 16) app/controllers/application_controller/dialog_runner.rb:177 — DialogRunner.dialog_get_form_vars 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 · MiqRequestMethods.prov_set_show_vars (cyclomatic 16) · ×1
  • MiqRequestMethods.prov_set_show_vars (cyclomatic 16) REDACTED:853 — MiqRequestMethods.prov_set_show_vars 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 · PolicySupport.protect (cyclomatic 16) · ×1
  • PolicySupport.protect (cyclomatic 16) REDACTED:5 — PolicySupport.protect 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 · CatalogController.get_form_vars (cyclomatic 16) · ×1
  • CatalogController.get_form_vars (cyclomatic 16) REDACTED:1493 — CatalogController.get_form_vars 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 · CatalogController.set_record_vars_ovf_template (cyclomatic 16) · ×1
  • CatalogController.set_record_vars_ovf_template (cyclomatic 16) REDACTED:2127 — CatalogController.set_record_vars_ovf_template 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 · InfraNetworkingController.replace_right_cell (cyclomatic 16) · ×1
  • InfraNetworkingController.replace_right_cell (cyclomatic 16) app/controllers/infra_networking_controller.rb:288 — InfraNetworkingController.replace_right_cell 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 · OldDialogs.old_dialogs_update_create (cyclomatic 16) · ×1
  • OldDialogs.old_dialogs_update_create (cyclomatic 16) REDACTED:281 — OldDialogs.old_dialogs_update_create 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 · MiqAlertController.alert_set_record_vars (cyclomatic 16) · ×1
  • MiqAlertController.alert_set_record_vars (cyclomatic 16) REDACTED:565 — MiqAlertController.alert_set_record_vars 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 · OpsController.explorer (cyclomatic 16) · ×1
  • OpsController.explorer (cyclomatic 16) REDACTED:157 — OpsController.explorer 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 · Schedules.schedule_edit (cyclomatic 16) · ×1
  • Schedules.schedule_edit (cyclomatic 16) REDACTED:60 — Schedules.schedule_edit 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 · Schedules.build_schedule_options_for_select (cyclomatic 16) · ×1
  • Schedules.build_schedule_options_for_select (cyclomatic 16) REDACTED:608 — Schedules.build_schedule_options_for_select 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 · Menus.edit_reports (cyclomatic 16) · ×1
  • Menus.edit_reports (cyclomatic 16) app/controllers/report_controller/menus.rb:268 — Menus.edit_reports 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 · Widgets.widget_set_record_vars (cyclomatic 16) · ×1
  • Widgets.widget_set_record_vars (cyclomatic 16) REDACTED:549 — Widgets.widget_set_record_vars 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 · expression-adapter.miqToRqb (cyclomatic 16) · ×1
  • expression-adapter.miqToRqb (cyclomatic 16) app/javascript/components/expression-editor/expression-adapter.js:103 — expression-adapter.miqToRqb has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 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 · file-upload-section.FileUploadSection (cyclomatic 16) · ×1
  • file-upload-section.FileUploadSection (cyclomatic 16) app/javascript/components/automate-import-export-form/file-upload-section.jsx:6 — file-upload-section.FileUploadSection has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (handleUpload, handleFileChange, handleFileDelete). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · attach-detach-cloud-volume-form.AttachDetachCloudVolumeForm (cyclomatic 16) · ×1
  • attach-detach-cloud-volume-form.AttachDetachCloudVolumeForm (cyclomatic 16) app/javascript/components/cloud-volume-form/attach-detach-cloud-volume-form.jsx:10 — attach-detach-cloud-volume-form.AttachDetachCloudVolumeForm has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 32, onSubmit, onCancel, …). 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.
D1 · Cyclomatic Complexity · index.GroupForm · ×1
  • index.GroupForm::onSubmit (cyclomatic 16) app/javascript/components/group-form/index.jsx:213 — index.GroupForm::onSubmit 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 · ToolbarList.ToolbarList (cyclomatic 16) · ×1
  • ToolbarList.ToolbarList (cyclomatic 16) app/javascript/components/toolbar/ToolbarList.jsx:11 — ToolbarList.ToolbarList has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 79, a function literal at line 36, keydownFunc, …). 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.
D1 · Cyclomatic Complexity · miq-toolbar.onClick (cyclomatic 16) · ×1
  • miq-toolbar.onClick (cyclomatic 16) app/javascript/components/miq-toolbar.jsx:37 — miq-toolbar.onClick has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.RetirementForm (cyclomatic 16) · ×1
  • index.RetirementForm (cyclomatic 16) app/javascript/components/retirement-form/index.jsx:13 — index.RetirementForm has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (onSubmit, a function literal at line 91, a function literal at line 89, …). 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.
D1 · Cyclomatic Complexity · helper.createRows (cyclomatic 16) · ×1
  • helper.createRows (cyclomatic 16) app/javascript/components/tenant-quota-form/helper.js:4 — helper.createRows has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function items inside it that branch (isDisabled, validate, isChanged, …). 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.
D1 · Cyclomatic Complexity · snapshot-tree.SnapshotTree (cyclomatic 16) · ×1
  • snapshot-tree.SnapshotTree (cyclomatic 16) app/javascript/components/vm-snapshot-tree-select/snapshot-tree.jsx:30 — snapshot-tree.SnapshotTree has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 42, a function literal at line 132, ArrowIcon, …). 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.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 16) · ×1
  • (anonymous) (cyclomatic 16) app/javascript/oldjs/controllers/dialog_user/dialog_user_controller.js:1 — (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 19 function items inside it that branch (a function literal at line 23, submitButtonClicked, a function literal at line 88, …). 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.
D17 · Explicit Debt · TodoComment repeated across 10 files · ×1
  • TodoComment repeated across 10 files app/helpers/application_helper/toolbar/miq_templates_center.rb:80 — The identical TodoComment appears in 10 files (10 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 10 independent debts. Fix the systemic cause once rather than file-by-file. Text: "# TODO: Add this button back when the page is fixed". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D2 · Cognitive Complexity · ReportController.replace_right_cell (cognitive 153) · ×1
  • ReportController.replace_right_cell (cognitive 153) REDACTED:636 — ReportController.replace_right_cell has cognitive complexity 153 (threshold 15). Drivers by points: if/else 60 (105 pts), ternaries 10 (26 pts), boolean chains 20, match/switch 1 (2 pts) (nesting depth added 62). To reduce it, split the body into named stages: move each independent 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.ChargebackAssignmentsForm (cognitive 125) · ×1
  • index.ChargebackAssignmentsForm (cognitive 125) app/javascript/components/chargeback-assignments-form/index.jsx:14 — index.ChargebackAssignmentsForm has cognitive complexity 125 (threshold 15). Drivers by points: if/else 52 (92 pts), boolean chains 28, error handling 2, ternaries 1 (2 pts), match/switch 1 (nesting depth added 41). Most of this is not in the body itself: 11 of the 125 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 86, handleSubmit, a function literal at line 233, …). 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 · Common.settings_get_form_vars (cognitive 113) · ×1
  • Common.settings_get_form_vars (cognitive 113) app/controllers/ops_controller/settings/common.rb:493 — Common.settings_get_form_vars has cognitive complexity 113 (threshold 15). Drivers by points: if/else 49 (94 pts), boolean chains 16, error handling 1, match/switch 1, ternaries 1 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CatalogController.replace_right_cell (cognitive 106) · ×1
  • CatalogController.replace_right_cell (cognitive 106) REDACTED:2299 — CatalogController.replace_right_cell has cognitive complexity 106 (threshold 15). Drivers by points: if/else 42 (64 pts), boolean chains 28, ternaries 3 (9 pts), match/switch 2 (5 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqRequestMethods.prov_get_form_vars (cognitive 91) · ×1
  • MiqRequestMethods.prov_get_form_vars (cognitive 91) REDACTED:725 — MiqRequestMethods.prov_get_form_vars has cognitive complexity 91 (threshold 15). Drivers by points: if/else 44 (87 pts), error handling 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VmCommon.replace_right_cell (cognitive 89) · ×1
  • VmCommon.replace_right_cell (cognitive 89) REDACTED:951 — VmCommon.replace_right_cell has cognitive complexity 89 (threshold 15). Drivers by points: if/else 45 (71 pts), boolean chains 16, ternaries 1 (2 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validation.validateReportForm (cognitive 83) · ×1
  • validation.validateReportForm (cognitive 83) app/javascript/components/report-editor/validation.ts:7 — validation.validateReportForm has cognitive complexity 83 (threshold 15). Drivers by points: if/else 38 (68 pts), boolean chains 11, ternaries 3 (4 pts) (nesting depth added 31). Of this number, 82 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 · Menus.menu_field_changed (cognitive 82) · ×1
  • Menus.menu_field_changed (cognitive 82) app/controllers/report_controller/menus.rb:64 — Menus.menu_field_changed has cognitive complexity 82 (threshold 15). Drivers by points: if/else 33 (75 pts), boolean chains 6, ternaries 1 (nesting depth added 42). 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 · BreadcrumbsMixin.data_for_breadcrumbs (cognitive 77) · ×1
  • BreadcrumbsMixin.data_for_breadcrumbs (cognitive 77) app/controllers/mixins/breadcrumbs_mixin.rb:24 — BreadcrumbsMixin.data_for_breadcrumbs has cognitive complexity 77 (threshold 15). Drivers by points: if/else 22 (51 pts), boolean chains 23, ternaries 1 (3 pts) (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CatalogController.st_get_form_vars (cognitive 76) · ×1
  • CatalogController.st_get_form_vars (cognitive 76) REDACTED:1692 — CatalogController.st_get_form_vars has cognitive complexity 76 (threshold 15). Drivers by points: if/else 23 (69 pts), match/switch 1 (4 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 50). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · EmsCommon.button (cognitive 74) · ×1
  • EmsCommon.button (cognitive 74) REDACTED:193 — EmsCommon.button has cognitive complexity 74 (threshold 15). Drivers by points: if/else 37 (57 pts), match/switch 4 (9 pts), boolean chains 8 (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 · UtilizationController.chart_chooser (cognitive 73) · ×1
  • UtilizationController.chart_chooser (cognitive 73) REDACTED:34 — UtilizationController.chart_chooser has cognitive complexity 73 (threshold 15). Drivers by points: if/else 20 (41 pts), ternaries 9 (30 pts), boolean chains 2 (nesting depth added 42). 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 · index.ApForm (cognitive 71) · ×1
  • index.ApForm (cognitive 71) app/javascript/components/ap-form/index.jsx:15 — index.ApForm has cognitive complexity 71 (threshold 15). Drivers by points: boolean chains 40, ternaries 18 (21 pts), if/else 10 (nesting depth added 3). Of this number, 16 points are the body's own statements and 55 belong to 14 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · CatalogController.atomic_req_submit (cognitive 70) · ×1
  • CatalogController.atomic_req_submit (cognitive 70) REDACTED:1001 — CatalogController.atomic_req_submit has cognitive complexity 70 (threshold 15). Drivers by points: if/else 38 (55 pts), boolean chains 8, ternaries 3 (5 pts), match/switch 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Widgets.widget_set_form_vars (cognitive 66) · ×1
  • Widgets.widget_set_form_vars (cognitive 66) REDACTED:305 — Widgets.widget_set_form_vars has cognitive complexity 66 (threshold 15). Drivers by points: if/else 27 (42 pts), boolean chains 13, ternaries 6 (11 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · carbon-value-editor.CarbonValueEditor (cognitive 65) · ×1
  • carbon-value-editor.CarbonValueEditor (cognitive 65) app/javascript/components/expression-editor/carbon-value-editor.jsx:273 — carbon-value-editor.CarbonValueEditor has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 26, ternaries 13 (20 pts), if/else 14 (19 pts) (nesting depth added 12). Of this number, 47 points are the body's own statements and 18 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 · index.GroupForm (cognitive 65) · ×1
  • index.GroupForm (cognitive 65) app/javascript/components/group-form/index.jsx:42 — index.GroupForm has cognitive complexity 65 (threshold 15). Drivers by points: boolean chains 33, ternaries 17 (22 pts), if/else 10 (nesting depth added 5). Most of this is not in the body itself: 11 of the 65 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 93, onSubmit, a function literal at line 74, …). 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 · ApplicationHelper.view_to_url (cognitive 64) · ×1
  • ApplicationHelper.view_to_url (cognitive 64) REDACTED:238 — ApplicationHelper.view_to_url has cognitive complexity 64 (threshold 15). Drivers by points: if/else 23 (41 pts), boolean chains 16, ternaries 2 (4 pts), match/switch 1 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationController.get_view (cognitive 62) · ×1
  • ApplicationController.get_view (cognitive 62) REDACTED:1050 — ApplicationController.get_view has cognitive complexity 62 (threshold 15). Drivers by points: boolean chains 29, if/else 22 (24 pts), ternaries 8 (9 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MiqAlertController.alert_valid_record? (cognitive 62) · ×1
  • MiqAlertController.alert_valid_record? (cognitive 62) REDACTED:603 — MiqAlertController.alert_valid_record? has cognitive complexity 62 (threshold 15). Drivers by points: if/else 30 (47 pts), boolean chains 13, ternaries 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EmsClusterController.button (cognitive 60) · ×1
  • EmsClusterController.button (cognitive 60) app/controllers/ems_cluster_controller.rb:27 — EmsClusterController.button has cognitive complexity 60 (threshold 15). Drivers by points: if/else 31 (54 pts), boolean chains 6 (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 · instance-form.InstanceForm (cognitive 60) · ×1
  • instance-form.InstanceForm (cognitive 60) app/javascript/components/miq-ae-class/instance-form.jsx:12 — instance-form.InstanceForm has cognitive complexity 60 (threshold 15). Drivers by points: boolean chains 44, if/else 8 (9 pts), ternaries 7 (nesting depth added 1). Of this number, 23 points are the body's own statements and 37 belong to 13 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · MiqAlertController.alert_field_changed (cognitive 59) · ×1
  • MiqAlertController.alert_field_changed (cognitive 59) REDACTED:95 — MiqAlertController.alert_field_changed has cognitive complexity 59 (threshold 15). Drivers by points: if/else 40 (47 pts), ternaries 4 (7 pts), boolean chains 5 (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 · Diagnostics.diagnostics_set_form_vars (cognitive 58) · ×1
  • Diagnostics.diagnostics_set_form_vars (cognitive 58) REDACTED:466 — Diagnostics.diagnostics_set_form_vars has cognitive complexity 58 (threshold 15). Drivers by points: if/else 32 (54 pts), boolean chains 4 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HostController.button (cognitive 57) · ×1
  • HostController.button (cognitive 57) REDACTED:178 — HostController.button has cognitive complexity 57 (threshold 15). Drivers by points: if/else 28 (46 pts), boolean chains 9, match/switch 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VmCommon.show (cognitive 57) · ×1
  • VmCommon.show (cognitive 57) REDACTED:143 — VmCommon.show has cognitive complexity 57 (threshold 15). Drivers by points: if/else 31 (37 pts), ternaries 5 (11 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OpsController.set_form_locals (cognitive 55) · ×1
  • OpsController.set_form_locals (cognitive 55) REDACTED:383 — OpsController.set_form_locals has cognitive complexity 55 (threshold 15). Drivers by points: if/else 21 (30 pts), ternaries 5 (17 pts), boolean chains 8 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CustomButtons.ab_get_node_info (cognitive 54) · ×1
  • CustomButtons.ab_get_node_info (cognitive 54) app/controllers/miq_ae_customization_controller/custom_buttons.rb:6 — CustomButtons.ab_get_node_info has cognitive complexity 54 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 10, ternaries 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chargeback-filter.ChargebackFilter (cognitive 54) · ×1
  • chargeback-filter.ChargebackFilter (cognitive 54) app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:112 — chargeback-filter.ChargebackFilter has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 37, if/else 15, ternaries 2. Of this number, 42 points are the body's own statements and 12 belong to 7 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.
D2 · Cognitive Complexity · MiqAlertController.alert_build_edit_screen (cognitive 52) · ×1
  • MiqAlertController.alert_build_edit_screen (cognitive 52) REDACTED:277 — MiqAlertController.alert_build_edit_screen has cognitive complexity 52 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 15, ternaries 6 (14 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 · atomToHuman (cognitive 52) · ×1
  • atomToHuman (cognitive 52) app/javascript/components/expression-editor/expression-human.js:89 — atomToHuman has cognitive complexity 52 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 13, ternaries 6 (12 pts), other 8 (nesting depth added 11). Of this number, 51 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · helper.getFirewallRules (cognitive 51) · ×1
  • helper.getFirewallRules (cognitive 51) app/javascript/components/network-security-groups-form/helper.js:2 — helper.getFirewallRules has cognitive complexity 51 (threshold 15). Drivers by points: if/else 16 (46 pts), boolean chains 5 (nesting depth added 30). Most of this is not in the body itself: 6 of the 51 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 9, 53). 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 · Schedules.schedule_get_form_vars (cognitive 50) · ×1
  • Schedules.schedule_get_form_vars (cognitive 50) REDACTED:358 — Schedules.schedule_get_form_vars has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (28 pts), ternaries 5 (12 pts), boolean chains 10 (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 · MiqRequestMethods.build_grid (cognitive 49) · ×1
  • MiqRequestMethods.build_grid (cognitive 49) REDACTED:527 — MiqRequestMethods.build_grid has cognitive complexity 49 (threshold 15). Drivers by points: if/else 22 (45 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MiqRequestMethods.workflow_instance_from_vars (cognitive 49) · ×1
  • MiqRequestMethods.workflow_instance_from_vars (cognitive 49) REDACTED:1001 — MiqRequestMethods.workflow_instance_from_vars has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (37 pts), ternaries 3 (7 pts), boolean chains 4, error handling 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · label-selection.LabelSelection (cognitive 49) · ×1
  • label-selection.LabelSelection (cognitive 49) app/javascript/components/chargeback-assignments-form/label-selection.jsx:16 — label-selection.LabelSelection has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 23, if/else 18 (23 pts), error handling 3 (nesting depth added 5). Most of this is not in the body itself: 10 of the 49 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 76, a function literal at line 87, a function literal at line 140, …). 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 · ApplicationController.set_global_session_data (cognitive 48) · ×1
  • ApplicationController.set_global_session_data (cognitive 48) REDACTED:1553 — ApplicationController.set_global_session_data has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (30 pts), boolean chains 9, ternaries 5 (7 pts), match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Compare.prepare_data_for_compare_or_drift_report (cognitive 48) · ×1
  • Compare.prepare_data_for_compare_or_drift_report (cognitive 48) REDACTED:515 — Compare.prepare_data_for_compare_or_drift_report has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (35 pts), boolean chains 12, 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 · Performance.perf_gen_charts (cognitive 48) · ×1
  • Performance.perf_gen_charts (cognitive 48) REDACTED:1094 — Performance.perf_gen_charts has cognitive complexity 48 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 7 (23 pts), match/switch 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ToolbarChooser.center_toolbar_filename_classic (cognitive 48) · ×1
  • ToolbarChooser.center_toolbar_filename_classic (cognitive 48) app/helpers/application_helper/toolbar_chooser.rb:344 — ToolbarChooser.center_toolbar_filename_classic has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (29 pts), ternaries 4 (11 pts), boolean chains 8 (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 · index.RoleForm (cognitive 46) · ×1
  • index.RoleForm (cognitive 46) app/javascript/components/role-form/index.jsx:14 — index.RoleForm has cognitive complexity 46 (threshold 15). Drivers by points: if/else 23 (28 pts), boolean chains 12, ternaries 4 (5 pts), match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 46 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 125, onSubmit, findCheck, …). 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 · MiqAeClassController.form_method_field_changed (cognitive 45) · ×1
  • MiqAeClassController.form_method_field_changed (cognitive 45) REDACTED:800 — MiqAeClassController.form_method_field_changed has cognitive complexity 45 (threshold 15). Drivers by points: if/else 29 (33 pts), boolean chains 12 (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 · miq_explorer.ManageIQ.explorer.processReplaceRightCell (cognitive 45) · ×1
  • miq_explorer.ManageIQ.explorer.processReplaceRightCell (cognitive 45) app/javascript/oldjs/miq_explorer.js:183 — miq_explorer.ManageIQ.explorer.processReplaceRightCell has cognitive complexity 45 (threshold 15). Drivers by points: if/else 32 (43 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqAeClassController.get_method_form_vars (cognitive 44) · ×1
  • MiqAeClassController.get_method_form_vars (cognitive 44) REDACTED:2176 — MiqAeClassController.get_method_form_vars has cognitive complexity 44 (threshold 15). Drivers by points: if/else 21 (39 pts), boolean chains 4, ternaries 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VmCommon.list_child_vms (cognitive 44) · ×1
  • VmCommon.list_child_vms (cognitive 44) REDACTED:841 — VmCommon.list_child_vms has cognitive complexity 44 (threshold 15). Drivers by points: if/else 21 (36 pts), ternaries 3 (6 pts), boolean chains 2 (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 · index.RequestsTable (cognitive 43) · ×1
  • index.RequestsTable (cognitive 43) app/javascript/components/data-tables/requests-table/index.jsx:6 — index.RequestsTable has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (36 pts), boolean chains 3, ternaries 3, match/switch 1 (nesting depth added 20). Most of this is not in the body itself: 1 of the 43 points is its own statement and the rest belongs to 9 function items inside it that branch (onSort, a function literal at line 21, a function literal at line 54, …). 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 · DashboardController.show (cognitive 42) · ×1
  • DashboardController.show (cognitive 42) REDACTED:133 — DashboardController.show has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (26 pts), boolean chains 15, match/switch 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 · Widgets.widget_get_form_vars (cognitive 41) · ×1
  • Widgets.widget_get_form_vars (cognitive 41) REDACTED:471 — Widgets.widget_get_form_vars has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (34 pts), boolean chains 6, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqRequestMethods.prov_set_form_vars (cognitive 40) · ×1
  • MiqRequestMethods.prov_set_form_vars (cognitive 40) REDACTED:909 — MiqRequestMethods.prov_set_form_vars has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19 (34 pts), boolean chains 6 (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 · index.SettingsReplicationForm (cognitive 40) · ×1
  • index.SettingsReplicationForm (cognitive 40) app/javascript/components/settings-replication-form/index.jsx:15 — index.SettingsReplicationForm has cognitive complexity 40 (threshold 15). Drivers by points: if/else 18 (23 pts), ternaries 5 (10 pts), boolean chains 7 (nesting depth added 10). Most of this is not in the body itself: 5 of the 40 points are its own statements and the rest belongs to 13 function items inside it that branch (handleConfirmCallback, a function literal at line 70, a function literal at line 114, …). 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 · PxeController.replace_right_cell (cognitive 39) · ×1
  • PxeController.replace_right_cell (cognitive 39) app/controllers/pxe_controller.rb:141 — PxeController.replace_right_cell has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (24 pts), match/switch 4 (8 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Dashboards.db_edit (cognitive 39) · ×1
  • Dashboards.db_edit (cognitive 39) REDACTED:116 — Dashboards.db_edit has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 5 (14 pts), boolean chains 4, match/switch 1 (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · CatalogController.atomic_form_field_changed (cognitive 38) · ×1
  • CatalogController.atomic_form_field_changed (cognitive 38) REDACTED:235 — CatalogController.atomic_form_field_changed has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (30 pts), boolean chains 7, 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 · OpsController.settings_replace_right_cell (cognitive 38) · ×1
  • OpsController.settings_replace_right_cell (cognitive 38) REDACTED:544 — OpsController.settings_replace_right_cell has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 4 (12 pts), boolean chains 2, match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · miqAtomToRule (cognitive 38) · ×1
  • miqAtomToRule (cognitive 38) app/javascript/components/expression-editor/expression-adapter.js:20 — miqAtomToRule has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 12, ternaries 7 (12 pts), other 8, if/else 6 (nesting depth added 5). 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, split the body into named stages: move each independent 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 · MiqRequestMethods.prov_field_changed (cognitive 37) · ×1
  • MiqRequestMethods.prov_field_changed (cognitive 37) REDACTED:9 — MiqRequestMethods.prov_field_changed has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 6, error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqActionController.action_field_changed (cognitive 37) · ×1
  • MiqActionController.action_field_changed (cognitive 37) REDACTED:57 — MiqActionController.action_field_changed has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 4, ternaries 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 · Common.settings_update_save (cognitive 37) · ×1
  • Common.settings_update_save (cognitive 37) app/controllers/ops_controller/settings/common.rb:302 — Common.settings_update_save has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (34 pts), boolean chains 2, match/switch 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 · Schedules.build_search_filter_from_params (cognitive 37) · ×1
  • Schedules.build_search_filter_from_params (cognitive 37) REDACTED:520 — Schedules.build_search_filter_from_params has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (24 pts), match/switch 7 (13 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Schedules.schedule_edit (cognitive 37) · ×1
  • Schedules.schedule_edit (cognitive 37) REDACTED:191 — Schedules.schedule_edit has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 5, ternaries 2 (4 pts), match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · StorageController.button (cognitive 37) · ×1
  • StorageController.button (cognitive 37) REDACTED:73 — StorageController.button has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · summary-tab.SummaryTab (cognitive 37) · ×1
  • summary-tab.SummaryTab (cognitive 37) app/javascript/components/report-editor/tabs/summary-tab.tsx:112 — summary-tab.SummaryTab has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 30, ternaries 5, if/else 2. Of this number, 31 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · index.SortableList (cognitive 37) · ×1
  • index.SortableList (cognitive 37) app/javascript/components/sortable-list/index.jsx:22 — index.SortableList has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 22, if/else 9 (10 pts), ternaries 4 (5 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 164, handleDragStart, getLabel, …). 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 · customer-tags-tab.CustomerTagsTab (cognitive 36) · ×1
  • customer-tags-tab.CustomerTagsTab (cognitive 36) app/javascript/components/group-form/customer-tags-tab.jsx:28 — customer-tags-tab.CustomerTagsTab has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 12 (20 pts), boolean chains 8, if/else 7 (8 pts) (nesting depth added 9). Of this number, 16 points are the body's own statements and 20 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 · report-form-values.buildInitialValues (cognitive 36) · ×1
  • report-form-values.buildInitialValues (cognitive 36) app/javascript/components/report-editor/report-form-values.ts:73 — report-form-values.buildInitialValues has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 35, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · PolicySupport.protect (cognitive 35) · ×1
  • PolicySupport.protect (cognitive 35) REDACTED:5 — PolicySupport.protect has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (34 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · namespace-tree-modal.NamespaceTreeModal (cognitive 35) · ×1
  • namespace-tree-modal.NamespaceTreeModal (cognitive 35) app/javascript/components/miq-ae-class/namespace-tree-modal.jsx:42 — namespace-tree-modal.NamespaceTreeModal has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 14, ternaries 8 (14 pts), if/else 6 (7 pts) (nesting depth added 7). Most of this is not in the body itself: 4 of the 35 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 194, a function literal at line 182, onLoadData, …). 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 · review-import-form.ReviewImportForm (cognitive 35) · ×1
  • review-import-form.ReviewImportForm (cognitive 35) app/javascript/components/automate-import-export-form/review-import-form.jsx:10 — review-import-form.ReviewImportForm has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 16, ternaries 6 (11 pts), if/else 7 (8 pts) (nesting depth added 6). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 27, getNamespacesForDomain, handleSubmit, …). 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 · index.ExpressionEditor (cognitive 35) · ×1
  • index.ExpressionEditor (cognitive 35) app/javascript/components/expression-editor/index.jsx:36 — index.ExpressionEditor has cognitive complexity 35 (threshold 15). Drivers by points: if/else 22 (23 pts), boolean chains 9, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 4 of the 35 points are its own statements and the rest belongs to 18 function literals inside it that branch (lines 154, 182, 46, …). 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 · index.SettingsCUCollectionTab (cognitive 35) · ×1
  • index.SettingsCUCollectionTab (cognitive 35) app/javascript/components/settings-cu-collection/index.jsx:13 — index.SettingsCUCollectionTab has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 9, ternaries 3, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to 10 function items inside it that branch (transformTree, a function literal at line 122, handleSubmit, …). 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 · Filter.exp_commit_find (cognitive 34) · ×1
  • Filter.exp_commit_find (cognitive 34) REDACTED:630 — Filter.exp_commit_find has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 6, ternaries 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.ButtonGroupForm (cognitive 34) · ×1
  • index.ButtonGroupForm (cognitive 34) app/javascript/components/button-group/index.jsx:13 — index.ButtonGroupForm has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 9 (10 pts), boolean chains 8 (nesting depth added 3). Most of this is not in the body itself: 7 of the 34 points are its own statements and the rest belongs to 8 function items inside it that branch (onCancel, a function literal at line 37, a function literal at line 47, …). 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 · tag-selection.TagSelection (cognitive 34) · ×1
  • tag-selection.TagSelection (cognitive 34) app/javascript/components/chargeback-assignments-form/tag-selection.jsx:16 — tag-selection.TagSelection has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 22, if/else 9, error handling 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 65, a function literal at line 99, a function literal at line 33, …). 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 · find-value-editor.FindValueEditor (cognitive 34) · ×1
  • find-value-editor.FindValueEditor (cognitive 34) app/javascript/components/expression-editor/find-value-editor.jsx:115 — find-value-editor.FindValueEditor has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 25, ternaries 5, if/else 4. Of this number, 28 points are the body's own statements and 6 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 · index.MiqDataTable (cognitive 34) · ×1
  • index.MiqDataTable (cognitive 34) app/javascript/components/miq-data-table/index.jsx:19 — index.MiqDataTable has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 11, ternaries 7 (9 pts) (nesting depth added 7). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 8 function items inside it that branch (classNameRow, headerSortDirection, a function literal at line 169, …). 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 · PolicyMixin.validate_snmp_options (cognitive 33) · ×1
  • PolicyMixin.validate_snmp_options (cognitive 33) REDACTED:91 — PolicyMixin.validate_snmp_options has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 20, if/else 11 (13 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · remove-generic-item-modal.removeItems (cognitive 33) · ×1
  • remove-generic-item-modal.removeItems (cognitive 33) app/javascript/components/remove-generic-item-modal.jsx:37 — remove-generic-item-modal.removeItems has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 4 (9 pts), boolean chains 5 (nesting depth added 12). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 87, 66, 72, …). 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 · Explorer.x_button (cognitive 32) · ×1
  • Explorer.x_button (cognitive 32) app/controllers/application_controller/explorer.rb:71 — Explorer.x_button has cognitive complexity 32 (threshold 15). Drivers by points: if/else 20 (26 pts), match/switch 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CatalogController.st_edit (cognitive 32) · ×1
  • CatalogController.st_edit (cognitive 32) REDACTED:437 — CatalogController.st_edit has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (27 pts), ternaries 2 (3 pts), boolean chains 1, match/switch 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 · LabelTagMapping.label_tag_mapping_edit (cognitive 32) · ×1
  • LabelTagMapping.label_tag_mapping_edit (cognitive 32) REDACTED:53 — LabelTagMapping.label_tag_mapping_edit has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 4, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · index.ReconfigureVmForm (cognitive 32) · ×1
  • index.ReconfigureVmForm (cognitive 32) app/javascript/components/reconfigure-vm-form/index.jsx:24 — index.ReconfigureVmForm has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 6, ternaries 4 (nesting depth added 5). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 10 function items inside it that branch (setRenderForm, setButtonClick, onSubmit, …). 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 · createClassFieldsSchema · ×1
  • createClassFieldsSchema::getInitialValue (cognitive 32) app/javascript/components/data-tables/datastore/schema/modal-form.schema.js:43 — createClassFieldsSchema::getInitialValue has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 9, ternaries 1 (5 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 · DialogRunner.dialog_form_button_pressed (cognitive 31) · ×1
  • DialogRunner.dialog_form_button_pressed (cognitive 31) app/controllers/application_controller/dialog_runner.rb:29 — DialogRunner.dialog_form_button_pressed has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (28 pts), error handling 1 (2 pts), match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Reconfigure.build_reconfigure_hash (cognitive 31) · ×1
  • Reconfigure.build_reconfigure_hash (cognitive 31) app/controllers/mixins/actions/vm_actions/reconfigure.rb:109 — Reconfigure.build_reconfigure_hash has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 5 (10 pts), boolean chains 4 (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 · AutomateTreeHelper.at_tree_select_toggle (cognitive 31) · ×1
  • AutomateTreeHelper.at_tree_select_toggle (cognitive 31) app/helpers/automate_tree_helper.rb:67 — AutomateTreeHelper.at_tree_select_toggle has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 7, match/switch 2 (3 pts), ternaries 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 · index.DashboardWidget (cognitive 31) · ×1
  • index.DashboardWidget (cognitive 31) app/javascript/components/dashboard-widgets/dashboard-charts/index.jsx:9 — index.DashboardWidget has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 7 (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 · ruleToMiqAtom (cognitive 31) · ×1
  • ruleToMiqAtom (cognitive 31) app/javascript/components/expression-editor/expression-adapter.js:161 — ruleToMiqAtom has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (11 pts), ternaries 3 (5 pts), other 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.
D2 · Cognitive Complexity · Buttons.buttons_get_node_info (cognitive 30) · ×1
  • Buttons.buttons_get_node_info (cognitive 30) REDACTED:470 — Buttons.buttons_get_node_info has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · MiqRequestMethods.prov_set_show_vars (cognitive 30) · ×1
  • MiqRequestMethods.prov_set_show_vars (cognitive 30) REDACTED:853 — MiqRequestMethods.prov_set_show_vars has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 14). 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 · MiqAeClassController.replace_right_cell (cognitive 30) · ×1
  • MiqAeClassController.replace_right_cell (cognitive 30) REDACTED:278 — MiqAeClassController.replace_right_cell has cognitive complexity 30 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 10 (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 · MiqAeCustomizationController.upload_import_file (cognitive 30) · ×1
  • MiqAeCustomizationController.upload_import_file (cognitive 30) REDACTED:38 — MiqAeCustomizationController.upload_import_file has cognitive complexity 30 (threshold 15). Drivers by points: error handling 6 (27 pts), if/else 2, boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · date-value-editor.DateValueEditor (cognitive 30) · ×1
  • date-value-editor.DateValueEditor (cognitive 30) app/javascript/components/expression-editor/date-value-editor.jsx:178 — date-value-editor.DateValueEditor has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 8, boolean chains 5 (nesting depth added 3). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 208, handleToggle, a function literal at line 214, …). 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 · expression-validator.validateRule (cognitive 30) · ×1
  • expression-validator.validateRule (cognitive 30) app/javascript/components/expression-editor/expression-validator.js:82 — expression-validator.validateRule has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · main-menu.MainMenu (cognitive 30) · ×1
  • main-menu.MainMenu (cognitive 30) app/javascript/menu/main-menu.tsx:27 — main-menu.MainMenu has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 12, ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 10 function items inside it that branch (onSelect, a function literal at line 135, toggleMenu, …). 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 · (anonymous).link (cognitive 30) · ×1
  • (anonymous).link (cognitive 30) app/javascript/oldjs/directives/checkchange.js:4 — (anonymous).link has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 11, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (viewModelDateComparison, a function literal at line 22, viewModelComparison, …). 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 · Performance.perf_util_daily_gen_data (cognitive 29) · ×1
  • Performance.perf_util_daily_gen_data (cognitive 29) REDACTED:983 — Performance.perf_util_daily_gen_data has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 5, ternaries 2 (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 · MiqActionController.action_valid_record? (cognitive 29) · ×1
  • MiqActionController.action_valid_record? (cognitive 29) REDACTED:333 — MiqActionController.action_valid_record? has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 9 (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 · index.MiqCustomTab (cognitive 29) · ×1
  • index.MiqCustomTab (cognitive 29) app/javascript/components/miq-custom-tab/index.jsx:8 — index.MiqCustomTab has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 5). None of this is in the body itself: all 29 points belong to 10 function items inside it that branch (staticContents, a function literal at line 94, onTabSelect, …). 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 · index.ReportEditor (cognitive 29) · ×1
  • index.ReportEditor (cognitive 29) app/javascript/components/report-editor/index.tsx:61 — index.ReportEditor has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 15, if/else 8, ternaries 6. Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 90, a function literal at line 145, a function literal at line 83, …). 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 · ApplicationController.get_view_process_search_text (cognitive 28) · ×1
  • ApplicationController.get_view_process_search_text (cognitive 28) REDACTED:971 — ApplicationController.get_view_process_search_text has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 6, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqRequestMethods.prov_edit (cognitive 28) · ×1
  • MiqRequestMethods.prov_edit (cognitive 28) REDACTED:219 — MiqRequestMethods.prov_edit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 4 (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 · Performance.perf_chart_chooser (cognitive 28) · ×1
  • Performance.perf_chart_chooser (cognitive 28) REDACTED:9 — Performance.perf_chart_chooser has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Common.settings_form_field_changed (cognitive 28) · ×1
  • Common.settings_form_field_changed (cognitive 28) app/controllers/ops_controller/settings/common.rb:13 — Common.settings_form_field_changed has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 3, match/switch 2 (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 · OrchestrationStackController.button (cognitive 28) · ×1
  • OrchestrationStackController.button (cognitive 28) app/controllers/orchestration_stack_controller.rb:59 — OrchestrationStackController.button has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · expression-editor-field.ExpressionEditorInner (cognitive 28) · ×1
  • expression-editor-field.ExpressionEditorInner (cognitive 28) app/javascript/components/condition-form/expression-editor-field.jsx:10 — expression-editor-field.ExpressionEditorInner has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 11, ternaries 5 (nesting depth added 3). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 5 function items inside it that branch (handleQueryChange, a function literal at line 66, updatePreviewText, …). 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 · field-picker.FieldPicker (cognitive 28) · ×1
  • field-picker.FieldPicker (cognitive 28) app/javascript/components/report-editor/field-picker.tsx:17 — field-picker.FieldPicker has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, if/else 9, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 75, a function literal at line 54, a function literal at line 38, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · MiqAeClassController.instance_form_data (cognitive 27) · ×1
  • MiqAeClassController.instance_form_data (cognitive 27) REDACTED:1222 — MiqAeClassController.instance_form_data has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 19, error handling 2 (3 pts), if/else 3, ternaries 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · checkbox_tree.CheckboxTreeComponent (cognitive 27) · ×1
  • checkbox_tree.CheckboxTreeComponent (cognitive 27) app/javascript/components/tree-view/checkbox_tree.jsx:8 — checkbox_tree.CheckboxTreeComponent has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 16, ternaries 4 (6 pts), if/else 5 (nesting depth added 2). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 27, 32, 49, …). 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 · import-datastore-via-git-modal.ImportDatastoreViaGitModal (cognitive 27) · ×1
  • import-datastore-via-git-modal.ImportDatastoreViaGitModal (cognitive 27) app/javascript/components/automate-import-export-form/import-datastore-via-git-modal.jsx:9 — import-datastore-via-git-modal.ImportDatastoreViaGitModal has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 16, if/else 10, ternaries 1. Most of this is not in the body itself: 6 of the 27 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 47, a function literal at line 91, a function literal at line 40, …). 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 · miq-toolbar.onClick (cognitive 27) · ×1
  • miq-toolbar.onClick (cognitive 27) app/javascript/components/miq-toolbar.jsx:37 — miq-toolbar.onClick has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 3 (nesting depth added 11). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent 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 · OldDialogs.old_dialogs_update_create (cognitive 26) · ×1
  • OldDialogs.old_dialogs_update_create (cognitive 26) REDACTED:281 — OldDialogs.old_dialogs_update_create has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), error handling 2 (5 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Widgets.widget_get_node_info (cognitive 26) · ×1
  • Widgets.widget_get_node_info (cognitive 26) REDACTED:262 — Widgets.widget_get_node_info has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.AbForm (cognitive 26) · ×1
  • index.AbForm (cognitive 26) app/javascript/components/ab-form/index.jsx:13 — index.AbForm has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 15, ternaries 5 (6 pts), if/else 4 (5 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 80, a function literal at line 43, onSubmit, …). 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 · workflow-entry-points.WorkflowEntryPoints · ×1
  • workflow-entry-points.WorkflowEntryPoints::onSort (cognitive 26) app/javascript/components/workflows/workflow-entry-points.jsx:52 — workflow-entry-points.WorkflowEntryPoints::onSort has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 2 (8 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 · buildSubmitData (cognitive 26) · ×1
  • buildSubmitData (cognitive 26) app/javascript/components/ab-form/helper.js:100 — buildSubmitData has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 9, ternaries 3, other 1 (nesting depth added 2). Of this number, 21 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ApplicationController.prov_redirect (cognitive 25) · ×1
  • ApplicationController.prov_redirect (cognitive 25) REDACTED:1401 — ApplicationController.prov_redirect has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2 (4 pts), match/switch 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 · DialogRunner.dialog_get_form_vars (cognitive 25) · ×1
  • DialogRunner.dialog_get_form_vars (cognitive 25) app/controllers/application_controller/dialog_runner.rb:177 — DialogRunner.dialog_get_form_vars has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Filter.exp_button (cognitive 25) · ×1
  • Filter.exp_button (cognitive 25) REDACTED:16 — Filter.exp_button has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 1 (2 pts), match/switch 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 · GenericButtonMixin.button (cognitive 25) · ×1
  • GenericButtonMixin.button (cognitive 25) app/controllers/mixins/generic_button_mixin.rb:47 — GenericButtonMixin.button has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 7 (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 · Common.settings_get_info (cognitive 25) · ×1
  • Common.settings_get_info (cognitive 25) app/controllers/ops_controller/settings/common.rb:739 — Common.settings_get_info has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 4 (8 pts) (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Schedules.schedule_edit (cognitive 25) · ×1
  • Schedules.schedule_edit (cognitive 25) REDACTED:60 — Schedules.schedule_edit has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ToolbarChooser.center_toolbar_filename_ops (cognitive 25) · ×1
  • ToolbarChooser.center_toolbar_filename_ops (cognitive 25) app/helpers/application_helper/toolbar_chooser.rb:206 — ToolbarChooser.center_toolbar_filename_ops has cognitive complexity 25 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · CatalogHelper.catalog_basic_information (cognitive 25) · ×1
  • CatalogHelper.catalog_basic_information (cognitive 25) app/helpers/catalog_helper.rb:98 — CatalogHelper.catalog_basic_information has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 5, ternaries 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · index.AnsibleRepositoryForm (cognitive 25) · ×1
  • index.AnsibleRepositoryForm (cognitive 25) app/javascript/components/ansible-repository-form/index.jsx:9 — index.AnsibleRepositoryForm has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (onSubmit, a function literal at line 16, a function literal at line 21, …). 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 · index.AutomateEntryPoints (cognitive 25) · ×1
  • index.AutomateEntryPoints (cognitive 25) app/javascript/components/automate-entry-points/index.jsx:23 — index.AutomateEntryPoints has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 9, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 91, onLoadData, wrappedOnLoadData, …). 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 · index.EmbeddedTerraformRepositoryForm (cognitive 25) · ×1
  • index.EmbeddedTerraformRepositoryForm (cognitive 25) app/javascript/components/embedded-terraform-repository-form/index.jsx:9 — index.EmbeddedTerraformRepositoryForm has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (onSubmit, a function literal at line 16, a function literal at line 21, …). 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 · charts-tab.ChartsTab (cognitive 25) · ×1
  • charts-tab.ChartsTab (cognitive 25) app/javascript/components/report-editor/tabs/charts-tab.tsx:48 — charts-tab.ChartsTab has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, ternaries 9, if/else 5. Of this number, 16 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · index.RoutersForm (cognitive 25) · ×1
  • index.RoutersForm (cognitive 25) app/javascript/components/routers-form/index.jsx:9 — index.RoutersForm has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 4, boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 8 function items inside it that branch (getSubmitData, formatInitialData, a function literal at line 68, …). 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 · index.UserForm (cognitive 25) · ×1
  • index.UserForm (cognitive 25) app/javascript/components/user-form/index.jsx:10 — index.UserForm has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 3 (nesting depth added 9). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 51, onSubmit, a function literal at line 21, …). 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 · index.WorkflowRepositoryForm (cognitive 25) · ×1
  • index.WorkflowRepositoryForm (cognitive 25) app/javascript/components/workflow-repository-form/index.jsx:9 — index.WorkflowRepositoryForm has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (onSubmit, a function literal at line 16, a function literal at line 21, …). 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 · aeMethodFormController (cognitive 25) · ×1
  • aeMethodFormController (cognitive 25) app/javascript/angular/miq_ae_class/ae_method_form_controller.js:4 — aeMethodFormController has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14, boolean chains 7, error handling 2, ternaries 2. None of this is in the body itself: all 25 points belong to 31 function items inside it that branch (getConfigInfo, setConfigInfo, a function literal at line 287, …). 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 · MiqRequestMethods.pre_prov (cognitive 24) · ×1
  • MiqRequestMethods.pre_prov (cognitive 24) REDACTED:88 — MiqRequestMethods.pre_prov has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (21 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Widgets.widget_edit (cognitive 24) · ×1
  • Widgets.widget_edit (cognitive 24) REDACTED:54 — Widgets.widget_edit has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 3 (6 pts), boolean chains 4, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · UtilizationController.get_node_info (cognitive 24) · ×1
  • UtilizationController.get_node_info (cognitive 24) REDACTED:129 — UtilizationController.get_node_info has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 8, ternaries 3 (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 · VmCommon.set_right_cell_vars (cognitive 24) · ×1
  • VmCommon.set_right_cell_vars (cognitive 24) REDACTED:1203 — VmCommon.set_right_cell_vars has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 3 (8 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · createSchema (cognitive 24) · ×1
  • createSchema (cognitive 24) app/javascript/components/settings-replication-form/settings-replication-form.schema.js:6 — createSchema has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 7, error handling 1, match/switch 1 (nesting depth added 1). None of this is in the body itself: all 24 points belong to 17 function items inside it that branch (a function literal at line 114, a function literal at line 81, deleteSubscription, …). 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 · ApplicationController.view_to_hash (cognitive 23) · ×1
  • ApplicationController.view_to_hash (cognitive 23) REDACTED:642 — ApplicationController.view_to_hash has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 6, error handling 1 (2 pts), 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 · Compare.build_download_rpt (cognitive 23) · ×1
  • Compare.build_download_rpt (cognitive 23) REDACTED:231 — Compare.build_download_rpt has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Filter.exp_remove (cognitive 23) · ×1
  • Filter.exp_remove (cognitive 23) REDACTED:702 — Filter.exp_remove has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · PolicyMixin.build_snmp_options (cognitive 23) · ×1
  • PolicyMixin.build_snmp_options (cognitive 23) REDACTED:124 — PolicyMixin.build_snmp_options has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pf_aggregate_status_card.PfAggregateStatusCard (cognitive 23) · ×1
  • pf_aggregate_status_card.PfAggregateStatusCard (cognitive 23) app/javascript/components/pf_aggregate_status_card.jsx:4 — pf_aggregate_status_card.PfAggregateStatusCard has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 18, ternaries 5. Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (renderMiniLayout, renderNormalLayout, displayNotification, …). 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 · redux.TreeView (cognitive 23) · ×1
  • redux.TreeView (cognitive 23) REDACTED:126 — redux.TreeView has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 7 (nesting depth added 4). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 184, 249, 258, …). 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 · helper.menuItemOnClick (cognitive 23) · ×1
  • helper.menuItemOnClick (cognitive 23) app/javascript/components/dashboard-widgets/widget-wrapper/helper.jsx:84 — helper.menuItemOnClick has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (23 pts) (nesting depth added 9). Of this number, 13 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.RetirementForm (cognitive 23) · ×1
  • index.RetirementForm (cognitive 23) app/javascript/components/retirement-form/index.jsx:13 — index.RetirementForm has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 4 function items inside it that branch (onSubmit, a function literal at line 91, a function literal at line 89, …). 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 · helper.createRows (cognitive 23) · ×1
  • helper.createRows (cognitive 23) app/javascript/components/tenant-quota-form/helper.js:4 — helper.createRows has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 6). None of this is in the body itself: all 23 points belong to 5 function items inside it that branch (isDisabled, validate, isChanged, …). 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 · workers-form.WorkersForm (cognitive 23) · ×1
  • workers-form.WorkersForm (cognitive 23) app/javascript/components/workers-form/workers-form.jsx:12 — workers-form.WorkersForm has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 21, if/else 1, ternaries 1. Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 21, onSubmit::isDifferent). 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 · MiqRequestMethods.prov_req_submit (cognitive 22) · ×1
  • MiqRequestMethods.prov_req_submit (cognitive 22) REDACTED:670 — MiqRequestMethods.prov_req_submit has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, match/switch 1 (2 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 · CatalogController.atomic_st_edit (cognitive 22) · ×1
  • CatalogController.atomic_st_edit (cognitive 22) REDACTED:176 — CatalogController.atomic_st_edit has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EmsConfigurationController.button (cognitive 22) · ×1
  • EmsConfigurationController.button (cognitive 22) app/controllers/ems_configuration_controller.rb:27 — EmsConfigurationController.button has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4, match/switch 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 · OldDialogs.provision_dialogs_update_create (cognitive 22) · ×1
  • OldDialogs.provision_dialogs_update_create (cognitive 22) REDACTED:224 — OldDialogs.provision_dialogs_update_create has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (5 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Policies.policy_field_changed (cognitive 22) · ×1
  • Policies.policy_field_changed (cognitive 22) REDACTED:126 — Policies.policy_field_changed has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 1 (3 pts), match/switch 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 · OpsRbac.rbac_user_delete (cognitive 22) · ×1
  • OpsRbac.rbac_user_delete (cognitive 22) REDACTED:187 — OpsRbac.rbac_user_delete has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SavedReports.show_saved_report (cognitive 22) · ×1
  • SavedReports.show_saved_report (cognitive 22) app/controllers/report_controller/saved_reports.rb:37 — SavedReports.show_saved_report has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ToolbarChooser.center_toolbar_filename_automate_customization (cognitive 22) · ×1
  • ToolbarChooser.center_toolbar_filename_automate_customization (cognitive 22) app/helpers/application_helper/toolbar_chooser.rb:140 — ToolbarChooser.center_toolbar_filename_automate_customization has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6, 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 · ToolbarChooser.center_toolbar_filename_report (cognitive 22) · ×1
  • ToolbarChooser.center_toolbar_filename_report (cognitive 22) app/helpers/application_helper/toolbar_chooser.rb:252 — ToolbarChooser.center_toolbar_filename_report has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) (cognitive 22) · ×1
  • (anonymous) (cognitive 22) app/javascript/oldjs/controllers/dialog_editor/dialog_editor_controller.js:1 — (anonymous) has cognitive complexity 22 (threshold 15). Drivers by points: if/else 18 (19 pts), ternaries 2, boolean chains 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 27 function items inside it that branch (init, customizer, saveDialogDetails, …). 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 · OrcherstrationTemplateForm (cognitive 22) · ×1
  • OrcherstrationTemplateForm (cognitive 22) app/javascript/components/orchestration-template/orcherstration-template-form.js:39 — OrcherstrationTemplateForm has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 9, boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 48, onSubmit, onCancel, …). 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 · ApplicationController.render_or_redirect_partial (cognitive 21) · ×1
  • ApplicationController.render_or_redirect_partial (cognitive 21) REDACTED:1246 — ApplicationController.render_or_redirect_partial has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 6 (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 · ChargebackReportController.fetch_saved_report (cognitive 21) · ×1
  • ChargebackReportController.fetch_saved_report (cognitive 21) app/controllers/chargeback_report_controller.rb:43 — ChargebackReportController.fetch_saved_report has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EmsInfraController.register_nodes (cognitive 21) · ×1
  • EmsInfraController.register_nodes (cognitive 21) REDACTED:139 — EmsInfraController.register_nodes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 3 (8 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OldDialogs.old_dialogs_button_operation (cognitive 21) · ×1
  • OldDialogs.old_dialogs_button_operation (cognitive 21) REDACTED:27 — OldDialogs.old_dialogs_button_operation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GenericShowMixin.show (cognitive 21) · ×1
  • GenericShowMixin.show (cognitive 21) app/controllers/mixins/generic_show_mixin.rb:3 — GenericShowMixin.show has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2, match/switch 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 · OpsController.change_tab (cognitive 21) · ×1
  • OpsController.change_tab (cognitive 21) REDACTED:229 — OpsController.change_tab has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (5 pts), boolean chains 4, 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 · Schedules.schedule_set_form_vars (cognitive 21) · ×1
  • Schedules.schedule_set_form_vars (cognitive 21) REDACTED:296 — Schedules.schedule_set_form_vars has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, ternaries 5 (6 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Widgets.widget_set_record_vars (cognitive 21) · ×1
  • Widgets.widget_set_record_vars (cognitive 21) REDACTED:549 — Widgets.widget_set_record_vars has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4 (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 · VmCommon.button (cognitive 21) · ×1
  • VmCommon.button (cognitive 21) REDACTED:29 — VmCommon.button has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Navbar.item_active? (cognitive 21) · ×1
  • Navbar.item_active? (cognitive 21) app/helpers/application_helper/navbar.rb:27 — Navbar.item_active? has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 6 (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 · ToolbarChooser.center_toolbar_filename_services (cognitive 21) · ×1
  • ToolbarChooser.center_toolbar_filename_services (cognitive 21) app/helpers/application_helper/toolbar_chooser.rb:167 — ToolbarChooser.center_toolbar_filename_services has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Buttons.ab_group_reorder (cognitive 20) · ×1
  • Buttons.ab_group_reorder (cognitive 20) REDACTED:18 — Buttons.ab_group_reorder has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Filter.exp_add_joiner (cognitive 20) · ×1
  • Filter.exp_add_joiner (cognitive 20) REDACTED:465 — Filter.exp_add_joiner has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CatalogController.get_node_info_handle_leaf_node (cognitive 20) · ×1
  • CatalogController.get_node_info_handle_leaf_node (cognitive 20) REDACTED:1908 — CatalogController.get_node_info_handle_leaf_node has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqRequestController.stamp (cognitive 20) · ×1
  • MiqRequestController.stamp (cognitive 20) REDACTED:154 — MiqRequestController.stamp has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PolicyMixin.send_button_changes (cognitive 20) · ×1
  • PolicyMixin.send_button_changes (cognitive 20) REDACTED:3 — PolicyMixin.send_button_changes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ReportController.set_form_locals (cognitive 20) · ×1
  • ReportController.set_form_locals (cognitive 20) REDACTED:559 — ReportController.set_form_locals has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 3 (7 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Dashboards.db_get_node_info (cognitive 20) · ×1
  • Dashboards.db_get_node_info (cognitive 20) REDACTED:268 — Dashboards.db_get_node_info has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, ternaries 2 (4 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 · Widgets.widget_validate_entries (cognitive 20) · ×1
  • Widgets.widget_validate_entries (cognitive 20) REDACTED:589 — Widgets.widget_validate_entries has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RestfulRedirectController.index (cognitive 20) · ×1
  • RestfulRedirectController.index (cognitive 20) REDACTED:4 — RestfulRedirectController.index has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 1 (4 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · AutomateTreeHelper.build_automate_tree (cognitive 20) · ×1
  • AutomateTreeHelper.build_automate_tree (cognitive 20) app/helpers/automate_tree_helper.rb:19 — AutomateTreeHelper.build_automate_tree has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExplorerPresenter.for_render_default (cognitive 20) · ×1
  • ExplorerPresenter.for_render_default (cognitive 20) app/presenters/explorer_presenter.rb:236 — ExplorerPresenter.for_render_default has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (20 pts) (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.
D2 · Cognitive Complexity · GtlFormatter.format_cols (cognitive 20) · ×1
  • GtlFormatter.format_cols (cognitive 20) lib/gtl_formatter.rb:67 — GtlFormatter.format_cols has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · request-workflow-status-item.RequestWorkflowStatusItem (cognitive 20) · ×1
  • request-workflow-status-item.RequestWorkflowStatusItem (cognitive 20) app/javascript/components/request-workflow-status/request-workflow-status-item.jsx:11 — request-workflow-status-item.RequestWorkflowStatusItem has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), ternaries 1 (3 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 35, a function literal at line 32, a function literal at line 69, …). 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 · index.HelpMenuTab (cognitive 20) · ×1
  • index.HelpMenuTab (cognitive 20) app/javascript/components/settings-help-menu-form/index.jsx:14 — index.HelpMenuTab has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 18, ternaries 2. Of this number, 13 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · user-form.schema.createSchema (cognitive 20) · ×1
  • user-form.schema.createSchema (cognitive 20) app/javascript/components/user-form/user-form.schema.js:4 — user-form.schema.createSchema has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (14 pts), if/else 3 (4 pts), boolean chains 2 (nesting depth added 10). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, 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 · MiqAeClassController.update_instance (cognitive 19) · ×1
  • MiqAeClassController.update_instance (cognitive 19) REDACTED:599 — MiqAeClassController.update_instance has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), ternaries 1 (2 pts), error handling 1 (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 · MiqAeClassController.method_form_fields (cognitive 19) · ×1
  • MiqAeClassController.method_form_fields (cognitive 19) REDACTED:914 — MiqAeClassController.method_form_fields has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, if/else 4 (5 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 · MiqAeCustomizationController.handle_bottom_cell (cognitive 19) · ×1
  • MiqAeCustomizationController.handle_bottom_cell (cognitive 19) REDACTED:298 — MiqAeCustomizationController.handle_bottom_cell has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 2 (7 pts), boolean chains 3 (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 · MiqAlertController.alert_set_record_vars (cognitive 19) · ×1
  • MiqAlertController.alert_set_record_vars (cognitive 19) REDACTED:565 — MiqAlertController.alert_set_record_vars has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reconfigure.reconfigure_handle_submit_button (cognitive 19) · ×1
  • Reconfigure.reconfigure_handle_submit_button (cognitive 19) app/controllers/mixins/actions/vm_actions/reconfigure.rb:393 — Reconfigure.reconfigure_handle_submit_button has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 6, boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EmsCommon.deleteemss (cognitive 19) · ×1
  • EmsCommon.deleteemss (cognitive 19) REDACTED:534 — EmsCommon.deleteemss has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OpsRbac.rbac_edit_reset (cognitive 19) · ×1
  • OpsRbac.rbac_edit_reset (cognitive 19) REDACTED:587 — OpsRbac.rbac_edit_reset has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 3 (4 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Schedules.determine_filter_type_and_value (cognitive 19) · ×1
  • Schedules.determine_filter_type_and_value (cognitive 19) REDACTED:330 — Schedules.determine_filter_type_and_value has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 1 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ToolbarBuilder.twostate_button_selected (cognitive 19) · ×1
  • ToolbarBuilder.twostate_button_selected (cognitive 19) app/helpers/application_helper/toolbar_builder.rb:375 — ToolbarBuilder.twostate_button_selected has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 9. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ToolbarChooser.center_toolbar_filename_pxe (cognitive 19) · ×1
  • ToolbarChooser.center_toolbar_filename_pxe (cognitive 19) app/helpers/application_helper/toolbar_chooser.rb:289 — ToolbarChooser.center_toolbar_filename_pxe has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (19 pts) (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 · WidgetPresenter.widget_buttons (cognitive 19) · ×1
  • WidgetPresenter.widget_buttons (cognitive 19) app/presenters/widget_presenter.rb:23 — WidgetPresenter.widget_buttons has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.ContainerGroupConsole (cognitive 19) · ×1
  • index.ContainerGroupConsole (cognitive 19) app/javascript/components/container-group-console/index.jsx:8 — index.ContainerGroupConsole has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 5, ternaries 2. Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 111, closeConsole, a function literal at line 52, …). 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 · helper.getInitialValues (cognitive 19) · ×1
  • helper.getInitialValues (cognitive 19) app/javascript/components/generic-objects-form/custom-button-form/helper.js:29 — helper.getInitialValues has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 32, 50). 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 · index.GenericObjectForm (cognitive 19) · ×1
  • index.GenericObjectForm (cognitive 19) app/javascript/components/generic-objects-form/index.jsx:14 — index.GenericObjectForm has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 1 (3 pts), boolean chains 2, ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 71, a function literal at line 30, onCancel, …). 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 · gtl-view.GtlView · ×1
  • gtl-view.GtlView::onItemClick (cognitive 19) app/javascript/components/gtl-view.jsx:433 — gtl-view.GtlView::onItemClick has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7, ternaries 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 · standard-filter.StandardFilter (cognitive 19) · ×1
  • standard-filter.StandardFilter (cognitive 19) app/javascript/components/report-editor/tabs/filter/standard-filter.tsx:16 — standard-filter.StandardFilter has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (8 pts), if/else 3 (nesting depth added 2). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 31, 42, 52, …). 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 · preview-tab.PreviewTab (cognitive 19) · ×1
  • preview-tab.PreviewTab (cognitive 19) app/javascript/components/report-editor/tabs/preview-tab.tsx:40 — preview-tab.PreviewTab has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 6, ternaries 1. None of this is in the body itself: all 19 points belong to 9 function items inside it that branch (renderContent, a function literal at line 65, a function literal at line 77, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.SettingsTimeProfileForm (cognitive 19) · ×1
  • index.SettingsTimeProfileForm (cognitive 19) app/javascript/components/settings-time-profile-form/index.jsx:10 — index.SettingsTimeProfileForm has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 3 (nesting depth added 2). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (onSubmit, onCancel, a function literal at line 75, …). 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 · ApplicationController.drop_breadcrumb (cognitive 18) · ×1
  • ApplicationController.drop_breadcrumb (cognitive 18) REDACTED:757 — ApplicationController.drop_breadcrumb has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 7 (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 · Buttons.custom_buttons (cognitive 18) · ×1
  • Buttons.custom_buttons (cognitive 18) REDACTED:180 — Buttons.custom_buttons has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Filter.exp_commit_field (cognitive 18) · ×1
  • Filter.exp_commit_field (cognitive 18) REDACTED:551 — Filter.exp_commit_field has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CatalogController.fetch_playbook_details (cognitive 18) · ×1
  • CatalogController.fetch_playbook_details (cognitive 18) REDACTED:2178 — CatalogController.fetch_playbook_details has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InfraNetworkingController.replace_right_cell (cognitive 18) · ×1
  • InfraNetworkingController.replace_right_cell (cognitive 18) app/controllers/infra_networking_controller.rb:288 — InfraNetworkingController.replace_right_cell has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5 (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 · Common.settings_set_form_vars (cognitive 18) · ×1
  • Common.settings_set_form_vars (cognitive 18) app/controllers/ops_controller/settings/common.rb:694 — Common.settings_set_form_vars has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Reports.get_all_reps (cognitive 18) · ×1
  • Reports.get_all_reps (cognitive 18) REDACTED:61 — Reports.get_all_reps has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EditorMapping.report_validation_errors (cognitive 18) · ×1
  • EditorMapping.report_validation_errors (cognitive 18) app/controllers/report_controller/reports/editor_mapping.rb:376 — EditorMapping.report_validation_errors has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StorageController.load_or_clear_adv_search (cognitive 18) · ×1
  • StorageController.load_or_clear_adv_search (cognitive 18) REDACTED:214 — StorageController.load_or_clear_adv_search has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, 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 · MiqActionHelper.miq_summary_action_type (cognitive 18) · ×1
  • MiqActionHelper.miq_summary_action_type (cognitive 18) app/helpers/miq_action_helper.rb:22 — MiqActionHelper.miq_summary_action_type has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.ConditionForm (cognitive 18) · ×1
  • index.ConditionForm (cognitive 18) app/javascript/components/condition-form/index.jsx:27 — index.ConditionForm has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10, boolean chains 6, if/else 2. Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (onSubmit, a function literal at line 83, a function literal at line 91, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · field-config.buildFieldConfig (cognitive 18) · ×1
  • field-config.buildFieldConfig (cognitive 18) app/javascript/components/expression-editor/field-config.js:74 — field-config.buildFieldConfig has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 8, if/else 2. Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 82). 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 · index.SubnetForm (cognitive 18) · ×1
  • index.SubnetForm (cognitive 18) app/javascript/components/subnet-form/index.jsx:10 — index.SubnetForm has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 4, boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 48, a function literal at line 33, onCancel, …). 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 · ApplicationController.get_global_session_data (cognitive 17) · ×1
  • ApplicationController.get_global_session_data (cognitive 17) REDACTED:1489 — ApplicationController.get_global_session_data has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 5, boolean chains 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 · Buttons.group_set_form_vars (cognitive 17) · ×1
  • Buttons.group_set_form_vars (cognitive 17) REDACTED:386 — Buttons.group_set_form_vars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Compare.comparemiq (cognitive 17) · ×1
  • Compare.comparemiq (cognitive 17) REDACTED:679 — Compare.comparemiq has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Filter.exp_token_pressed (cognitive 17) · ×1
  • Filter.exp_token_pressed (cognitive 17) REDACTED:92 — Filter.exp_token_pressed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, error handling 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 · CatalogController.get_form_vars (cognitive 17) · ×1
  • CatalogController.get_form_vars (cognitive 17) REDACTED:1493 — CatalogController.get_form_vars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, ternaries 3 (5 pts), boolean chains 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 · MiqAlertController.show (cognitive 17) · ×1
  • MiqAlertController.show (cognitive 17) REDACTED:235 — MiqAlertController.show has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6, boolean chains 5, ternaries 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Dashboards.db_get_form_vars (cognitive 17) · ×1
  • Dashboards.db_get_form_vars (cognitive 17) REDACTED:326 — Dashboards.db_get_form_vars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SecurityGroupController.update (cognitive 17) · ×1
  • SecurityGroupController.update (cognitive 17) REDACTED:138 — SecurityGroupController.update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · VmCommon.tree_select (cognitive 17) · ×1
  • VmCommon.tree_select (cognitive 17) REDACTED:742 — VmCommon.tree_select has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 2 (3 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 · VmCommon.get_node_info (cognitive 17) · ×1
  • VmCommon.get_node_info (cognitive 17) REDACTED:909 — VmCommon.get_node_info has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TextualSummaryHelper.textual_collection_link (cognitive 17) · ×1
  • TextualSummaryHelper.textual_collection_link (cognitive 17) app/helpers/textual_summary_helper.rb:143 — TextualSummaryHelper.textual_collection_link has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · middleware.taggingMiddleware.<returned closure>.<returned closure> (cognitive 17) · ×1
  • middleware.taggingMiddleware.<returned closure>.<returned closure> (cognitive 17) app/javascript/miq-redux/middleware.js:33 — middleware.taggingMiddleware.<returned closure>.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · miq_tabs_init (cognitive 17) · ×1
  • miq_tabs_init (cognitive 17) REDACTED:804 — miq_tabs_init has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 805, 828, 812, …). 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 · createTreeReducer (cognitive 17) · ×1
  • createTreeReducer (cognitive 17) app/javascript/components/tree-view/reducers/index.js:63 — createTreeReducer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 7, ternaries 1. None of this is in the body itself: all 17 points belong to 19 function literals inside it that branch (lines 66, 71, 76, …). 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 · (anonymous) (cognitive 17) · ×1
  • (anonymous) (cognitive 17) app/javascript/oldjs/controllers/dialog_user/dialog_user_controller.js:1 — (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 17 points belong to 19 function items inside it that branch (a function literal at line 23, submitButtonClicked, a function literal at line 88, …). 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 · CiProcessing.process_show_list (cognitive 16) · ×1
  • CiProcessing.process_show_list (cognitive 16) REDACTED:182 — CiProcessing.process_show_list has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Performance.perf_gen_data_before_wait (cognitive 16) · ×1
  • Performance.perf_gen_data_before_wait (cognitive 16) REDACTED:630 — Performance.perf_gen_data_before_wait has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Performance.perf_gen_top_data_before_wait (cognitive 16) · ×1
  • Performance.perf_gen_top_data_before_wait (cognitive 16) REDACTED:864 — Performance.perf_gen_top_data_before_wait has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 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 · CloudTenantController.button (cognitive 16) · ×1
  • CloudTenantController.button (cognitive 16) app/controllers/cloud_tenant_controller.rb:16 — CloudTenantController.button has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Events.miq_event_edit (cognitive 16) · ×1
  • Events.miq_event_edit (cognitive 16) REDACTED:4 — Events.miq_event_edit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2, boolean chains 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MiqPolicyRsopController.rsop (cognitive 16) · ×1
  • MiqPolicyRsopController.rsop (cognitive 16) REDACTED:33 — MiqPolicyRsopController.rsop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 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 · ContainersCommonMixin.button (cognitive 16) · ×1
  • ContainersCommonMixin.button (cognitive 16) app/controllers/mixins/containers_common_mixin.rb:6 — ContainersCommonMixin.button has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 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, 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 · PolicyMixin.folder_get_info (cognitive 16) · ×1
  • PolicyMixin.folder_get_info (cognitive 16) REDACTED:324 — PolicyMixin.folder_get_info has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 1 (3 pts), boolean chains 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 · OpsController.rbac_replace_right_cell (cognitive 16) · ×1
  • OpsController.rbac_replace_right_cell (cognitive 16) REDACTED:613 — OpsController.rbac_replace_right_cell has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 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 · Upload.upload_csv (cognitive 16) · ×1
  • Upload.upload_csv (cognitive 16) app/controllers/ops_controller/settings/upload.rb:67 — Upload.upload_csv has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), match/switch 2 (5 pts), boolean chains 2, error handling 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 · EditorMapping.chargeback_validation_errors (cognitive 16) · ×1
  • EditorMapping.chargeback_validation_errors (cognitive 16) app/controllers/report_controller/reports/editor_mapping.rb:400 — EditorMapping.chargeback_validation_errors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.AeInlineMethod (cognitive 16) · ×1
  • index.AeInlineMethod (cognitive 16) app/javascript/components/AeInlineMethod/index.jsx:15 — index.AeInlineMethod has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 4, match/switch 1. Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (renderModalSelector, onItemSelect, onCellClickHandler, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.AnsiblePlayBookEditCatalogForm (cognitive 16) · ×1
  • index.AnsiblePlayBookEditCatalogForm (cognitive 16) app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:22 — index.AnsiblePlayBookEditCatalogForm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 5, boolean chains 3 (nesting depth added 2). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 67, onSubmit, a function literal at line 168, …). 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 · file-upload-section.FileUploadSection (cognitive 16) · ×1
  • file-upload-section.FileUploadSection (cognitive 16) app/javascript/components/automate-import-export-form/file-upload-section.jsx:6 — file-upload-section.FileUploadSection has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 2, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (handleUpload, handleFileChange, handleFileDelete). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · class-fields-editor.ClassFieldsEditor · ×1
  • class-fields-editor.ClassFieldsEditor::formatFieldValues (cognitive 16) app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx:76 — class-fields-editor.ClassFieldsEditor::formatFieldValues has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 14, if/else 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 · index.MiqAeClass (cognitive 16) · ×1
  • index.MiqAeClass (cognitive 16) app/javascript/components/miq-ae-class/index.jsx:10 — index.MiqAeClass has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 6 (7 pts), boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 54, onSubmit, a function literal at line 19, …). 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 · index.MiqAeCustomization (cognitive 16) · ×1
  • index.MiqAeCustomization (cognitive 16) app/javascript/components/miq-ae-customization/index.jsx:9 — index.MiqAeCustomization has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 6, if/else 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 17, onSubmit, a function literal at line 19, …). 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 · miq-table-cell.MiqTableCell · ×1
  • miq-table-cell.MiqTableCell::cellComponent (cognitive 16) app/javascript/components/miq-data-table/miq-table-cell.jsx:220 — miq-table-cell.MiqTableCell::cellComponent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.ProviderForm (cognitive 16) · ×1
  • index.ProviderForm (cognitive 16) app/javascript/components/provider-form/index.jsx:24 — index.ProviderForm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 4 (6 pts), boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (onSubmit, a function literal at line 86, a function literal at line 118, …). 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 · (anonymous) (cognitive 16) · ×1
  • (anonymous) (cognitive 16) app/javascript/oldjs/miq_ujs_bindings.js:5 — (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, ternaries 3. None of this is in the body itself: all 16 points belong to 17 function items inside it that branch (a function literal at line 11, a function literal at line 78, a function literal at line 120, …). 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (14 members, 50+ identical tokens) app/helpers/cloud_volume_helper/textual_summary.rb:71 — app/helpers/cloud_volume_helper/textual_summary.rb:71-81 | app/helpers/cloud_volume_helper/textual_summary.rb:85-95 | app/helpers/cloud_volume_helper/textual_summary.rb:99-105 | app/helpers/cloud_volume_snapshot_helper/textual_summary.rb:41-47 | app/helpers/host_helper/textual_summary.rb:275-281 | app/helpers/host_helper/textual_summary.rb:331-341 | app/helpers/service_helper/textual_summary.rb:154-160 | app/helpers/vm_helper/textual_summary.rb:227-234 | app/helpers/vm_helper/textual_summary.rb:238-245 | app/helpers/vm_helper/textual_summary.rb:249-255 | app/helpers/vm_helper/textual_summary.rb:290-298 | app/helpers/vm_helper/textual_summary.rb:302-308 | app/helpers/vm_helper/textual_summary.rb:312-318 | app/helpers/vm_helper/textual_summary.rb:440-446 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (10 members, 50+ identical tokens) app/helpers/auth_key_pair_cloud_helper/textual_summary.rb:27 — app/helpers/auth_key_pair_cloud_helper/textual_summary.rb:27-33 | app/helpers/availability_zone_helper/textual_summary.rb:22-28 | app/helpers/availability_zone_helper/textual_summary.rb:32-38 | app/helpers/cloud_network_helper/textual_summary.rb:43-49 | app/helpers/cloud_tenant_helper/textual_summary.rb:43-49 | app/helpers/cloud_tenant_helper/textual_summary.rb:53-59 | app/helpers/cloud_tenant_helper/textual_summary.rb:97-103 | app/helpers/security_group_helper/textual_summary.rb:68-74 | app/helpers/security_policy_rule_helper/textual_summary.rb:120-126 | app/helpers/security_policy_rule_helper/textual_summary.rb:134-140 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) app/helpers/cloud_subnet_helper/textual_summary.rb:71 — app/helpers/cloud_subnet_helper/textual_summary.rb:71-77 | app/helpers/flavor_helper/textual_summary.rb:76-82 | app/helpers/host_aggregate_helper/textual_summary.rb:17-23 | app/helpers/host_aggregate_helper/textual_summary.rb:27-33 | app/helpers/network_router_helper/textual_summary.rb:73-79 | app/helpers/orchestration_stack_helper/textual_summary.rb:91-97 | app/helpers/placement_group_helper/textual_summary.rb:30-36 | app/helpers/storage_helper/textual_summary.rb:98-104 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (7 members, 50+ identical tokens) app/helpers/ems_cluster_helper/textual_summary.rb:140 — app/helpers/ems_cluster_helper/textual_summary.rb:140-146 | app/helpers/ems_cluster_helper/textual_summary.rb:150-156 | app/helpers/ems_cluster_helper/textual_summary.rb:160-166 | app/helpers/ems_cluster_helper/textual_summary.rb:170-178 | app/helpers/resource_pool_helper/textual_summary.rb:107-113 | app/helpers/resource_pool_helper/textual_summary.rb:117-123 | app/helpers/resource_pool_helper/textual_summary.rb:127-133 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Edited copy of a member (50 corresponding lines) · ×1
  • Edited copy of a member (50 corresponding lines) REDACTED:547 — REDACTED:547-596 | REDACTED:600-651 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (66 corresponding lines) · ×1
  • Edited copy of a member (66 corresponding lines) app/controllers/ems_cluster_controller.rb:28 — app/controllers/ems_cluster_controller.rb:28-93 | REDACTED:74-144 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) REDACTED:969 — REDACTED:969-1009 | REDACTED:1122-1171 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) REDACTED:1163 — REDACTED:1163-1186 | REDACTED:1755-1779 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 28+ corresponding lines) app/controllers/miq_ae_customization_controller/dialogs.rb:78 — app/controllers/miq_ae_customization_controller/dialogs.rb:78-105 | REDACTED:7-37 | REDACTED:87-117 | REDACTED:30-59 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) REDACTED:39 — REDACTED:39-65 | REDACTED:41-66 | REDACTED:49-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) REDACTED:1698 — REDACTED:1698-1720 | REDACTED:1724-1746 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) app/helpers/configuration_script_helper.rb:37 — app/helpers/configuration_script_helper.rb:37-59 | app/helpers/configuration_script_helper.rb:139-158 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) REDACTED:429 — REDACTED:429-446 | REDACTED:562-579 | REDACTED:479-499 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 18+ corresponding lines) REDACTED:450 — REDACTED:450-467 | REDACTED:583-602 | REDACTED:397-416 | REDACTED:420-441 | REDACTED:503-525 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 18+ corresponding lines) app/controllers/report_controller/menus.rb:388 — app/controllers/report_controller/menus.rb:388-405 | app/controllers/report_controller/menus.rb:409-428 | app/controllers/report_controller/menus.rb:432-449 | app/controllers/report_controller/menus.rb:453-470 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 17+ corresponding lines) app/controllers/miq_ae_customization_controller/dialogs.rb:10 — app/controllers/miq_ae_customization_controller/dialogs.rb:10-29 | REDACTED:46-64 | app/controllers/pxe_controller/pxe_image_types.rb:39-55 | REDACTED:68-84 | app/controllers/storage_controller/storage_d.rb:6-22 | app/controllers/storage_controller/storage_pod.rb:6-23 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) app/services/container_service_mixin.rb:147 — app/services/container_service_mixin.rb:147-163 | app/services/container_service_mixin.rb:167-183 | app/services/container_service_mixin.rb:187-203 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 9+ corresponding lines) app/helpers/request_info_helper.rb:126 — app/helpers/request_info_helper.rb:126-134 | app/helpers/request_info_helper.rb:138-146 | app/helpers/request_info_helper.rb:150-159 | app/helpers/request_info_helper.rb:163-171 | app/helpers/request_info_helper.rb:175-186 | app/helpers/request_info_helper.rb:190-198 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) REDACTED:1068 — REDACTED:1068-1085 | REDACTED:1545-1560 | REDACTED:1676-1694 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) app/helpers/host_helper/textual_summary.rb:221 — app/helpers/host_helper/textual_summary.rb:221-229 | app/helpers/host_helper/textual_summary.rb:470-476 | app/helpers/textual_mixins/vm_common.rb:169-177 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) app/helpers/request_info_helper.rb:206 — app/helpers/request_info_helper.rb:206-216 | app/helpers/request_info_helper.rb:220-230 | app/helpers/request_info_helper.rb:234-244 | app/helpers/request_info_helper.rb:248-258 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) app/helpers/configuration_job_helper/textual_summary.rb:33 — app/helpers/configuration_job_helper/textual_summary.rb:33-42 | app/helpers/configuration_job_helper/textual_summary.rb:46-55 | app/helpers/orchestration_stack_helper/textual_summary.rb:51-60 | app/helpers/vm_helper/textual_summary.rb:348-357 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) app/helpers/ops_helper/textual_summary.rb:122 — app/helpers/ops_helper/textual_summary.rb:122-135 | app/helpers/ops_helper/textual_summary.rb:139-148 | app/helpers/ops_helper/textual_summary.rb:152-161 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 16+ corresponding lines) REDACTED:19 — REDACTED:19-35 | app/controllers/cloud_subnet_controller.rb:19-34 | REDACTED:22-37 | REDACTED:19-36 | REDACTED:30-45 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 7+ corresponding lines) app/helpers/cloud_object_store_container_helper/textual_summary.rb:41 — app/helpers/cloud_object_store_container_helper/textual_summary.rb:41-47 | app/helpers/cloud_tenant_helper/textual_summary.rb:75-82 | app/helpers/cloud_tenant_helper/textual_summary.rb:86-93 | app/helpers/cloud_volume_helper/textual_summary.rb:109-115 | app/helpers/cloud_volume_helper/textual_summary.rb:119-125 | app/helpers/cloud_volume_helper/textual_summary.rb:129-135 | app/helpers/cloud_volume_snapshot_helper/textual_summary.rb:19-25 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) app/helpers/miq_ae_class_helper.rb:456 — app/helpers/miq_ae_class_helper.rb:456-457 | app/helpers/shared_helper/ab_list_helper.rb:20-21 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 13+ corresponding lines) app/services/container_dashboard_service.rb:221 — app/services/container_dashboard_service.rb:221-235 | app/services/container_dashboard_service.rb:239-251 | app/services/container_service_mixin.rb:83-95 | app/services/container_service_mixin.rb:99-111 | app/services/container_service_mixin.rb:131-143 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 5+ corresponding lines) REDACTED:272 — REDACTED:272-277 | app/controllers/security_policy_controller.rb:35-39 | app/controllers/security_policy_rule_controller.rb:51-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) REDACTED:77 — REDACTED:77-83 | app/controllers/workflow_credential_controller.rb:67-72 | app/controllers/workflow_repository_controller.rb:73-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 3+ corresponding lines) app/helpers/container_summary_helper.rb:85 — app/helpers/container_summary_helper.rb:85-87 | app/helpers/ems_container_helper/textual_summary.rb:130-132 | app/helpers/host_helper/textual_summary.rb:480-483 | app/helpers/service_helper/textual_summary.rb:215-217 | app/helpers/textual_mixins/vm_common.rb:227-229 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) REDACTED:159 — REDACTED:159-184 | REDACTED:194-218 — 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) REDACTED:426 — REDACTED:426-448 | REDACTED:457-478 — 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) REDACTED:132 — REDACTED:132-154 | REDACTED:225-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (19–22 lines × 2) · ×1
  • Duplicated block (19–22 lines × 2) app/controllers/mixins/actions/vm_actions/evacuate.rb:51 — app/controllers/mixins/actions/vm_actions/evacuate.rb:51-69 | app/controllers/mixins/actions/vm_actions/live_migrate.rb:33-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) REDACTED:164 — REDACTED:164-180 | REDACTED:247-263 — 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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) REDACTED:141 — REDACTED:141-156 | REDACTED:224-239 | REDACTED:109-124 | REDACTED:202-217 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (12–16 lines × 2) · ×1
  • Duplicated block (12–16 lines × 2) REDACTED:70 — REDACTED:70-81 | REDACTED:216-231 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) app/controllers/infra_networking_controller.rb:508 — app/controllers/infra_networking_controller.rb:508-522 | REDACTED:446-458 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) REDACTED:1106 — REDACTED:1106-1118 | REDACTED:1134-1147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) app/controllers/infra_networking_controller.rb:210 — app/controllers/infra_networking_controller.rb:210-222 | app/controllers/infra_networking_controller.rb:226-238 | app/controllers/infra_networking_controller.rb:242-254 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) REDACTED:191 — REDACTED:191-215 | REDACTED:381-405 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • Duplicated block (8–12 lines × 2) REDACTED:69 — REDACTED:69-76 | REDACTED:149-160 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) REDACTED:539 — REDACTED:539-549 | REDACTED:558-568 | REDACTED:570-580 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:539` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) REDACTED:542 — REDACTED:542-551 | REDACTED:573-582 | REDACTED:587-596 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:542` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1
  • Duplicated block (8–9 lines × 5) REDACTED:634 — REDACTED:634-641 | REDACTED:644-651 | REDACTED:653-661 | REDACTED:668-675 | REDACTED:677-684 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:634` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:664` calls `_` and `REDACTED:633` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) REDACTED:79 — REDACTED:79-87 | REDACTED:109-117 | app/controllers/workflow_credential_controller.rb:81-89 | app/controllers/workflow_repository_controller.rb:124-132 — before extracting anything, compare `REDACTED` and `app/controllers/workflow_credential_controller.rb` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) app/controllers/ems_cluster_controller.rb:56 — app/controllers/ems_cluster_controller.rb:56-64 | REDACTED:110-117 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/controllers/ems_cluster_controller.rb:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) app/helpers/condition_helper.rb:12 — app/helpers/condition_helper.rb:12-26 | app/helpers/condition_helper.rb:30-44 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) REDACTED:70 — REDACTED:70-77 | REDACTED:150-161 | REDACTED:216-227 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (6 lines × 10) · ×1
  • Duplicated block (6 lines × 10) app/helpers/auth_key_pair_cloud_helper/textual_summary.rb:28 — app/helpers/auth_key_pair_cloud_helper/textual_summary.rb:28-33 | app/helpers/availability_zone_helper/textual_summary.rb:23-28 | app/helpers/availability_zone_helper/textual_summary.rb:33-38 | app/helpers/cloud_network_helper/textual_summary.rb:44-49 | app/helpers/cloud_tenant_helper/textual_summary.rb:44-49 | app/helpers/cloud_tenant_helper/textual_summary.rb:54-59 | app/helpers/cloud_tenant_helper/textual_summary.rb:98-103 | app/helpers/security_group_helper/textual_summary.rb:69-74 | app/helpers/security_policy_rule_helper/textual_summary.rb:121-126 | app/helpers/security_policy_rule_helper/textual_summary.rb:135-140 — there are 10 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 10 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (6 lines × 8) · ×1
  • Duplicated block (6 lines × 8) app/helpers/cloud_subnet_helper/textual_summary.rb:72 — app/helpers/cloud_subnet_helper/textual_summary.rb:72-77 | app/helpers/flavor_helper/textual_summary.rb:77-82 | app/helpers/host_aggregate_helper/textual_summary.rb:18-23 | app/helpers/host_aggregate_helper/textual_summary.rb:28-33 | app/helpers/network_router_helper/textual_summary.rb:74-79 | app/helpers/orchestration_stack_helper/textual_summary.rb:92-97 | app/helpers/placement_group_helper/textual_summary.rb:31-36 | app/helpers/storage_helper/textual_summary.rb:99-104 — there are 8 copies across 7 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) app/helpers/cloud_volume_helper/textual_summary.rb:140 — app/helpers/cloud_volume_helper/textual_summary.rb:140-145 | app/helpers/host_initiator_group_helper/textual_summary.rb:62-67 | app/helpers/host_initiator_helper/textual_summary.rb:56-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (5 lines × 14) · ×1
  • Duplicated block (5 lines × 14) app/helpers/cloud_volume_helper/textual_summary.rb:74 — app/helpers/cloud_volume_helper/textual_summary.rb:74-81 | app/helpers/cloud_volume_helper/textual_summary.rb:88-95 | app/helpers/cloud_volume_helper/textual_summary.rb:101-105 | app/helpers/cloud_volume_snapshot_helper/textual_summary.rb:43-47 | app/helpers/host_helper/textual_summary.rb:277-281 | app/helpers/host_helper/textual_summary.rb:335-341 | app/helpers/service_helper/textual_summary.rb:156-160 | app/helpers/vm_helper/textual_summary.rb:230-234 | app/helpers/vm_helper/textual_summary.rb:241-245 | app/helpers/vm_helper/textual_summary.rb:251-255 | app/helpers/vm_helper/textual_summary.rb:292-298 | app/helpers/vm_helper/textual_summary.rb:304-308 | app/helpers/vm_helper/textual_summary.rb:314-318 | app/helpers/vm_helper/textual_summary.rb:442-446 — there are 14 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 14 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/helpers/cloud_volume_helper/textual_summary.rb:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×1
  • Duplicated block (6 lines × 7) app/helpers/ems_cluster_helper/textual_summary.rb:141 — app/helpers/ems_cluster_helper/textual_summary.rb:141-146 | app/helpers/ems_cluster_helper/textual_summary.rb:151-156 | app/helpers/ems_cluster_helper/textual_summary.rb:161-166 | app/helpers/ems_cluster_helper/textual_summary.rb:173-178 | app/helpers/resource_pool_helper/textual_summary.rb:108-113 | app/helpers/resource_pool_helper/textual_summary.rb:118-123 | app/helpers/resource_pool_helper/textual_summary.rb:128-133 — there are 7 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (3–5 lines × 4) · ×1
  • Duplicated block (3–5 lines × 4) REDACTED:59 — REDACTED:59-62 | REDACTED:89-91 | REDACTED:258-263 | REDACTED:293-297 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:293` calls `exp_build_table` and `REDACTED:89` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–5 lines × 4) · ×1
  • Duplicated block (2–5 lines × 4) app/helpers/vm_helper/textual_summary.rb:558 — app/helpers/vm_helper/textual_summary.rb:558-559 | app/helpers/vm_helper/textual_summary.rb:568-572 | app/helpers/vm_helper/textual_summary.rb:577-579 | app/helpers/vm_helper/textual_summary.rb:588-592 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/helpers/vm_helper/textual_summary.rb:577` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) app/controllers/host_initiator_controller.rb:16 — app/controllers/host_initiator_controller.rb:16-74 | app/controllers/volume_mapping_controller.rb:16-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (8 lines × 9) · ×1
  • Duplicated block (8 lines × 9) app/controllers/cloud_tenant_controller.rb:159 — app/controllers/cloud_tenant_controller.rb:159-166 | REDACTED:124-131 | app/controllers/ems_cluster_controller.rb:149-156 | app/controllers/ems_container_controller.rb:61-68 | REDACTED:350-357 | app/controllers/ems_physical_infra_controller.rb:57-64 | app/controllers/flavor_controller.rb:65-72 | REDACTED:314-321 | REDACTED:418-425 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 9 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×1
  • Duplicated block (7 lines × 6) app/controllers/condition_controller.rb:75 — app/controllers/condition_controller.rb:75-81 | REDACTED:406-412 | REDACTED:721-727 | REDACTED:309-315 | app/controllers/miq_event_definition_controller.rb:56-62 | REDACTED:55-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) app/controllers/infra_networking_controller.rb:557 — app/controllers/infra_networking_controller.rb:557-563 | REDACTED:2617-2623 | app/controllers/pxe_controller.rb:251-257 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) app/helpers/diagnostics_tabs_helper.rb:8 — app/helpers/diagnostics_tabs_helper.rb:8-13 | app/helpers/diagnostics_tabs_helper.rb:47-52 | app/helpers/diagnostics_tabs_helper.rb:82-87 | app/helpers/settings_tabs_helper.rb:16-20 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience REDACTED:17 — `Net::HTTP.start` 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.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 45 typed · 1075 plain JS — the untyped files are app/javascript/angular/index.js, app/javascript/angular/miq_ae_class/ae_method_form_controller.js, app/javascript/components/AeInlineMethod/FilterNamespace.jsx, app/javascript/components/AeInlineMethod/NamespaceSelector.jsx, app/javascript/components/AeInlineMethod/helper.js, app/javascript/components/AeInlineMethod/index.jsx (+1069 more).
R10 · Code Duplication · Duplication concentrated across 104 sibling directories (138 clone groups) · ×1
  • Duplication concentrated across 104 sibling directories (138 clone groups) app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:51 — 138 duplicated blocks under app/javascript/components/ have copies in at least two of the sibling directories ab-form, action-form, ansible-credentials-form, ansible-playbook-edit-catalog-form, ansible-playbook-workflow, ansible-repository-form (+98 more sibling(s) not listed) — 100 of them are reported below, and 38 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 138 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 138 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 138 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 8 sibling directories (16 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (16 clone groups) app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.js:9 — 16 duplicated blocks under app/javascript/components/provider-dashboard-charts/ have copies in at least two of the sibling directories events-bar-chart, heat-map-chart, pod-trend-charts, provider-dashboard-utilization-chart, recent-host-chart, recent-vm-chart (+2 more sibling(s) not listed) — 11 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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 (15 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (15 clone groups) app/javascript/components/miq-about-modal/helper.js:26 — 15 duplicated blocks under app/javascript/ have copies in at least two of the sibling directories components, helpers, oldjs, tagging — 13 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 12 sibling directories (12 clone groups) · ×1
  • Duplication concentrated across 12 sibling directories (12 clone groups) app/javascript/components/data-tables/datastore/index.jsx:27 — 12 duplicated blocks under app/javascript/components/data-tables/ have copies in at least two of the sibling directories button-group-list, button-list, catalog-items-table, datastore, iso-datastore-table, object-types-list (+6 more sibling(s) not listed) — 9 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (124 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (124 matched lines × 2 locations) app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:51 — app/javascript/components/ansible-playbook-edit-catalog-form/index.jsx:51 · app/javascript/components/terraform-template-catalog-form/index.jsx:43 — the two spans are one implementation copied and then locally edited — 862 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 · Wholesale file copy (124 identical lines × 2 files) · ×1
  • Wholesale file copy (124 identical lines × 2 files) app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:1 — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:1 · app/javascript/components/workflow-credential-mapping-form/workflow-credential-mapping-form.schema.js:1 — these 2 files are line-for-line copies of one another — 124 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (122 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (122 matched lines × 2 locations) app/javascript/components/miq-ae-class/index.jsx:12 — app/javascript/components/miq-ae-class/index.jsx:12 · app/javascript/components/miq-ae-customization/index.jsx:10 — the two spans are one implementation copied and then locally edited — 646 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 (109 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (109 matched lines × 2 locations) app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js:8 — app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js:8 · app/javascript/components/storage-service-form/storage-service-form.schema.js:6 — the two spans are one implementation copied and then locally edited — 750 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 (93 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (93 matched lines × 2 locations) app/javascript/components/async-action-button.jsx:13 — app/javascript/components/async-action-button.jsx:13 · app/javascript/components/async-credentials/async-credentials.jsx:13 — the two spans are one implementation copied and then locally edited — 686 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 · Wholesale file copy (88 identical lines × 3 files) · ×1
  • Wholesale file copy (88 identical lines × 3 files) app/javascript/components/ansible-repository-form/index.jsx:1 — app/javascript/components/ansible-repository-form/index.jsx:1 · app/javascript/components/embedded-terraform-repository-form/index.jsx:1 · app/javascript/components/workflow-repository-form/index.jsx:1 — these 3 files are line-for-line copies of one another — 88 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (86 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (86 matched lines × 2 locations) app/javascript/components/utilization/utilization-report.tsx:17 — app/javascript/components/utilization/utilization-report.tsx:17 · app/javascript/components/utilization/utilization-summary.tsx:13 — the two spans are one implementation copied and then locally edited — 524 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 (81 lines × 2 locations) · ×1
  • Duplicated block (81 lines × 2 locations) app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:13 — app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:13 · app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block with local edits (71 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (71 matched lines × 2 locations) app/javascript/components/embedded-automate-entry-point/index.jsx:8 — app/javascript/components/embedded-automate-entry-point/index.jsx:8 · app/javascript/components/embedded-workflow-entry-point/index.jsx:8 — the two spans are one implementation copied and then locally edited — 451 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 (71 lines × 2 locations) · ×1
  • Duplicated block (71 lines × 2 locations) app/javascript/components/miq-about-modal/helper.js:26 — app/javascript/components/miq-about-modal/helper.js:26 · app/javascript/oldjs/miq_browser_detect.js:32 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
R10 · Code Duplication · Duplicated block (68 lines × 2 locations) · ×1
  • Duplicated block (68 lines × 2 locations) app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:7 — app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:7 · app/javascript/components/terraform-template-catalog-form/helper.js:7 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (68 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (68 matched lines × 2 locations) app/javascript/components/remove-catalog-item-modal.jsx:30 — app/javascript/components/remove-catalog-item-modal.jsx:30 · app/javascript/components/remove-generic-item-modal.jsx:68 — the two spans are one implementation copied and then locally edited — 463 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 (67 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (67 matched lines × 2 locations) app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx:9 — app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx:9 · app/javascript/components/workflow-credential-mapping-form/index.jsx:11 — the two spans are one implementation copied and then locally edited — 448 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 · Wholesale file copy (65 identical lines × 2 files) · ×1
  • Wholesale file copy (65 identical lines × 2 files) app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationDonutChart.js:1 — app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationDonutChart.js:1 · app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationMemoryDonutChart.js:1 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (64 identical lines × 3 files) · ×1
  • Wholesale file copy (64 identical lines × 3 files) app/javascript/components/ansible-repository-form/ansible-repository-form.schema.js:1 — app/javascript/components/ansible-repository-form/ansible-repository-form.schema.js:1 · app/javascript/components/embedded-terraform-repository-form/embedded-terraform-repository-form.schema.js:1 · app/javascript/components/workflow-repository-form/workflow-repository-form.schema.js:1 — these 3 files are line-for-line copies of one another — 64 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (63 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (63 matched lines × 2 locations) app/javascript/components/network-security-groups-form/index.jsx:19 — app/javascript/components/network-security-groups-form/index.jsx:19 · app/javascript/components/routers-form/index.jsx:77 — the two spans are one implementation copied and then locally edited — 320 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 (61 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (61 matched lines × 2 locations) app/javascript/components/cloud-volume-form/index.jsx:34 — app/javascript/components/cloud-volume-form/index.jsx:34 · app/javascript/components/storage-service-form/index.jsx:41 — the two spans are one implementation copied and then locally edited — 384 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 (60 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (60 matched lines × 2 locations) app/javascript/components/host-initiator-group-form/index.jsx:18 — app/javascript/components/host-initiator-group-form/index.jsx:18 · app/javascript/components/physical-storage-form/index.jsx:41 — the two spans are one implementation copied and then locally edited — 373 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 (56 lines × 3 locations) · ×1
  • Duplicated block (56 lines × 3 locations) app/javascript/components/ansible-credentials-form/ansible-credentials-form.schema.js:3 — app/javascript/components/ansible-credentials-form/ansible-credentials-form.schema.js:3 · app/javascript/components/embedded-terraform-credentials-form/embedded-terraform-credentials-form.schema.js:3 · app/javascript/components/workflow-credentials-form/workflow-credentials-form.schema.js:3 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (56 lines × 2 locations) · ×1
  • Duplicated block (56 lines × 2 locations) app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:108 — app/javascript/components/ansible-playbook-edit-catalog-form/helper.js:108 · app/javascript/components/terraform-template-catalog-form/helper.js:91 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (54 lines × 2 locations) · ×1
  • Duplicated block (54 lines × 2 locations) app/javascript/components/ap-form/event-log-tab.jsx:39 — app/javascript/components/ap-form/event-log-tab.jsx:39 · app/javascript/components/ap-form/file-tab.jsx:33 — 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 (53 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (53 matched lines × 2 locations) app/javascript/components/chargeback-assignments-form/simple-list.jsx:25 — app/javascript/components/chargeback-assignments-form/simple-list.jsx:25 · app/javascript/components/chargeback-assignments-form/tenant-tree.jsx:44 — the two spans are one implementation copied and then locally edited — 389 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 (48 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (48 matched lines × 2 locations) app/javascript/components/data-tables/datastore/index.jsx:27 — app/javascript/components/data-tables/datastore/index.jsx:27 · app/javascript/components/data-tables/time-profile-table/index.jsx:16 — the two spans are one implementation copied and then locally edited — 415 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 (47 lines × 2 locations) · ×1
  • Duplicated block (47 lines × 2 locations) app/javascript/components/ansible-playbook-edit-catalog-form/schemaHelper.js:2 — app/javascript/components/ansible-playbook-edit-catalog-form/schemaHelper.js:2 · app/javascript/components/terraform-template-catalog-form/schemaHelper.js:2 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (47 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (47 matched lines × 2 locations) app/javascript/components/button-group/index.jsx:150 — app/javascript/components/button-group/index.jsx:150 · app/javascript/components/generic-objects-form/custom-button-form/index.jsx:110 — the two spans are one implementation copied and then locally edited — 387 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 (46 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (46 matched lines × 2 locations) app/javascript/components/host-initiator-form/index.jsx:11 — app/javascript/components/host-initiator-form/index.jsx:11 · app/javascript/components/volume-mapping-form/index.jsx:16 — the two spans are one implementation copied and then locally edited — 286 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 (45 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (45 matched lines × 2 locations) app/javascript/components/cloud-database-form/cloud-database-form.jsx:38 — app/javascript/components/cloud-database-form/cloud-database-form.jsx:38 · app/javascript/components/cloud-tenant-form/index.jsx:14 — the two spans are one implementation copied and then locally edited — 255 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 (44 lines × 2 locations) · ×1
  • Duplicated block (44 lines × 2 locations) app/javascript/components/reconfigure-vm-form/helpers/disk.js:59 — app/javascript/components/reconfigure-vm-form/helpers/disk.js:59 · app/javascript/components/reconfigure-vm-form/helpers/network.js:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:259 — app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:259 · app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.js:199 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block with local edits (39 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (39 matched lines × 2 locations) app/javascript/components/tagging-editor/tag.jsx:9 — app/javascript/components/tagging-editor/tag.jsx:9 · app/javascript/tagging/components/InnerComponents/Tag.js:9 — the two spans are one implementation copied and then locally edited — 202 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) app/javascript/components/ab-form/ab-form.schema.js:85 — app/javascript/components/ab-form/ab-form.schema.js:85 · app/javascript/components/generic-objects-form/custom-button-form/custom-button-form.schema.js:79 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.js:9 — app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.js:9 · app/javascript/components/provider-dashboard-charts/servers-pie-chart/index.js:9 — the two spans are one implementation copied and then locally edited — 237 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.
R2 · Cyclomatic Complexity · Complex function CarbonValueEditor (cyclomatic 53, cognitive 52) · ×1
  • Complex function CarbonValueEditor (cyclomatic 53, cognitive 52) app/javascript/components/expression-editor/carbon-value-editor.jsx:273 — CarbonValueEditor has cyclomatic complexity 53 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 (anonymous) (cyclomatic 50, cognitive 82) · ×1
  • Complex function (anonymous) (cyclomatic 50, cognitive 82) app/javascript/components/report-editor/validation.ts:7 — (anonymous) has cyclomatic complexity 50 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 ChargebackFilter (cyclomatic 45, cognitive 41) · ×1
  • Complex function ChargebackFilter (cyclomatic 45, cognitive 41) app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:112 — ChargebackFilter has cyclomatic complexity 45 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function atomToHuman (cyclomatic 41, cognitive 51) · ×1
  • Complex function atomToHuman (cyclomatic 41, cognitive 51) app/javascript/components/expression-editor/expression-human.js:89 — atomToHuman has cyclomatic complexity 41 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 40, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 40, cognitive 38) app/javascript/components/report-editor/report-form-values.ts:73 — (anonymous) has cyclomatic complexity 40 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function processReplaceRightCell (cyclomatic 33, cognitive 45) · ×1
  • Complex function processReplaceRightCell (cyclomatic 33, cognitive 45) app/javascript/oldjs/miq_explorer.js:183 — processReplaceRightCell has cyclomatic complexity 33 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function miqAtomToRule (cyclomatic 33, cognitive 37) · ×1
  • Complex function miqAtomToRule (cyclomatic 33, cognitive 37) app/javascript/components/expression-editor/expression-adapter.js:20 — miqAtomToRule has cyclomatic complexity 33 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 FindValueEditor (cyclomatic 33, cognitive 31) · ×1
  • Complex function FindValueEditor (cyclomatic 33, cognitive 31) app/javascript/components/expression-editor/find-value-editor.jsx:115 — FindValueEditor has cyclomatic complexity 33 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 InstanceForm (cyclomatic 30, cognitive 24) · ×1
  • Complex function InstanceForm (cyclomatic 30, cognitive 24) app/javascript/components/miq-ae-class/instance-form.jsx:12 — InstanceForm has cyclomatic complexity 30 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ruleToMiqAtom (cyclomatic 28, cognitive 31) · ×1
  • Complex function ruleToMiqAtom (cyclomatic 28, cognitive 31) app/javascript/components/expression-editor/expression-adapter.js:161 — ruleToMiqAtom has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 SummaryTab (cyclomatic 28, cognitive 25) · ×1
  • Complex function SummaryTab (cyclomatic 28, cognitive 25) app/javascript/components/report-editor/tabs/summary-tab.tsx:112 — SummaryTab has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 validateRule (cyclomatic 24, cognitive 30) · ×1
  • Complex function validateRule (cyclomatic 24, cognitive 30) app/javascript/components/expression-editor/expression-validator.js:82 — validateRule has cyclomatic complexity 24 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ChargebackAssignmentsForm (cyclomatic 24, cognitive 11) · ×1
  • Complex function ChargebackAssignmentsForm (cyclomatic 24, cognitive 11) app/javascript/components/chargeback-assignments-form/index.jsx:14 — ChargebackAssignmentsForm has cyclomatic complexity 24 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 (anonymous) (cyclomatic 23, cognitive 40) · ×1
  • Complex function (anonymous) (cyclomatic 23, cognitive 40) app/javascript/components/chargeback-assignments-form/index.jsx:86 — (anonymous) has cyclomatic complexity 23 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 23, cognitive 27) · ×1
  • Complex function (anonymous) (cyclomatic 23, cognitive 27) app/javascript/components/group-form/index.jsx:93 — (anonymous) has cyclomatic complexity 23 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 21) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 21) app/javascript/components/workers-form/workers-form.jsx:21 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 DashboardWidget (cyclomatic 20, cognitive 31) · ×1
  • Complex function DashboardWidget (cyclomatic 20, cognitive 31) app/javascript/components/dashboard-widgets/dashboard-charts/index.jsx:9 — DashboardWidget has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 ReviewImportForm (cyclomatic 20, cognitive 9) · ×1
  • Complex function ReviewImportForm (cyclomatic 20, cognitive 9) app/javascript/components/automate-import-export-form/review-import-form.jsx:10 — ReviewImportForm has cyclomatic complexity 20 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 buildSubmitData (cyclomatic 19, cognitive 21) · ×1
  • Complex function buildSubmitData (cyclomatic 19, cognitive 21) app/javascript/components/ab-form/helper.js:100 — buildSubmitData has cyclomatic complexity 19 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onSubmit (cyclomatic 19, cognitive 17) · ×1
  • Complex function onSubmit (cyclomatic 19, cognitive 17) app/javascript/components/ap-form/index.jsx:146 — onSubmit has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ChartsTab (cyclomatic 19, cognitive 17) · ×1
  • Complex function ChartsTab (cyclomatic 19, cognitive 17) app/javascript/components/report-editor/tabs/charts-tab.tsx:48 — ChartsTab has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getInitialValue (cyclomatic 18, cognitive 32) · ×1
  • Complex function getInitialValue (cyclomatic 18, cognitive 32) app/javascript/components/data-tables/datastore/schema/modal-form.schema.js:43 — getInitialValue has cyclomatic complexity 18 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onItemClick (cyclomatic 18, cognitive 19) · ×1
  • Complex function onItemClick (cyclomatic 18, cognitive 19) app/javascript/components/gtl-view.jsx:433 — onItemClick has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function formatFieldValues (cyclomatic 18, cognitive 18) · ×1
  • Complex function formatFieldValues (cyclomatic 18, cognitive 18) app/javascript/components/data-tables/datastore/schema/class-fields-editor.jsx:76 — formatFieldValues has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function CheckboxTreeComponent (cyclomatic 18, cognitive 13) · ×1
  • Complex function CheckboxTreeComponent (cyclomatic 18, cognitive 13) app/javascript/components/tree-view/checkbox_tree.jsx:8 — CheckboxTreeComponent has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onSubmit (cyclomatic 17, cognitive 22) · ×1
  • Complex function onSubmit (cyclomatic 17, cognitive 22) app/javascript/components/group-form/index.jsx:213 — onSubmit has cyclomatic complexity 17 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 ApForm (cyclomatic 17, cognitive 16) · ×1
  • Complex function ApForm (cyclomatic 17, cognitive 16) app/javascript/components/ap-form/index.jsx:15 — ApForm has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 LabelSelection (cyclomatic 16, cognitive 9) · ×1
  • Complex function LabelSelection (cyclomatic 16, cognitive 9) app/javascript/components/chargeback-assignments-form/label-selection.jsx:16 — LabelSelection has cyclomatic complexity 16 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 onClick (cyclomatic 15, cognitive 30) · ×1
  • Complex function onClick (cyclomatic 15, cognitive 30) app/javascript/components/miq-toolbar.jsx:37 — onClick has cyclomatic complexity 15 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ExpressionEditorInner (cyclomatic 15, cognitive 12) · ×1
  • Complex function ExpressionEditorInner (cyclomatic 15, cognitive 12) app/javascript/components/condition-form/expression-editor-field.jsx:10 — ExpressionEditorInner has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 11) · ×1
  • Complex function (anonymous) (cyclomatic 15, cognitive 11) app/javascript/components/async-credentials/async-credentials.jsx:89 — (anonymous) has cyclomatic complexity 15 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 fetchResources (cyclomatic 15, cognitive 9) · ×1
  • Complex function fetchResources (cyclomatic 15, cognitive 9) app/javascript/components/chargeback-assignments-form/index.jsx:233 — fetchResources has cyclomatic complexity 15 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 (anonymous) (cyclomatic 14, cognitive 23) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 23) app/javascript/components/network-security-groups-form/helper.js:9 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildErrorDetails (cyclomatic 14, cognitive 14) · ×1
  • Complex function buildErrorDetails (cyclomatic 14, cognitive 14) app/javascript/components/miq-error-modal/miq-error-modal.jsx:24 — buildErrorDetails has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this 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 DateValueEditor (cyclomatic 14, cognitive 13) · ×1
  • Complex function DateValueEditor (cyclomatic 14, cognitive 13) app/javascript/components/expression-editor/date-value-editor.jsx:178 — DateValueEditor has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 13) cypress/support/commands/provider_helper_commands.js:180 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function fetchSavedTagCategory (cyclomatic 14, cognitive 11) · ×1
  • Complex function fetchSavedTagCategory (cyclomatic 14, cognitive 11) app/javascript/components/chargeback-assignments-form/tag-selection.jsx:65 — fetchSavedTagCategory has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 prepareSubmitData (cyclomatic 13, cognitive 15) · ×1
  • Complex function prepareSubmitData (cyclomatic 13, cognitive 15) app/javascript/components/generic-objects-form/custom-button-form/helper.js:82 — prepareSubmitData has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1231 lines of code REDACTED:1 — REDACTED has 1231 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 · app/javascript/components/ansible-playbook-edit-catalog-form/schema.js · ×1
  • app/javascript/components/ansible-playbook-edit-catalog-form/schema.js: 578 lines of code app/javascript/components/ansible-playbook-edit-catalog-form/schema.js:1 — app/javascript/components/ansible-playbook-edit-catalog-form/schema.js has 578 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 · app/javascript/components/action-form/action-form.schema.js · ×1
  • app/javascript/components/action-form/action-form.schema.js: 545 lines of code app/javascript/components/action-form/action-form.schema.js:1 — app/javascript/components/action-form/action-form.schema.js has 545 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 · app/javascript/components/expression-editor/carbon-value-editor.jsx · ×1
  • app/javascript/components/expression-editor/carbon-value-editor.jsx: 508 lines of code app/javascript/components/expression-editor/carbon-value-editor.jsx:1 — app/javascript/components/expression-editor/carbon-value-editor.jsx has 508 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 · app/javascript/components/chargeback-assignments-form/index.jsx · ×1
  • app/javascript/components/chargeback-assignments-form/index.jsx: 505 lines of code app/javascript/components/chargeback-assignments-form/index.jsx:1 — app/javascript/components/chargeback-assignments-form/index.jsx has 505 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 · app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx · ×1
  • app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx: 501 lines of code app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx:1 — app/javascript/components/report-editor/tabs/filter/chargeback-filter.tsx has 501 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 · app/javascript/components/gtl-view.jsx · ×1
  • app/javascript/components/gtl-view.jsx: 489 lines of code app/javascript/components/gtl-view.jsx:1 — app/javascript/components/gtl-view.jsx has 489 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 · app/javascript/components/schedule-form/helper.ts · ×1
  • app/javascript/components/schedule-form/helper.ts: 462 lines of code app/javascript/components/schedule-form/helper.ts:1 — app/javascript/components/schedule-form/helper.ts has 462 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 · app/javascript/packs/component-definitions-common.js · ×1
  • app/javascript/packs/component-definitions-common.js: 432 lines of code app/javascript/packs/component-definitions-common.js:1 — app/javascript/packs/component-definitions-common.js has 432 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 · app/javascript/components/container-projects/helper.jsx · ×1
  • app/javascript/components/container-projects/helper.jsx: 427 lines of code app/javascript/components/container-projects/helper.jsx:1 — app/javascript/components/container-projects/helper.jsx has 427 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 typecheck script · ×1
  • No 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.
R6 · Tooling · This package's lint script runs in no CI job · ×1
  • This package's lint script runs in no CI job package.json:22 — The root package declares the lint script `lint` (`eslint .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `.` (or the workspace's task runner).
R6 · Tooling · This lint config makes every finding a warning, so the linter cannot fail a step · ×1
  • This lint config makes every finding a warning, so the linter cannot fail a step .stylelintrc:2 — This stylelint config makes every finding a warning, and stylelint exits 0 on warnings: the lint step passes however many fire, so it gates nothing. Set the rules the team enforces to `error`, or run stylelint with `--max-warnings 0` where CI runs it.
R7 · Dead Code · Dead file (~540 LoC) · ×1
  • Dead file (~540 LoC) app/javascript/components/gtl-view.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~435 LoC) · ×1
  • Dead file (~435 LoC) app/javascript/packs/component-definitions-common.js — no import path from any entry point (25 application, 12 tooling, 391 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 (~334 LoC) · ×1
  • Dead file (~334 LoC) app/javascript/oldjs/miq_explorer.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (~309 LoC) · ×1
  • Dead file (~309 LoC) app/javascript/angular/miq_ae_class/ae_method_form_controller.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/angular/index.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 (~301 LoC) · ×1
  • Dead file (~301 LoC) app/javascript/components/terraform-template-catalog-form/terraform-template-catalog-form.schema.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/terraform-template-catalog-form/index.jsx) — 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 (~300 LoC) · ×1
  • Dead file (~300 LoC) app/javascript/components/host-initiator-form/host-initiator-form.schema.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/host-initiator-form/index.jsx) — 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 (~294 LoC) · ×1
  • Dead file (~294 LoC) app/javascript/oldjs/controllers/playbook-reusable-code-mixin.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/controllers/index.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 (~284 LoC) · ×1
  • Dead file (~284 LoC) app/javascript/oldjs/miq_qe.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (~273 LoC) · ×1
  • Dead file (~273 LoC) app/javascript/components/terraform-template-catalog-form/helper.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/terraform-template-catalog-form/index.jsx) — 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 (~252 LoC) · ×1
  • Dead file (~252 LoC) app/javascript/oldjs/controllers/dialog_editor/dialog_editor_controller.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/controllers/index.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 (~249 LoC) · ×1
  • Dead file (~249 LoC) app/javascript/components/provider-form/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~246 LoC) · ×1
  • Dead file (~246 LoC) app/javascript/components/settings-company-tags/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~223 LoC) · ×1
  • Dead file (~223 LoC) app/javascript/components/container-group-console/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~218 LoC) · ×1
  • Dead file (~218 LoC) app/javascript/components/volume-mapping-form/volume-mapping-form.schema.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/volume-mapping-form/index.jsx) — 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 (~211 LoC) · ×1
  • Dead file (~211 LoC) app/javascript/components/terraform-template-catalog-form/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~196 LoC) · ×1
  • Dead file (~196 LoC) app/javascript/components/miq-about-modal/miq-about-modal.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~186 LoC) · ×1
  • Dead file (~186 LoC) app/javascript/oldjs/miq_c3_config.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (~184 LoC) · ×1
  • Dead file (~184 LoC) app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/cloud-volume-form/index.jsx) — 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 (~176 LoC) · ×1
  • Dead file (~176 LoC) app/javascript/oldjs/miq_ujs_bindings.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/application.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 (~172 LoC) · ×1
  • Dead file (~172 LoC) app/javascript/components/data-tables/requests-table/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~171 LoC) · ×1
  • Dead file (~171 LoC) app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx) — 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 (~167 LoC) · ×1
  • Dead file (~167 LoC) app/javascript/components/taggingWrapper.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~163 LoC) · ×1
  • Dead file (~163 LoC) app/javascript/components/provider-dashboard-charts/heat-map-chart/HeatMapChartGraph.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/provider-dashboard-charts/heat-map-chart/index.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 (~155 LoC) · ×1
  • Dead file (~155 LoC) app/javascript/components/request-workflow-status/request-workflow-status-item.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/request-workflow-status/index.jsx) — 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 (~151 LoC) · ×1
  • Dead file (~151 LoC) app/javascript/components/miq-error-modal/miq-error-modal.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~149 LoC) · ×1
  • Dead file (~149 LoC) app/javascript/components/storage-service-form/storage-service-form.schema.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/storage-service-form/index.jsx) — 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 (~148 LoC) · ×1
  • Dead file (~148 LoC) app/javascript/components/async-action-button.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/storage-service-form/get-compliant-resources.jsx) — 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 (~135 LoC) · ×1
  • Dead file (~135 LoC) app/javascript/components/miq-about-modal/helper.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/miq-about-modal/miq-about-modal.jsx) — 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 (~127 LoC) · ×1
  • Dead file (~127 LoC) app/javascript/components/embedded-terraform-credential-mapping-form/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~125 LoC) · ×1
  • Dead file (~125 LoC) app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/utilizationDonutChart.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/provider-dashboard-charts/provider-dashboard-utilization-chart/index.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 (~122 LoC) · ×1
  • Dead file (~122 LoC) app/javascript/oldjs/controllers/dialog_user/dialog_user_controller.js — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/oldjs/controllers/index.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 (~121 LoC) · ×1
  • Dead file (~121 LoC) app/javascript/components/storage-service-form/index.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/packs/component-definitions-common.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 (~116 LoC) · ×1
  • Dead file (~116 LoC) app/javascript/components/AeInlineMethod/NamespaceSelector.jsx — no import path from any entry point (25 application, 12 tooling, 391 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/javascript/components/AeInlineMethod/index.jsx) — 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
Minor — 323 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×192
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file app/helpers/host_helper/textual_summary.rb: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 app/controllers/mixins/actions/vm_actions/reconfigure.rb: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 app/helpers/application_helper/toolbar_chooser.rb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file app/controllers/infra_networking_controller.rb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file app/helpers/application_helper/toolbar_builder.rb: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 app/presenters/tree_builder.rb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file app/helpers/catalog_helper.rb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file app/helpers/application_helper/toolbar/x_vm_center.rb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file app/controllers/mixins/actions/host_actions/misc.rb: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 app/helpers/service_helper/textual_summary.rb: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 app/helpers/application_helper/toolbar/vm_infras_center.rb: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 app/helpers/miq_alert_helper.rb: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 app/presenters/explorer_presenter.rb: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.
  • + 167 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×42
  • redundant comment app/javascript/components/automate-import-export-form/review-import-form.jsx:28 — "Parse import data" repeats the code it sits on: 3 of its 3 words (parse, import, data) are already in `const data = typeof importResponse === 'string' ? JSON.parse(importResponse) : importResponse;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/dashboard-widgets/widget-wrapper/helper.jsx:176 — "Handles print or export to PDF button" repeats the code it sits on: 4 of its 5 words (print, export, pdf, button) are already in `if (buttonTitle === __('Print the full report (all rows) or export it as a PDF file'))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/drift-history/index.jsx:18 — "Parse timestamps if it's a JSON string" repeats the code it sits on: 4 of its 4 words (parse, timestamps, json, string) are already in `const parsedTimestamps = useMemo(() => (typeof timestamps === 'string' ? JSON.parse(timestamps) : timestamps), [timestam …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/expression-editor/expression-validator.js:64 — "Validate the value for a date or datetime field." repeats the code it sits on: 4 of its 5 words (validate, value, date, datetime) are already in `const validateDateRule = (value, operator, isDatetime) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/expression-editor/find-value-editor.jsx:69 — "Server returns [{ label, name, col_type }, ...]" repeats the code it sits on: 5 of its 6 words (returns, label, name, col, type) are already in `setCheckFields(raw.map((entry) => (Array.isArray(entry)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/git-domain-refresh-form/index.jsx:20 — "Set initial values based on ref type" repeats the code it sits on: 5 of its 6 words (set, initial, values, ref, type) are already in `const initialValues = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/miq-ae-class/copy-objects-form.jsx:24 — "Transform selected items object to array" repeats the code it sits on: 4 of its 5 words (selected, items, object, array) are already in `const selectedItemsArray = Object.values(editData.selected_items);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/components/vm-edit-form/helper.js:9 — "Get VM Parent Options and filter out current VM" repeats the code it sits on: 5 of its 6 words (get, vm, parent, options, filter) are already in `API.get(`/api/vms/?filter[]=ems_id=${emsId}&expand=resources`)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:91 — "Check if this state has credentials" repeats the code it sits on: 3 of its 3 words (check, state, credentials) are already in `if (!state.Credentials || typeof state.Credentials !== 'object')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:98 — "Extract the actual credential reference from the JSONPath value" repeats the code it sits on: 6 of its 7 words (extract, credential, reference, json, path, value) are already in `const credentialRef = extractCredentialReference(jsonPathValue);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/miq-component/registry.js:110 — "create new instance" repeats the code it sits on: 3 of its 3 words (create, new, instance) are already in `let newInstance = blueprint.create(actualProps, mountTo);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/oldjs/controllers/dialog_editor/dialog_editor_controller.js:8 — "options for tree selector" repeats the code it sits on: 3 of its 3 words (options, tree, selector) are already in `vm.treeOptions = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/spec/embedded-terraform-repository-form/embedded-terraform-repository-form.spec.js:32 — "Mock the provider API call" repeats the code it sits on: 4 of its 4 words (mock, provider, api, call) are already in `fetchMock.get(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/spec/embedded-terraform-repository-form/embedded-terraform-repository-form.spec.js:39 — "Mock the credentials API call" repeats the code it sits on: 4 of its 4 words (mock, credentials, api, call) are already in `fetchMock.get(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/spec/group-form/filter-tabs.spec.jsx:188 — "VAT-only key already checked" repeats the code it sits on: 4 of its 5 words (vat, only, key, checked) are already in `fieldState.value = { belongstoChecked: [VAT_ONLY_KEY] };`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment app/javascript/spec/group-form/filter-tabs.spec.jsx:210 — "HAC-only key already checked" repeats the code it sits on: 4 of its 5 words (hac, only, key, checked) are already in `fieldState.value = { belongstoChecked: [HAC_ONLY_KEY] };`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment config/webpack/shared.js:121 — "Create marker file" repeats the code it sits on: 3 of its 3 words (create, marker, file) are already in `fs.writeFileSync(markerPath, new Date().toISOString());`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Automation/Embedded-Automate/Explorer/domains-priority-form.cy.js:21 — "Create test domains" repeats the code it sits on: 3 of its 3 words (create, test, domains) are already in `cy.appFactories([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Automation/Embedded-Automate/Explorer/domains-priority-form.cy.js:172 — "Create a disabled domain using enabled: false" repeats the code it sits on: 5 of its 6 words (create, disabled, domain, enabled, false) are already in `cy.appFactories([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Automation/Embedded-Automate/Explorer/git-domain-refresh-form.cy.js:62 — 7 comments in this file only repeat the code they sit on (lines 62, 98, 116, 121, 137, 147, 192), for example "Create the git domain with a name matching the repository". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Automation/Embedded-Automate/import-export.cy.js:316 — "Click Import button" repeats the code it sits on: 3 of its 3 words (click, import, button) are already in `cy.contains('button', 'Import').click();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Compute/Infrastructure/PXE/pxe-image-edit-form.cy.js:5 — "Create a PXE Server" repeats the code it sits on: 3 of its 3 words (create, pxe, server) are already in `cy.appFactories([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Compute/Infrastructure/PXE/pxe-image-edit-form.cy.js:11 — "Create a PXE Image linked to the server" repeats the code it sits on: 4 of its 5 words (create, pxe, image, server) are already in `cy.appFactories([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Compute/Infrastructure/PXE/pxe-windows-image-edit-form.cy.js:5 — "Create a PXE Server" repeats the code it sits on: 3 of its 3 words (create, pxe, server) are already in `cy.appFactories([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cypress/e2e/ui/Compute/Infrastructure/PXE/pxe-windows-image-edit-form.cy.js:11 — "Create a Windows Image linked to the server" repeats the code it sits on: 4 of its 5 words (create, windows, image, server) are already in `cy.appFactories([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 17 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js:88 — `!condition || parseCondition(condition, getState().values).result` appears character-identically in 2 files — app/javascript/components/cloud-volume-form/cloud-volume-form.schema.js, app/javascript/components/storage-service-form/storage-service-form.schema.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 app/javascript/components/pxe-image-edit-form/index.jsx:16 — `!pxeImageTypes || !Array.isArray(pxeImageTypes)` appears character-identically in 2 files — app/javascript/components/pxe-image-edit-form/index.jsx, app/javascript/components/pxe-windows-image-edit-form/index.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/chargeback-assignments-form/label-selection.jsx:77 — `!savedAssignments || savedAssignments.length === 0` appears character-identically in 2 files — app/javascript/components/chargeback-assignments-form/label-selection.jsx, app/javascript/components/chargeback-assignments-form/tag-selection.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/dashboard-widgets/dashboard-charts/index.jsx:50 — `(data.miqChart === 'StackedColumn' || data.miqChart === 'Column') && !data.data.groups` appears character-identically in 2 files — app/javascript/components/dashboard-widgets/dashboard-charts/index.jsx, app/javascript/components/performance-charts/index.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/async-credentials/edit-password-field.jsx:29 — `(meta.touched || validateOnMount) && meta.error` appears character-identically in 2 files — app/javascript/components/async-credentials/edit-password-field.jsx, app/javascript/components/miq-ae-class/namespace-selector.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/custom-url-tabs/helper.js:6 — `ManageIQ.redux.store.getState().FormButtons && ManageIQ.redux.store.getState().FormButtons.in_a_form` appears character-identically in 2 files — app/javascript/components/custom-url-tabs/helper.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/ap-form/event-log-tab.jsx:72 — `action === 'buttonCallback' && selectedRow.callbackAction` appears character-identically in 3 files — app/javascript/components/ap-form/event-log-tab.jsx, app/javascript/components/ap-form/file-tab.jsx, app/javascript/components/ap-form/registry-tab.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:30 — `cellType === 'buttonCallback' && credentials[selectedRow.cells[0].value]` appears character-identically in 2 files — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js, app/javascript/components/workflow-credential-mapping-form/workflow-credential-mapping-form.schema.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 app/javascript/components/ap-form/event-log-tab.jsx:76 — `clickedCell && !clickedCell.classList.contains('action-cell-holder')` appears character-identically in 3 files — app/javascript/components/ap-form/event-log-tab.jsx, app/javascript/components/ap-form/file-tab.jsx, app/javascript/components/ap-form/registry-tab.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/expression-editor/expression-validator.js:125 — `colType === 'date' || colType === 'datetime'` appears character-identically in 3 files — app/javascript/components/expression-editor/expression-validator.js, app/javascript/components/expression-editor/field-config.js, app/javascript/components/expression-editor/find-value-editor.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/expression-editor/expression-human.js:25 — `colType === 'integer' || colType === 'float'` appears character-identically in 3 files — app/javascript/components/expression-editor/expression-human.js, app/javascript/components/expression-editor/field-config.js, app/javascript/components/expression-editor/find-value-editor.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:105 — `credentials[input.value] && credentialReferences !== input.value` appears character-identically in 2 files — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js, app/javascript/components/workflow-credential-mapping-form/workflow-credential-mapping-form.schema.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 app/javascript/components/reconfigure-vm-form/helper.js:137 — `data.submitParams.drives.disconnect || []` appears character-identically in 2 files — app/javascript/components/reconfigure-vm-form/helper.js, app/javascript/components/reconfigure-vm-form/helpers/drive.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 app/javascript/components/miq-about-modal/helper.js:5 — `data[i].versionSearch || data[i].identity` appears character-identically in 2 files — app/javascript/components/miq-about-modal/helper.js, app/javascript/oldjs/miq_browser_detect.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 app/javascript/components/async-action-button.jsx:99 — `dirtyFields[field] && dependencies.includes(field)` appears character-identically in 2 files — app/javascript/components/async-action-button.jsx, app/javascript/components/async-credentials/async-credentials.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/helpers/handle-failure.js:7 — `e.data && e.data.error && e.data.error.message` appears character-identically in 2 files — app/javascript/helpers/handle-failure.js, app/javascript/oldjs/services/miq_service.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 app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:93 — `meta.pristine && credentialReferences !== undefined` appears character-identically in 2 files — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js, app/javascript/components/workflow-credential-mapping-form/workflow-credential-mapping-form.schema.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 app/javascript/components/ansible-playbook-edit-catalog-form/schemaHelper.js:63 — `options && options.become_method && options.become_method !== ''` appears character-identically in 2 files — app/javascript/components/ansible-playbook-edit-catalog-form/schemaHelper.js, app/javascript/components/terraform-template-catalog-form/schemaHelper.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 app/javascript/react/generic_group_wrapper.jsx:5 — `props.onClick || textualSummaryGenericClick` appears character-identically in 3 files — app/javascript/react/generic_group_wrapper.jsx, app/javascript/react/table_list_view_wrapper.js, app/javascript/react/textual_summary_wrapper.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/embedded-automate-entry-point/index.jsx:39 — `selectedValue && selectedValue.name && selectedValue.name.text` appears character-identically in 2 files — app/javascript/components/embedded-automate-entry-point/index.jsx, app/javascript/components/embedded-workflow-entry-point/index.jsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js:13 — `state.workflowCredentials && state.credentialField` appears character-identically in 2 files — app/javascript/components/embedded-terraform-credential-mapping-form/embedded-terraform-credential-mapping-form.schema.js, app/javascript/components/workflow-credential-mapping-form/workflow-credential-mapping-form.schema.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:393 — `!params[:show].nil? || !params[:x_show].nil?` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/controllers/mixins/actions/vm_actions/reconfigure.rb:54 — `!session[:checked_items].nil? && (@lastaction == "set_checked_items" || params[:pressed] == "miq_request_edit")` appears character-identically in 2 files — app/controllers/mixins/actions/vm_actions/reconfigure.rb, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:516 — `@custom_button.visibility && @custom_button.visibility[:roles] && @custom_button.visibility[:roles][0] != "_ALL_"` appears character-identically in 2 files — REDACTED, app/controllers/miq_ae_customization_controller/custom_buttons.rb. 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:227 — `@edit[:adv_search_applied] && MiqExpression.quick_search?(@edit[:adv_search_applied][:exp]) && %w[reload tree_select].include?(params[:actio…` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 15 more in this group — see findings.md.
X7 · Silent fallback defaults · Pending state with no failure state · ×23
  • Pending state with no failure state app/javascript/components/aggregate_status_card.jsx:33 — The view draws `loading...` under `data . loading`, but `data` 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 app/javascript/components/workflows/workflow-entry-points.jsx:136 — The view draws `<Loading active small withOverlay= class="loading"/>` under `data . isLoading`, but `data` 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 app/javascript/components/vm-edit-form/index.jsx:70 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/vm-cloud-add-remove-security-group-form/index.jsx:99 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/visual-settings-form/index.jsx:54 — The view draws `<div class="loadSettings">` under `isLoading`, but `isLoading` 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 app/javascript/components/user-form/index.jsx:155 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/subnet-form/index.jsx:90 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/schedule-form/index.tsx:99 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `data . isLoading`, but `data` 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 app/javascript/components/routers-form/index.jsx:158 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/role-form/index.jsx:270 — The view draws `<div class="summary-spinner">` under `formData . isLoading`, but `formData` 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 app/javascript/components/request-workflow-status/request-workflow-status-item.jsx:110 — The view draws `<Loading active small withOverlay= class="loading"/>` under `data . isLoading`, but `data` 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 app/javascript/components/report-editor/tabs/trend-columns-tab.tsx:103 — The view draws `<Loading small withOverlay= description= />` under `fieldsLoading`, but `fieldsLoading` 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 app/javascript/components/policy-profile-form/index.js:59 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading || ( options === undefined )`, but `isLoading` 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 app/javascript/components/network-security-groups-form/index.jsx:104 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/miq-alert-set-form/index.jsx:101 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/generic-objects-form/custom-button-form/index.jsx:95 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/cloud-object-store-container-form/index.jsx:70 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading`, but `isLoading` 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 app/javascript/components/chargeback-assignments-form/index.jsx:443 — The view draws `<div class="chargeback-assignments-loading">` 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 app/javascript/components/chargeback-assignments-form/index.jsx:451 — The view draws `<div class="chargeback-assignments-loading">` under `submitting`, but `submitting` 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 app/javascript/components/chargeback-assignments-form/index.jsx:483 — The view draws `<div class="chargeback-assignments-loading">` under `loadingResources`, but `loadingResources` 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 app/javascript/components/chargeback-assignments-form/tag-selection.jsx:129 — The view draws `<div class="tag-selection-loading">` 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 app/javascript/components/button-group/index.jsx:135 — The view draws `<Loading class="export-spinner" withOverlay= small/>` under `isLoading || ( options === undefined )`, but `isLoading` 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 app/javascript/components/automate-simulation-form/index.jsx:123 — The view draws `<div class="summary-spinner">` under `formData . isLoading`, but `formData` 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.
D10 · Test Quality · Mock-dominated test · ×9
  • Mock-dominated test: passes the intercepted action to next app/javascript/spec/miq-redux/middleware.spec.js:22 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: toggles from %s to %s app/javascript/spec/expression-editor/date-value-editor.spec.js:113 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: appends default time when operator changes from IS to BEFORE on a datetime field with a date app/javascript/spec/expression-editor/date-value-editor.spec.js:202 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: strips time when operator changes from BEFORE to IS on a datetime field app/javascript/spec/expression-editor/date-value-editor.spec.js:229 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: does not call handleOnChange when operator changes but value already matches app/javascript/spec/expression-editor/date-value-editor.spec.js:256 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: does not call handleOnChange when value is empty app/javascript/spec/expression-editor/date-value-editor.spec.js:284 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should handle API errors gracefully app/javascript/spec/chargeback-assignments-form/label-selection.spec.js:235 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should handle API errors gracefully app/javascript/spec/chargeback-assignments-form/tag-selection.spec.js:238 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should call onSelectGitRepo when branch is selected app/javascript/spec/automate-import-export-form/import-datastore-via-git-modal.spec.js:259 — This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D16 · Bus Factor · Off-boarding risk · ×3
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 9 significant file(s) lose their only recent owner: REDACTED, REDACTED, REDACTED, REDACTED, app/helpers/application_helper/toolbar/x_miq_template_center.rb, app/helpers/application_helper/toolbar/vms_center.rb, app/javascript/components/utilization/utilization-report.tsx, app/javascript/components/utilization/utilization-summary.tsx (+1 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: app/javascript/components/schedule-form/schedule-form-fields.ts, app/javascript/components/schedule-form/schedule-form-types.ts, app/javascript/menu/search.tsx, app/javascript/components/schedule-form/index.tsx. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 5 significant file(s) lose their only recent owner: app/controllers/report_controller/reports/editor.rb, REDACTED, app/controllers/ops_controller/settings/cap_and_u.rb, app/controllers/expression_editor_controller.rb, app/presenters/tree_builder_belongs_to_hac.rb. Pair on, review, or document these before any departure.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file app/presenters/menu/default_menu.rb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file app/helpers/vm_helper/textual_summary.rb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file REDACTED:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
C2 · Access Controls · Thin authorization enforcement · ×1
  • Thin authorization enforcement — Only 2 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (25 single-owned of 251 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 251 of the 1282 production source files in this repository met that bar). They are anonymized user #4 (3 file(s)), anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: REDACTED, REDACTED, lib/extensions/database_cleaner-activerecord-seeded_deletion.rb, app/helpers/application_helper/toolbar/vm_clouds_center.rb, app/helpers/application_helper/toolbar/cloud/instance_operations_button_group_mixin.rb, app/helpers/application_helper/toolbar/cloud_volumes_center.rb, REDACTED.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found bin/rails:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `bin/rails` makes this repository a deployable product (line 1).
D34 · Knowledge Freshness · Concentrated knowledge decay · ×1
  • Concentrated knowledge decay — 195 of 315 significant files have no living knowledge, while the repository is still being changed at a low rate (418 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 195 separate risks. Counted over 315 of the 1282 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P1 · CI/CD gates · CI build step not evidenced · ×1
  • CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:3 — No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
X5 · Nullable reference types · Ruby's type checker does not check nil everywhere · ×1
  • Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1237 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch app/javascript/components/group-form/belongs-to-tab.jsx:120 — `BelongsToTab` 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.
Minor — 1 finding(s)
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names app/javascript/components/schedule-form/schedule-form-types.ts:75 — 7 of 101 documented parameters and 10 of 599 summaries in `manageiq-ui-classic` only repeat the member or parameter name (e.g. "Form state" for `FormState`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

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-b068e6d748a04c97bcc92de510ab4e39/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=800" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=3016" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=7216 --max-count=2955" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-4.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-4.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=10171 --max-count=3710" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-5.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-5.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=13881 --max-count=4749" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-6.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-6.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=18630 --max-count=5898" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-7.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-7.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=24528 --max-count=7348" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-8.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-8.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=31876 --max-count=8998" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-9.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-9.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=40874 --max-count=2189" --report-format json --report-path /tmp/watchdog-gitleaks-b068e6d748a04c97bcc92de510ab4e39/history-10.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-10.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-b068e6d748a04c97bcc92de510ab4e39/tree.json --exit-code 0 --source .3artifacts/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 .254artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .4artifacts/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—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.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 01a1e5f7-5b73-79a7-ad9b-331494692d87 · 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