Public report of DROOdotFOO/raxol, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 09:55 UTC · Survey ID cd_7b2daecef3f04e5e9706402f27e68f8e
DROOdotFOO/raxol
Measured 17 November 2026, 09:54 UTC, at code version 87ab761
First survey, so nothing to compare with yet
CAI scoreAdequate
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 large codebase: 303,539 lines of product code in 16 projects, tests not counted · Estimated rebuild effort: about 3.3 person-years · Weakest lens: Accessibility, 45.3
Findings by how serious they are
129 critical896 serious310 minor
16 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 09:54 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 ▸
65of 65 dimensions measured by tools.
1303of 1335 findings point to an exact file and line, so you can open each one in the code. The other 32 concern the repository as a whole, such as missing documentation.
65dimensions across 7 lenses, read from 303,539 lines of product code in 16 projects.
DROOdotFOO/raxol falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 54.8 out of 100 and is rated Adequate, and 113 of its 129 critical findings are security problems.
Accessibility, at 45.3, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 6.1 points. Making the controls keyboard-usable comes next, worth about 4.9 points. Raising Accessibility to 70 would lift the score to about 61.5.
Ninety-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen settings leave the servers or containers unsafe, and four parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, correcting the unsafe settings and having someone learn the forgotten files would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The nine uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 303,539 lines, about €490,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 45.3 to 70, the lowest score rated Strong, the score would rise from 54.8 to about 61.5.
Code composition: what the lines of code are
Product code 62%Tests 38%
Rebuild cost: about €490,000 · Estimate
Cost to rebuild
€160,000 to €810,000, for 2,684 to 8,516 hours of work, about 3.3 person-years for 1 to 7 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 303,539 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
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.
Raises the score by about 6.1 points · Medium effort · Text alternatives
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 4.9 points · Medium effort · Keyboard semantics
3
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 2.1 points · Medium effort · Page structure
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 €490,000 to build again, about 3.3 person-years of work. Its weakest lens is Accessibility, at 45.3 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 6.1 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
313 modules, with 109 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 273 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.
Raxol.Agent.Journal uses Raxol.Agent, so a change to Raxol.Agent can break Raxol.Agent.Journal, while a change to Raxol.Agent.Journal can't break Raxol.Agent.
Position
Below the diagonal: Raxol.Agent.Journal uses a module listed above it, which is the healthy direction.
Raxol.Agent.Journal.Records.Checkpoint uses Raxol.Agent.Journal.Records, so a change to Raxol.Agent.Journal.Records can break Raxol.Agent.Journal.Records.Checkpoint, while a change to Raxol.Agent.Journal.Records.Checkpoint can't break Raxol.Agent.Journal.Records.
Position
Below the diagonal: Raxol.Agent.Journal.Records.Checkpoint uses a module listed above it, which is the healthy direction.
Raxol.Animation uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Animation, while a change to Raxol.Animation can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Animation uses a module listed above it, which is the healthy direction.
Raxol.Animation.Gestures uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Animation.Gestures, while a change to Raxol.Animation.Gestures can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Animation.Gestures uses a module listed above it, which is the healthy direction.
Raxol.Core.Accessibility uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.Accessibility, while a change to Raxol.Core.Accessibility can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.Accessibility uses a module listed above it, which is the healthy direction.
Raxol.Core.Events uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.Events, while a change to Raxol.Core.Events can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.Events uses a module listed above it, which is the healthy direction.
Raxol.Core.FocusManager uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.FocusManager, while a change to Raxol.Core.FocusManager can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.FocusManager uses a module listed above it, which is the healthy direction.
Raxol.Core.KeyboardNavigator uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.KeyboardNavigator, while a change to Raxol.Core.KeyboardNavigator can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.KeyboardNavigator uses a module listed above it, which is the healthy direction.
Raxol.Core.KeyboardShortcuts uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.KeyboardShortcuts, while a change to Raxol.Core.KeyboardShortcuts can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.KeyboardShortcuts uses a module listed above it, which is the healthy direction.
Raxol.Core.Metrics uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.Metrics, while a change to Raxol.Core.Metrics can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.Metrics uses a module listed above it, which is the healthy direction.
Raxol.Core.Renderer.Views uses Raxol.UI.Components.Base, so a change to Raxol.UI.Components.Base can break Raxol.Core.Renderer.Views, while a change to Raxol.Core.Renderer.Views can't break Raxol.UI.Components.Base.
Position
Below the diagonal: Raxol.Core.Renderer.Views uses a module listed above it, which is the healthy direction.
Raxol.Core.Runtime uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.Runtime, while a change to Raxol.Core.Runtime can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.Runtime uses a module listed above it, which is the healthy direction.
Raxol.Core.Runtime.Directive.Executor.Raxol.Core.Runtime.Directive uses Raxol.Core.Runtime.Directive, so a change to Raxol.Core.Runtime.Directive can break Raxol.Core.Runtime.Directive.Executor.Raxol.Core.Runtime.Directive, while a change to Raxol.Core.Runtime.Directive.Executor.Raxol.Core.Runtime.Directive can't break Raxol.Core.Runtime.Directive.
Position
Below the diagonal: Raxol.Core.Runtime.Directive.Executor.Raxol.Core.Runtime.Directive uses a module listed above it, which is the healthy direction.
Raxol.Core.Runtime.Events uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.Runtime.Events, while a change to Raxol.Core.Runtime.Events can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.Runtime.Events uses a module listed above it, which is the healthy direction.
Raxol.Core.Runtime.Plugins uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core.Runtime.Plugins, while a change to Raxol.Core.Runtime.Plugins can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core.Runtime.Plugins uses a module listed above it, which is the healthy direction.
Raxol.Core.Runtime.Plugins uses Raxol.Core.Runtime.Plugins.LifecycleHelper, so a change to Raxol.Core.Runtime.Plugins.LifecycleHelper can break Raxol.Core.Runtime.Plugins, while a change to Raxol.Core.Runtime.Plugins can't break Raxol.Core.Runtime.Plugins.LifecycleHelper.
Position
Below the diagonal: Raxol.Core.Runtime.Plugins uses a module listed above it, which is the healthy direction.
Raxol.Gateway uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Gateway, while a change to Raxol.Gateway can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Gateway uses a module listed above it, which is the healthy direction.
Raxol.MCP uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.MCP, while a change to Raxol.MCP can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.MCP uses a module listed above it, which is the healthy direction.
Raxol.Terminal uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Terminal, while a change to Raxol.Terminal can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Terminal uses a module listed above it, which is the healthy direction.
Raxol.Terminal uses Raxol.Core.Telemetry, so a change to Raxol.Core.Telemetry can break Raxol.Terminal, while a change to Raxol.Terminal can't break Raxol.Core.Telemetry.
Position
Below the diagonal: Raxol.Terminal uses a module listed above it, which is the healthy direction.
Raxol.Terminal.ANSI uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Terminal.ANSI, while a change to Raxol.Terminal.ANSI can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Terminal.ANSI uses a module listed above it, which is the healthy direction.
Raxol.Terminal.Emulator uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Terminal.Emulator, while a change to Raxol.Terminal.Emulator can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Terminal.Emulator uses a module listed above it, which is the healthy direction.
Raxol.UI.Rendering uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.UI.Rendering, while a change to Raxol.UI.Rendering can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.UI.Rendering uses a module listed above it, which is the healthy direction.
Raxol.UI.Theming uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.UI.Theming, while a change to Raxol.UI.Theming can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.UI.Theming uses a module listed above it, which is the healthy direction.
Raxol.UI.Theming uses Raxol.UI.Components.Base, so a change to Raxol.UI.Components.Base can break Raxol.UI.Theming, while a change to Raxol.UI.Theming can't break Raxol.UI.Components.Base.
Position
Below the diagonal: Raxol.UI.Theming uses a module listed above it, which is the healthy direction.
Raxol.Core uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Core, while a change to Raxol.Core can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Core uses a module listed above it, which is the healthy direction.
Raxol.Core uses Raxol.Core.Accessibility, so a change to Raxol.Core.Accessibility can break Raxol.Core, while a change to Raxol.Core can't break Raxol.Core.Accessibility.
Position
Below the diagonal: Raxol.Core uses a module listed above it, which is the healthy direction.
Raxol.Core uses Raxol.Core.FocusManager, so a change to Raxol.Core.FocusManager can break Raxol.Core, while a change to Raxol.Core can't break Raxol.Core.FocusManager.
Position
Below the diagonal: Raxol.Core uses a module listed above it, which is the healthy direction.
Raxol.Telegram uses Raxol.Core.Behaviours, so a change to Raxol.Core.Behaviours can break Raxol.Telegram, while a change to Raxol.Telegram can't break Raxol.Core.Behaviours.
Position
Below the diagonal: Raxol.Telegram uses a module listed above it, which is the healthy direction.
Raxol.UI.Charts uses Raxol.Core.Accessibility, so a change to Raxol.Core.Accessibility can break Raxol.UI.Charts, while a change to Raxol.UI.Charts can't break Raxol.Core.Accessibility.
Position
Below the diagonal: Raxol.UI.Charts uses a module listed above it, which is the healthy direction.
Raxol.UI.Components uses Raxol.UI.Components.Base, so a change to Raxol.UI.Components.Base can break Raxol.UI.Components, while a change to Raxol.UI.Components can't break Raxol.UI.Components.Base.
Position
Below the diagonal: Raxol.UI.Components uses a module listed above it, which is the healthy direction.
Raxol.UI.Components uses Raxol.Core.Accessibility, so a change to Raxol.Core.Accessibility can break Raxol.UI.Components, while a change to Raxol.UI.Components can't break Raxol.Core.Accessibility.
Position
Below the diagonal: Raxol.UI.Components uses a module listed above it, which is the healthy direction.
Raxol.UI.Components uses Raxol.MCP, so a change to Raxol.MCP can break Raxol.UI.Components, while a change to Raxol.UI.Components can't break Raxol.MCP.
Position
Below the diagonal: Raxol.UI.Components uses a module listed above it, which is the healthy direction.
Raxol.UI.Components.Display uses Raxol.UI.Components.Base, so a change to Raxol.UI.Components.Base can break Raxol.UI.Components.Display, while a change to Raxol.UI.Components.Display can't break Raxol.UI.Components.Base.
Position
Below the diagonal: Raxol.UI.Components.Display uses a module listed above it, which is the healthy direction.
Raxol.UI.Components.Display uses Raxol.Core.Accessibility, so a change to Raxol.Core.Accessibility can break Raxol.UI.Components.Display, while a change to Raxol.UI.Components.Display can't break Raxol.Core.Accessibility.
Position
Below the diagonal: Raxol.UI.Components.Display uses a module listed above it, which is the healthy direction.
Raxol.UI.Components.Display uses Raxol.MCP, so a change to Raxol.MCP can break Raxol.UI.Components.Display, while a change to Raxol.UI.Components.Display can't break Raxol.MCP.
Position
Below the diagonal: Raxol.UI.Components.Display uses a module listed above it, which is the healthy direction.
Raxol.UI.Components.Input uses Raxol.UI.Components.Base, so a change to Raxol.UI.Components.Base can break Raxol.UI.Components.Input, while a change to Raxol.UI.Components.Input can't break Raxol.UI.Components.Base.
Position
Below the diagonal: Raxol.UI.Components.Input uses a module listed above it, which is the healthy direction.
Raxol.UI.Components.Input uses Raxol.Core.Accessibility, so a change to Raxol.Core.Accessibility can break Raxol.UI.Components.Input, while a change to Raxol.UI.Components.Input can't break Raxol.Core.Accessibility.
Position
Below the diagonal: Raxol.UI.Components.Input uses a module listed above it, which is the healthy direction.
Raxol.UI.Components.Input uses Raxol.MCP, so a change to Raxol.MCP can break Raxol.UI.Components.Input, while a change to Raxol.UI.Components.Input can't break Raxol.MCP.
Position
Below the diagonal: Raxol.UI.Components.Input uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 56.7 · Adequate · gated by R1, R3 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
102
High / Critical
A02:2025 — Security Misconfiguration
19
High / Critical
A03:2025 — Software Supply Chain Failures
9
Medium
Roadmap
Top priorities: 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; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
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.
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 — 129
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 — 896
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 — 310
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 65 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1303 of 1335 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`excoveralls`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.exs, .ex, .php, .ts, .js), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
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 39 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 956 test source file(s) (.exs, .ex, .php) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.exs, .ex, .php, .ts, .js) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Hex package 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.
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.
D25 ADR Conformance — 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 code index reads C#, Razor, TypeScript, JavaScript and Vue. A rule whose scope holds production code in another language is not called honoured, because its uses could sit in that code.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — postgres Pulling elixir Pulling elixir Error pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied postgres Error context canceled Error response from daemon: pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: postgres Pulling elixir Pulling elixir Error pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied postgres Error context canceled Error response from daemon: pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Elixir, c, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Elixir, c, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C, Lua is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Go source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Go was found, and this repository's C, Elixir, Lua is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — 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. 66 further occurrence(s) are not listed individually; the score already reflects all 106.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was app.document.addEventListener("DOMContentLoaded") at 29. A further 4 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 Attributes.translate_with_charset at 32 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: packages/raxol_terminal/lib/raxol/terminal/screen_buffer/attributes.ex (Attributes.translate_with_charset at 32), packages/raxol_terminal/lib/raxol/terminal/ansi/sgr.ex (Formatter.parse_sgr_param at 31), packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/sequence_router.ex (SequenceRouter.handle_sequence at 23), packages/raxol_terminal/lib/raxol/terminal/ansi/character_sets/handler.ex (Handler.code_to_charset at 16). 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with app.document.addEventListener("DOMContentLoaded") (cyclomatic 29), (anonymous) (cyclomatic 29), mounted::onKey (cyclomatic 21). — 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 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with buildMask (cognitive 30), Renderer.build_ansi_prefix (cognitive 28), app.document.addEventListener("DOMContentLoaded") (cognitive 25). — 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 11 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 90 TooManyFunctions finding(s) in God Classes — start with text_formatting.ex (2), manager.ex (2), screen_buffer.ex. — One of this dimension's main actionable groups (90 warning-level).
Resolve the 38 FileTooLong finding(s) in God Classes — start with server.ex (2), engine.ex (2), landing_components.ex. — One of this dimension's main actionable groups (38 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
198 duplicated block group(s) detected. 4.6 % of the production lines (14,103 of 303,539) are in a reported copy. A further 470 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 131 of the 668 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (14 corresponding lines) · ×26lib/raxol/harness/recency_policy.ex:314
Edited copy of a member (10 corresponding lines) · ×25packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:289
Edited copy of a member (4 corresponding lines) · ×24lib/raxol/adaptive/behavior_tracker.ex:302
Edited copy of a member (7 corresponding lines) · ×23packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:63
Edited copy of a member (11 corresponding lines) · ×20lib/raxol/scoreboard.ex:391
+ 168 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 26 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with image_renderer.ex (2), demo.exs (2), recency_policy.ex. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 25 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with terminal_config_manager.ex (2), particles.ex (2), extended_sequences.ex. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 24 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with engine.ex (2), behavior_tracker.ex, optimizer.ex. — One of this dimension's main actionable groups (24 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
15 production modules (npm+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
Off the main sequence: raxol (OTP) · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with style.ex, theme.ex. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.6 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 39 tests. Measured on the JavaScript/TypeScript suite only — at least 956 test source file(s) (.exs, .ex, .php) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: cleans up on unmounttest/js/components/Terminal.test.js:55
What to do
Resolve the 1 No assertions finding(s) in Test Quality — start with Terminal.test.js. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
18 outdated, 0 retired direct Hex dependencies, 0 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from mix.lock there.
Outdated: bumblebee · ×18
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 70 shipped Hex package(s) use a banned license. Licences were resolved from hex.pm over the packages a consumer installs — this repository's mix.lock closed over the declarations its mix.exs files do not gate behind `only:`. Packages it asks for ONLY under `only: [:dev, :test]` (or any other non-prod environment, such as `:docs`) are excluded: they are not installed by anything that depends on this repository. Each licence is the one hex.pm publishes for the package's current release. A further 3 package(s) the closure reaches resolve from git, a path or a local override and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's Hex package 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.
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.
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.
291 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/raxol/harness/surface.ex. Counted over 1054 of the 1369 production source files in this repository: 314 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
4 deducted task-comment markers across 303539 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 4 TodoComment finding(s) in Explicit Debt — start with text_field_test.exs, dispatcher.ex, raxol.demo.ex. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
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.
0 of 18 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
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.
doc comments repeat the namesscripts/testing/check_coverage.js:45
What to do
Resolve the 17 redundant comment finding(s) in Comment Value — start with app.js (4), search.js (2), terminal_visual_test.js (2). — One of this dimension's main actionable groups (17 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 16 build units (Mix, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×4mix.exs:1
What to do
Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with mix.exs (4). — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
32 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
102 finding(s): 0 critical, 99 high, 3 medium, 0 low. 94 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 4 file(s) — `packages/raxol_terminal/lib/termbox2_nif/c_src/termbox2/termbox2.h`, `scripts/check_toolchain.sh` (line 82), `scripts/harness/t0/probes/p04_region_algorithm.sh` (line 17), `scripts/harness/t0/probes/p06_teardown.sh` (line 22) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 94 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 (94 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 14 High IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
184 of 1055 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scripts/harness/t0/ringb/measurements.ex. Counted over 1055 of the 1369 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 4 Orphaned knowledge finding(s) in Knowledge Freshness — start with measurements.ex, char_editor.ex, golden.ex. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 180 Orphaned file finding(s) in Knowledge Freshness — start with cursor.ex (3), style.ex (3), cell.ex (2). — One of this dimension's main actionable groups (180 recommendation-level).
Resolve the 1 Further orphaned files (smaller) 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.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Change coupling finding(s) in Change Coupling — start with engine.ex, element_renderer.ex, mode_manager.ex. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — web/lib/raxol_playground_web/components/landing_components.ex:318
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels7.1 / 10Strong✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — web/lib/raxol_playground_web/live/gallery_live.ex:214
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — web/lib/raxol_playground_web/components/layouts/root.html.heex:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — web/lib/raxol_playground_web/components/layouts/root.html.heex:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — web/lib/raxol_playground_web/live/playground_live.ex:573
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. (×32) — web/priv/demo_previews/heatmap.html:5, web/priv/demo_previews/heatmap.html:5, web/priv/demo_previews/heatmap.html:6, …
`.command-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — web/priv/static/css/app.css:181, web/assets/css/app.css:1587
`input[type="range"]` 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. — web/assets/css/app.css:2531
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
C2 · Access Controls4.7 / 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.
Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Only 12/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`, `.`, `.`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:12
What to do
Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
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.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety2.3 / 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.
5 typed · 17 plain JS — the untyped files are assets/js/app.js, assets/js/terminal_hook.js, scripts/testing/check_coverage.js, test/js/__mocks__/fileMock.js, test/js/accessibility/TerminalAccessibility.test.js, test/js/accessibility/terminal_accessibility_test.js (+11 more).
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
web/assets/js/app.js:442 · web/assets/js/app.js:807 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/assets/js/app.js:442
web/assets/js/app.js:369 · web/assets/js/app.js:694 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/assets/js/app.js:369
web/assets/js/app.js:75 · web/priv/static/js/app.js:111 — 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. — web/assets/js/app.js:75
web/assets/js/app.js:411 · web/assets/js/app.js:746 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/assets/js/app.js:411
web/assets/js/app.js:356 · web/assets/js/app.js:677 — 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. — web/assets/js/app.js:356
web/assets/js/app.js:550 · web/assets/js/app.js:1064 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/assets/js/app.js:550
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 29 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. — web/assets/js/app.js:1164
onKey has cyclomatic complexity 21 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 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. — web/assets/js/app.js:840
intent has cyclomatic complexity 20 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. — web/assets/js/app.js:273
buildMask has cyclomatic complexity 14 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. — web/assets/js/app.js:971
Do you agree with this assessment?
R3 · Large Files3.3 / 10Weak✓ 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.
web/assets/js/app.js has 1096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/assets/js/app.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
23 file(s) (~2816 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: web/priv/static/js/app.js imports '../vendor/topbar', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here.
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. (×9) — web/priv/static/js/app.js:9, web/priv/static/js/app.js:10, test/js/components/terminal_component_test.js:3, …
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's Elixir source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. This repository serves HTTP itself (lib/raxol/endpoint.ex:10 — `Phoenix.Endpoint`), so its Elixir source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Elixir spelling appears in production source, not proven on every route. A router that plugs Phoenix's `put_secure_browser_headers` is credited the headers Phoenix sends by default (`content-security-policy` from Phoenix 1.8, `x-frame-options` before it, as the `mix.lock` pins), and a cookie Plug sets the HttpOnly flag it sets by default.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`:crypto.hash(:sha256, data)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — lib/raxol/core/error_experience.ex:650, packages/raxol_terminal/lib/raxol/terminal/image_cache.ex:183
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `lib/raxol/core/error_experience.ex:650` (:crypto.hash(:md5, …)), `packages/raxol_terminal/lib/raxol/terminal/image_cache.ex:183` (:crypto.hash(:md5, …)). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`:file.open(path, [:write, :exclusive, :binary, :raw])` opens a file here (line 211), and the `with` clause `:ok <- …` on line 212 can fail to match, and `with` then returns without running the block that closes it. Nothing else owns it: it is not returned, kept in a process's state or handed to another process, so it stays open until the process that opened it exits — one more file held per call in a long-lived process, `:emfile` under load. Close it on every path: `try … after File.close(…) end`, a block form that closes for you (`File.open(path, modes, fn device -> … end)`), or a close in every branch — or hand it to the process that owns it. — lib/raxol/harness/editor_session.ex:211
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 60 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: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; this repository's Go 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 PHP 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 Python 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; 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.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — postgres Pulling elixir Pulling elixir Error pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied postgres Error context canceled Error response from daemon: pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: postgres Pulling elixir Pulling elixir Error pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied postgres Error context canceled Error response from daemon: pull access denied for elixir-arm64, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (Ecto, Postgrex, MyXQL, Mongo, EventStore, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an Ecto schema, an Ecto migration or an Ash resource — and no database or data-store client (an Ecto repo, Postgrex, MyXQL, Exqlite, Mongo, Mnesia, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — no .exs test runner
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 (71109 declarations, no unit with a dominant convention).
D22 Internal API Consistency — N/A — too few peer members to establish a convention across 1 exposed TypeScript types.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — 1 binding ADR(s) rule out an element in code we do not index (.ex, .exs, .go, .py, .rb, .rs); their rules were neither confirmed nor broken.
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.
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.
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 49 value object(s); 6 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (57 Elixir aggregate(s) emitting domain events (%Event{} from execute/2))
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 19 test file(s) reach none of 5 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X1 Async correctness — X1 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines), python (55 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — X30 reached only 1% of this repository's production lines — elixir (303,147 lines), c (300 lines), lua (214 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Orphaned knowledge scripts/harness/t0/ringb/measurements.ex:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/raxol_terminal/lib/raxol/terminal/buffer/char_editor.ex:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/raxol/harness/surface/golden.ex:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/raxol/harness/editor_session.ex:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label web/lib/raxol_playground_web/live/gallery_live.ex:214— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> web/lib/raxol_playground_web/components/layouts/root.html.heex: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 <div> · ×1
Click handler on a non-interactive <div> web/lib/raxol_playground_web/live/playground_live.ex:573— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Unlisted import '@codemirror/lang-elixir' web/priv/static/js/app.js:9— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@codemirror/theme-one-dark' web/priv/static/js/app.js:10— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@testing-library/jest-dom' test/js/components/terminal_component_test.js:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@testing-library/react' test/js/accessibility/TerminalAccessibility.test.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@testing-library/user-event' test/js/e2e/terminal_e2e_test.js:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'codemirror' web/priv/static/js/app.js:8— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'jest-axe' test/js/accessibility/terminal_accessibility_test.js:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'jest-image-snapshot' test/js/visual/terminal_visual_test.js:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react' test/js/accessibility/terminal_accessibility_test.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
TooManyFunctions: ScreenBuffer packages/raxol_terminal/lib/raxol/terminal/screen_buffer.ex:1— TooManyFunctions — 69 functions. The bar is 30 functions; this is 39 over it, 2.30× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Manager packages/raxol_terminal/lib/raxol/terminal/parser/state/parser_state_manager.ex:1— TooManyFunctions — 68 functions. The bar is 30 functions; this is 38 over it, 2.27× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: AccessibilityServer packages/raxol_core/lib/raxol/core/accessibility/accessibility_server.ex:1— TooManyFunctions — 64 functions. The bar is 30 functions; this is 34 over it, 2.13× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Accessibility packages/raxol_core/lib/raxol/core/accessibility.ex:1— TooManyFunctions — 63 functions. The bar is 30 functions; this is 33 over it, 2.10× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: TextFormatting packages/raxol_terminal/lib/raxol/terminal/ansi/text_formatting.ex:1— TooManyFunctions — 60 functions. The bar is 30 functions; this is 30 over it, 2.00× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Platform lib/raxol/system/platform.ex:1— TooManyFunctions — 59 functions. The bar is 30 functions; this is 29 over it, 1.97× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Attributes packages/raxol_terminal/lib/raxol/terminal/screen_buffer/attributes.ex:1— TooManyFunctions — 59 functions. The bar is 30 functions; this is 29 over it, 1.97× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Advanced lib/mix/tasks/raxol.bench.advanced.ex:1— TooManyFunctions — 56 functions. The bar is 30 functions; this is 26 over it, 1.87× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: CharEditor packages/raxol_terminal/lib/raxol/terminal/buffer/char_editor.ex:1— TooManyFunctions — 55 functions. The bar is 30 functions; this is 25 over it, 1.83× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Chart lib/raxol/core/renderer/views/chart.ex:1— TooManyFunctions — 52 functions. The bar is 30 functions; this is 22 over it, 1.73× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Emitter packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:259— TooManyFunctions — 50 functions. The bar is 30 functions; this is 20 over it, 1.67× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Manipulation packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:285— TooManyFunctions — 50 functions. The bar is 30 functions; this is 20 over it, 1.67× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Operations packages/raxol_terminal/lib/raxol/terminal/screen_buffer/operations.ex:1— TooManyFunctions — 49 functions. The bar is 30 functions; this is 19 over it, 1.63× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Profiler lib/raxol/performance/profiler.ex:1— TooManyFunctions — 48 functions. The bar is 30 functions; this is 18 over it, 1.60× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: BlockBuilder lib/raxol/harness/projection/block_builder.ex:1— TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: SafeEmulator packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:1— TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Manager packages/raxol_terminal/lib/raxol/terminal/input/input_manager.ex:1— TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: BehaviourImpl packages/raxol_terminal/lib/raxol/terminal/screen_buffer/behaviour_impl.ex:1— TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: ThemeResolver lib/raxol/ui/theme_resolver.ex:1— TooManyFunctions — 44 functions. The bar is 30 functions; this is 14 over it, 1.47× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Log packages/raxol_core/lib/raxol/core/runtime/log.ex:1— TooManyFunctions — 44 functions. The bar is 30 functions; this is 14 over it, 1.47× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: CommandHandler packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:1— TooManyFunctions — 44 functions. The bar is 30 functions; this is 14 over it, 1.47× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Buffer packages/raxol_terminal/lib/raxol/terminal/terminal_buffer.ex:1— TooManyFunctions — 44 functions. The bar is 30 functions; this is 14 over it, 1.47× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: TrueColor packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:1— TooManyFunctions — 43 functions. The bar is 30 functions; this is 13 over it, 1.43× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Manager packages/raxol_terminal/lib/raxol/terminal/cursor/cursor_manager.ex:1— TooManyFunctions — 43 functions. The bar is 30 functions; this is 13 over it, 1.43× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
TooManyFunctions: Loader lib/raxol/config/loader.ex:1— TooManyFunctions — 42 functions. The bar is 30 functions; this is 12 over it, 1.40× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
FileTooLong: mcp/server.ex packages/raxol_mcp/lib/raxol/mcp/server.ex— FileTooLong — 1460 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 98 functions. The bar is 500 significant lines; this is 960 over it, 2.92× 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: components/landing_components.ex web/lib/raxol_playground_web/components/landing_components.ex— FileTooLong — 1252 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 36 functions. The bar is 500 significant lines; this is 752 over it, 2.50× 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: workflow/runtime.ex lib/raxol/workflow/runtime.ex— FileTooLong — 1241 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 68 functions. The bar is 500 significant lines; this is 741 over it, 2.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: harness/surface.ex lib/raxol/harness/surface.ex— FileTooLong — 1227 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 109 functions. The bar is 500 significant lines; this is 727 over it, 2.45× 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: repl/sandbox.ex lib/raxol/repl/sandbox.ex— FileTooLong — 1188 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 94 functions. The bar is 500 significant lines; this is 688 over it, 2.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: raxol/headless.ex lib/raxol/headless.ex— FileTooLong — 1053 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 110 functions. The bar is 500 significant lines; this is 553 over it, 2.11× 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: layout/engine.ex lib/raxol/ui/layout/engine.ex— FileTooLong — 1034 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 60 functions. The bar is 500 significant lines; this is 534 over it, 2.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: harness/diff_viewer.ex lib/raxol/ui/components/harness/diff_viewer.ex— FileTooLong — 1024 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 96 functions. The bar is 500 significant lines; this is 524 over it, 2.05× 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: release/package_check.ex lib/raxol/release/package_check.ex— FileTooLong — 829 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 87 functions. The bar is 500 significant lines; this is 329 over it, 1.66× 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: events/dispatcher.ex lib/raxol/core/runtime/events/dispatcher.ex— FileTooLong — 781 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 54 functions. 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: file_store/writer.ex packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex— FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 82 functions. The bar is 500 significant lines; this is 213 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: js/app.js web/assets/js/app.js— FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 190 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: components/table.ex lib/raxol/ui/components/table.ex— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 48 functions. 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: rendering/engine.ex lib/raxol/core/runtime/rendering/engine.ex— FileTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 55 functions. The bar is 500 significant lines; this is 171 over it, 1.34× 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: paint_authority/inline_authority.ex lib/raxol/ui/rendering/paint_authority/inline_authority.ex— FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 57 functions. The bar is 500 significant lines; this is 166 over it, 1.33× 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: harness/block.ex lib/raxol/ui/components/harness/block.ex— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 86 functions. The bar is 500 significant lines; this is 128 over it, 1.26× 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: plugin/plugin_server.ex packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex— FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 67 functions. The bar is 500 significant lines; this is 108 over it, 1.22× 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: runtime/component_manager.ex lib/raxol/core/runtime/component_manager.ex— FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 44 functions. The bar is 500 significant lines; this is 105 over it, 1.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: ansi/sgr.ex packages/raxol_terminal/lib/raxol/terminal/ansi/sgr.ex— FileTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 101 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: live/playground_live.ex web/lib/raxol_playground_web/live/playground_live.ex— FileTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 85 over it, 1.17× 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: script/script_server.ex packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 56 functions. The bar is 500 significant lines; this is 78 over it, 1.16× 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: runtime/lifecycle.ex lib/raxol/core/runtime/lifecycle.ex— FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 45 functions. The bar is 500 significant lines; this is 67 over it, 1.13× 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: raxol/application.ex lib/raxol/application.ex— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 55 functions. The bar is 500 significant lines; this is 64 over it, 1.13× 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: live_view/terminal_bridge.ex packages/raxol_liveview/lib/raxol/live_view/terminal_bridge.ex— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 45 functions. The bar is 500 significant lines; this is 62 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: terminal/inline_driver.ex packages/raxol_terminal/lib/raxol/terminal/inline_driver.ex— FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 45 functions. The bar is 500 significant lines; this is 57 over it, 1.11× 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.
+ 13 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×26
Edited copy of a member (14 corresponding lines) lib/raxol/harness/recency_policy.ex:314— lib/raxol/harness/recency_policy.ex:314-337 | lib/raxol/harness/recency_policy.ex:364-377 — 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) lib/raxol/ui/components/display/tree.ex:50— lib/raxol/ui/components/display/tree.ex:50-66 | lib/raxol/ui/components/input/menu.ex:55-68 — 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) lib/raxol/ui/charts/line_chart.ex:39— lib/raxol/ui/charts/line_chart.ex:39-52 | lib/raxol/ui/charts/scatter_chart.ex:39-52 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:146— packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:146-163 | packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:168-181 — 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) lib/raxol/protocols/plugin_system_integration.ex:224— lib/raxol/protocols/plugin_system_integration.ex:224-237 | lib/raxol/protocols/plugin_system_integration.ex:241-254 — 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) lib/raxol/ui/components/harness/diff_viewer.ex:1414— lib/raxol/ui/components/harness/diff_viewer.ex:1414-1427 | lib/raxol/ui/components/harness/diff_viewer.ex:1448-1461 — 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) examples/apps/file_browser.exs:276— examples/apps/file_browser.exs:276-290 | lib/raxol/ui/components/display/tree.ex:233-246 — 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) lib/raxol/ui/style_processor.ex:272— lib/raxol/ui/style_processor.ex:272-285 | lib/raxol/ui/theme_resolver.ex:38-51 — 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) lib/raxol/memory/optimizer.ex:76— lib/raxol/memory/optimizer.ex:76-89 | lib/raxol/memory/optimizer.ex:93-106 — 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) lib/raxol/rate.ex:75— lib/raxol/rate.ex:75-88 | lib/raxol/scoreboard.ex:228-241 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) packages/raxol_core/lib/raxol/core/user_preferences.ex:92— packages/raxol_core/lib/raxol/core/user_preferences.ex:92-105 | packages/raxol_core/lib/raxol/core/user_preferences.ex:263-276 — 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) lib/raxol/core/runtime/rendering/engine.ex:744— lib/raxol/core/runtime/rendering/engine.ex:744-757 | lib/raxol/core/runtime/rendering/engine.ex:787-801 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/registry.ex:58— packages/raxol_terminal/lib/raxol/terminal/commands/registry.ex:58-71 | packages/raxol_terminal/lib/raxol/terminal/plugin/terminal_plugin_manager.ex:68-83 — 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) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:194— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:194-207 | packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:211-225 — 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) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/operations/erasing.ex:79— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/operations/erasing.ex:79-92 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/operations/erasing.ex:96-109 — 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) lib/raxol/plugins/visualization/image_renderer.ex:233— lib/raxol/plugins/visualization/image_renderer.ex:233-246 | lib/raxol/plugins/visualization/image_renderer.ex:304-318 — 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) lib/raxol/core/metrics/aggregator.ex:169— lib/raxol/core/metrics/aggregator.ex:169-185 | lib/raxol/core/metrics/alert_manager.ex:188-201 — 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) lib/raxol/plugins/visualization/image_renderer.ex:85— lib/raxol/plugins/visualization/image_renderer.ex:85-106 | lib/raxol/plugins/visualization/image_renderer.ex:118-131 — 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) lib/raxol/swarm/strategy/tailscale.ex:88— lib/raxol/swarm/strategy/tailscale.ex:88-101 | lib/raxol/swarm/strategy/tailscale.ex:105-118 — 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) packages/raxol_terminal/lib/raxol/terminal/extension/extension_manager.ex:237— packages/raxol_terminal/lib/raxol/terminal/extension/extension_manager.ex:237-251 | packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:288-301 — 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) lib/raxol/memory/collector.ex:288— lib/raxol/memory/collector.ex:288-301 | lib/raxol/memory/optimizer.ex:110-123 — 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) examples/demo.exs:544— examples/demo.exs:544-558 | lib/raxol/demo/dashboard.ex:375-388 — 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) examples/demo.exs:238— examples/demo.exs:238-252 | lib/raxol/demo/dashboard.ex:150-163 — 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) examples/dev/hot_reload_demo.exs:47— examples/dev/hot_reload_demo.exs:47-61 | examples/ssh/ssh_counter.exs:50-63 — 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) lib/raxol/plugins/examples/git_integration_plugin.ex:485— lib/raxol/plugins/examples/git_integration_plugin.ex:485-498 | lib/raxol/plugins/examples/git_integration_plugin.ex:502-515 — 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.
+ 1 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×25
Edited copy of a member (10 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:289— packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:289-298 | packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:376-391 — 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) lib/raxol/ui/components/harness/message_block.ex:48— lib/raxol/ui/components/harness/message_block.ex:48-58 | lib/raxol/ui/components/harness/reasoning_block.ex:35-44 — 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) lib/raxol/ui/components/harness/activity_indicator.ex:41— lib/raxol/ui/components/harness/activity_indicator.ex:41-52 | lib/raxol/ui/components/harness/axol_face.ex:104-113 — 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) lib/raxol/ui/charts/bar_chart.ex:549— lib/raxol/ui/charts/bar_chart.ex:549-558 | lib/raxol/ui/charts/scatter_chart.ex:169-182 — 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) lib/mix/tasks/raxol.demo.ex:112— lib/mix/tasks/raxol.demo.ex:112-121 | lib/mix/tasks/raxol/templates.ex:20-35 — 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) bench/suites/protocol_performance_benchmark.exs:345— bench/suites/protocol_performance_benchmark.exs:345-355 | lib/raxol/performance/profiler.ex:405-414 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_event_processor.ex:115— packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_event_processor.ex:115-133 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_event_processor.ex:314-323 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:99— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:99-108 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:207-217 — 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) lib/raxol/performance/flame_graph.ex:113— lib/raxol/performance/flame_graph.ex:113-124 | lib/raxol/performance/flame_graph.ex:137-146 — 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) lib/raxol/workflow/graph.ex:389— lib/raxol/workflow/graph.ex:389-398 | lib/raxol/workflow/graph.ex:402-411 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:436— packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:436-445 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:450-459 — 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) lib/raxol/harness/fixture/bless.ex:85— lib/raxol/harness/fixture/bless.ex:85-97 | packages/raxol_journal/lib/raxol/agent/journal/file_store/reader.ex:209-218 — 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) lib/raxol/demo/session_manager.ex:182— lib/raxol/demo/session_manager.ex:182-191 | packages/raxol_terminal/lib/raxol/terminal/session_manager.ex:493-505 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:105— packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:105-114 | packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:123-132 — 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) lib/raxol/ui/components/display/tree.ex:198— lib/raxol/ui/components/display/tree.ex:198-207 | lib/raxol/ui/components/input/menu.ex:215-224 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) web/lib/raxol_playground_web/live/demo_live.ex:133— web/lib/raxol_playground_web/live/demo_live.ex:133-142 | web/lib/raxol_playground_web/live/playground_live.ex:168-180 — 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) web/lib/raxol_playground_web/controllers/capabilities_controller.ex:55— web/lib/raxol_playground_web/controllers/capabilities_controller.ex:55-67 | web/lib/raxol_playground_web/controllers/skill_controller.ex:10-19 — 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) packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket.ex:327— packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket.ex:327-336 | packages/raxol_telegram/lib/raxol/telegram/update_poller.ex:197-208 — 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) packages/raxol_terminal/lib/raxol/terminal/config/terminal_config_manager.ex:42— packages/raxol_terminal/lib/raxol/terminal/config/terminal_config_manager.ex:42-51 | packages/raxol_terminal/lib/raxol/terminal/terminal_config.ex:48-57 — 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) packages/raxol_terminal/lib/raxol/terminal/config/terminal_config_manager.ex:56— packages/raxol_terminal/lib/raxol/terminal/config/terminal_config_manager.ex:56-65 | packages/raxol_terminal/lib/raxol/terminal/terminal_config.ex:74-83 — 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) lib/raxol/demo/particles.ex:311— lib/raxol/demo/particles.ex:311-321 | lib/raxol/demo/text_formation.ex:229-238 — 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) lib/raxol/demo/particles.ex:102— lib/raxol/demo/particles.ex:102-111 | lib/raxol/demo/text_formation.ex:209-220 — 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) examples/advanced/architecture/architecture_demo.exs:77— examples/advanced/architecture/architecture_demo.exs:77-86 | examples/advanced/architecture/architecture_demo.exs:117-129 — 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) examples/apps/showcase_app.exs:115— examples/apps/showcase_app.exs:115-124 | lib/raxol/demo/showcase.ex:117-126 — 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) bench/suites/performance/event_handling.ex:55— bench/suites/performance/event_handling.ex:55-66 | bench/suites/performance/rendering.ex: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.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×24
Edited copy of a member (4 corresponding lines) lib/raxol/adaptive/behavior_tracker.ex:302— lib/raxol/adaptive/behavior_tracker.ex:302-305 | lib/raxol/adaptive/behavior_tracker.ex:372-376 — 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) packages/raxol_terminal/lib/raxol/terminal/scroll/optimizer.ex:45— packages/raxol_terminal/lib/raxol/terminal/scroll/optimizer.ex:45-56 | packages/raxol_terminal/lib/raxol/terminal/scroll/sync.ex:41-44 — 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) packages/raxol_terminal/lib/raxol/terminal/driver/background_query.ex:135— packages/raxol_terminal/lib/raxol/terminal/driver/background_query.ex:135-138 | packages/raxol_terminal/lib/raxol/terminal/renderer.ex:503-506 — 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) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:170— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:170-179 | packages/raxol_gateway/lib/raxol/gateway/session_router.ex:391-394 — 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) lib/raxol/ui/components/harness/memory_panel.ex:73— lib/raxol/ui/components/harness/memory_panel.ex:73-78 | lib/raxol/ui/components/harness/worktracks_panel.ex:106-109 — 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) lib/raxol/plugins/visualization/image_renderer.ex:157— lib/raxol/plugins/visualization/image_renderer.ex:157-162 | packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:237-240 — 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) packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:359— packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:359-362 | packages/raxol_terminal/lib/raxol/terminal/tab/tab_server.ex:190-193 — 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) lib/raxol/core/metrics/aggregator.ex:161— lib/raxol/core/metrics/aggregator.ex:161-164 | lib/raxol/core/metrics/alert_manager.ex:172-175 — 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) lib/raxol/core/runtime/rendering/engine.ex:159— lib/raxol/core/runtime/rendering/engine.ex:159-162 | packages/raxol_gateway/lib/raxol/gateway/session_router.ex:193-200 — 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) lib/raxol/ui/layout/engine.ex:799— lib/raxol/ui/layout/engine.ex:799-802 | lib/raxol/ui/layout/view_nodes.ex:378-381 — 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) lib/raxol/ui/theming/theme_manager.ex:84— lib/raxol/ui/theming/theme_manager.ex:84-91 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:142-145 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:118— packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:118-121 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_event_processor.ex:89-100 — 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) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/attributes.ex:339— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/attributes.ex:339-342 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/selection.ex:197-200 — 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) lib/raxol/config/loader.ex:287— lib/raxol/config/loader.ex:287-290 | lib/raxol/harness/fixture.ex:355-361 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/coordinator.ex:63— packages/raxol_terminal/lib/raxol/terminal/emulator/coordinator.ex:63-66 | packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:381-384 — 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) lib/raxol/style/colors/color.ex:84— lib/raxol/style/colors/color.ex:84-87 | packages/raxol_terminal/lib/raxol/terminal/config/capabilities.ex:142-148 — 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) lib/raxol/protocols/behaviour_adapter.ex:198— lib/raxol/protocols/behaviour_adapter.ex:198-201 | lib/raxol/protocols/component_framework.ex:281-287 — 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) packages/raxol_gateway/lib/raxol/gateway/pipeline/transcribe.ex:147— packages/raxol_gateway/lib/raxol/gateway/pipeline/transcribe.ex:147-150 | packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:176-179 — 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) lib/mix/tasks/raxol.demo.ex:125— lib/mix/tasks/raxol.demo.ex:125-128 | lib/mix/tasks/raxol.record.ex:139-144 — 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) packages/raxol_terminal/lib/raxol/terminal/escape/parsers/base_parser.ex:59— packages/raxol_terminal/lib/raxol/terminal/escape/parsers/base_parser.ex:59-62 | scripts/harness/t0/lib/verdict_resolver_core.exs:191-194 — 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) lib/raxol/harness/editor_session.ex:305— lib/raxol/harness/editor_session.ex:305-308 | packages/raxol_terminal/lib/raxol/terminal/input/clipboard_handler.ex:68-74 — 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) lib/raxol/playground/demos/repl_demo.ex:312— lib/raxol/playground/demos/repl_demo.ex:312-315 | lib/raxol/playground/demos/vfs_demo.ex:326-329 — 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) scripts/harness/t0/ringb/drivers/iterm2.ex:171— scripts/harness/t0/ringb/drivers/iterm2.ex:171-174 | scripts/harness/t0/ringb/drivers/terminal_app.ex:175-178 — 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) lib/raxol/plugins/examples/command_palette_plugin.ex:263— lib/raxol/plugins/examples/command_palette_plugin.ex:263-266 | lib/raxol/plugins/examples/file_browser_plugin.ex:240-247 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×23
Edited copy of a member (7 corresponding lines) packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:63— packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:63-69 | packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:139-149 — 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) packages/raxol_gateway/lib/raxol/gateway/session_router.ex:401— packages/raxol_gateway/lib/raxol/gateway/session_router.ex:401-407 | packages/raxol_telegram/lib/raxol/telegram/session_router.ex:216-227 — 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) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:211— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:211-217 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:217-223 — 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) packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:101— packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:101-107 | packages/raxol_gateway/lib/raxol/gateway/adapter/discord/gateway_socket/mint_transport.ex:112-118 — 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) lib/raxol/ui/layout/engine.ex:318— lib/raxol/ui/layout/engine.ex:318-334 | lib/raxol/ui/layout/engine.ex:392-398 — 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) lib/raxol/core/metrics.ex:87— lib/raxol/core/metrics.ex:87-95 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_validator.ex:321-327 — 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) lib/raxol/core/runtime/component_manager.ex:152— lib/raxol/core/runtime/component_manager.ex:152-164 | packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:520-526 — 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) lib/raxol/ui/charts/braille_canvas.ex:80— lib/raxol/ui/charts/braille_canvas.ex:80-86 | lib/raxol/ui/charts/braille_canvas.ex:107-117 — 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) lib/raxol/ui/components/harness/markdown_body.ex:335— lib/raxol/ui/components/harness/markdown_body.ex:335-341 | packages/raxol_terminal/lib/raxol/terminal/event_processor.ex:110-122 — 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) lib/raxol/rbac.ex:54— lib/raxol/rbac.ex:54-60 | lib/raxol/rbac.ex:140-146 — 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) lib/raxol/commands/file_system.ex:172— lib/raxol/commands/file_system.ex:172-178 | lib/raxol/commands/file_system.ex:261-267 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:246— packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:246-252 | packages/raxol_terminal/lib/raxol/terminal/events/events_handler.ex:12-24 — 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) lib/raxol/ui/components/harness/line_diff.ex:38— lib/raxol/ui/components/harness/line_diff.ex:38-44 | lib/raxol/ui/components/harness/word_diff.ex:152-158 — 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) lib/raxol/liveview.ex:97— lib/raxol/liveview.ex:97-103 | packages/raxol_terminal/lib/raxol/terminal/extension/extension_manager.ex:307-313 — 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) lib/raxol/performance/profiler.ex:524— lib/raxol/performance/profiler.ex:524-532 | bench/suites/visualization/visualization_benchmark.ex:370-376 — 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) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:221— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:221-227 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:227-233 — 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) packages/raxol_mcp/lib/raxol/mcp/client/reference_server/legacy.ex:79— packages/raxol_mcp/lib/raxol/mcp/client/reference_server/legacy.ex:79-87 | packages/raxol_mcp/lib/raxol/mcp/client/reference_server/modern.ex:74-80 — 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) lib/raxol/config/generator.ex:466— lib/raxol/config/generator.ex:466-473 | lib/raxol/config/loader.ex:466-472 — 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) lib/raxol/animation/gestures/gesture_server.ex:91— lib/raxol/animation/gestures/gesture_server.ex:91-97 | lib/raxol/ui/state/management/state_management_server.ex:91-97 — 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) lib/raxol/animation/gestures/gesture_server.ex:161— lib/raxol/animation/gestures/gesture_server.ex:161-167 | lib/raxol/ui/state/management/state_management_server.ex:111-117 — 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) lib/raxol/core/renderer_compat.ex:257— lib/raxol/core/renderer_compat.ex:257-263 | packages/raxol_terminal/lib/raxol/terminal/renderer.ex:284-290 — 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) lib/raxol/ui/state/management/state_management_server.ex:35— lib/raxol/ui/state/management/state_management_server.ex:35-41 | packages/raxol_terminal/lib/raxol/terminal/session.ex:162-168 — 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) lib/raxol/demo/particles.ex:88— lib/raxol/demo/particles.ex:88-94 | lib/raxol/demo/particles.ex:180-186 — 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 (11 corresponding lines) · ×20
Edited copy of a member (11 corresponding lines) lib/raxol/scoreboard.ex:391— lib/raxol/scoreboard.ex:391-401 | lib/raxol/scoreboard.ex:448-468 — 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) packages/raxol_mcp/lib/raxol/mcp/server.ex:1513— packages/raxol_mcp/lib/raxol/mcp/server.ex:1513-1527 | packages/raxol_mcp/lib/raxol/mcp/server.ex:1539-1549 — 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) lib/raxol/ui/components/display/status_bar.ex:25— lib/raxol/ui/components/display/status_bar.ex:25-36 | lib/raxol/ui/components/input/tabs.ex:35-45 — 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) lib/raxol/ui/text_layout.ex:141— lib/raxol/ui/text_layout.ex:141-154 | lib/raxol/ui/text_layout.ex:165-175 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:79— packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:79-89 | packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:105-115 — 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) packages/raxol_mcp/lib/raxol/mcp/registry.ex:508— packages/raxol_mcp/lib/raxol/mcp/registry.ex:508-518 | packages/raxol_mcp/lib/raxol/mcp/registry.ex:527-537 — 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) lib/raxol/rbac.ex:74— lib/raxol/rbac.ex:74-84 | lib/raxol/rbac.ex:96-109 — 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) packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:72— packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:72-82 | packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:92-102 — 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) lib/raxol/effects/border_beam/effect.ex:80— lib/raxol/effects/border_beam/effect.ex:80-90 | lib/raxol/effects/border_beam/effect.ex:109-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) packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:787— packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:787-799 | packages/raxol_journal/lib/raxol/agent/journal/records/checkpoint/file_backend.ex:602-612 — 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) packages/raxol_mcp/lib/raxol/mcp/server.ex:1334— packages/raxol_mcp/lib/raxol/mcp/server.ex:1334-1344 | packages/raxol_mcp/lib/raxol/mcp/server.ex:1349-1369 — 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) packages/raxol_core/lib/raxol/core/keyboard_navigator/navigator_server.ex:215— packages/raxol_core/lib/raxol/core/keyboard_navigator/navigator_server.ex:215-227 | packages/raxol_terminal/lib/raxol/terminal/window/manager/navigation_ops.ex:11-21 — 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) packages/raxol_terminal/lib/raxol/terminal/input/input_buffer.ex:161— packages/raxol_terminal/lib/raxol/terminal/input/input_buffer.ex:161-171 | packages/raxol_terminal/lib/raxol/terminal/input/input_buffer.ex:178-188 — 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) lib/raxol/style/colors/accessibility.ex:179— lib/raxol/style/colors/accessibility.ex:179-189 | lib/raxol/style/colors/utilities.ex:181-191 — 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) packages/raxol_core/lib/raxol/core/telemetry/context.ex:300— packages/raxol_core/lib/raxol/core/telemetry/context.ex:300-310 | packages/raxol_core/lib/raxol/core/telemetry/trace_context.ex:334-344 — 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) lib/raxol/plugins/examples/file_browser_plugin.ex:415— lib/raxol/plugins/examples/file_browser_plugin.ex:415-425 | lib/raxol/plugins/examples/file_browser_plugin.ex:454-466 — 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) lib/raxol/playground/demos/panel_highlights_demo.ex:93— lib/raxol/playground/demos/panel_highlights_demo.ex:93-105 | lib/raxol/playground/demos/panel_highlights_demo.ex:111-121 — 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) bench/suites/kitty_graphics_benchmark.exs:316— bench/suites/kitty_graphics_benchmark.exs:316-328 | bench/suites/kitty_graphics_benchmark.exs:332-342 — 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) lib/raxol/plugins/examples/terminal_multiplexer/pane_manager.ex:176— lib/raxol/plugins/examples/terminal_multiplexer/pane_manager.ex:176-186 | lib/raxol/plugins/examples/terminal_multiplexer/pane_manager.ex:190-200 — 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) lib/raxol/harness/fixture.ex:218— lib/raxol/harness/fixture.ex:218-231 | lib/raxol/harness/fixture.ex:339-349 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×20
Edited copy of a member (3 corresponding lines) lib/raxol/ui/cell_dim.ex:175— lib/raxol/ui/cell_dim.ex:175-177 | lib/raxol/ui/color_resolver.ex:923-925 — 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) lib/raxol/ui/components/display/progress.ex:175— lib/raxol/ui/components/display/progress.ex:175-177 | lib/raxol/ui/components/input/scrubber.ex:657-659 — 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) lib/mix/tasks/raxol.gen.component.ex:95— lib/mix/tasks/raxol.gen.component.ex:95-97 | lib/mix/tasks/raxol/generator.ex:162-165 — 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) web/lib/raxol_playground_web/components/landing_components.ex:976— web/lib/raxol_playground_web/components/landing_components.ex:976-978 | web/lib/raxol_playground_web/live/landing_live.ex:56-60 — 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) lib/raxol/core/runtime/rendering/backends.ex:186— lib/raxol/core/runtime/rendering/backends.ex:186-190 | packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_parser.ex:314-316 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:55— packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:55-63 | packages/raxol_terminal/lib/raxol/terminal/cursor.ex:35-37 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:131— packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/cursor.ex:131-139 | packages/raxol_terminal/lib/raxol/terminal/cursor.ex:62-64 — 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) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:49— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:49-51 | packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:53-55 — 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) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:53— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:53-55 | packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:57-59 — 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) lib/raxol/recording/index.ex:170— lib/raxol/recording/index.ex:170-172 | web/lib/raxol_playground_web/live/replay_live.ex:489-493 — 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) lib/raxol/ui/border_renderer.ex:166— lib/raxol/ui/border_renderer.ex:166-168 | lib/raxol/ui/charts/heatmap.ex:171-173 — 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) lib/raxol/animation/gestures/gesture_server.ex:212— lib/raxol/animation/gestures/gesture_server.ex:212-216 | lib/raxol/ui/state/management/state_management_server.ex:289-291 — 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) lib/mix/tasks/raxol.record.ex:79— lib/mix/tasks/raxol.record.ex:79-81 | lib/mix/tasks/raxol/templates.ex:77-87 — 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) lib/raxol/style/colors/accessibility.ex:111— lib/raxol/style/colors/accessibility.ex:111-113 | lib/raxol/ui/harness/prominence.ex:242-244 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/history.ex:34— packages/raxol_terminal/lib/raxol/terminal/commands/history.ex:34-37 | packages/raxol_terminal/lib/raxol/terminal/history_buffer.ex:28-30 — 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) lib/raxol/config/generator.ex:224— lib/raxol/config/generator.ex:224-226 | lib/raxol/config/loader.ex:437-439 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/mouse.ex:629— packages/raxol_terminal/lib/raxol/terminal/ansi/mouse.ex:629-631 | packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:431-436 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/mouse.ex:635— packages/raxol_terminal/lib/raxol/terminal/ansi/mouse.ex:635-637 | packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:447-452 — 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) examples/getting_started/todo_app.exs:222— examples/getting_started/todo_app.exs:222-228 | lib/raxol/demo/todo.ex:160-162 — 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) examples/demo.exs:675— examples/demo.exs:675-677 | lib/raxol/demo/dashboard.ex:449-451 — 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 (15 corresponding lines) · ×19
Edited copy of a member (15 corresponding lines) lib/raxol/style/colors/formats.ex:147— lib/raxol/style/colors/formats.ex:147-161 | lib/raxol/style/colors/formats.ex:165-181 — 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) packages/raxol_terminal/lib/raxol/terminal/input/input_processor.ex:78— packages/raxol_terminal/lib/raxol/terminal/input/input_processor.ex:78-92 | packages/raxol_terminal/lib/raxol/terminal/input/input_processor.ex:96-112 — 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) lib/raxol/workflow/runtime.ex:1040— lib/raxol/workflow/runtime.ex:1040-1054 | lib/raxol/workflow/runtime.ex:1569-1594 — 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) lib/raxol/harness/surface.ex:2527— lib/raxol/harness/surface.ex:2527-2544 | lib/raxol/harness/surface.ex:2611-2625 — 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) packages/raxol_terminal/lib/raxol/terminal/buffer/cell.ex:359— packages/raxol_terminal/lib/raxol/terminal/buffer/cell.ex:359-373 | packages/raxol_terminal/lib/raxol/terminal/buffer/cell.ex:377-391 — 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) lib/raxol/core/renderer/view/layout/flex.ex:30— lib/raxol/core/renderer/view/layout/flex.ex:30-44 | lib/raxol/core/renderer/view/layout/flex.ex:115-129 — 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) lib/raxol/ui/rendering/paint_authority/inline_authority.ex:1389— lib/raxol/ui/rendering/paint_authority/inline_authority.ex:1389-1403 | lib/raxol/ui/rendering/paint_authority/inline_authority.ex:1443-1460 — 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) lib/raxol/swarm/crdt/or_set.ex:89— lib/raxol/swarm/crdt/or_set.ex:89-103 | lib/raxol/swarm/tactical_overlay.ex:458-479 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_helper.ex:160— packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_helper.ex:160-174 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_helper.ex:184-198 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_lifecycle.ex:295— packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_lifecycle.ex:295-309 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_lifecycle.ex:313-327 — 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) lib/raxol/protocols/plugin_system_integration.ex:283— lib/raxol/protocols/plugin_system_integration.ex:283-297 | lib/raxol/protocols/theme_implementations.ex:235-252 — 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) packages/raxol_terminal/lib/raxol/terminal/session.ex:321— packages/raxol_terminal/lib/raxol/terminal/session.ex:321-335 | packages/raxol_terminal/lib/raxol/terminal/session.ex:339-358 — 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) packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:767— packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:767-781 | packages/raxol_journal/lib/raxol/agent/journal/records/checkpoint/file_backend.ex:584-598 — 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) lib/raxol/ui/components/input/multi_line_input.ex:193— lib/raxol/ui/components/input/multi_line_input.ex:193-207 | lib/raxol/ui/components/input/multi_line_input.ex:211-225 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/kitty_graphics.ex:103— packages/raxol_terminal/lib/raxol/terminal/ansi/kitty_graphics.ex:103-117 | packages/raxol_terminal/lib/raxol/terminal/ansi/kitty_graphics.ex:135-149 — 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) packages/raxol_terminal/lib/raxol/terminal/event_handler.ex:72— packages/raxol_terminal/lib/raxol/terminal/event_handler.ex:72-86 | packages/raxol_terminal/lib/raxol/terminal/event_handler.ex:91-105 — 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) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:71— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:71-85 | packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:118-134 — 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) lib/raxol/plugins/examples/git_integration_plugin.ex:288— lib/raxol/plugins/examples/git_integration_plugin.ex:288-302 | lib/raxol/plugins/examples/git_integration_plugin.ex:323-337 — 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) lib/raxol/plugins/testing/plugin_test_framework.ex:688— lib/raxol/plugins/testing/plugin_test_framework.ex:688-702 | lib/raxol/plugins/testing/plugin_test_framework.ex:706-720 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×19
Edited copy of a member (2 corresponding lines) lib/raxol/ui/components/input/checkbox.ex:153— lib/raxol/ui/components/input/checkbox.ex:153-154 | lib/raxol/ui/components/input/scrubber.ex:643-644 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/ui/components/input/checkbox.ex:158— lib/raxol/ui/components/input/checkbox.ex:158-159 | lib/raxol/ui/components/input/scrubber.ex:648-649 — 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.
Edited copy of a member (2 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/core.ex:192— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/core.ex:192-193 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/erase_operations.ex:283-284 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/effects/border_beam.ex:445— lib/raxol/effects/border_beam.ex:445-446 | lib/raxol/effects/cursor_trail.ex:326-327 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/harness/event_boundary.ex:154— lib/raxol/harness/event_boundary.ex:154-155 | lib/raxol/harness/surface.ex:1473-1474 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/ui/layout/layout_utils.ex:139— lib/raxol/ui/layout/layout_utils.ex:139-140 | lib/raxol/ui/terminal.ex:122-130 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/ui/charts/line_chart.ex:87— lib/raxol/ui/charts/line_chart.ex:87-88 | lib/raxol/ui/charts/scatter_chart.ex:87-88 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/ui/components/harness/line_diff.ex:88— lib/raxol/ui/components/harness/line_diff.ex:88-89 | lib/raxol/ui/components/harness/word_diff.ex:195-196 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/ui/components/harness/line_diff.ex:93— lib/raxol/ui/components/harness/line_diff.ex:93-94 | lib/raxol/ui/components/harness/word_diff.ex:200-201 — 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.
Edited copy of a member (2 corresponding lines) web/lib/raxol_playground_web/live/demo_live.ex:159— web/lib/raxol_playground_web/live/demo_live.ex:159-160 | web/lib/raxol_playground_web/live/playground_live.ex:237-238 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/effects/halo.ex:95— lib/raxol/effects/halo.ex:95-96 | lib/raxol/ui/layout/min_content.ex:123-124 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/ui/harness/overlay_panel.ex:184— lib/raxol/ui/harness/overlay_panel.ex:184-185 | lib/raxol/ui/rendering/paint_authority/viewport_authority.ex:260-261 — 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.
Edited copy of a member (2 corresponding lines) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:189— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:189-190 | packages/raxol_telegram/lib/raxol/telegram/http.ex:109-110 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/config.ex:307— lib/raxol/config.ex:307-309 | lib/raxol/config/loader.ex:447-448 — 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.
Edited copy of a member (2 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:63— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:63-64 | packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:67-68 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/harness/surface.ex:3203— lib/raxol/harness/surface.ex:3203-3204 | packages/raxol_mcp/lib/raxol/mcp/tree_walker.ex:559-560 — 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.
Edited copy of a member (2 corresponding lines) packages/raxol_core/lib/raxol/core/outbound.ex:291— packages/raxol_core/lib/raxol/core/outbound.ex:291-292 | packages/raxol_mcp/lib/raxol/mcp/authorizer.ex:83-84 — 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.
Edited copy of a member (2 corresponding lines) lib/raxol/playground/demos/repl_demo.ex:192— lib/raxol/playground/demos/repl_demo.ex:192-193 | lib/raxol/playground/demos/vfs_demo.ex:36-37 — 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.
Edited copy of a member (2 corresponding lines) examples/agents/zero_system.exs:321— examples/agents/zero_system.exs:321-325 | packages/raxol_telegram/examples/telegram_demo.exs:57-58 — 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 copy of a member (5 corresponding lines) · ×18
Edited copy of a member (5 corresponding lines) lib/raxol/effects/border_beam.ex:399— lib/raxol/effects/border_beam.ex:399-403 | lib/raxol/effects/border_beam/effect.ex:60-69 — 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) lib/raxol/style/colors/advanced.ex:36— lib/raxol/style/colors/advanced.ex:36-40 | packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:296-301 — 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) lib/raxol/harness/surface/parity.ex:386— lib/raxol/harness/surface/parity.ex:386-392 | lib/raxol/rate.ex:107-111 — 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) lib/raxol/ui/layout/engine.ex:1300— lib/raxol/ui/layout/engine.ex:1300-1304 | lib/raxol/ui/layout/style_inheritance.ex:54-58 — 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) lib/raxol/rate.ex:65— lib/raxol/rate.ex:65-69 | lib/raxol/scoreboard.ex:209-216 — 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) packages/raxol_gateway/lib/raxol/gateway/handler/lifecycle.ex:229— packages/raxol_gateway/lib/raxol/gateway/handler/lifecycle.ex:229-233 | packages/raxol_telegram/lib/raxol/telegram/input_adapter.ex:78-89 — 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) lib/mix/tasks/raxol/generator.ex:148— lib/mix/tasks/raxol/generator.ex:148-158 | lib/mix/tasks/raxol.gen.component.ex:51-55 — 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) lib/raxol/animation/state_server.ex:210— lib/raxol/animation/state_server.ex:210-219 | packages/raxol_core/lib/raxol/core/navigation_utils.ex:12-16 — 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) lib/raxol/ui/theming/colors.ex:65— lib/raxol/ui/theming/colors.ex:65-74 | lib/raxol/utils/color_conversion.ex:42-46 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:39— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:39-43 | packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:264-268 — 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) lib/raxol/demo/dashboard.ex:66— lib/raxol/demo/dashboard.ex:66-71 | lib/raxol/debug/debugger_app.ex:130-134 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:47— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:47-51 | packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:281-285 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:31— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:31-35 | packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:235-239 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:55— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/cursor.ex:55-59 | packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:252-256 — 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) lib/raxol/ui/components/harness/block.ex:756— lib/raxol/ui/components/harness/block.ex:756-761 | lib/raxol/ui/components/harness/tool_call_block.ex:109-113 — 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) lib/raxol/system/platform.ex:24— lib/raxol/system/platform.ex:24-28 | scripts/dev/release.exs:99-104 — 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) packages/raxol_core/lib/raxol/core/runtime/backpressure.ex:98— packages/raxol_core/lib/raxol/core/runtime/backpressure.ex:98-102 | packages/raxol_core/lib/raxol/core/runtime/plugins/resource_budget.ex:347-356 — 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) bench/memory/load_memory_benchmark.exs:62— bench/memory/load_memory_benchmark.exs:62-66 | bench/memory/terminal_memory_benchmark.exs:54-63 — 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×18
Edited copy of a member (9 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/integration/integration_renderer.ex:232— packages/raxol_terminal/lib/raxol/terminal/integration/integration_renderer.ex:232-240 | packages/raxol_terminal/lib/raxol/terminal/integration/integration_renderer.ex:244-252 — 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) lib/raxol/effects/cursor_trail.ex:366— lib/raxol/effects/cursor_trail.ex:366-374 | lib/raxol/ui/charts/line_chart.ex:152-168 — 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) lib/raxol/core/terminal/osc/handlers/color_palette.ex:291— lib/raxol/core/terminal/osc/handlers/color_palette.ex:291-299 | lib/raxol/core/terminal/osc/handlers/color_palette.ex:309-317 — 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) lib/mix/tasks/raxol.flamegraph.ex:265— lib/mix/tasks/raxol.flamegraph.ex:265-273 | lib/mix/tasks/raxol.flamegraph.ex:277-286 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:388— packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:388-401 | packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:666-674 — 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) packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:15— packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:15-23 | packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:30-39 — 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) lib/raxol/swarm/topology.ex:179— lib/raxol/swarm/topology.ex:179-187 | lib/raxol/swarm/topology.ex:208-217 — 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) lib/raxol/core/renderer/views/chart.ex:253— lib/raxol/core/renderer/views/chart.ex:253-261 | lib/raxol/core/renderer/views/chart.ex:265-273 — 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) packages/raxol_terminal/lib/raxol/terminal/event_processor.ex:164— packages/raxol_terminal/lib/raxol/terminal/event_processor.ex:164-174 | packages/raxol_terminal/lib/raxol/terminal/event_processor.ex:196-204 — 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) lib/raxol/heex.ex:256— lib/raxol/heex.ex:256-265 | lib/raxol/heex.ex:269-277 — 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) packages/raxol_core/lib/raxol/core/accessibility/accessibility_server.ex:387— packages/raxol_core/lib/raxol/core/accessibility/accessibility_server.ex:387-395 | packages/raxol_core/lib/raxol/core/accessibility/accessibility_server.ex:404-412 — 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) lib/mix/tasks/raxol.ex:55— lib/mix/tasks/raxol.ex:55-65 | lib/mix/tasks/raxol.ex:75-83 — 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) packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:410— packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:410-424 | packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:456-464 — 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) packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:392— packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:392-400 | packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:458-468 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/registry.ex:129— packages/raxol_terminal/lib/raxol/terminal/commands/registry.ex:129-137 | packages/raxol_terminal/lib/raxol/terminal/plugin/terminal_plugin_manager.ex:170-186 — 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) lib/mix/tasks/raxol.release.check.ex:36— lib/mix/tasks/raxol.release.check.ex:36-46 | lib/mix/tasks/raxol.scoreboard.ex:57-65 — 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) lib/raxol/plugins/event_handler/common.ex:134— lib/raxol/plugins/event_handler/common.ex:134-142 | lib/raxol/plugins/lifecycle/error_handling.ex:119-127 — 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) examples/scripts/subscriptions.exs:53— examples/scripts/subscriptions.exs:53-66 | examples/advanced/architecture/architecture_demo.exs:105-113 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×17
Edited copy of a member (16 corresponding lines) lib/raxol/ui/charts/line_chart.ex:67— lib/raxol/ui/charts/line_chart.ex:67-82 | lib/raxol/ui/charts/scatter_chart.ex:67-82 — 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) lib/raxol/ui/layout/split_pane.ex:210— lib/raxol/ui/layout/split_pane.ex:210-225 | lib/raxol/ui/layout/split_pane/resize.ex:117-141 — 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) lib/raxol/ui/components/input/menu.ex:263— lib/raxol/ui/components/input/menu.ex:263-278 | lib/raxol/ui/components/input/menu.ex:294-316 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:221— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:221-237 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:241-256 — 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) packages/raxol_mcp/lib/raxol/mcp/structured_screenshot.ex:95— packages/raxol_mcp/lib/raxol/mcp/structured_screenshot.ex:95-110 | packages/raxol_mcp/lib/raxol/mcp/tree_walker.ex:419-434 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_graphics.ex:599— packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_graphics.ex:599-628 | packages/raxol_terminal/lib/raxol/terminal/input/clipboard_handler.ex:251-266 — 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) lib/raxol/core/runtime/rendering/engine.ex:257— lib/raxol/core/runtime/rendering/engine.ex:257-272 | lib/raxol/core/runtime/rendering/engine.ex:295-317 — 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) packages/raxol_terminal/lib/raxol/terminal/tab/window_integration.ex:19— packages/raxol_terminal/lib/raxol/terminal/tab/window_integration.ex:19-35 | packages/raxol_terminal/lib/raxol/terminal/tab/window_integration.ex:53-68 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/device_ops.ex:29— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/device_ops.ex:29-44 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:274-299 — 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) lib/raxol/core/runtime/application.ex:228— lib/raxol/core/runtime/application.ex:228-249 | lib/raxol/core/runtime/events/dispatcher.ex:118-133 — 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) packages/raxol_terminal/lib/raxol/terminal/plugin/terminal_plugin_manager.ex:91— packages/raxol_terminal/lib/raxol/terminal/plugin/terminal_plugin_manager.ex:91-107 | packages/raxol_terminal/lib/raxol/terminal/plugin/terminal_plugin_manager.ex:141-156 — 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) lib/raxol/core/runtime/rendering/engine.ex:533— lib/raxol/core/runtime/rendering/engine.ex:533-548 | lib/raxol/core/runtime/rendering/engine.ex:553-569 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/character_sets/handler.ex:101— packages/raxol_terminal/lib/raxol/terminal/ansi/character_sets/handler.ex:101-119 | packages/raxol_terminal/lib/raxol/terminal/ansi/character_sets/state_manager.ex:371-386 — 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) lib/raxol/ui/components/harness/diff_viewer.ex:1087— lib/raxol/ui/components/harness/diff_viewer.ex:1087-1102 | lib/raxol/ui/components/harness/diff_viewer.ex:1141-1156 — 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) examples/harness_fixture_demo.exs:107— examples/harness_fixture_demo.exs:107-122 | examples/harness_fixture_demo.exs:134-152 — 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) lib/raxol/playground/demos/easing_demo.ex:147— lib/raxol/playground/demos/easing_demo.ex:147-162 | lib/raxol/playground/demos/focus_ring_demo.ex:68-84 — 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) examples/demo.exs:164— examples/demo.exs:164-179 | lib/raxol/demo/dashboard.ex:124-139 — 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 (13 corresponding lines) · ×17
Edited copy of a member (13 corresponding lines) lib/raxol/debug/debugger_app.ex:196— lib/raxol/debug/debugger_app.ex:196-208 | lib/raxol/playground/app.ex:178-193 — 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) lib/raxol/core/renderer/color.ex:217— lib/raxol/core/renderer/color.ex:217-235 | lib/raxol/ui/theming/palette.ex:592-604 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_runtime.ex:196— packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_runtime.ex:196-208 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_runtime.ex:258-270 — 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) packages/raxol_watch/lib/raxol/watch/push/apns.ex:28— packages/raxol_watch/lib/raxol/watch/push/apns.ex:28-41 | packages/raxol_watch/lib/raxol/watch/push/fcm.ex:22-34 — 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) lib/raxol/ui/layout/flexbox/positioner.ex:46— lib/raxol/ui/layout/flexbox/positioner.ex:46-58 | lib/raxol/ui/layout/flexbox/positioner.ex:260-275 — 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) packages/raxol_terminal/lib/raxol/terminal/advanced_features.ex:474— packages/raxol_terminal/lib/raxol/terminal/advanced_features.ex:474-486 | packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/colors.ex:244-256 — 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) lib/raxol/navigation/vim.ex:126— lib/raxol/navigation/vim.ex:126-138 | lib/raxol/navigation/vim.ex:158-172 — 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) packages/raxol_mcp/lib/raxol/mcp/registry.ex:304— packages/raxol_mcp/lib/raxol/mcp/registry.ex:304-316 | packages/raxol_mcp/lib/raxol/mcp/registry.ex:415-427 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:184— packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:184-197 | packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:206-218 — 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) lib/raxol/ui/rendering/renderer.ex:195— lib/raxol/ui/rendering/renderer.ex:195-212 | lib/raxol/ui/rendering/renderer.ex:229-241 — 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) packages/raxol_terminal/lib/raxol/terminal/event/event_handler.ex:21— packages/raxol_terminal/lib/raxol/terminal/event/event_handler.ex:21-33 | packages/raxol_terminal/lib/raxol/terminal/event/event_handler.ex:37-49 — 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) packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:234— packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:234-246 | packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:255-267 — 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) examples/harness_fixture_demo.exs:180— examples/harness_fixture_demo.exs:180-192 | lib/raxol/recording/session.ex:83-95 — 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) lib/mix/tasks/raxol.memory.profiler.ex:229— lib/mix/tasks/raxol.memory.profiler.ex:229-248 | lib/mix/tasks/raxol.mutation.ex:508-520 — 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) lib/raxol/playground/demos/line_chart_demo.ex:25— lib/raxol/playground/demos/line_chart_demo.ex:25-40 | lib/raxol/playground/demos/scatter_chart_demo.ex:36-48 — 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) lib/raxol/plugins/examples/rainbow_theme_plugin.ex:200— lib/raxol/plugins/examples/rainbow_theme_plugin.ex:200-212 | lib/raxol/plugins/examples/rainbow_theme_plugin.ex:256-270 — 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) lib/raxol/bench/dashboard.ex:229— lib/raxol/bench/dashboard.ex:229-242 | lib/raxol/bench/dashboard.ex:275-287 — 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 (6 corresponding lines) · ×17
Edited copy of a member (6 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/input/input_processor.ex:60— packages/raxol_terminal/lib/raxol/terminal/input/input_processor.ex:60-65 | packages/raxol_terminal/lib/raxol/terminal/input/input_processor.ex:69-74 — 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) bench/core/scoreboard_legacy.exs:244— bench/core/scoreboard_legacy.exs:244-251 | lib/raxol/scoreboard.ex:439-444 — 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) lib/raxol/demo/effects.ex:116— lib/raxol/demo/effects.ex:116-121 | packages/raxol_terminal/lib/raxol/terminal/color/true_color/conversion.ex:11-17 — 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) packages/raxol_terminal/lib/raxol/terminal/buffer/line_operations/deletion.ex:58— packages/raxol_terminal/lib/raxol/terminal/buffer/line_operations/deletion.ex:58-63 | packages/raxol_terminal/lib/raxol/terminal/buffer/line_operations/insertion.ex:78-84 — 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) lib/mix/tasks/raxol.flamegraph.ex:114— lib/mix/tasks/raxol.flamegraph.ex:114-119 | lib/mix/tasks/raxol.memory.gates.ex:600-609 — 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) lib/raxol/ui/components/input/text_input.ex:349— lib/raxol/ui/components/input/text_input.ex:349-363 | lib/raxol/ui/components/input/text_input.ex:444-449 — 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) lib/raxol/ui/components/input/menu.ex:228— lib/raxol/ui/components/input/menu.ex:228-236 | lib/raxol/ui/components/input/menu.ex:240-245 — 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) lib/mix/tasks/raxol.demo.ex:91— lib/mix/tasks/raxol.demo.ex:91-96 | lib/mix/tasks/raxol/templates.ex:53-59 — 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) lib/raxol/style/colors/system.ex:175— lib/raxol/style/colors/system.ex:175-188 | lib/raxol/style/colors/system/color_system_server.ex:606-611 — 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) packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:349— packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:349-354 | lib/raxol/style/colors/utilities.ex:69-76 — 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) lib/raxol/ui/components/display/text.ex:272— lib/raxol/ui/components/display/text.ex:272-279 | lib/raxol/core/renderer/views/table.ex:364-369 — 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) lib/mix/tasks/raxol.playground.ex:48— lib/mix/tasks/raxol.playground.ex:48-53 | lib/raxol/release.ex:17-23 — 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) lib/raxol/playground/demos/status_bar_demo.ex:90— lib/raxol/playground/demos/status_bar_demo.ex:90-95 | lib/raxol/ui/components/harness/status_bar.ex:62-67 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/command_registry.ex:226— packages/raxol_core/lib/raxol/core/runtime/plugins/command_registry.ex:226-231 | packages/raxol_terminal/lib/raxol/terminal/config/config_validator.ex:63-68 — 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) lib/raxol/core/runtime/lifecycle/shutdown.ex:51— lib/raxol/core/runtime/lifecycle/shutdown.ex:51-56 | lib/raxol/headless.ex:1706-1714 — 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) examples/getting_started/todo_app.exs:209— examples/getting_started/todo_app.exs:209-218 | lib/raxol/demo/todo.ex:149-154 — 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) scripts/harness/t0/ringb/drivers/iterm2.ex:123— scripts/harness/t0/ringb/drivers/iterm2.ex:123-128 | scripts/harness/t0/ringb/drivers/terminal_app.ex:156-161 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×17
Edited copy of a member (12 corresponding lines) lib/raxol/minimal.ex:501— lib/raxol/minimal.ex:501-514 | lib/raxol/minimal.ex:518-529 — 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) lib/raxol/debug/time_travel.ex:225— lib/raxol/debug/time_travel.ex:225-236 | lib/raxol/debug/time_travel.ex:240-251 — 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) packages/raxol_speech/lib/raxol/speech/speaker.ex:41— packages/raxol_speech/lib/raxol/speech/speaker.ex:41-53 | packages/raxol_watch/lib/raxol/watch/notifier.ex:63-74 — 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) lib/raxol/performance/cycle_profiler/stats.ex:30— lib/raxol/performance/cycle_profiler/stats.ex:30-41 | packages/raxol_terminal/lib/raxol/terminal/metrics/metrics_server.ex:429-441 — 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) lib/mix/tasks/raxol.memory.debug.ex:146— lib/mix/tasks/raxol.memory.debug.ex:146-158 | lib/mix/tasks/raxol.memory.debug.ex:162-173 — 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) packages/raxol_terminal/lib/raxol/terminal/history_buffer.ex:72— packages/raxol_terminal/lib/raxol/terminal/history_buffer.ex:72-83 | packages/raxol_terminal/lib/raxol/terminal/history_buffer.ex:91-102 — 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) lib/raxol/ui/layout/elements.ex:36— lib/raxol/ui/layout/elements.ex:36-47 | lib/raxol/ui/layout/elements.ex:57-69 — 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) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:154— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:154-165 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:162-173 — 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) lib/raxol/security/user_context/context_server.ex:127— lib/raxol/security/user_context/context_server.ex:127-138 | lib/raxol/security/user_context/context_server.ex:168-180 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:162— packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:162-173 | packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:187-198 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:47— packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:47-58 | packages/raxol_terminal/lib/raxol/terminal/ansi/window.ex:353-370 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:405— packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:405-418 | packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:475-486 — 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) packages/raxol_terminal/lib/raxol/terminal/integration/integration_renderer.ex:395— packages/raxol_terminal/lib/raxol/terminal/integration/integration_renderer.ex:395-412 | lib/raxol/core/runtime/lifecycle.ex:892-903 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:22— packages/raxol_terminal/lib/raxol/terminal/commands/cursor_handler.ex:22-35 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/cursor_ops.ex:64-75 — 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) lib/raxol/core/core.ex:227— lib/raxol/core/core.ex:227-241 | lib/raxol/ui/components/dashboard/layout_persistence.ex:47-58 — 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) examples/dev/hot_reload_demo.exs:23— examples/dev/hot_reload_demo.exs:23-41 | examples/ssh/ssh_counter.exs:33-45 — 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) lib/raxol/playground/demos/markdown_demo.ex:186— lib/raxol/playground/demos/markdown_demo.ex:186-200 | lib/raxol/playground/demos/text_demo.ex:36-47 — 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.
Duplicated block (8 lines × 2) lib/raxol/core/renderer/view/layout/flex.ex:30— lib/raxol/core/renderer/view/layout/flex.ex:30-37 | lib/raxol/core/renderer/view/layout/flex.ex:115-122 — 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 `lib/raxol/core/renderer/view/layout/flex.ex:30` 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 (8 lines × 2) lib/raxol/core/runtime/lifecycle.ex:264— lib/raxol/core/runtime/lifecycle.ex:264-271 | lib/raxol/core/runtime/lifecycle/initializer.ex:238-245 — 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, `lib/raxol/core/runtime/lifecycle.ex:263` calls `get_app_name` and `lib/raxol/core/runtime/lifecycle/initializer.ex:237` 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 (8 lines × 2) lib/raxol/effects/border_beam.ex:275— lib/raxol/effects/border_beam.ex:275-282 | lib/raxol/effects/border_beam.ex:328-335 — 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 `lib/raxol/effects/border_beam.ex:275` 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 (8 lines × 2) lib/raxol/ui/charts/bar_chart.ex:549— lib/raxol/ui/charts/bar_chart.ex:549-556 | lib/raxol/ui/charts/line_chart.ex:212-219 — 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) lib/raxol/ui/charts/line_chart.ex:75— lib/raxol/ui/charts/line_chart.ex:75-82 | lib/raxol/ui/charts/scatter_chart.ex:75-82 — 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 `lib/raxol/ui/charts/line_chart.ex:75` 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) lib/raxol/ui/components/harness/line_diff.ex:64— lib/raxol/ui/components/harness/line_diff.ex:64-71 | lib/raxol/ui/components/harness/word_diff.ex:171-178 — before extracting anything, compare `lib/raxol/ui/components/harness/line_diff.ex` and `lib/raxol/ui/components/harness/word_diff.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/raxol/ui/style_processor.ex:278— lib/raxol/ui/style_processor.ex:278-285 | lib/raxol/ui/theme_resolver.ex:44-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 (8 lines × 2) packages/raxol_terminal/lib/raxol/terminal/buffer/char_editor.ex:518— packages/raxol_terminal/lib/raxol/terminal/buffer/char_editor.ex:518-525 | packages/raxol_terminal/lib/raxol/terminal/buffer/char_editor.ex:539-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:82— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:82-89 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:107-114 — 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) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:140— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:140-147 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:163-170 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:95— packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:95-102 | packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:123-130 — 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 `packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:95` 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) lib/mix/tasks/raxol.bench.ex:347— lib/mix/tasks/raxol.bench.ex:347-354 | lib/mix/tasks/raxol.bench.memory_analysis.ex:267-274 — 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) lib/mix/tasks/raxol.memory.profiler.ex:626— lib/mix/tasks/raxol.memory.profiler.ex:626-633 | lib/mix/tasks/raxol.memory.stability.ex:413-420 — 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) lib/raxol/harness/surface/view_text.ex:296— lib/raxol/harness/surface/view_text.ex:296-303 | lib/raxol/ui/components/harness/text_util.ex:18-25 — 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) examples/advanced/documentation_browser.exs:39— examples/advanced/documentation_browser.exs:39-46 | examples/advanced/documentation_browser.exs:50-57 — 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) examples/apps/showcase_app.exs:231— examples/apps/showcase_app.exs:231-238 | lib/raxol/demo/showcase.ex:243-250 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/apps/showcase_app.exs:231` 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 (8 lines × 2) lib/raxol/playground/demos/harness_approval_demo.ex:129— lib/raxol/playground/demos/harness_approval_demo.ex:129-136 | lib/raxol/playground/demos/modal_demo.ex:107-114 — 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) lib/raxol/core/renderer/views/chart.ex:253— lib/raxol/core/renderer/views/chart.ex:253-259 | lib/raxol/core/renderer/views/chart.ex:265-271 — 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 `lib/raxol/core/renderer/views/chart.ex:253` 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 (7 lines × 2) lib/raxol/swarm/topology.ex:179— lib/raxol/swarm/topology.ex:179-185 | lib/raxol/swarm/topology.ex:208-214 — 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, `lib/raxol/swarm/topology.ex:215` calls `run_election` and `lib/raxol/swarm/topology.ex:186` 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.
Duplicated block (7 lines × 2) packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:363— packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:363-373 | packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:419-425 — 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 `packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:363` 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 (7 lines × 2) lib/raxol/workflow/graph.ex:471— lib/raxol/workflow/graph.ex:471-477 | lib/raxol/workflow/graph.ex:481-487 — 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) lib/raxol/debug/diff_formatter.ex:101— lib/raxol/debug/diff_formatter.ex:101-107 | lib/raxol/debug/inspector.ex:108-114 — 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) packages/raxol_core/lib/raxol/core/runtime/plugins/loader.ex:145— packages/raxol_core/lib/raxol/core/runtime/plugins/loader.ex:145-151 | packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:114-120 — 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 `packages/raxol_core/lib/raxol/core/runtime/plugins/loader.ex:145` 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 (7 lines × 2) packages/raxol_core/lib/raxol/core/runtime/plugins/manifest.ex:187— packages/raxol_core/lib/raxol/core/runtime/plugins/manifest.ex:187-193 | packages/raxol_plugin/lib/raxol/plugin/manifest.ex:158-164 — 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) web/lib/raxol_playground_web/live/demo_live.ex:123— web/lib/raxol_playground_web/live/demo_live.ex:123-129 | web/lib/raxol_playground_web/live/playground_live.ex:193-199 — 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) lib/mix/tasks/raxol.bench.advanced.ex:475— lib/mix/tasks/raxol.bench.advanced.ex:475-481 | lib/mix/tasks/raxol.memory.gates.ex:579-587 — 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) packages/raxol_mcp/lib/raxol/mcp/protocol.ex:227— packages/raxol_mcp/lib/raxol/mcp/protocol.ex:227-233 | packages/raxol_mcp/lib/raxol/mcp/transport/sse.ex:237-243 — 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) packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:43— packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:43-49 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/selection.ex:33-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/buffer/selection.ex:43` 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 (7 lines × 2) packages/raxol_terminal/lib/raxol/terminal/modes/handlers/screen_buffer_handler.ex:26— packages/raxol_terminal/lib/raxol/terminal/modes/handlers/screen_buffer_handler.ex:26-32 | packages/raxol_terminal/lib/raxol/terminal/modes/handlers/standard_handler.ex:16-22 — 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 `packages/raxol_terminal/lib/raxol/terminal/modes/handlers/screen_buffer_handler.ex:26` 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 (7 lines × 2) examples/components/displays/viewport_demo.exs:48— examples/components/displays/viewport_demo.exs:48-54 | lib/raxol/playground/demos/scroll_anchor_demo.ex:53-59 — 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) lib/raxol/plugins/examples/rainbow_theme_plugin.ex:200— lib/raxol/plugins/examples/rainbow_theme_plugin.ex:200-206 | lib/raxol/plugins/examples/rainbow_theme_plugin.ex:256-264 — 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 `lib/raxol/plugins/examples/rainbow_theme_plugin.ex:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) scripts/harness/t0/ringb/measurements.ex:167— scripts/harness/t0/ringb/measurements.ex:167-173 | scripts/harness/t0/ringb/measurements.ex:360-366 — 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 `scripts/harness/t0/ringb/measurements.ex:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) bench/core/box_benchmark.exs:29— bench/core/box_benchmark.exs:29-35 | bench/core/comprehensive_benchmark.exs:204-210 — 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 `bench/core/box_benchmark.exs:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) lib/raxol/demo/particles.ex:311— lib/raxol/demo/particles.ex:311-317 | lib/raxol/demo/text_formation.ex:229-235 — 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 `lib/raxol/demo/particles.ex:311` 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.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:5— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:6— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:7— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:8— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:9— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:10— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:11— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:12— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:13— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:14— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:15— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:16— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:17— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:18— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:19— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (4.0:1) web/priv/demo_previews/heatmap.html:20— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:5— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:6— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:7— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:8— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:9— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:10— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:11— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:12— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:13— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:14— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:15— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:16— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:17— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:18— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:19— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (1.4:1) web/priv/demo_previews/heatmap.html:20— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×15
Edited copy of a member (17 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/buffer/line_operations/deletion.ex:18— packages/raxol_terminal/lib/raxol/terminal/buffer/line_operations/deletion.ex:18-34 | packages/raxol_terminal/lib/raxol/terminal/buffer/line_operations/insertion.ex:38-55 — 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) lib/raxol/memory/collector.ex:29— lib/raxol/memory/collector.ex:29-46 | lib/raxol/memory/collector.ex:51-67 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_graphics.ex:124— packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_graphics.ex:124-140 | packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_graphics.ex:159-175 — 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) lib/mix/tasks/raxol.harness.goldens.bless.ex:43— lib/mix/tasks/raxol.harness.goldens.bless.ex:43-59 | lib/mix/tasks/raxol.harness.parity.bless.ex:35-52 — 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) lib/raxol/style/colors/system.ex:229— lib/raxol/style/colors/system.ex:229-245 | lib/raxol/style/colors/system.ex:249-265 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:132— packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:132-148 | packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:152-169 — 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) lib/raxol/ui/components/input/text_field.ex:212— lib/raxol/ui/components/input/text_field.ex:212-231 | lib/raxol/ui/components/input/text_field.ex:235-251 — 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) lib/raxol/core/renderer/views/table.ex:235— lib/raxol/core/renderer/views/table.ex:235-251 | lib/raxol/core/renderer/views/table.ex:278-294 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler.ex:131— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler.ex:131-147 | packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler.ex:151-167 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/mode_operations.ex:17— packages/raxol_terminal/lib/raxol/terminal/emulator/mode_operations.ex:17-35 | packages/raxol_terminal/lib/raxol/terminal/emulator/mode_operations.ex:43-59 — 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) packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:257— packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:257-273 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:277-293 — 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) packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:99— packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:99-115 | packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:328-344 — 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) examples/demo.exs:57— examples/demo.exs:57-78 | lib/raxol/demo/dashboard.ex:31-47 — 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) bench/memory/load_memory_benchmark.exs:31— bench/memory/load_memory_benchmark.exs:31-47 | bench/memory/plugin_memory_benchmark.exs:31-49 — 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) lib/raxol/plugins/examples/status_line_plugin.ex:61— lib/raxol/plugins/examples/status_line_plugin.ex:61-80 | lib/raxol/plugins/examples/status_line_plugin.ex:94-110 — 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.
Duplicated block (6 lines × 2) packages/raxol_terminal/lib/raxol/terminal/commands/parameter_validation.ex:85— packages/raxol_terminal/lib/raxol/terminal/commands/parameter_validation.ex:85-90 | packages/raxol_terminal/lib/raxol/terminal/commands/parameter_validation.ex:101-106 — 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 `packages/raxol_terminal/lib/raxol/terminal/commands/parameter_validation.ex:85` 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 (6 lines × 2) packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:15— packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:15-20 | packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:30-35 — 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 `packages/raxol_terminal/lib/raxol/terminal/window/manager/state_ops.ex:15` 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) lib/raxol/animation/helpers.ex:164— lib/raxol/animation/helpers.ex:164-169 | lib/raxol/core/renderer/view/components/box.ex:92-97 — 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 `lib/raxol/animation/helpers.ex:164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) lib/raxol/ui/components/harness/line_diff.ex:55— lib/raxol/ui/components/harness/line_diff.ex:55-60 | lib/raxol/ui/components/harness/word_diff.ex:162-167 — before extracting anything, compare `lib/raxol/ui/components/harness/line_diff.ex` and `lib/raxol/ui/components/harness/word_diff.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/raxol/ui/components/harness/line_diff.ex:47` calls `lines`, `split` and `lib/raxol/ui/components/harness/word_diff.ex:159` 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) packages/raxol_terminal/lib/raxol/terminal/commands/command_server.ex:288— packages/raxol_terminal/lib/raxol/terminal/commands/command_server.ex:288-293 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/helpers.ex:11-16 — 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 `packages/raxol_terminal/lib/raxol/terminal/commands/command_server.ex:288` 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 (6 lines × 2) web/lib/raxol_playground_web/live/demo_live.ex:114— web/lib/raxol_playground_web/live/demo_live.ex:114-119 | web/lib/raxol_playground_web/live/playground_live.ex:184-189 — 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 (6 lines × 2) lib/raxol/protocols/component_framework.ex:330— lib/raxol/protocols/component_framework.ex:330-335 | lib/raxol/protocols/event_system_integration.ex:167-172 — 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 (6 lines × 2) lib/raxol/effects/border_beam/css.ex:21— lib/raxol/effects/border_beam/css.ex:21-26 | packages/raxol_liveview/lib/raxol/live_view/terminal_bridge.ex:535-540 — 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 (6 lines × 2) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:212— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:212-217 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:218-223 — 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 (6 lines × 2) packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:289— packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:289-294 | packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:378-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) examples/demo.exs:553— examples/demo.exs:553-558 | lib/raxol/demo/dashboard.ex:383-388 — 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 `examples/demo.exs:553` 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, `examples/demo.exs:551` calls `text`, `scroll_hint` and `lib/raxol/demo/dashboard.ex:382` 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) examples/dev/hot_reload_demo.exs:23— examples/dev/hot_reload_demo.exs:23-28 | examples/scripts/event_handling.exs:32-38 — 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 `examples/dev/hot_reload_demo.exs:23` 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 (6 lines × 2) lib/raxol/playground/demos/repl_demo.ex:337— lib/raxol/playground/demos/repl_demo.ex:337-342 | lib/raxol/playground/demos/vfs_demo.ex:315-320 — 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 (6 lines × 2) lib/raxol/playground/demos/repl_demo.ex:354— lib/raxol/playground/demos/repl_demo.ex:354-359 | lib/raxol/playground/demos/vfs_demo.ex:345-350 — 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· Edited copy of a member (8 corresponding lines) · ×11
Edited copy of a member (8 corresponding lines) packages/raxol_core/lib/raxol/core/runtime/plugins/command_helper.ex:211— packages/raxol_core/lib/raxol/core/runtime/plugins/command_helper.ex:211-218 | packages/raxol_core/lib/raxol/core/runtime/plugins/command_registry.ex:296-303 — 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) lib/raxol/adaptive/behavior_tracker.ex:288— lib/raxol/adaptive/behavior_tracker.ex:288-298 | lib/raxol/adaptive/behavior_tracker.ex:348-355 — 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) lib/raxol/ui/cell_dim.ex:152— lib/raxol/ui/cell_dim.ex:152-164 | lib/raxol/ui/theming/salience_theme.ex:47-54 — 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) packages/raxol_mcp/lib/raxol/mcp/server.ex:1428— packages/raxol_mcp/lib/raxol/mcp/server.ex:1428-1435 | packages/raxol_mcp/lib/raxol/mcp/server.ex:1498-1505 — 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) lib/raxol/core/runtime/lifecycle/initializer.ex:35— lib/raxol/core/runtime/lifecycle/initializer.ex:35-42 | lib/raxol/core/runtime/lifecycle/initializer.ex:46-55 — 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) lib/raxol/ui/components/input/multi_line_input/navigation_helper.ex:66— lib/raxol/ui/components/input/multi_line_input/navigation_helper.ex:66-73 | lib/raxol/ui/components/input/multi_line_input/navigation_helper.ex:77-84 — 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) lib/raxol/ui/charts/line_chart.ex:56— lib/raxol/ui/charts/line_chart.ex:56-63 | lib/raxol/ui/charts/scatter_chart.ex:56-63 — 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) lib/raxol/ui/theming/colors.ex:133— lib/raxol/ui/theming/colors.ex:133-140 | lib/raxol/ui/theming/colors.ex:160-167 — 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) lib/raxol/ui/components/input/single_line_input.ex:206— lib/raxol/ui/components/input/single_line_input.ex:206-213 | lib/raxol/ui/components/input/single_line_input.ex:217-224 — 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) lib/raxol/core/runtime/rendering/engine.ex:574— lib/raxol/core/runtime/rendering/engine.ex:574-581 | packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:459-466 — 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) lib/raxol/plugins/examples/terminal_multiplexer/window_manager.ex:42— lib/raxol/plugins/examples/terminal_multiplexer/window_manager.ex:42-49 | lib/raxol/plugins/examples/terminal_multiplexer/window_manager.ex:54-64 — 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 (21 corresponding lines) · ×10
Edited copy of a member (21 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/sync/sync_server.ex:150— packages/raxol_terminal/lib/raxol/terminal/sync/sync_server.ex:150-170 | packages/raxol_terminal/lib/raxol/terminal/sync/sync_server.ex:190-216 — 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) lib/raxol/plugins/visualization/treemap_renderer.ex:126— lib/raxol/plugins/visualization/treemap_renderer.ex:126-158 | lib/raxol/plugins/visualization/treemap_renderer.ex:589-609 — 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) lib/raxol/workflow/runtime.ex:694— lib/raxol/workflow/runtime.ex:694-720 | lib/raxol/workflow/runtime.ex:1537-1557 — 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) lib/mix/tasks/raxol.new.ex:146— lib/mix/tasks/raxol.new.ex:146-180 | lib/mix/tasks/raxol.replay.ex:173-193 — 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) lib/raxol/swarm/tactical_overlay.ex:211— lib/raxol/swarm/tactical_overlay.ex:211-240 | lib/raxol/swarm/tactical_overlay.ex:284-304 — 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) lib/raxol/ui/layout/responsive.ex:86— lib/raxol/ui/layout/responsive.ex:86-110 | lib/raxol/ui/layout/responsive.ex:145-165 — 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) packages/raxol_terminal/lib/raxol/terminal/driver.ex:888— packages/raxol_terminal/lib/raxol/terminal/driver.ex:888-919 | packages/raxol_terminal/lib/raxol/terminal/inline_driver.ex:1066-1086 — 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) lib/raxol/adaptive/layout_recommender.ex:439— lib/raxol/adaptive/layout_recommender.ex:439-459 | lib/raxol/adaptive/layout_recommender.ex:463-483 — 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) examples/components/displays/markdown_demo.exs:60— examples/components/displays/markdown_demo.exs:60-80 | examples/scripts/event_handling.exs:32-65 — 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) lib/raxol/playground/demos/harness_approval_demo.ex:105— lib/raxol/playground/demos/harness_approval_demo.ex:105-125 | lib/raxol/playground/demos/modal_demo.ex:81-102 — 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.
Duplicated block (10 lines × 2) lib/mix/tasks/raxol.bench.memory_analysis.ex:471— lib/mix/tasks/raxol.bench.memory_analysis.ex:471-486 | lib/mix/tasks/raxol.memory.stability.ex:87-96 — 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.
Duplicated block (10 lines × 2) lib/raxol/ui/components/harness/diff_viewer.ex:1417— lib/raxol/ui/components/harness/diff_viewer.ex:1417-1426 | lib/raxol/ui/components/harness/diff_viewer.ex:1450-1459 — 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) lib/raxol/ui/components/input/checkbox.ex:172— lib/raxol/ui/components/input/checkbox.ex:172-182 | lib/raxol/ui/components/modal.ex:349-358 — 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 `lib/raxol/ui/components/input/checkbox.ex:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) lib/raxol/ui/layout/flexbox/positioner.ex:147— lib/raxol/ui/layout/flexbox/positioner.ex:147-156 | lib/raxol/ui/layout/flexbox/positioner.ex:325-334 — 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) packages/raxol_terminal/lib/raxol/terminal/character_handling.ex:250— packages/raxol_terminal/lib/raxol/terminal/character_handling.ex:250-271 | web/lib/raxol_playground/settlement_sandbox.ex:250-259 — 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 `packages/raxol_terminal/lib/raxol/terminal/character_handling.ex:250` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) lib/raxol/plugins/event_handler/common.ex:187— lib/raxol/plugins/event_handler/common.ex:187-196 | lib/raxol/plugins/lifecycle/error_handling.ex:106-115 — 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) packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:1168— packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:1168-1177 | packages/raxol_journal/lib/raxol/agent/journal/records/checkpoint/file_backend.ex:616-625 — 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 `packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:1168` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) packages/raxol_terminal/lib/raxol/terminal/emulator/buffer_operations.ex:28— packages/raxol_terminal/lib/raxol/terminal/emulator/buffer_operations.ex:28-37 | packages/raxol_terminal/lib/raxol/terminal/emulator/struct.ex:274-283 — 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 `packages/raxol_terminal/lib/raxol/terminal/emulator/buffer_operations.ex:28` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) examples/components/forms/form_validation.exs:54— examples/components/forms/form_validation.exs:54-63 | examples/components/input/multi_line_input_demo.exs:48-57 — 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 `examples/components/forms/form_validation.exs:54` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) scripts/harness/t0/ringb/measurements.ex:75— scripts/harness/t0/ringb/measurements.ex:75-84 | scripts/harness/t0/ringb/measurements.ex:455-464 — 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 `scripts/harness/t0/ringb/measurements.ex:75` 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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×9
Edited copy of a member (18 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/ansi/state_machine.ex:323— packages/raxol_terminal/lib/raxol/terminal/ansi/state_machine.ex:323-348 | packages/raxol_terminal/lib/raxol/terminal/ansi/state_machine.ex:356-373 — 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) packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:241— packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:241-258 | packages/raxol_terminal/lib/raxol/terminal/extension/extension_server.ex:262-279 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:86— packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:86-110 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:115-132 — 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) packages/raxol_terminal/lib/raxol/terminal/buffer/scroll_region.ex:227— packages/raxol_terminal/lib/raxol/terminal/buffer/scroll_region.ex:227-244 | packages/raxol_terminal/lib/raxol/terminal/buffer/scroll_region.ex:287-304 — 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) packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:183— packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:183-200 | packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:215-237 — 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) lib/raxol/ui/element_renderer.ex:128— lib/raxol/ui/element_renderer.ex:128-145 | lib/raxol/ui/ui_renderer.ex:180-197 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/input_processing.ex:23— packages/raxol_terminal/lib/raxol/terminal/emulator/input_processing.ex:23-40 | packages/raxol_terminal/lib/raxol/terminal/emulator/input_processing.ex:44-61 — 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) lib/raxol/ui/components/input/button.ex:225— lib/raxol/ui/components/input/button.ex:225-242 | lib/raxol/ui/components/input/button.ex:332-350 — 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) lib/raxol/navigation/vim.ex:194— lib/raxol/navigation/vim.ex:194-211 | lib/raxol/navigation/vim.ex:215-233 — 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.
Duplicated block (9 lines × 2) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:229— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:229-237 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:248-256 — 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, `packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:227` calls `drop` and `packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:246` 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.
Duplicated block (9 lines × 2) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:329— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:329-337 | packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:457-465 — 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) packages/raxol_terminal/lib/raxol/terminal/screen_updater.ex:188— packages/raxol_terminal/lib/raxol/terminal/screen_updater.ex:188-196 | packages/raxol_terminal/lib/raxol/terminal/screen_updater.ex:200-208 — 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) packages/raxol_watch/lib/raxol/watch/push/apns.ex:33— packages/raxol_watch/lib/raxol/watch/push/apns.ex:33-41 | packages/raxol_watch/lib/raxol/watch/push/fcm.ex:26-34 — 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 `packages/raxol_watch/lib/raxol/watch/push/apns.ex:33` 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) packages/raxol_terminal/lib/raxol/terminal/buffer/queries.ex:200— packages/raxol_terminal/lib/raxol/terminal/buffer/queries.ex:200-209 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer.ex:420-428 — 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 `packages/raxol_terminal/lib/raxol/terminal/buffer/queries.ex:200` 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) packages/raxol_terminal/lib/raxol/terminal/cursor/cursor_manager.ex:205— packages/raxol_terminal/lib/raxol/terminal/cursor/cursor_manager.ex:205-213 | packages/raxol_terminal/lib/raxol/terminal/cursor/movement.ex:205-213 — 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) bench/suites/kitty_graphics_benchmark.exs:102— bench/suites/kitty_graphics_benchmark.exs:102-110 | bench/suites/kitty_graphics_benchmark.exs:167-175 — 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) lib/raxol/plugins/examples/git_integration_plugin.ex:174— lib/raxol/plugins/examples/git_integration_plugin.ex:174-182 | lib/raxol/plugins/examples/git_integration_plugin.ex:210-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/plugins/examples/git_integration_plugin.ex:174` 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) examples/demo.exs:727— examples/demo.exs:727-735 | lib/raxol/demo/dashboard.ex:507-515 — 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· Edited copies of one member (3 members, 4+ corresponding lines) · ×8
Edited copies of one member (3 members, 4+ corresponding lines) lib/raxol/core/renderer/view/components/box.ex:112— lib/raxol/core/renderer/view/components/box.ex:112-115 | packages/raxol_terminal/lib/raxol/terminal/ansi/sgr.ex:530-534 | packages/raxol_terminal/lib/raxol/terminal/ansi/sgr.ex:537-541 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) lib/raxol/style/colors/persistence.ex:318— lib/raxol/style/colors/persistence.ex:318-324 | packages/raxol_terminal/lib/raxol/terminal/ansi/sgr.ex:423-426 | packages/raxol_terminal/lib/raxol/terminal/commands/commands_parser.ex:41-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) packages/raxol_core/lib/raxol/core/events/termbox_converter.ex:103— packages/raxol_core/lib/raxol/core/events/termbox_converter.ex:103-108 | packages/raxol_terminal/lib/raxol/terminal/driver/event_translator.ex:93-98 | packages/raxol_terminal/lib/raxol/terminal/plugin/terminal_plugin_manager.ex:223-226 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_lifecycle.ex:283— packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_lifecycle.ex:283-291 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:131-137 | packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:287-290 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) lib/mix/tasks/raxol.release.check.ex:82— lib/mix/tasks/raxol.release.check.ex:82-85 | lib/raxol/workflow/checkpoint/saver/postgrex.ex:215-219 | scripts/docs/generate_api_docs.exs:123-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) lib/mix/tasks/raxol.scoreboard.ex:86— lib/mix/tasks/raxol.scoreboard.ex:86-94 | lib/raxol/plugins/examples/status_line_plugin.ex:344-347 | lib/raxol/system/platform.ex:259-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) lib/raxol/core/metrics/cloud.ex:544— lib/raxol/core/metrics/cloud.ex:544-547 | lib/raxol/query.ex:76-80 | packages/raxol_telegram/lib/raxol/telegram/output_adapter.ex:159-162 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) packages/raxol_core/lib/raxol/core/focus_manager.ex:30— packages/raxol_core/lib/raxol/core/focus_manager.ex:30-33 | packages/raxol_core/lib/raxol/core/keyboard_navigator.ex:36-39 | packages/raxol_core/lib/raxol/core/keyboard_shortcuts.ex:32-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×7
Edited copy of a member (27 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:319— packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:319-345 | packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:349-375 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) packages/raxol_core/lib/raxol/core/telemetry/context.ex:340— packages/raxol_core/lib/raxol/core/telemetry/context.ex:340-387 | packages/raxol_core/lib/raxol/core/telemetry/trace_context.ex:377-403 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) lib/raxol/harness/surface.ex:2293— lib/raxol/harness/surface.ex:2293-2319 | lib/raxol/harness/surface.ex:2405-2450 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) lib/raxol/ui/charts/bar_chart.ex:182— lib/raxol/ui/charts/bar_chart.ex:182-208 | lib/raxol/ui/charts/bar_chart.ex:355-381 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) lib/raxol/adaptive/layout_recommender.ex:572— lib/raxol/adaptive/layout_recommender.ex:572-600 | lib/raxol/adaptive/layout_recommender.ex:604-630 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) scripts/harness/t0/ringb/measurements.ex:75— scripts/harness/t0/ringb/measurements.ex:75-101 | scripts/harness/t0/ringb/measurements.ex:455-483 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) lib/raxol/playground/demos/line_chart_demo.ex:46— lib/raxol/playground/demos/line_chart_demo.ex:46-72 | lib/raxol/playground/demos/scatter_chart_demo.ex:53-79 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×7
Edited copy of a member (23 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:93— packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:93-115 | packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_dithering.ex:121-143 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) lib/raxol/debug/debugger_app.ex:271— lib/raxol/debug/debugger_app.ex:271-293 | lib/raxol/debug/debugger_app.ex:297-319 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:477— packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:477-499 | packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:567-599 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/session_manager.ex:362— packages/raxol_terminal/lib/raxol/terminal/session_manager.ex:362-384 | packages/raxol_terminal/lib/raxol/terminal/session_manager.ex:388-414 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/sync/sync_manager.ex:145— packages/raxol_terminal/lib/raxol/terminal/sync/sync_manager.ex:145-167 | packages/raxol_terminal/lib/raxol/terminal/sync/sync_manager.ex:175-197 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) lib/raxol/ui/layout/responsive.ex:47— lib/raxol/ui/layout/responsive.ex:47-72 | lib/raxol/ui/layout/responsive.ex:119-141 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) bench/suites/parser/parser_benchmark.exs:56— bench/suites/parser/parser_benchmark.exs:56-87 | bench/suites/parser/parser_benchmark.exs:91-113 — 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) · ×7
Edited copy of a member (20 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/buffer/line_editor.ex:25— packages/raxol_terminal/lib/raxol/terminal/buffer/line_editor.ex:25-46 | packages/raxol_terminal/lib/raxol/terminal/buffer/line_editor.ex:69-88 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) lib/raxol/ui/components/input/select_list.ex:711— lib/raxol/ui/components/input/select_list.ex:711-730 | lib/raxol/ui/components/input/tabs.ex:232-251 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) lib/raxol/ui/layout/flexbox/positioner.ex:9— lib/raxol/ui/layout/flexbox/positioner.ex:9-28 | lib/raxol/ui/layout/flexbox/positioner.ex:218-240 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/device_handler.ex:48— packages/raxol_terminal/lib/raxol/terminal/commands/device_handler.ex:48-67 | packages/raxol_terminal/lib/raxol/terminal/device/status.ex:10-33 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:214— packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:214-233 | packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:307-327 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) lib/raxol/config/schema/definitions.ex:95— lib/raxol/config/schema/definitions.ex:95-115 | lib/raxol/config/schema/definitions.ex:352-371 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) examples/components/displays/progress_bar_demo.ex:58— examples/components/displays/progress_bar_demo.ex:58-78 | examples/components/forms/form_validation.exs:89-108 — 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.
Duplicated block (13 lines × 2) packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:104— packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:104-116 | packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:133-145 — 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 `packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:104` 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 (13 lines × 2) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:119— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:119-131 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:170-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.
Duplicated block (13 lines × 2) packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:488— packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:488-500 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:514-526 — 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) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:86— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:86-98 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:144-156 — 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) examples/apps/showcase_app.exs:170— examples/apps/showcase_app.exs:170-182 | lib/raxol/demo/showcase.ex:174-186 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/apps/showcase_app.exs:170` 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 (13 lines × 2) examples/apps/showcase_app.exs:214— examples/apps/showcase_app.exs:214-226 | lib/raxol/demo/showcase.ex:227-239 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/raxol/playground/demos/harness_approval_demo.ex:105— lib/raxol/playground/demos/harness_approval_demo.ex:105-117 | lib/raxol/playground/demos/modal_demo.ex:81-93 — 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 `lib/raxol/playground/demos/harness_approval_demo.ex:105` 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) lib/raxol/navigation/vim.ex:128— lib/raxol/navigation/vim.ex:128-138 | lib/raxol/navigation/vim.ex:162-172 — 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) packages/raxol_terminal/lib/raxol/terminal/ansi/state_machine.ex:363— packages/raxol_terminal/lib/raxol/terminal/ansi/state_machine.ex:363-373 | packages/raxol_terminal/lib/raxol/terminal/ansi/state_machine.ex:381-391 — 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) packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:139— packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:139-149 | packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:274-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:139` 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 (11 lines × 2) bench/suites/parser/parser_benchmark.exs:77— bench/suites/parser/parser_benchmark.exs:77-87 | bench/suites/parser/parser_benchmark.exs:103-113 — 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 `bench/suites/parser/parser_benchmark.exs:77` 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 (11 lines × 2) examples/demo.exs:242— examples/demo.exs:242-252 | lib/raxol/demo/dashboard.ex:153-163 — 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 (11 lines × 2) examples/getting_started/todo_app.exs:28— examples/getting_started/todo_app.exs:28-38 | lib/raxol/demo/todo.ex:18-28 — before extracting anything, compare `examples/getting_started/todo_app.exs` and `lib/raxol/demo/todo.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) bench/suites/visualization/visualization_benchmark.ex:316— bench/suites/visualization/visualization_benchmark.ex:316-326 | bench/suites/visualization/visualization_benchmark_simple.ex:200-210 — 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.
Change coupling: engine.ex ↔ ui_renderer.ex lib/raxol/ui/layout/engine.ex:1— `lib/raxol/ui/layout/engine.ex` and `lib/raxol/ui/ui_renderer.ex` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 7 shared commits counted here, the most recent 3 are `ba9e3caa` Make every View DSL constructor render (#1131); `a2c943bd` Render modals as dialogs over dimmed, undisturbed content (#476); `553f3175` Auto-ellipsis for overflowing text; cursor-follow list scrolling with… — run `git show` on any of them.
Change coupling: element_renderer.ex ↔ engine.ex lib/raxol/ui/element_renderer.ex:1— `lib/raxol/ui/element_renderer.ex` and `lib/raxol/ui/layout/engine.ex` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 7 shared commits counted here, the most recent 3 are `ba9e3caa` Make every View DSL constructor render (#1131); `553f3175` Auto-ellipsis for overflowing text; cursor-follow list scrolling with…; `84a13932` Fix phantom borders: renderer border default matches layout (:none) (… — run `git show` on any of them.
Change coupling: mode_manager.ex ↔ dec_private_handler.ex packages/raxol_terminal/lib/raxol/terminal/mode_manager.ex:1— `packages/raxol_terminal/lib/raxol/terminal/mode_manager.ex` and `packages/raxol_terminal/lib/raxol/terminal/modes/handlers/dec_private_handler.ex` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — 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 `4c0fb0cf` Define DEC mode lookup once in the mode registry (#1009); `5a85b6a7` Enhance core runtime, terminal integration, and UI components (at that commit the files were still `lib/raxol/terminal/mode_manager.ex` and `lib/raxol/terminal/modes/handlers/dec_private_handler.ex`); `ae5cf7f8` feat: enhance terminal emulator with improved command handling and re… (at that commit the files were still `lib/raxol/terminal/mode_manager.ex` and `lib/raxol/terminal/modes/handlers/dec_private_handler.ex`) — run `git show` on any of them.
Change coupling: config.exs ↔ mix.exs config/config.exs:1— `config/config.exs` and `mix.exs` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 8 shared commits counted here, the most recent 3 are `11963d83` chore: cleanup non-existent doc refs, suppress Tesla warning; `056f6d50` feat: add web and SSH terminal demo; `adfcb221` Update core system configuration and application setup — run `git show` on any of them.
Change coupling: demo_live.ex ↔ playground_live.ex web/lib/raxol_playground_web/live/demo_live.ex:1— `web/lib/raxol_playground_web/live/demo_live.ex` and `web/lib/raxol_playground_web/live/playground_live.ex` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `b72951c0` playground: revamp nav, chrome, fonts, theming, perf; `b92a9de5` fix playground crash: unlink Lifecycle, push via hook; `143cf03b` fix LiveView crash: push terminal HTML via JS hook — run `git show` on any of them.
Change coupling: raxol.ex ↔ mix.exs lib/raxol.ex:1— `lib/raxol.ex` and `mix.exs` 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 — 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 `f2721643` Stop advertising Raxol.REPL.Evaluator as a sandbox (#1038); `3ebc49aa` reposition as multi-surface runtime; `94fce6e2` docs: update changelog, readme, hexdocs for v2.3.0 — run `git show` on any of them.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×6
Edited copies of one member (4 members, 4+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:188— packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:188-194 | packages/raxol_terminal/lib/raxol/terminal/sync/sync_manager.ex:201-204 | packages/raxol_terminal/lib/raxol/terminal/sync/system.ex:129-132 | packages/raxol_terminal/lib/raxol/terminal/window/manager/window_manager_server.ex:288-291 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) lib/mix/tasks/raxol.check.ex:135— lib/mix/tasks/raxol.check.ex:135-138 | lib/mix/tasks/raxol.flamegraph.ex:292-295 | lib/mix/tasks/raxol.mutation.ex:111-114 | packages/raxol_telegram/examples/telegram_demo.exs:133-136 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) lib/raxol/animation/gestures.ex:18— lib/raxol/animation/gestures.ex:18-21 | lib/raxol/security/user_context.ex:12-15 | lib/raxol/style/colors/system.ex:24-27 | lib/raxol/ui/state/store.ex:84-87 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) lib/raxol/harness/fixture.ex:118— lib/raxol/harness/fixture.ex:118-121 | packages/raxol_gateway/lib/raxol/gateway/handler/lifecycle.ex:265-268 | packages/raxol_telegram/lib/raxol/telegram/output_adapter.ex:148-151 | scripts/harness/t0/ringb/capture.ex:35-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) lib/raxol/headless.ex:1230— lib/raxol/headless.ex:1230-1233 | lib/raxol/headless/docs_resource.ex:76-79 | lib/raxol/plugins/visualization/image_renderer.ex:136-140 | packages/raxol_journal/lib/raxol/agent/journal/records/checkpoint/file_backend.ex:573-576 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) lib/raxol/profiler.ex:28— lib/raxol/profiler.ex:28-32 | lib/raxol/recording/video.ex:255-259 | lib/raxol/recording/video/rasterizer/chromic_pdf.ex:51-55 | scripts/gen_replay_recording.exs:320-323 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (16 lines × 2) lib/mix/tasks/raxol.memory.gates.ex:78— lib/mix/tasks/raxol.memory.gates.ex:78-93 | lib/mix/tasks/raxol.memory.stability.ex:77-92 — 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 `lib/mix/tasks/raxol.memory.gates.ex:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) lib/raxol/ui/components/harness/line_diff.ex:98— lib/raxol/ui/components/harness/line_diff.ex:98-113 | lib/raxol/ui/components/harness/word_diff.ex:205-220 — before extracting anything, compare `lib/raxol/ui/components/harness/line_diff.ex` and `lib/raxol/ui/components/harness/word_diff.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:191— packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:191-206 | packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:217-232 — 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 `packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:191` 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) packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:42— packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:42-57 | packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:149-164 — 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, `packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:167` calls `get` and `packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:59` 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.
Duplicated block (16 lines × 2) packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:185— packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:185-200 | packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:222-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) examples/apps/showcase_app.exs:194— examples/apps/showcase_app.exs:194-209 | lib/raxol/demo/showcase.ex:208-223 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/apps/showcase_app.exs:194` 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 (5 lines × 2) lib/raxol/ui/components/harness/line_diff.ex:78— lib/raxol/ui/components/harness/line_diff.ex:78-82 | lib/raxol/ui/components/harness/word_diff.ex:185-189 — before extracting anything, compare `lib/raxol/ui/components/harness/line_diff.ex` and `lib/raxol/ui/components/harness/word_diff.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/raxol/ui/layout/flex_item.ex:362— lib/raxol/ui/layout/flex_item.ex:362-366 | lib/raxol/ui/layout/flexbox.ex:467-471 — 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 `lib/raxol/ui/layout/flex_item.ex:362` 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 (5 lines × 2) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:128— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:128-139 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:146-150 — 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 (5 lines × 2) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:57— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:57-61 | packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:61-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:561— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:561-565 | packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:608-612 — 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) lib/raxol/bench/dashboard.ex:155— lib/raxol/bench/dashboard.ex:155-159 | lib/raxol/bench/dashboard.ex:247-251 — 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· Edited copy of a member (24 corresponding lines) · ×5
Edited copy of a member (24 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:383— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:383-406 | packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:600-623 — 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.
Edited copy of a member (24 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/input/mouse_handler.ex:163— packages/raxol_terminal/lib/raxol/terminal/input/mouse_handler.ex:163-188 | packages/raxol_terminal/lib/raxol/terminal/input/mouse_handler.ex:193-216 — 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.
Edited copy of a member (24 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/erase_ops.ex:24— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/erase_ops.ex:24-49 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/erase_ops.ex:53-76 — 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.
Edited copy of a member (24 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/screen_buffer.ex:113— packages/raxol_terminal/lib/raxol/terminal/screen_buffer.ex:113-136 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/core.ex:59-83 — 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.
Edited copy of a member (24 corresponding lines) lib/raxol/animation/gestures/gesture_server.ex:514— lib/raxol/animation/gestures/gesture_server.ex:514-538 | lib/raxol/animation/gestures/gesture_server.ex:543-566 — 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 copy of a member (19 corresponding lines) · ×5
Edited copy of a member (19 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:63— packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:63-81 | packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:306-324 — 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) lib/raxol/system/clipboard.ex:137— lib/raxol/system/clipboard.ex:137-155 | lib/raxol/system/clipboard.ex:162-187 — 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) packages/raxol_core/lib/raxol/core/focus_manager/focus_server.ex:249— packages/raxol_core/lib/raxol/core/focus_manager/focus_server.ex:249-267 | packages/raxol_core/lib/raxol/core/focus_manager/focus_server.ex:272-290 — 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) packages/raxol_liveview/lib/raxol/live_view/terminal_bridge.ex:418— packages/raxol_liveview/lib/raxol/live_view/terminal_bridge.ex:418-437 | packages/raxol_liveview/lib/raxol/live_view/terminal_bridge.ex:469-487 — 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) lib/raxol/playground/demos/button_demo.ex:40— lib/raxol/playground/demos/button_demo.ex:40-64 | lib/raxol/playground/demos/menu_demo.ex:57-75 — 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 copies of one member (3 members, 9+ corresponding lines) · ×5
Edited copies of one member (3 members, 9+ corresponding lines) packages/raxol_mcp/lib/raxol/mcp/server.ex:1443— packages/raxol_mcp/lib/raxol/mcp/server.ex:1443-1455 | packages/raxol_mcp/lib/raxol/mcp/server.ex:1466-1476 | packages/raxol_mcp/lib/raxol/mcp/server.ex:1484-1492 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) lib/raxol/core/renderer/view/components.ex:23— lib/raxol/core/renderer/view/components.ex:23-31 | lib/raxol/core/renderer/view/components.ex:50-58 | lib/raxol/core/renderer/view/components.ex:79-88 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) packages/raxol_watch/lib/raxol/watch/formatter.ex:94— packages/raxol_watch/lib/raxol/watch/formatter.ex:94-102 | packages/raxol_watch/lib/raxol/watch/formatter.ex:110-119 | packages/raxol_watch/lib/raxol/watch/formatter.ex:140-148 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/emulator/reset.ex:95— packages/raxol_terminal/lib/raxol/terminal/emulator/reset.ex:95-106 | packages/raxol_terminal/lib/raxol/terminal/emulator_lite.ex:305-313 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/charset.ex:7-15 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) examples/plugins/background_task_plugin.exs:12— examples/plugins/background_task_plugin.exs:12-20 | examples/plugins/basic_plugin.exs:11-20 | examples/plugins/file_system_plugin.exs:12-20 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×5
Edited copies of one member (3 members, 3+ corresponding lines) lib/raxol/demo/dashboard.ex:529— lib/raxol/demo/dashboard.ex:529-542 | packages/raxol_terminal/lib/raxol/terminal/display/ascii_art.ex:193-195 | web/lib/raxol_playground_web/presence.ex:160-176 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 3+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:31— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:31-43 | packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:31-33 | packages/raxol_terminal/lib/raxol/terminal/parser/states/ground_state.ex:99-101 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 3+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/cursor.ex:104— packages/raxol_terminal/lib/raxol/terminal/cursor.ex:104-106 | packages/raxol_terminal/lib/raxol/terminal/cursor/cursor_manager.ex:409-411 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/attributes.ex:18-20 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 3+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:133— packages/raxol_terminal/lib/raxol/terminal/operations/screen_operations.ex:133-135 | packages/raxol_terminal/lib/raxol/terminal/operations/selection_operations.ex:9-11 | packages/raxol_terminal/lib/raxol/terminal/operations/text_operations.ex:9-11 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 3+ corresponding lines) lib/raxol/adaptive/behavior_tracker.ex:166— lib/raxol/adaptive/behavior_tracker.ex:166-169 | lib/raxol/adaptive/layout_recommender.ex:136-139 | packages/raxol_sensor/lib/raxol/sensor/fusion.ex:87-89 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
TodoComment test/raxol/ui/components/input/text_field_test.exs:577— # and scroll bugs. See TODO refactor backlog and the planned — 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/raxol/core/runtime/events/dispatcher.ex:748— # see the module 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 lib/mix/tasks/raxol.demo.ex:9— # Todo list — 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 examples/getting_started/todo_app.exs:1— # Todo List Example — 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:165— packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:165-188 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:195-218 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:10-44 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:51-85 — 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) packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:26— packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:26-129 | packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:136-242 | packages/raxol_terminal/lib/raxol/terminal/emulator/factory.ex:29-114 | packages/raxol_terminal/lib/raxol/terminal/emulator_lite.ex:317-327 — 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) packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:231— packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:231-246 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:284-299 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:520-535 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:563-587 — 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) scripts/testing/test_dashboard_layout_integration.exs:17— scripts/testing/test_dashboard_layout_integration.exs:17-343 | scripts/testing/test_layout_persistence.exs:15-237 | scripts/testing/test_terminal_visualization.exs:25-123 | scripts/testing/test_visualization.exs:24-120 — 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 (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) lib/raxol/memory/formatter.ex:123— lib/raxol/memory/formatter.ex:123-157 | lib/raxol/memory/formatter.ex:161-182 — 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) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:30— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:30-51 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:55-79 — 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) lib/raxol/plugins/examples/file_browser_plugin.ex:19— lib/raxol/plugins/examples/file_browser_plugin.ex:19-40 | lib/raxol/plugins/examples/git_integration_plugin.ex:24-50 — 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) scripts/check_duplicate_filenames.exs:131— scripts/check_duplicate_filenames.exs:131-165 | scripts/docs/generate_api_docs.exs:98-119 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×4
Edited copies of one member (3 members, 15+ corresponding lines) lib/mix/tasks/raxol/generator.ex:211— lib/mix/tasks/raxol/generator.ex:211-225 | lib/mix/tasks/raxol/generator.ex:229-244 | lib/mix/tasks/raxol/generator.ex:248-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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, 15+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:139— packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:139-155 | packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:274-290 | packages/raxol_terminal/lib/raxol/terminal/buffer/buffer_server.ex:304-318 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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, 15+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/mouse/mouse_server.ex:232— packages/raxol_terminal/lib/raxol/terminal/mouse/mouse_server.ex:232-246 | packages/raxol_terminal/lib/raxol/terminal/mouse/mouse_server.ex:255-269 | packages/raxol_terminal/lib/raxol/terminal/mouse/mouse_server.ex:290-304 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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, 15+ corresponding lines) lib/raxol/core/state_manager.ex:219— lib/raxol/core/state_manager.ex:219-236 | lib/raxol/core/state_manager.ex:245-259 | lib/raxol/core/state_manager.ex:264-281 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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, 10+ corresponding lines) · ×4
Edited copies of one member (3 members, 10+ corresponding lines) lib/raxol/view/components.ex:259— lib/raxol/view/components.ex:259-270 | lib/raxol/view/components.ex:344-353 | lib/raxol/view/components.ex:479-488 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) lib/raxol/workflow/checkpoint/saver/postgrex.ex:116— lib/raxol/workflow/checkpoint/saver/postgrex.ex:116-128 | lib/raxol/workflow/checkpoint/saver/postgrex.ex:133-142 | lib/raxol/workflow/checkpoint/saver/postgrex.ex:158-167 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:187— packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:187-200 | packages/raxol_terminal/lib/raxol/terminal/tab/tab_manager.ex:370-383 | packages/raxol_terminal/lib/raxol/terminal/tab/tab_server.ex:198-207 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) lib/raxol/demo/session_manager.ex:138— lib/raxol/demo/session_manager.ex:138-147 | packages/raxol_gateway/lib/raxol/gateway/session_router.ex:361-370 | packages/raxol_terminal/lib/raxol/terminal/session_manager.ex:472-481 — 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.
Duplicated block (5 lines × 3) packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex:30— packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex:30-36 | packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_maybe_st_state.ex:37-46 | packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_state.ex:43-47 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_maybe_st_state.ex:37` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 3) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:69— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:69-73 | packages/raxol_gateway/lib/raxol/gateway/adapter/email.ex:120-124 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:71-75 — 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.
Duplicated block (5 lines × 3) packages/raxol_terminal/lib/raxol/terminal/emulator/ansi_handler.ex:325— packages/raxol_terminal/lib/raxol/terminal/emulator/ansi_handler.ex:325-329 | packages/raxol_terminal/lib/raxol/terminal/emulator/ansi_handler.ex:333-337 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:322-326 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 3) packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:245— packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:245-249 | packages/raxol_gateway/lib/raxol/gateway/adapter/email.ex:457-461 | packages/raxol_telegram/lib/raxol/telegram/gateway_adapter.ex:256-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_gateway/lib/raxol/gateway/adapter/discord.ex:245` 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 (6 lines × 3) lib/raxol/swarm/overlay_renderer.ex:210— lib/raxol/swarm/overlay_renderer.ex:210-215 | lib/raxol/ui/charts/chart_utils.ex:239-244 | packages/raxol_sensor/lib/raxol/sensor/hud.ex:265-270 — 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.
Duplicated block (6 lines × 3) lib/raxol/protocols/theme_implementations.ex:71— lib/raxol/protocols/theme_implementations.ex:71-76 | lib/raxol/ui/components/display/progress.ex:312-317 | lib/raxol/ui/theming/theme.ex:492-500 — 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.
Duplicated block (6 lines × 3) examples/advanced/editor.exs:48— examples/advanced/editor.exs:48-53 | examples/apps/showcase_app.exs:62-68 | examples/components/forms/form_validation.exs:60-65 — before extracting anything, compare `examples/advanced/editor.exs` and `examples/components/forms/form_validation.exs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/advanced/editor.exs:48` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 3) examples/charts/chart_showcase.exs:41— examples/charts/chart_showcase.exs:41-46 | examples/demo.exs:91-96 | lib/raxol/playground/demos/beam_dashboard_demo.ex:45-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `examples/charts/chart_showcase.exs:41` 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement web/priv/static/css/app.css:181— `.command-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement web/assets/css/app.css:1587— `.command-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement web/assets/css/app.css:2531— `input[type="range"]` 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.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×3
Edited copies of one member (3 members, 13+ corresponding lines) lib/raxol/ui/components/input/password_field.ex:76— lib/raxol/ui/components/input/password_field.ex:76-88 | lib/raxol/ui/components/input/text_area.ex:81-93 | lib/raxol/ui/components/input/text_input.ex:246-258 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) packages/raxol_core/lib/raxol/core/runtime/plugins/dependency_resolver.ex:81— packages/raxol_core/lib/raxol/core/runtime/plugins/dependency_resolver.ex:81-93 | packages/raxol_core/lib/raxol/core/runtime/plugins/dependency_resolver.ex:102-117 | packages/raxol_core/lib/raxol/core/runtime/plugins/dependency_resolver.ex:150-162 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) lib/raxol/plugins/visualization/chart_renderer.ex:41— lib/raxol/plugins/visualization/chart_renderer.ex:41-59 | lib/raxol/plugins/visualization/image_renderer.ex:38-50 | lib/raxol/plugins/visualization/treemap_renderer.ex:49-69 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×3
Edited copies of one member (3 members, 18+ corresponding lines) lib/raxol/ui/components/input/password_field.ex:40— lib/raxol/ui/components/input/password_field.ex:40-57 | lib/raxol/ui/components/input/text_area.ex:37-59 | lib/raxol/ui/components/input/text_input.ex:185-202 — 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.
Edited copies of one member (3 members, 18+ corresponding lines) packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:282— packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:282-299 | packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:333-350 | packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:357-374 — 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.
Edited copies of one member (3 members, 18+ corresponding lines) bench/suites/kitty_graphics_benchmark.exs:93— bench/suites/kitty_graphics_benchmark.exs:93-110 | bench/suites/kitty_graphics_benchmark.exs:157-175 | bench/suites/kitty_graphics_benchmark.exs:186-207 — 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 copy of a member (25 corresponding lines) · ×3
Edited copy of a member (25 corresponding lines) lib/mix/tasks/raxol.memory.stability.ex:385— lib/mix/tasks/raxol.memory.stability.ex:385-409 | lib/raxol/memory/leak_detector.ex:54-78 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) examples/apps/showcase_app.exs:231— examples/apps/showcase_app.exs:231-255 | lib/raxol/demo/showcase.ex:243-278 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) lib/raxol/playground/demos/text_area_demo.ex:102— lib/raxol/playground/demos/text_area_demo.ex:102-133 | lib/raxol/playground/demos/text_demo.ex:52-76 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×3
Edited copies of one member (3 members, 14+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/ansi/benchmark.ex:51— packages/raxol_terminal/lib/raxol/terminal/ansi/benchmark.ex:51-66 | packages/raxol_terminal/lib/raxol/terminal/ansi/benchmark.ex:83-96 | packages/raxol_terminal/lib/raxol/terminal/ansi/benchmark.ex:116-132 — 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) packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:196— packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:196-209 | packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:214-227 | packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:232-245 — 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) lib/raxol/ui/components/display/tree.ex:138— lib/raxol/ui/components/display/tree.ex:138-151 | lib/raxol/ui/components/input/menu.ex:153-166 | lib/raxol/ui/components/input/text_field.ex:316-333 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×3
Edited copies of one member (3 members, 8+ corresponding lines) lib/raxol/heex.ex:107— lib/raxol/heex.ex:107-115 | lib/raxol/heex.ex:119-126 | lib/raxol/heex.ex:132-139 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) lib/raxol/view/components.ex:68— lib/raxol/view/components.ex:68-75 | lib/raxol/view/components.ex:83-91 | lib/raxol/view/components.ex:99-107 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) lib/raxol/core/runtime/events/dispatcher.ex:427— lib/raxol/core/runtime/events/dispatcher.ex:427-434 | packages/raxol_core/lib/raxol/core/runtime/plugins/discovery.ex:203-210 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_error_handler.ex:10-17 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×3
Edited copies of one member (3 members, 7+ corresponding lines) lib/raxol/ui/components/input/multi_line_input/text_helper.ex:100— lib/raxol/ui/components/input/multi_line_input/text_helper.ex:100-106 | lib/raxol/ui/components/input/multi_line_input/text_helper.ex:110-116 | lib/raxol/ui/components/input/multi_line_input/text_helper.ex:130-137 — 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.
Edited copies of one member (3 members, 7+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/input/input_manager.ex:393— packages/raxol_terminal/lib/raxol/terminal/input/input_manager.ex:393-400 | packages/raxol_terminal/lib/raxol/terminal/input/input_manager.ex:441-447 | packages/raxol_terminal/lib/raxol/terminal/input/input_manager.ex:536-547 — 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.
Edited copies of one member (3 members, 7+ corresponding lines) lib/raxol/config/loader.ex:452— lib/raxol/config/loader.ex:452-458 | packages/raxol_core/lib/raxol/core/config/config.ex:185-192 | packages/raxol_terminal/lib/raxol/terminal/config/utils.ex:14-21 — 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.
Duplicated block (17–18 lines × 3) lib/raxol/ui/components/input/select_list.ex:654— lib/raxol/ui/components/input/select_list.ex:654-670 | lib/raxol/ui/components/input/tabs.ex:180-197 | lib/raxol/ui/components/table.ex:872-888 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/input/select_list.ex:654` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17–18 lines × 3) bench/suites/enhanced/performance_dashboard.exs:141— bench/suites/enhanced/performance_dashboard.exs:141-158 | bench/suites/enhanced/performance_dashboard.exs:175-191 | bench/suites/enhanced/performance_dashboard.exs:213-230 — 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 `bench/suites/enhanced/performance_dashboard.exs:141` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17–18 lines × 3) scripts/testing/test_dashboard_layout_integration.exs:26— scripts/testing/test_dashboard_layout_integration.exs:26-42 | scripts/testing/test_terminal_visualization.exs:33-50 | scripts/testing/test_visualization.exs:31-48 — before extracting anything, compare `scripts/testing/test_dashboard_layout_integration.exs` and `scripts/testing/test_terminal_visualization.exs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/testing/test_dashboard_layout_integration.exs:26` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) lib/raxol/style/colors/system.ex:229— lib/raxol/style/colors/system.ex:229-243 | lib/raxol/style/colors/system.ex:249-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/style/colors/system.ex:229` 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 (15 lines × 2) packages/raxol_terminal/lib/raxol/terminal/commands/screen.ex:105— packages/raxol_terminal/lib/raxol/terminal/commands/screen.ex:105-119 | packages/raxol_terminal/lib/raxol/terminal/commands/screen.ex:137-151 — 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 (15 lines × 2) scripts/harness/t0/ringb/drivers/iterm2.ex:62— scripts/harness/t0/ringb/drivers/iterm2.ex:62-76 | scripts/harness/t0/ringb/drivers/terminal_app.ex:72-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 (12 lines × 2) packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:186— packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:186-197 | packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:207-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/ansi/utils.ex:186` 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) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:111— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:111-122 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/scroll_ops.ex:167-178 — 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) examples/apps/showcase_app.exs:287— examples/apps/showcase_app.exs:287-298 | lib/raxol/demo/showcase.ex:308-319 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/apps/showcase_app.exs:287` 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.
Off the main sequence: raxol (OTP) — raxol (OTP): abstractness 0.03, instability 0.00, distance 0.97 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
Off the main sequence: raxol_mcp — raxol_mcp: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: raxol_core — raxol_core: abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×2
Edited copy of a member (39 corresponding lines) packages/raxol_core/lib/raxol/core/error_recovery.ex:369— packages/raxol_core/lib/raxol/core/error_recovery.ex:369-408 | packages/raxol_core/lib/raxol/core/error_recovery.ex:412-450 — These two members are one piece of code written twice and then edited apart: 39 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 (39 corresponding lines) lib/raxol/playground/demos/repl_demo.ex:198— lib/raxol/playground/demos/repl_demo.ex:198-236 | lib/raxol/playground/demos/vfs_demo.ex:60-101 — These two members are one piece of code written twice and then edited apart: 39 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 (38 corresponding lines) · ×2
Edited copy of a member (38 corresponding lines) lib/raxol/ui/components/display/tree.ex:341— lib/raxol/ui/components/display/tree.ex:341-378 | lib/raxol/ui/components/table.ex:872-910 — These two members are one piece of code written twice and then edited apart: 38 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 (38 corresponding lines) bench/scripts/ansi_parser_bench.exs:8— bench/scripts/ansi_parser_bench.exs:8-45 | bench/suites/parser/parser_benchmark.exs:8-52 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:75— packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:75-100 | packages/raxol_telegram/lib/raxol/telegram/guardian/mcp_tools.ex:104-129 — 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) lib/raxol/playground/demos/osc_ambient_demo.ex:57— lib/raxol/playground/demos/osc_ambient_demo.ex:57-93 | lib/raxol/playground/demos/progress_demo.ex:46-71 — 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 (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/screen.ex:105— packages/raxol_terminal/lib/raxol/terminal/commands/screen.ex:105-133 | packages/raxol_terminal/lib/raxol/terminal/commands/screen.ex:137-165 — 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) lib/raxol/protocols/renderer_implementations.ex:62— lib/raxol/protocols/renderer_implementations.ex:62-90 | lib/raxol/protocols/theme_implementations.ex:39-67 — 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 copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/screen_buffer/erase_operations.ex:29— packages/raxol_terminal/lib/raxol/terminal/screen_buffer/erase_operations.ex:29-59 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/erase_operations.ex:73-103 — 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) scripts/check_package_boundaries.exs:1202— scripts/check_package_boundaries.exs:1202-1234 | scripts/check_package_boundaries.exs:1264-1294 — 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 copies of one member (3 members, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) lib/raxol/harness/fixture/bless.ex:71— lib/raxol/harness/fixture/bless.ex:71-81 | packages/raxol_core/lib/raxol/core/runtime/plugins/mission_profile.ex:193-207 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:260-276 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) lib/raxol/ui/layout/preparer.ex:46— lib/raxol/ui/layout/preparer.ex:46-56 | lib/raxol/ui/layout/preparer.ex:60-70 | lib/raxol/ui/layout/preparer.ex:74-85 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×2
Edited copies of one member (3 members, 21+ corresponding lines) lib/mix/tasks/raxol.check.ex:142— lib/mix/tasks/raxol.check.ex:142-162 | lib/mix/tasks/raxol.check.ex:328-348 | lib/mix/tasks/raxol.check.ex:362-384 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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, 21+ corresponding lines) lib/raxol/workflow/runtime.ex:168— lib/raxol/workflow/runtime.ex:168-188 | lib/raxol/workflow/runtime.ex:959-979 | lib/raxol/workflow/runtime.ex:996-1019 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) lib/mix/tasks/raxol.mutation.ex:223— lib/mix/tasks/raxol.mutation.ex:223-239 | lib/mix/tasks/raxol.mutation.ex:244-260 | lib/mix/tasks/raxol.mutation.ex:265-281 — 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.
Edited copies of one member (3 members, 17+ corresponding lines) lib/raxol/demo/dashboard.ex:169— lib/raxol/demo/dashboard.ex:169-188 | lib/raxol/demo/dashboard.ex:240-256 | lib/raxol/demo/dashboard.ex:326-343 — 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 (3 members, 6+ corresponding lines) · ×2
Edited copies of one member (3 members, 6+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:431— packages/raxol_terminal/lib/raxol/terminal/emulator/safe_emulator.ex:431-439 | packages/raxol_terminal/lib/raxol/terminal/mode_manager.ex:71-87 | packages/raxol_terminal/lib/raxol/terminal/mode_manager.ex:107-112 — 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.
Edited copies of one member (3 members, 6+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/buffer/scroller.ex:120— packages/raxol_terminal/lib/raxol/terminal/buffer/scroller.ex:120-125 | packages/raxol_terminal/lib/raxol/terminal/buffer/scroller.ex:156-161 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/erase_operations.ex:296-305 — 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 (4 members, 8+ corresponding lines) · ×2
Edited copies of one member (4 members, 8+ corresponding lines) lib/raxol/ui/components/harness/advisory_feed.ex:34— lib/raxol/ui/components/harness/advisory_feed.ex:34-41 | lib/raxol/ui/components/harness/memory_panel.ex:30-38 | lib/raxol/ui/components/harness/rules_panel.ex:33-41 | lib/raxol/ui/components/harness/worktracks_panel.ex:32-40 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 8+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:102— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:102-109 | packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:130-140 | packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:271-279 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:119-126 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 4+ corresponding lines) · ×2
Edited copies of one member (5 members, 4+ corresponding lines) lib/raxol/style/colors/hsl.ex:122— lib/raxol/style/colors/hsl.ex:122-126 | lib/raxol/style/colors/hsl.ex:144-147 | lib/raxol/style/colors/hsl.ex:165-168 | lib/raxol/style/colors/hsl.ex:186-189 | lib/raxol/style/colors/hsl.ex:207-210 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 4+ corresponding lines) lib/raxol/core/connection_pool.ex:174— lib/raxol/core/connection_pool.ex:174-180 | lib/raxol/performance/adaptive_optimizer.ex:88-94 | packages/raxol_gateway/lib/raxol/gateway/session_router.ex:204-207 | packages/raxol_telegram/lib/raxol/telegram/session_router.ex:113-116 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:204-210 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) packages/raxol_plugin/lib/raxol/plugin/testing.ex:47— packages/raxol_plugin/lib/raxol/plugin/testing.ex:47-62 | packages/raxol_plugin/lib/raxol/plugin/testing.ex:77-92 | packages/raxol_plugin/lib/raxol/plugin/testing.ex:134-149 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/input/file_drop_handler.ex:485— packages/raxol_terminal/lib/raxol/terminal/input/file_drop_handler.ex:485-502 | packages/raxol_terminal/lib/raxol/terminal/input/file_drop_handler.ex:506-521 | packages/raxol_terminal/lib/raxol/terminal/input/file_drop_handler.ex:525-541 — 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, 2+ corresponding lines) · ×2
Edited copies of one member (3 members, 2+ corresponding lines) lib/raxol/style/colors/advanced.ex:233— lib/raxol/style/colors/advanced.ex:233-234 | packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:133-140 | packages/raxol_terminal/lib/raxol/terminal/color/true_color.ex:154-161 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 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, 2+ corresponding lines) lib/raxol/debug/time_travel.ex:51— lib/raxol/debug/time_travel.ex:51-53 | lib/raxol/performance/cycle_profiler.ex:71-73 | packages/raxol_mcp/lib/raxol/mcp/transport/stdio.ex:120-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (24 lines × 2) lib/raxol/core/metrics/visualizer.ex:213— lib/raxol/core/metrics/visualizer.ex:213-236 | lib/raxol/core/metrics/visualizer.ex:291-314 — 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 `lib/raxol/core/metrics/visualizer.ex:213` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) scripts/testing/test_dashboard_layout_integration.exs:138— scripts/testing/test_dashboard_layout_integration.exs:138-161 | scripts/testing/test_dashboard_layout_integration.exs:178-201 — 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 `scripts/testing/test_dashboard_layout_integration.exs:138` 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 (17 lines × 2) lib/raxol/ui/components/harness/diff_viewer.ex:1059— lib/raxol/ui/components/harness/diff_viewer.ex:1059-1075 | lib/raxol/ui/components/harness/diff_viewer.ex:1113-1129 — 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 (17 lines × 2) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:143— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:143-159 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:187-203 — 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 (14–16 lines × 2) lib/raxol/ui/components/input/scrubber.ex:712— lib/raxol/ui/components/input/scrubber.ex:712-727 | lib/raxol/ui/components/input/text_area.ex:44-57 — before extracting anything, compare `lib/raxol/ui/components/input/scrubber.ex` and `lib/raxol/ui/components/input/text_area.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/input/scrubber.ex:712` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–16 lines × 2) examples/apps/showcase_app.exs:242— examples/apps/showcase_app.exs:242-255 | lib/raxol/demo/showcase.ex:263-278 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/demo/showcase.ex:263` 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 × 4) packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:172— packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:172-185 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:202-215 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:28-41 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:69-82 — 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.
Duplicated block (14 lines × 4) packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:231— packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:231-244 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:284-297 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:520-533 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:563-576 — 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.
Duplicated block (14 lines × 2) packages/raxol_terminal/lib/raxol/terminal/config/persistence.ex:45— packages/raxol_terminal/lib/raxol/terminal/config/persistence.ex:45-58 | packages/raxol_terminal/lib/raxol/terminal/session/storage.ex:65-78 — 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 (14 lines × 2) packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:160— packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:160-173 | packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:178-191 — 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 `packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex:160` 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 (11–12 lines × 2) bench/suites/comparison/framework_comparison.exs:253— bench/suites/comparison/framework_comparison.exs:253-264 | lib/mix/tasks/raxol.bench.ex:287-297 — 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 (11–12 lines × 2) lib/raxol/ui/components/input/scrubber.ex:719— lib/raxol/ui/components/input/scrubber.ex:719-729 | lib/raxol/ui/components/modal.ex:350-361 — 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 `lib/raxol/ui/components/input/scrubber.ex:719` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 3) lib/raxol/ui/components/harness/context_meter.ex:36— lib/raxol/ui/components/harness/context_meter.ex:36-43 | lib/raxol/ui/components/harness/drift_indicator.ex:35-42 | lib/raxol/ui/components/harness/spend_meter.ex:35-42 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/harness/context_meter.ex:36` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 3) lib/raxol/animation/gestures/gesture_server.ex:391— lib/raxol/animation/gestures/gesture_server.ex:391-398 | lib/raxol/security/user_context/context_server.ex:268-275 | lib/raxol/ui/state/management/state_management_server.ex:439-446 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/animation/gestures/gesture_server.ex:391` 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 (21 lines × 3) scripts/testing/test_dashboard_layout_integration.exs:144— scripts/testing/test_dashboard_layout_integration.exs:144-164 | scripts/testing/test_dashboard_layout_integration.exs:184-204 | scripts/testing/test_dashboard_layout_integration.exs:304-324 — 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 `scripts/testing/test_dashboard_layout_integration.exs:144` 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 (21 lines × 3) scripts/testing/test_dashboard_layout_integration.exs:148— scripts/testing/test_dashboard_layout_integration.exs:148-169 | scripts/testing/test_dashboard_layout_integration.exs:188-209 | scripts/testing/test_dashboard_layout_integration.exs:258-278 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note 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 (8–9 lines × 2) examples/components/displays/markdown_demo.exs:61— examples/components/displays/markdown_demo.exs:61-68 | examples/scripts/event_handling.exs:41-49 — 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–9 lines × 2) lib/raxol/plugins/examples/file_browser_plugin.ex:417— lib/raxol/plugins/examples/file_browser_plugin.ex:417-425 | lib/raxol/plugins/examples/file_browser_plugin.ex:459-466 — 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.
Low cohesion: Style (LCOM4 5) lib/raxol/style/style.ex:1— Style's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Theme (LCOM4 4) lib/raxol/ui/theming/theme.ex:1— Theme's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Weak hash algorithm lib/raxol/core/error_experience.ex:650— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`:crypto.hash(:sha256, data)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/raxol_terminal/lib/raxol/terminal/image_cache.ex:183— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`:crypto.hash(:sha256, data)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
AC1 · Text alternatives· <canvas> without a text alternative · ×1
<canvas> without a text alternative web/lib/raxol_playground_web/components/landing_components.ex:318— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark web/lib/raxol_playground_web/components/layouts/root.html.heex:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
app.document.addEventListener("DOMContentLoaded") (cyclomatic 29) web/assets/js/app.js:1163— app.document.addEventListener("DOMContentLoaded") has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to one function literal inside it that branches (line 1164). 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.
(anonymous) (cyclomatic 29) web/assets/js/app.js:1163— (anonymous) has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to one function literal inside it that branches (line 1164). 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.
mounted::onKey (cyclomatic 21) web/assets/js/app.js:840— mounted::onKey has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
intent (cyclomatic 20) web/assets/js/app.js:273— intent 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.
Unicode.wide_char? (cyclomatic 18) packages/raxol_terminal/lib/raxol/terminal/unicode.ex:134— Unicode.wide_char? 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.
mounted (cyclomatic 16) web/assets/js/app.js:665— mounted has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (onKeydown, step, onClick, …). 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.
No assertions: cleans up on unmount test/js/components/Terminal.test.js:55— 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.
buildMask (cognitive 30) web/assets/js/app.js:971— buildMask has cognitive complexity 30 (threshold 15). Drivers by points: loops 8 (20 pts), if/else 2 (8 pts), boolean chains 2 (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: web/assets/js/app.js holds 5 of the 11 methods over the threshold — including the worst — and 31 of the 69 points over it (45%), 2.4× the next-largest file (packages/raxol_terminal/lib/raxol/terminal/renderer.ex at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Renderer.build_ansi_prefix (cognitive 28) packages/raxol_terminal/lib/raxol/terminal/renderer.ex:303— Renderer.build_ansi_prefix has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (17 pts), match/switch 8 (11 pts) (nesting depth added 4). 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.
app.document.addEventListener("DOMContentLoaded") (cognitive 25) web/assets/js/app.js:1163— app.document.addEventListener("DOMContentLoaded") has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 7 (11 pts), ternaries 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 1164). 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.
(anonymous) (cognitive 25) web/assets/js/app.js:1163— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 7 (11 pts), ternaries 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 1164). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: web/assets/js/app.js holds 5 of the 11 methods over the threshold — including the worst — and 31 of the 69 points over it (45%), 2.4× the next-largest file (packages/raxol_terminal/lib/raxol/terminal/renderer.ex at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Format.to_ansi_sequences (cognitive 20) packages/raxol_terminal/lib/raxol/terminal/format.ex:296— Format.to_ansi_sequences has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Session.start_lifecycle (cognitive 19) packages/raxol_telegram/lib/raxol/telegram/session.ex:154— Session.start_lifecycle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), error handling 2 (6 pts), match/switch 2 (6 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.
ExtendedSequences.parse_true_color (cognitive 19) packages/raxol_terminal/lib/raxol/terminal/ansi/extended_sequences.ex:375— ExtendedSequences.parse_true_color has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 7). 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.
mounted::onKey (cognitive 19) web/assets/js/app.js:840— mounted::onKey has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 9 (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. This file is where this pass's cognitive complexity CONCENTRATES: web/assets/js/app.js holds 5 of the 11 methods over the threshold — including the worst — and 31 of the 69 points over it (45%), 2.4× the next-largest file (packages/raxol_terminal/lib/raxol/terminal/renderer.ex at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Unicode.wide_char? (cognitive 17) packages/raxol_terminal/lib/raxol/terminal/unicode.ex:134— Unicode.wide_char? has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. 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.
intent (cognitive 16) web/assets/js/app.js:273— intent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, boolean chains 5, ternaries 2 (4 pts), 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. This file is where this pass's cognitive complexity CONCENTRATES: web/assets/js/app.js holds 5 of the 11 methods over the threshold — including the worst — and 31 of the 69 points over it (45%), 2.4× the next-largest file (packages/raxol_terminal/lib/raxol/terminal/renderer.ex at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
mounted (cognitive 16) web/assets/js/app.js:665— mounted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, boolean chains 4. 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 (onKeydown, step, onClick, …). 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. This file is where this pass's cognitive complexity CONCENTRATES: web/assets/js/app.js holds 5 of the 11 methods over the threshold — including the worst — and 31 of the 69 points over it (45%), 2.4× the next-largest file (packages/raxol_terminal/lib/raxol/terminal/renderer.ex at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) lib/mix/tasks/raxol.memory.stability.ex:222— lib/mix/tasks/raxol.memory.stability.ex:222-251 | lib/mix/tasks/raxol.memory.stability.ex:255-294 — These two members are one piece of code written twice and then edited apart: 30 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 (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) lib/mix/tasks/raxol.memory.gates.ex:66— lib/mix/tasks/raxol.memory.gates.ex:66-108 | lib/mix/tasks/raxol.memory.stability.ex:65-107 — These two members are one piece of code written twice and then edited apart: 43 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:119— packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:119-159 | packages/raxol_terminal/lib/raxol/terminal/commands/command_server/buffer_line_ops.ex:170-203 — These two members are one piece of code written twice and then edited apart: 34 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, 38+ corresponding lines) · ×1
Edited copies of one member (3 members, 38+ corresponding lines) lib/raxol/config/schema/definitions.ex:7— lib/raxol/config/schema/definitions.ex:7-44 | lib/raxol/config/schema/definitions.ex:151-191 | lib/raxol/config/schema/definitions.ex:238-285 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 38 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, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) lib/raxol/ui/components/harness/context_meter.ex:49— lib/raxol/ui/components/harness/context_meter.ex:49-80 | lib/raxol/ui/components/harness/drift_indicator.ex:48-76 | lib/raxol/ui/components/harness/spend_meter.ex:48-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) lib/raxol/core/metrics/visualizer.ex:168— lib/raxol/core/metrics/visualizer.ex:168-201 | lib/raxol/core/metrics/visualizer.ex:205-236 | lib/raxol/core/metrics/visualizer.ex:280-314 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 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 (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) lib/mix/tasks/raxol.memory.debug.ex:87— lib/mix/tasks/raxol.memory.debug.ex:87-131 | lib/mix/tasks/raxol.memory.profiler.ex:71-116 — These two members are one piece of code written twice and then edited apart: 45 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) lib/raxol/config/schema/definitions.ex:314— lib/raxol/config/schema/definitions.ex:314-348 | lib/raxol/config/schema/definitions.ex:375-414 — These two members are one piece of code written twice and then edited apart: 35 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, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:80— packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:80-112 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:225-248 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:264-301 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:339-370 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) lib/raxol/workflow/runtime.ex:454— lib/raxol/workflow/runtime.ex:454-485 | lib/raxol/workflow/runtime.ex:1144-1181 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/color/true_color/ansi_codes.ex:37— packages/raxol_terminal/lib/raxol/terminal/color/true_color/ansi_codes.ex:37-43 | packages/raxol_terminal/lib/raxol/terminal/color/true_color/ansi_codes.ex:50-57 | packages/raxol_terminal/lib/raxol/terminal/color/true_color/ansi_codes.ex:64-70 | packages/raxol_terminal/lib/raxol/terminal/color/true_color/ansi_codes.ex:77-84 — 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 copies of one member (5 members, 21+ corresponding lines) · ×1
Edited copies of one member (5 members, 21+ corresponding lines) lib/mix/tasks/raxol.check.ex:198— lib/mix/tasks/raxol.check.ex:198-218 | lib/mix/tasks/raxol.check.ex:222-245 | lib/mix/tasks/raxol.check.ex:249-272 | lib/mix/tasks/raxol.check.ex:276-299 | lib/mix/tasks/raxol.check.ex:303-324 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 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, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) lib/raxol/ui/components/harness/memory_panel.ex:44— lib/raxol/ui/components/harness/memory_panel.ex:44-63 | lib/raxol/ui/components/harness/rules_panel.ex:47-66 | lib/raxol/ui/components/harness/worktracks_panel.ex:46-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:40— packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:40-69 | packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:100-127 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) lib/raxol/ui/components/harness/context_meter.ex:32— lib/raxol/ui/components/harness/context_meter.ex:32-43 | lib/raxol/ui/components/harness/drift_indicator.ex:31-42 | lib/raxol/ui/components/harness/spend_meter.ex:31-42 | lib/raxol/ui/components/harness/toast.ex:33-42 | lib/raxol/ui/components/harness/tool_call_block.ex:42-52 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) lib/raxol/animation/dsl.ex:186— lib/raxol/animation/dsl.ex:186-207 | lib/raxol/animation/dsl.ex:227-248 | lib/raxol/animation/dsl.ex:258-279 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/screen.ex:47— packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/screen.ex:47-66 | packages/raxol_terminal/lib/raxol/terminal/commands/csi_handler/screen.ex:70-89 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:488-509 | packages/raxol_terminal/lib/raxol/terminal/emulator/command_handler.ex:514-535 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 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, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/cursor/movement.ex:16— packages/raxol_terminal/lib/raxol/terminal/cursor/movement.ex:16-30 | packages/raxol_terminal/lib/raxol/terminal/cursor/movement.ex:43-57 | packages/raxol_terminal/lib/raxol/terminal/cursor/movement.ex:65-79 | packages/raxol_terminal/lib/raxol/terminal/cursor/movement.ex:87-101 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 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 (7 members, 9+ corresponding lines) · ×1
Edited copies of one member (7 members, 9+ corresponding lines) lib/raxol/view/components.ex:144— lib/raxol/view/components.ex:144-152 | lib/raxol/view/components.ex:161-170 | lib/raxol/view/components.ex:183-191 | lib/raxol/view/components.ex:394-404 | lib/raxol/view/components.ex:412-421 | lib/raxol/view/components.ex:434-443 | lib/raxol/view/components.ex:502-511 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:170— packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:170-183 | packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:209-217 | packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:222-230 | packages/raxol_terminal/lib/raxol/terminal/split/split_manager.ex:249-257 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 22+ corresponding lines) · ×1
Edited copies of one member (4 members, 22+ corresponding lines) lib/raxol/plugins/hyperlink_plugin.ex:41— lib/raxol/plugins/hyperlink_plugin.ex:41-62 | lib/raxol/plugins/image_plugin.ex:50-73 | lib/raxol/plugins/search_plugin.ex:40-64 | lib/raxol/plugins/theme_plugin.ex:27-50 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 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, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) lib/raxol/ui/charts/scatter_chart.ex:141— lib/raxol/ui/charts/scatter_chart.ex:141-158 | lib/raxol/ui/components/display/viewport.ex:342-360 | lib/raxol/ui/components/input/menu.ex:373-389 | lib/raxol/ui/components/input/select_list.ex:654-677 — These 4 members are one piece of code written 4 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 4 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) packages/raxol_terminal/lib/raxol/terminal/buffer/concurrent_buffer.ex:271— packages/raxol_terminal/lib/raxol/terminal/buffer/concurrent_buffer.ex:271-275 | packages/raxol_terminal/lib/raxol/terminal/buffer/concurrent_buffer.ex:321-326 | packages/raxol_terminal/lib/raxol/terminal/screen_buffer/operations.ex:323-327 — 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, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) lib/raxol/plugins/event_handler/input_events.ex:43— lib/raxol/plugins/event_handler/input_events.ex:43-61 | lib/raxol/plugins/event_handler/mouse_events.ex:56-74 | lib/raxol/plugins/event_handler/output_events.ex:18-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 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, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) lib/raxol/ui/components/input/text_field.ex:84— lib/raxol/ui/components/input/text_field.ex:84-107 | lib/raxol/ui/components/input/text_field.ex:112-130 | lib/raxol/ui/components/input/text_field.ex:255-267 | lib/raxol/ui/components/input/text_field.ex:271-283 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:166— packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex:166-168 | packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_entry_state.ex:116-118 | packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_state.ex:101-103 | packages/raxol_terminal/lib/raxol/terminal/parser/states/escape_state.ex:67-69 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×1
Edited copy of a member (1 corresponding lines) lib/raxol/style/style.ex:50— lib/raxol/style/style.ex:50-52 | packages/raxol_terminal/lib/raxol/terminal/integration/integration_state.ex:126-126 — 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.
Duplicated block (52 lines × 2) packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:59— packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:59-110 | packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:169-220 — 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 `packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:59` 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 before the matched lines, `packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:167` calls `get` and `packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:57` 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.
Duplicated block (26–42 lines × 2) packages/raxol_core/lib/raxol/core/telemetry/context.ex:346— packages/raxol_core/lib/raxol/core/telemetry/context.ex:346-387 | packages/raxol_core/lib/raxol/core/telemetry/trace_context.ex:378-403 — 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 (34–35 lines × 2) lib/raxol/performance/caches/font_metrics_cache.ex:162— lib/raxol/performance/caches/font_metrics_cache.ex:162-195 | packages/raxol_terminal/lib/raxol/terminal/input.ex:138-172 — 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 (35 lines × 2) packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:10— packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:10-44 | packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_reloader.ex:51-85 — 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 (33–34 lines × 2) packages/raxol_core/lib/raxol/core/error_recovery.ex:375— packages/raxol_core/lib/raxol/core/error_recovery.ex:375-408 | packages/raxol_core/lib/raxol/core/error_recovery.ex:418-450 — 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 `packages/raxol_core/lib/raxol/core/error_recovery.ex:375` 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 (31–34 lines × 2) packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex:30— packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex:30-60 | packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_maybe_st_state.ex:37-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_maybe_st_state.ex:37` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (31 lines × 2) lib/raxol/ui/layout/css_grid.ex:104— lib/raxol/ui/layout/css_grid.ex:104-134 | lib/raxol/ui/layout/css_grid.ex:195-225 — 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 (19–28 lines × 2) packages/raxol_terminal/lib/raxol/terminal/driver.ex:888— packages/raxol_terminal/lib/raxol/terminal/driver.ex:888-915 | packages/raxol_terminal/lib/raxol/terminal/inline_driver.ex:1066-1084 — 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 (25–27 lines × 2) packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex:631— packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex:631-657 | packages/raxol_terminal/lib/raxol/terminal/charset/maps.ex:10-34 — 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 `packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex:631` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25–26 lines × 2) lib/raxol/ui/theming/theme.ex:211— lib/raxol/ui/theming/theme.ex:211-235 | lib/raxol/ui/theming/theme.ex:266-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/theming/theme.ex:211` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (24–25 lines × 10) packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:274— packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:274-297 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:304-327 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:334-357 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:364-387 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:394-417 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:424-447 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:454-477 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:484-507 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:514-537 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:544-568 — all 10 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 `packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:544` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) lib/raxol/ui/components/harness/context_meter.ex:59— lib/raxol/ui/components/harness/context_meter.ex:59-80 | lib/raxol/ui/components/harness/drift_indicator.ex:55-76 | lib/raxol/ui/components/harness/spend_meter.ex:58-79 — 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.
Duplicated block (18–21 lines × 3) packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:44— packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:44-64 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:231-248 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:350-370 — 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 `packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex: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.
Duplicated block (21 lines × 2) lib/raxol/plugins/visualization/treemap_renderer.ex:138— lib/raxol/plugins/visualization/treemap_renderer.ex:138-158 | lib/raxol/plugins/visualization/treemap_renderer.ex:589-609 — 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 (17–21 lines × 2) lib/raxol/ui/layout/responsive.ex:86— lib/raxol/ui/layout/responsive.ex:86-106 | lib/raxol/ui/layout/responsive.ex:145-161 — 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 `lib/raxol/ui/layout/responsive.ex:86` 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 (20 lines × 2) lib/raxol/headless/mcp_tools.ex:227— lib/raxol/headless/mcp_tools.ex:227-248 | lib/raxol/headless/mcp_tools.ex:249-268 — 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 `lib/raxol/headless/mcp_tools.ex:227` 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 (13–18 lines × 3) lib/mix/tasks/raxol.new.ex:146— lib/mix/tasks/raxol.new.ex:146-158 | lib/mix/tasks/raxol.new.ex:163-180 | lib/mix/tasks/raxol.replay.ex:173-185 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mix/tasks/raxol.new.ex:163` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/mix/tasks/raxol.replay.ex:188` calls `shell`, `error` and `lib/mix/tasks/raxol.new.ex:158` 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 (15–18 lines × 2) lib/raxol/ui/charts/line_chart.ex:175— lib/raxol/ui/charts/line_chart.ex:175-192 | lib/raxol/ui/charts/scatter_chart.ex:141-155 — 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 `lib/raxol/ui/charts/line_chart.ex: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. 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 (18 lines × 2) packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:171— packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:171-188 | packages/raxol_core/lib/raxol/core/runtime/plugins/lifecycle_manager.ex:201-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.
Duplicated block (11–17 lines × 2) lib/raxol/ui/layout/responsive.ex:47— lib/raxol/ui/layout/responsive.ex:47-63 | lib/raxol/ui/layout/responsive.ex:119-129 — 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 (15–17 lines × 2) packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:189— packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:189-203 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:207-223 — 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 `packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:189` 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 × 11) packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:281— packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:281-296 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:311-326 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:341-356 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:371-386 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:401-416 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:431-446 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:461-476 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:491-506 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:521-536 | packages/raxol_core/lib/raxol/core/theming/theme_registry.ex:551-566 | packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/colors.ex:52-67 — there are 11 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 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/colors.ex:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–16 lines × 2) bench/suites/comparison/framework_comparison.exs:187— bench/suites/comparison/framework_comparison.exs:187-202 | lib/mix/tasks/raxol.bench.ex:271-280 — 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. 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 (15 lines × 3) lib/raxol/ui/components/input/password_field.ex:40— lib/raxol/ui/components/input/password_field.ex:40-54 | lib/raxol/ui/components/input/text_area.ex:37-51 | lib/raxol/ui/components/input/text_input.ex:185-199 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/input/password_field.ex:40` 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–14 lines × 3) packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:93— packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:93-106 | packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:203-216 | packages/raxol_terminal/lib/raxol/terminal/emulator/factory.ex:84-95 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13–14 lines × 2) lib/raxol/memory/collector.ex:31— lib/raxol/memory/collector.ex:31-44 | lib/raxol/memory/collector.ex:53-65 — 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 `lib/raxol/memory/collector.ex:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–13 lines × 4) lib/raxol/ui/components/input/password_field.ex:47— lib/raxol/ui/components/input/password_field.ex:47-56 | lib/raxol/ui/components/input/scrubber.ex:711-723 | lib/raxol/ui/components/input/text_area.ex:44-52 | lib/raxol/ui/components/input/text_input.ex:192-201 — before extracting anything, compare `lib/raxol/ui/components/input/scrubber.ex` and `lib/raxol/ui/components/input/text_area.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/input/password_field.ex:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (13 lines × 3) packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex:635— packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex:635-658 | packages/raxol_terminal/lib/raxol/terminal/character_sets.ex:39-51 | packages/raxol_terminal/lib/raxol/terminal/charset/maps.ex:178-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex:635` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) lib/mix/tasks/raxol.memory.stability.ex:236— lib/mix/tasks/raxol.memory.stability.ex:236-246 | lib/mix/tasks/raxol.memory.stability.ex:275-287 — 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 `lib/mix/tasks/raxol.memory.stability.ex:236` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) lib/raxol/core/renderer/color.ex:218— lib/raxol/core/renderer/color.ex:218-229 | lib/raxol/ui/theming/palette.ex:592-604 — 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 (11–12 lines × 3) lib/raxol/ui/components/harness/memory_panel.ex:47— lib/raxol/ui/components/harness/memory_panel.ex:47-57 | lib/raxol/ui/components/harness/rules_panel.ex:50-61 | lib/raxol/ui/components/harness/worktracks_panel.ex:49-59 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/harness/memory_panel.ex:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) lib/raxol/ui/components/input/checkbox.ex:173— lib/raxol/ui/components/input/checkbox.ex:173-184 | lib/raxol/ui/components/input/scrubber.ex:725-736 | lib/raxol/ui/components/input/text_area.ex:48-59 — before extracting anything, compare `lib/raxol/ui/components/input/scrubber.ex` and `lib/raxol/ui/components/input/text_area.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/raxol/ui/components/input/checkbox.ex:173` 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–11 lines × 4) packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:94— packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:94-102 | packages/raxol_terminal/lib/raxol/terminal/emulator/constructors.ex:204-212 | packages/raxol_terminal/lib/raxol/terminal/emulator/factory.ex:85-93 | packages/raxol_terminal/lib/raxol/terminal/emulator_lite.ex:317-327 — there are 4 copies across 3 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.
Duplicated block (9–11 lines × 2) packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex:25— packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex:25-35 | packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_state.ex:38-46 — 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–10 lines × 2) lib/raxol/ui/components/input/menu.ex:271— lib/raxol/ui/components/input/menu.ex:271-278 | lib/raxol/ui/components/input/menu.ex:307-316 — 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–8 lines × 3) packages/raxol_watch/lib/raxol/watch/formatter.ex:94— packages/raxol_watch/lib/raxol/watch/formatter.ex:94-101 | packages/raxol_watch/lib/raxol/watch/formatter.ex:110-116 | packages/raxol_watch/lib/raxol/watch/formatter.ex:140-147 — 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 `packages/raxol_watch/lib/raxol/watch/formatter.ex:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (4–5 lines × 3) packages/raxol_terminal/lib/raxol/terminal/buffer/cell.ex:320— packages/raxol_terminal/lib/raxol/terminal/buffer/cell.ex:320-323 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:386-390 | packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:645-649 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/session/serializer.ex:386` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 3) lib/mix/tasks/raxol.bench.memory.ex:689— lib/mix/tasks/raxol.bench.memory.ex:689-703 | lib/mix/tasks/raxol.memory.profiler.ex:637-653 | lib/raxol/memory/formatter.ex:59-72 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/raxol/memory/formatter.ex:75` calls `print_top_processes` and `lib/mix/tasks/raxol.bench.memory.ex:703` 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 (7 lines × 4) lib/raxol/animation/gestures/gesture_server.ex:58— lib/raxol/animation/gestures/gesture_server.ex:58-64 | lib/raxol/performance/memoization/memoization_server.ex:25-31 | lib/raxol/security/user_context/context_server.ex:31-37 | lib/raxol/style/colors/system/color_system_server.ex:39-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (7 lines × 3) packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:143— packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:143-149 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:160-166 | packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex:193-199 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex: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.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) examples/apps/showcase_app.exs:170— examples/apps/showcase_app.exs:170-209 | lib/raxol/demo/showcase.ex:174-223 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) examples/advanced/architecture/architecture_demo.exs:27— examples/advanced/architecture/architecture_demo.exs:27-54 | examples/advanced/architecture/dashboard.exs:20-44 | examples/getting_started/counter.exs:32-64 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) lib/raxol/harness/fixture.ex:370— lib/raxol/harness/fixture.ex:370-380 | lib/raxol/harness/fixture.ex:384-394 | lib/raxol/harness/fixture.ex:398-408 | lib/raxol/harness/fixture.ex:412-422 | lib/raxol/harness/fixture.ex:426-436 | lib/raxol/harness/fixture.ex:440-450 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
Duplicated block (36 lines × 2) scripts/testing/test_dashboard_layout_integration.exs:62— scripts/testing/test_dashboard_layout_integration.exs:62-97 | scripts/testing/test_terminal_visualization.exs:61-96 — before extracting anything, compare `scripts/testing/test_dashboard_layout_integration.exs` and `scripts/testing/test_terminal_visualization.exs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/testing/test_dashboard_layout_integration.exs:62` 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 (25–34 lines × 2) bench/suites/visualization/visualization_benchmark.ex:81— bench/suites/visualization/visualization_benchmark.ex:81-114 | bench/suites/visualization/visualization_benchmark.ex:183-207 — 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 `bench/suites/visualization/visualization_benchmark.ex:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (32 lines × 2) scripts/testing/test_terminal_visualization.exs:32— scripts/testing/test_terminal_visualization.exs:32-63 | scripts/testing/test_visualization.exs:30-61 — before extracting anything, compare `scripts/testing/test_terminal_visualization.exs` and `scripts/testing/test_visualization.exs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (28 lines × 2) scripts/check_package_boundaries.exs:1207— scripts/check_package_boundaries.exs:1207-1234 | scripts/check_package_boundaries.exs:1267-1294 — 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 `scripts/check_package_boundaries.exs:1207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–26 lines × 2) scripts/testing/test_dashboard_layout_integration.exs:118— scripts/testing/test_dashboard_layout_integration.exs:118-136 | scripts/testing/test_dashboard_layout_integration.exs:151-176 — 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 `scripts/testing/test_dashboard_layout_integration.exs:118` 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 (21–25 lines × 2) examples/getting_started/counter.exs:71— examples/getting_started/counter.exs:71-95 | lib/raxol/demo/counter.ex:47-67 — before extracting anything, compare `examples/getting_started/counter.exs` and `lib/raxol/demo/counter.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12–24 lines × 2) bench/suites/performance/reporting.ex:34— bench/suites/performance/reporting.ex:34-57 | scripts/testing/verify_terminal_compatibility.exs:24-35 — 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 `bench/suites/performance/reporting.ex:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (23 lines × 2) examples/apps/showcase_app.exs:260— examples/apps/showcase_app.exs:260-282 | lib/raxol/demo/showcase.ex:282-304 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22–23 lines × 2) examples/demo.exs:83— examples/demo.exs:83-105 | lib/raxol/playground/demos/beam_dashboard_demo.ex:39-60 — 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 `examples/demo.exs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 3) scripts/testing/test_dashboard_layout_integration.exs:77— scripts/testing/test_dashboard_layout_integration.exs:77-94 | scripts/testing/test_layout_persistence.exs:52-70 | scripts/testing/test_terminal_visualization.exs:76-93 — before extracting anything, compare `scripts/testing/test_dashboard_layout_integration.exs` and `scripts/testing/test_terminal_visualization.exs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/testing/test_dashboard_layout_integration.exs:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 3) bench/memory/load_memory_benchmark.exs:31— bench/memory/load_memory_benchmark.exs:31-47 | bench/memory/plugin_memory_benchmark.exs:33-49 | bench/memory/terminal_memory_benchmark.exs:30-46 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bench/memory/plugin_memory_benchmark.exs:31` calls `ensure_plugin_runtime_started` and `bench/memory/load_memory_benchmark.exs:30` 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.
Duplicated block (16–17 lines × 2) examples/getting_started/todo_app.exs:232— examples/getting_started/todo_app.exs:232-247 | lib/raxol/demo/todo.ex:166-182 — before extracting anything, compare `examples/getting_started/todo_app.exs` and `lib/raxol/demo/todo.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 4) scripts/testing/test_dashboard_layout_integration.exs:147— scripts/testing/test_dashboard_layout_integration.exs:147-165 | scripts/testing/test_dashboard_layout_integration.exs:187-205 | scripts/testing/test_dashboard_layout_integration.exs:257-272 | scripts/testing/test_dashboard_layout_integration.exs:307-325 — 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.
Duplicated block (13–15 lines × 4) examples/apps/showcase_app.exs:266— examples/apps/showcase_app.exs:266-278 | examples/getting_started/counter.exs:78-92 | lib/raxol/demo/counter.ex:52-64 | lib/raxol/demo/showcase.ex:288-300 — before extracting anything, compare `examples/apps/showcase_app.exs` and `lib/raxol/demo/showcase.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/apps/showcase_app.exs:266` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/apps/showcase_app.exs:279` calls `text` and `examples/getting_started/counter.exs:93` 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.
Duplicated block (13–15 lines × 2) bench/suites/visualization/visualization_benchmark_realistic.ex:24— bench/suites/visualization/visualization_benchmark_realistic.ex:24-36 | bench/suites/visualization/visualization_benchmark_simple.ex:23-37 — 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 `bench/suites/visualization/visualization_benchmark_realistic.ex:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 2) scripts/testing/test_layout_persistence.exs:88— scripts/testing/test_layout_persistence.exs:88-102 | scripts/testing/test_layout_persistence.exs:190-203 — 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–14 lines × 9) examples/advanced/architecture/architecture_demo.exs:44— examples/advanced/architecture/architecture_demo.exs:44-54 | examples/advanced/architecture/cloud_integration.exs:70-80 | examples/advanced/architecture/dashboard.exs:34-44 | examples/advanced/commands.exs:32-42 | examples/components/displays/progress_bar_demo.ex:43-53 | examples/components/navigation/select_list_showcase.ex:52-62 | examples/demo.exs:149-159 | examples/getting_started/hello_world.exs:49-62 | examples/scripts/subscriptions.exs:38-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 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 9 times.
Duplicated block (13–14 lines × 3) scripts/testing/test_dashboard_layout_integration.exs:47— scripts/testing/test_dashboard_layout_integration.exs:47-60 | scripts/testing/test_terminal_visualization.exs:45-57 | scripts/testing/test_visualization.exs:43-55 — before extracting anything, compare `scripts/testing/test_dashboard_layout_integration.exs` and `scripts/testing/test_terminal_visualization.exs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/testing/test_dashboard_layout_integration.exs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–23 lines × 2) bench/live_view/rendering_benchmark.exs:32— bench/live_view/rendering_benchmark.exs:32-45 | bench/live_view/rendering_benchmark.exs:173-195 — 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 `bench/live_view/rendering_benchmark.exs: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 (12–14 lines × 2) bench/suites/visualization/visualization_benchmark.ex:115— bench/suites/visualization/visualization_benchmark.ex:115-128 | bench/suites/visualization/visualization_benchmark.ex:250-261 — 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 `bench/suites/visualization/visualization_benchmark.ex:115` 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–14 lines × 2) examples/getting_started/todo_app.exs:128— examples/getting_started/todo_app.exs:128-141 | lib/raxol/demo/todo.ex:81-91 — before extracting anything, compare `examples/getting_started/todo_app.exs` and `lib/raxol/demo/todo.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–13 lines × 4) scripts/testing/test_dashboard_layout_integration.exs:27— scripts/testing/test_dashboard_layout_integration.exs:27-39 | scripts/testing/test_layout_persistence.exs:23-32 | scripts/testing/test_terminal_visualization.exs:34-46 | scripts/testing/test_visualization.exs:32-44 — before extracting anything, compare `scripts/testing/test_dashboard_layout_integration.exs` and `scripts/testing/test_terminal_visualization.exs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/testing/test_dashboard_layout_integration.exs:27` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–13 lines × 3) examples/getting_started/counter.exs:70— examples/getting_started/counter.exs:70-82 | examples/ssh/ssh_counter.exs:50-60 | lib/raxol/demo/counter.ex:46-56 — before extracting anything, compare `examples/getting_started/counter.exs` and `lib/raxol/demo/counter.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/getting_started/counter.exs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) lib/raxol/demo/dashboard.ex:171— lib/raxol/demo/dashboard.ex:171-179 | lib/raxol/demo/dashboard.ex:242-250 | lib/raxol/demo/dashboard.ex:307-315 — 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 `lib/raxol/demo/dashboard.ex:171` 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–15 lines × 2) examples/advanced/editor.exs:45— examples/advanced/editor.exs:45-55 | examples/components/forms/form_validation.exs:53-67 — before extracting anything, compare `examples/advanced/editor.exs` and `examples/components/forms/form_validation.exs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/advanced/editor.exs:45` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5–8 lines × 3) examples/dev/hot_reload_demo.exs:34— examples/dev/hot_reload_demo.exs:34-41 | examples/getting_started/counter.exs:53-57 | examples/ssh/ssh_counter.exs:38-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `examples/getting_started/counter.exs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 15) examples/advanced/architecture/architecture_demo.exs:44— examples/advanced/architecture/architecture_demo.exs:44-50 | examples/advanced/architecture/cloud_integration.exs:70-76 | examples/advanced/architecture/dashboard.exs:34-40 | examples/advanced/commands.exs:32-38 | examples/advanced/documentation_browser.exs:69-75 | examples/advanced/snake.exs:46-52 | examples/apps/file_browser.exs:58-64 | examples/apps/showcase_app.exs:59-65 | examples/components/displays/code_block_demo.exs:67-73 | examples/components/displays/progress_bar_demo.ex:43-49 | examples/components/displays/viewport_demo.exs:40-46 | examples/components/navigation/select_list_showcase.ex:52-58 | examples/demo.exs:149-155 | examples/getting_started/hello_world.exs:49-56 | examples/scripts/subscriptions.exs:38-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 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 15 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/advanced/documentation_browser.exs:79` calls `max` and `examples/advanced/architecture/architecture_demo.exs:52` 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 (7 lines × 8) examples/advanced/documentation_browser.exs:69— examples/advanced/documentation_browser.exs:69-75 | examples/apps/file_browser.exs:58-64 | examples/apps/showcase_app.exs:59-65 | examples/components/displays/code_block_demo.exs:67-73 | examples/components/displays/viewport_demo.exs:40-46 | examples/components/forms/form_validation.exs:57-63 | examples/components/input/multi_line_input_demo.exs:51-57 | examples/getting_started/todo_app.exs:52-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times.
Duplicated block (5 lines × 7) examples/advanced/editor.exs:47— examples/advanced/editor.exs:47-51 | examples/apps/file_browser.exs:60-64 | examples/apps/showcase_app.exs:61-65 | examples/components/displays/code_block_demo.exs:69-73 | examples/components/forms/form_validation.exs:53-60 | examples/components/input/multi_line_input_demo.exs:47-54 | examples/getting_started/todo_app.exs:54-58 — before extracting anything, compare `examples/advanced/editor.exs` and `examples/components/forms/form_validation.exs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/components/forms/form_validation.exs:53` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/apps/file_browser.exs:58` calls `stop` and `examples/components/input/multi_line_input_demo.exs:46` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) scripts/harness/t0/ringb/drivers/iterm2.ex:100— scripts/harness/t0/ringb/drivers/iterm2.ex:100-112 | scripts/harness/t0/ringb/drivers/terminal_app.ex:94-103 | scripts/harness/t0/ringb/drivers/terminal_app.ex:131-141 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (19 lines × 2 locations) web/assets/js/app.js:442— web/assets/js/app.js:442 · web/assets/js/app.js:807 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) web/assets/js/app.js:369— web/assets/js/app.js:369 · web/assets/js/app.js:694 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) web/assets/js/app.js:75— web/assets/js/app.js:75 · web/priv/static/js/app.js:111 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) web/assets/js/app.js:411— web/assets/js/app.js:411 · web/assets/js/app.js:746 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) web/assets/js/app.js:356— web/assets/js/app.js:356 · web/assets/js/app.js:677 — 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 locations) web/assets/js/app.js:550— web/assets/js/app.js:550 · web/assets/js/app.js:1064 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function (anonymous) (cyclomatic 29, cognitive 25) web/assets/js/app.js:1164— (anonymous) has cyclomatic complexity 29 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.
Complex function onKey (cyclomatic 21, cognitive 19) web/assets/js/app.js:840— onKey has cyclomatic complexity 21 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 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 intent (cyclomatic 20, cognitive 16) web/assets/js/app.js:273— intent has cyclomatic complexity 20 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.
Complex function buildMask (cyclomatic 14, cognitive 30) web/assets/js/app.js:971— buildMask has cyclomatic complexity 14 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.
web/assets/js/app.js: 1096 lines of code web/assets/js/app.js:1— web/assets/js/app.js has 1096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked editors/vscode/package.json:93— editors/vscode/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X18 · Disposal-pattern correctness· Opened resource is not closed on every path · ×1
Opened resource is not closed on every path lib/raxol/harness/editor_session.ex:211— `:file.open(path, [:write, :exclusive, :binary, :raw])` opens a file here (line 211), and the `with` clause `:ok <- …` on line 212 can fail to match, and `with` then returns without running the block that closes it. Nothing else owns it: it is not returned, kept in a process's state or handed to another process, so it stays open until the process that opened it exits — one more file held per call in a long-lived process, `:emfile` under load. Close it on every path: `try … after File.close(…) end`, a block form that closes for you (`File.open(path, modes, fn device -> … end)`), or a close in every branch — or hand it to the process that owns it.
Orphaned file bench/suites/visualization/visualization_benchmark.ex: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 lib/raxol/harness/diff_expansion.ex: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 lib/raxol/animation/physics/physics_engine.ex: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 packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex: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 lib/raxol/harness/editor_suspend.ex: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 packages/raxol_terminal/lib/raxol/terminal/buffer/scroll_region.ex: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 lib/raxol/core/core.ex: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 lib/raxol/harness/fixture.ex: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 packages/raxol_terminal/lib/raxol/terminal/emulator/struct.ex: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 packages/raxol_terminal/lib/raxol/terminal/window/window_server.ex: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 packages/raxol_terminal/lib/raxol/terminal/mouse/mouse_server.ex: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 packages/raxol_terminal/lib/raxol/terminal/capabilities/reply_scanner.ex: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 lib/raxol/style/colors/gradient.ex: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 packages/raxol_terminal/lib/raxol/terminal/character_handling.ex: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 scripts/harness/t0/lib/verdict_resolver_core.exs: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 lib/raxol/style/colors/adaptive.ex: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 scripts/harness/t0/ringb/guard.ex: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 packages/raxol_terminal/lib/raxol/terminal/ansi/sequence_handler.ex: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 packages/raxol_terminal/lib/raxol/terminal/commands/window_handler.ex: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 packages/raxol_terminal/lib/raxol/terminal/cell.ex: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 packages/raxol_terminal/lib/raxol/terminal/theme/theme_server.ex: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 scripts/testing/test_dashboard_layout_integration.exs: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 lib/raxol/animation/easing.ex: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 bench/suites/visualization/visualization_benchmark_realistic.ex: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 packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/colors.ex: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.
Duplicated predicate lib/raxol/core/accessibility/theme_integration.ex:352— `Code.ensure_loaded?(Mix) and Mix.env() == :test` appears character-identically in 3 files — lib/raxol/core/accessibility/theme_integration.ex, lib/raxol/core/runtime/events/dispatcher.ex, packages/raxol_core/lib/raxol/core/user_preferences.ex. 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 lib/raxol/ui/style_processor.ex:289— `Code.ensure_loaded?(Raxol.Performance.ETSCacheManager) and Process.whereis(Raxol.Performance.ETSCacheManager) != nil` appears character-identically in 2 files — lib/raxol/ui/style_processor.ex, lib/raxol/ui/theme_resolver.ex. 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 packages/raxol_mcp/lib/raxol/mcp/tool_def.ex:209— `Map.get(annotations, key) || Map.get(annotations, Atom.to_string(key))` appears character-identically in 2 files — packages/raxol_mcp/lib/raxol/mcp/tool_def.ex, packages/raxol_mcp/lib/raxol/mcp/tree_walker.ex. 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 lib/raxol/ui/layout/engine.ex:440— `Map.get(box, :border) || Map.get(style, :border, :none)` appears character-identically in 2 files — lib/raxol/ui/layout/engine.ex, lib/raxol/ui/layout/min_content.ex. 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 lib/raxol/ui/border_renderer.ex:111— `Map.get(style, :bg) || Map.get(style, :background)` appears character-identically in 2 files — lib/raxol/ui/border_renderer.ex, lib/raxol/ui/element_renderer.ex. 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 lib/raxol/animation/adaptation.ex:40— `Raxol.Core.UserPreferences.get( [:accessibility, :cognitive_accessibility], user_preferences_pid ) || false` appears character-identically in 2 files — lib/raxol/animation/adaptation.ex, lib/raxol/animation/framework.ex. 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 lib/raxol/animation/adaptation.ex:34— `Raxol.Core.UserPreferences.get( [:accessibility, :reduced_motion], user_preferences_pid ) || false` appears character-identically in 2 files — lib/raxol/animation/adaptation.ex, lib/raxol/animation/framework.ex. 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 lib/raxol/ui/components/display/tree.ex:138— `Raxol.UI.FocusHelper.focused?(state.id, context) or state.focused` appears character-identically in 8 files — lib/raxol/ui/components/display/tree.ex, lib/raxol/ui/components/display/viewport.ex, lib/raxol/ui/components/input/checkbox.ex, lib/raxol/ui/components/input/menu.ex. 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 mix.exs:247— `System.get_env("HEX_BUILD") != nil or File.exists?("hex_metadata.config")` appears character-identically in 9 files — mix.exs, packages/raxol_gateway/mix.exs, packages/raxol_liveview/mix.exs, packages/raxol_mcp/mix.exs. 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 lib/raxol/application.ex:558— `System.get_env("RAXOL_SSH_HOST_KEYS_DIR") || "/app/ssh_keys"` appears character-identically in 2 files — lib/raxol/application.ex, web/lib/raxol_playground/application.ex. 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 web/lib/raxol_playground/application.ex:99— `System.get_env("RAXOL_SSH_PORT") || "2222"` appears character-identically in 2 files — web/lib/raxol_playground/application.ex, web/lib/raxol_playground_web/controllers/health_controller.ex. 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 packages/raxol_core/lib/raxol/core/error_recovery.ex:387— `Task.yield(task, 5000) || Task.shutdown(task, :brutal_kill)` appears character-identically in 3 files — packages/raxol_core/lib/raxol/core/error_recovery.ex, packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex, packages/raxol_terminal/lib/raxol/terminal/session.ex. 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 packages/raxol_core/lib/raxol/core/runtime/plugins/command_registry.ex:271— `Task.yield(task, timeout) || Task.shutdown(task, :brutal_kill)` appears character-identically in 4 files — packages/raxol_core/lib/raxol/core/runtime/plugins/command_registry.ex, packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_supervisor.ex, packages/raxol_core/lib/raxol/core/runtime/plugins/plugin_validator.ex, packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex. 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 lib/raxol/core/metrics.ex:89— `Task.yield(task, timeout_ms) || Task.shutdown(task)` appears character-identically in 2 files — lib/raxol/core/metrics.ex, packages/raxol_speech/lib/raxol/speech/recognizer.ex. 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 packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_state.ex:100— `abort_byte == 0x18 or abort_byte == 0x1A` appears character-identically in 2 files — packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/osc_string_state.ex. 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 packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex:155— `buffer.default_style || TextFormatting.new()` appears character-identically in 2 files — packages/raxol_terminal/lib/raxol/terminal/commands/scrolling.ex, packages/raxol_terminal/lib/raxol/terminal/screen_buffer/attributes.ex. 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 packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:54— `ignored_byte == 0x18 or ignored_byte == 0x1A` appears character-identically in 5 files — packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/dcs_passthrough_maybe_st_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/escape_state.ex. 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 packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:58— `ignored_byte >= 0 and ignored_byte <= 23 and ignored_byte != 0x18 and ignored_byte != 0x1A` appears character-identically in 2 files — packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex. 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 packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:60— `ignored_byte >= 27 and ignored_byte <= 31` appears character-identically in 2 files — packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex. 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 packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex:36— `intermediate_byte >= 0x20 and intermediate_byte <= 0x2F` appears character-identically in 2 files — packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_intermediate_state.ex, packages/raxol_terminal/lib/raxol/terminal/parser/states/csi_param_state.ex. 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 lib/raxol/core/runtime/events/dispatcher.ex:1041— `is_atom(event_type) and is_map(event_data)` appears character-identically in 2 files — lib/raxol/core/runtime/events/dispatcher.ex, packages/raxol_core/lib/raxol/core/events/event_manager.ex. 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 lib/raxol/workflow/graph.ex:87— `is_function(fun, 1) and is_function(compensate_fun, 1)` appears character-identically in 2 files — lib/raxol/workflow/graph.ex, lib/raxol/workflow/node.ex. 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 packages/raxol_terminal/lib/raxol/terminal/io_terminal.ex:199— `is_integer(color) and color >= 0 and color <= 255` appears character-identically in 2 files — packages/raxol_terminal/lib/raxol/terminal/io_terminal.ex, packages/raxol_terminal/lib/raxol/terminal/renderer.ex. 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 lib/raxol/core/terminal/osc/handlers/color_palette.ex:228— `is_integer(index) and index >= 0 and index <= 255` appears character-identically in 2 files — lib/raxol/core/terminal/osc/handlers/color_palette.ex, packages/raxol_terminal/lib/raxol/terminal/ansi/sixel_renderer.ex. 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 lib/raxol/core/runtime/subscription.ex:60— `is_integer(interval_ms) and interval_ms > 0` appears character-identically in 2 files — lib/raxol/core/runtime/subscription.ex, packages/raxol_core/lib/raxol/core/utils/timer_manager.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default on error web/lib/raxol_playground_web/controllers/health_controller.ex:60— `check_ssh` matches `{:error, _}` and answers `"down"` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error web/lib/raxol_playground_web/controllers/skill_controller.ex:13— `show` matches `{:error, _}` and answers `"# Raxol\n\nSkill file not found."` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/terminal_utils.ex:295— `probe_controlling_terminal` matches `_` and answers `false` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/scroll/scroll_manager.ex:147— `get_cached_scroll` matches `{:error, _}` and answers `{:miss, nil}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/script/script_server.ex:632— `load_script_metadata` matches `{:error, _}` and answers `%{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/plugin/plugin_server.ex:633— `load_extension_config` matches `{:error, _reason}` and answers `{:ok, %{}}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/output/output_manager.ex:137— `process_batch` matches `{:error, _}` and answers `{:halt, {:error, :invalid_event}}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/integration/integration_state.ex:137— `get_visible_content` matches `_` and answers `[]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/config/animation_cache.ex:111— `get_cache_size` matches `_` and answers `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/config/animation_cache.ex:265— `find_animation_files` matches `_` and answers `[]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/commands/command_server/helpers.ex:36— `get_position_from_pid` matches `_` and answers `{0, 0}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/colors.ex:251— `parse_rgb_color` matches `_` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_terminal/lib/raxol/terminal/ansi/sequences/colors.ex:264— `parse_hex_color` matches `{:error, _}` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_telegram/lib/raxol/telegram/rich_message/sender.ex:106— `payload_bytes` matches `{:error, _}` and answers `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_mcp/lib/raxol/mcp/server.ex:937— `async_action` matches `_other` and answers `:sync` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_mcp/lib/raxol/mcp/structured_screenshot.ex:58— `to_json` matches `{:error, _}` and answers `"[]"` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_mcp/lib/raxol/mcp/transport/sse.ex:84— `init` matches `{:error, _}` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_mcp/lib/raxol/mcp/client/reference_server.ex:160— `method` matches `_undecodable` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_mcp/lib/raxol/mcp/client/sse.ex:133— `frame_payload` matches `{:error, :no_data}` and answers `[]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_liveview/lib/raxol/live_view/terminal_bridge.ex:655— `aria_state` matches `_` and answers `[]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_journal/lib/raxol/agent/journal/records/checkpoint/file_backend.ex:301— `protected_floor` matches `{:error, _reason}` and answers `false` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_journal/lib/raxol/agent/journal/file_store/reader.ex:159— `first_line` matches `{:error, _reason}` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_journal/lib/raxol/agent/journal/file_store/reader.ex:167— `read_first_line` matches `_eof_or_error` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_journal/lib/raxol/agent/journal/file_store/reader.ex:216— `list_segments` matches `{:error, _}` and answers `[]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default on error packages/raxol_journal/lib/raxol/agent/journal/file_store/writer.ex:675— `head_offset` matches `_` and answers `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the reason or return the `{:error, reason}` tuple. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
redundant comment scripts/docs/maintenance.js:30— "Validate markdown files" repeats the code it sits on: 3 of its 3 words (validate, markdown, files) are already in `function validateMarkdownFiles()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/docs/search.js:9— "Generate search index" repeats the code it sits on: 3 of its 3 words (generate, search, index) are already in `function generateSearchIndex()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/docs/search.js:54— "Generate search suggestions" repeats the code it sits on: 3 of its 3 words (generate, search, suggestions) are already in `function generateSearchSuggestions(searchIndex)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/testing/check_coverage.js:12— "80% coverage threshold" repeats the code it sits on: 3 of its 3 words (80, coverage, threshold) are already in `const COVERAGE_THRESHOLD = 80;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/accessibility/TerminalAccessibility.test.js:8— "Mock the terminal emulator" repeats the code it sits on: 3 of its 3 words (mock, terminal, emulator) are already in `jest.mock('../../../lib/raxol/terminal/emulator', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/accessibility/terminal_accessibility_test.js:9— "Mock the terminal manager" repeats the code it sits on: 3 of its 3 words (mock, terminal, manager) are already in `jest.mock('../../../lib/raxol/terminal/manager', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/components/Terminal.test.js:4— "Mock the terminal emulator" repeats the code it sits on: 3 of its 3 words (mock, terminal, emulator) are already in `jest.mock('../../../lib/raxol/terminal/emulator', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/components/terminal_component_test.js:6— "Mock the terminal manager" repeats the code it sits on: 3 of its 3 words (mock, terminal, manager) are already in `jest.mock('../../../lib/raxol/terminal/manager', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/e2e/terminal_e2e_test.js:7— 7 comments in this file only repeat the code they sit on (lines 7, 15, 33, 74, 89, 108, 139), for example "Mock the terminal manager". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/setup.js:4— "Mock window.matchMedia" repeats the code it sits on: 4 of its 4 words (mock, window, match, media) are already in `Object.defineProperty(window, 'matchMedia', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/visual/TerminalVisual.test.js:8— "Mock the terminal emulator" repeats the code it sits on: 3 of its 3 words (mock, terminal, emulator) are already in `jest.mock('../../../lib/raxol/terminal/emulator', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/visual/terminal_visual_test.js:9— "Mock the terminal manager" repeats the code it sits on: 3 of its 3 words (mock, terminal, manager) are already in `jest.mock('../../../lib/raxol/terminal/manager', () => ({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/js/visual/terminal_visual_test.js:17— "Mock the TerminalComponent" repeats the code it sits on: 3 of its 3 words (mock, terminal, component) are already in `const TerminalComponentMock = () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment web/assets/js/app.js:9— "Copy to Clipboard Hook" repeats the code it sits on: 3 of its 3 words (copy, clipboard, hook) are already in `Hooks.CopyToClipboard = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment web/assets/js/app.js:41— "Code Editor Hook" repeats the code it sits on: 3 of its 3 words (code, editor, hook) are already in `Hooks.CodeEditor = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment web/assets/js/app.js:78— "Terminal Output Hook" repeats the code it sits on: 3 of its 3 words (terminal, output, hook) are already in `Hooks.TerminalOutput = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment web/priv/static/js/app.js:15— 5 comments in this file only repeat the code they sit on (lines 15, 56, 80, 114, 129), for example "Code Editor Hook". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×4
Projects may be oversized for their cohesion mix.exs:1— `(repository root)` (176838 LoC, 887 module-visible types across 166 directories) overshoots its size bounds. 4 of 16 build unit(s) (Mix, npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion packages/raxol_terminal/mix.exs:1— `packages/raxol_terminal` (72425 LoC, 404 module-visible types across 61 directories) overshoots its size bounds. 4 of 16 build unit(s) (Mix, npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion packages/raxol_core/mix.exs:1— `packages/raxol_core` (21391 LoC, 128 module-visible types across 23 directories) overshoots its size bounds. 4 of 16 build unit(s) (Mix, npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion web/mix.exs:1— `web` (8806 LoC, 44 module-visible types across 12 directories) overshoots its size bounds. 4 of 16 build unit(s) (Mix, npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Silent fallback default in catch packages/raxol_terminal/lib/raxol/terminal/driver.ex:948— `install_sigwinch_handler` catches `_, _` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log what was caught or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default in catch packages/raxol_telegram/lib/raxol/telegram/session.ex:172— `start_lifecycle` catches `:exit, {:timeout, _}` and answers `nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log what was caught or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default in catch packages/raxol_mcp/lib/raxol/mcp/server.ex:2069— `sensitive_tool_names` catches `:exit, _` and answers `[]` — a failure becomes a plausible value and a silent behavior change with no trail. Log what was caught or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default in catch packages/raxol_gateway/lib/raxol/gateway/handler/lifecycle.ex:146— `discover_pids` catches `:exit, {:timeout, _}` and answers `{nil, nil}` — a failure becomes a plausible value and a silent behavior change with no trail. Log what was caught or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 263 significant file(s) lose their only recent owner: packages/raxol_mcp/lib/raxol/mcp/server.ex, lib/raxol/repl/sandbox.ex, web/lib/raxol_playground_web/components/landing_components.ex, lib/raxol/headless.ex, lib/raxol/workflow/runtime.ex, packages/raxol_mcp/lib/raxol/mcp/client.ex, scripts/check_package_boundaries.exs, lib/raxol/headless/mcp_tools.ex (+255 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 28 significant file(s) lose their only recent owner: lib/raxol/harness/surface.ex, lib/raxol/ui/rendering/paint_authority/inline_authority.ex, lib/raxol/harness/seal_frontier.ex, packages/raxol_terminal/lib/raxol/terminal/scroll_region_manager.ex, lib/raxol/ui/list_scorer.ex, lib/raxol/ui/components/harness/composer.ex, lib/raxol/ui/text_layout/pretty.ex, lib/raxol/ui/harness/input_event.ex (+20 more). Pair on, review, or document these before any departure.
Silent fallback default in rescue packages/raxol_terminal/lib/raxol/terminal/inline_driver/reader_gate.ex:143— `otp_release` rescues `_` and answers `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the exception or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Silent fallback default in rescue packages/raxol_terminal/lib/raxol/terminal/driver/stty.ex:116— `run` rescues `_error` and answers `{"", 1}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the exception or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be produced, say so in a comment at the clause or in the `@doc`, and the row stops firing.
Thin authorization enforcement — Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 180 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: bench/suites/visualization/visualization_benchmark.ex, lib/raxol/harness/diff_expansion.ex, lib/raxol/animation/physics/physics_engine.ex, packages/raxol_terminal/lib/raxol/terminal/ansi/character_translations.ex, lib/raxol/harness/editor_suspend.ex, packages/raxol_terminal/lib/raxol/terminal/buffer/scroll_region.ex, lib/raxol/core/core.ex, lib/raxol/harness/fixture.ex (and 172 more) (184 orphaned of 1055 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; 1055 of the 1369 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Logging is not universal — Only 12/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`, `.`, `.`.
P3 · Security & performance tooling· Dependabot does not watch npm · ×1
Dependabot does not watch npm REDACTED:12— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Subsumed condition operand lib/raxol/benchmark/suite_registry.ex:418— `String.contains?(module_str, "Benchmark")` can never decide this `||` — every value satisfying `String.contains?(module_str, "Benchmark")` also satisfies `String.contains?(module_str, "Bench")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Outdated: bumblebee — `:bumblebee` is locked at 0.6.3 but 0.8.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.6"` requirement declared in packages/raxol_speech/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update bumblebee` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_core/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_gateway/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_terminal/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_mcp/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_plugin/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_sensor/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_watch/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_speech/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in packages/raxol_telegram/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
Outdated: elixir_make — `:elixir_make` is locked at 0.9.0 but 0.10.1 is the current stable release on hex.pm, and it already satisfies the `"~> 0.7"` requirement declared in packages/raxol_terminal/lib/termbox2_nif/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update elixir_make` and commit the updated mix.lock.
Outdated: swoosh — `:swoosh` is locked at 1.29.0 but 1.29.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in web/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update swoosh` and commit the updated mix.lock.
Outdated: telemetry — `:telemetry` is locked at 1.4.2 but 1.4.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in packages/raxol_watch/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry` and commit the updated mix.lock.
Outdated: telemetry — `:telemetry` is locked at 1.4.2 but 1.4.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in packages/raxol_speech/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry` and commit the updated mix.lock.
Outdated: telemetry — `:telemetry` is locked at 1.4.2 but 1.4.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in packages/raxol_journal/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry` and commit the updated mix.lock.
Outdated: telemetry — `:telemetry` is locked at 1.4.2 but 1.4.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in packages/raxol_gateway/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry` and commit the updated mix.lock.
Outdated: telemetry — `:telemetry` is locked at 1.4.2 but 1.4.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in packages/raxol_telegram/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry` and commit the updated mix.lock.
Outdated: telemetry — `:telemetry` is locked at 1.4.2 but 1.4.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.3"` requirement declared in packages/raxol_core/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update telemetry` and commit the updated mix.lock.
doc comments repeat the names scripts/testing/check_coverage.js:45— 0 of 0 documented parameters and 2 of 13 summaries in `.` only repeat the member or parameter name (e.g. "Calculate overall coverage" for `calculateOverallCoverage`). 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.
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.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e8ed-e9b6-7751-aa3b-3ba1cc59c54f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 129 · Warnings: 896 · Recommendations: 291 · Info: 19 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 09:54 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.