Public report of blinkenlights/polychrome, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 16 November 2026, 19:38 UTC · Survey ID cd_e49a5b24ada74b0195320da9d48c8a88
blinkenlights/polychrome
Measured 16 November 2026, 19:37 UTC, at code version eb9a6eb
First survey, so nothing to compare with yet
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 66,859 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 20.5
Findings by how serious they are
40 critical330 serious108 minor
14 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 19:37 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
58of 58 dimensions measured by tools.
432of 478 findings point to an exact file and line, so you can open each one in the code. The other 46 concern the repository as a whole, such as missing documentation.
58dimensions across 6 lenses, read from 66,859 lines of product code in 4 projects.
blinkenlights/polychrome falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 33.1 out of 100 and is rated Weak, and 21 of its 40 critical findings are security problems in its servers and containers and in the packages it uses.
Production Readiness, at 20.5, is the weakest lens and counts most in the score. The best first step is putting upper bounds on the open-ended dependency requirements, worth about 7.2 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 3.5 points. Raising Production Readiness to 70 would lift the score to about 43.8.
Twelve settings leave the servers or containers unsafe. Nine known security holes in the packages the code depends on can be used by attackers, and eleven form fields can't be read by a screen reader. Correcting the unsafe settings, updating the vulnerable packages and labelling the form fields would close these risks. The four images with no text description need a text description.
The product code is 66,859 lines, about €66,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 20.5 to 70, the lowest score rated Strong, the score would rise from 33.1 to about 43.8.
Code composition: what the lines of code are
Product code 87%Tests 13%
Rebuild cost: about €66,000 · Estimate
Cost to rebuild
€22,000 to €110,000, for 363 to 1,150 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 33. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 66,859 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene.
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 3.5 points · Medium effort · CI/CD gates
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 €66,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 20.5 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 7.2 points for low effort, because it clears the 2 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
113 modules, with 12 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; 73 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.
63 pairs of types, where a type in Octopus.Apps uses a type in Octopus. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
The types involved
Octopus.Apps.AnimatorTest → Octopus.App
Octopus.Apps.BeakTest → Octopus.App
Octopus.Apps.Blocks → Octopus.App
Octopus.Apps.BomberPerson → Octopus.App
Octopus.Apps.Calibrator → Octopus.App
Octopus.Apps.CanvasTest → Octopus.App
Octopus.Apps.CircularClock → Octopus.App
Octopus.Apps.Collective → Octopus.App
Octopus.Apps.Diamonds → Octopus.App
Octopus.Apps.DoomFire → Octopus.App
Octopus.Apps.Encounter → Octopus.App
Octopus.Apps.Eventphone → Octopus.App
Octopus.Apps.FairyDust → Octopus.App
Octopus.Apps.Fire → Octopus.App
Octopus.Apps.Fireworks → Octopus.App
Octopus.Apps.Fireworks → Octopus.Params
Octopus.Apps.FontTester → Octopus.App
Octopus.Apps.GravityMask → Octopus.App
Octopus.Apps.InputTest → Octopus.App
Octopus.Apps.Lemmings → Octopus.App
Octopus.Apps.MarioRun → Octopus.App
Octopus.Apps.Matrix → Octopus.App
Octopus.Apps.Ocean → Octopus.App
Octopus.Apps.OneWord → Octopus.App
Octopus.Apps.OneWord → Octopus.Params
Direction
Octopus.Apps uses Octopus, so a change to Octopus can break Octopus.Apps, while a change to Octopus.Apps can't break Octopus.
Position
Below the diagonal: Octopus.Apps uses a module listed above it, which is the healthy direction.
Octopus.Apps.Collective.Animations uses Octopus.Apps.Collective, so a change to Octopus.Apps.Collective can break Octopus.Apps.Collective.Animations, while a change to Octopus.Apps.Collective.Animations can't break Octopus.Apps.Collective.
Position
Below the diagonal: Octopus.Apps.Collective.Animations uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Octopus.Apps.Whackamole uses a type in Octopus.
The types involved
Octopus.Apps.Whackamole.Game → Octopus.Params
Direction
Octopus.Apps.Whackamole uses Octopus, so a change to Octopus can break Octopus.Apps.Whackamole, while a change to Octopus.Apps.Whackamole can't break Octopus.
Position
Below the diagonal: Octopus.Apps.Whackamole uses a module listed above it, which is the healthy direction.
Octopus.Radar.Transport uses Octopus.Radar, so a change to Octopus.Radar can break Octopus.Radar.Transport, while a change to Octopus.Radar.Transport can't break Octopus.Radar.
Position
Below the diagonal: Octopus.Radar.Transport uses a module listed above it, which is the healthy direction.
octopus.assets.js.hooks uses octopus.assets.js.hooks.nation, so a change to octopus.assets.js.hooks.nation can break octopus.assets.js.hooks, while a change to octopus.assets.js.hooks can't break octopus.assets.js.hooks.nation.
Position
Below the diagonal: octopus.assets.js.hooks uses a module listed above it, which is the healthy direction.
octopus.assets.js.hooks uses octopus.assets.js.hooks.pixels, so a change to octopus.assets.js.hooks.pixels can break octopus.assets.js.hooks, while a change to octopus.assets.js.hooks can't break octopus.assets.js.hooks.pixels.
Position
Below the diagonal: octopus.assets.js.hooks uses a module listed above it, which is the healthy direction.
octopus.assets.js.hooks uses octopus.assets.js.hooks.pixels3daframe, so a change to octopus.assets.js.hooks.pixels3daframe can break octopus.assets.js.hooks, while a change to octopus.assets.js.hooks can't break octopus.assets.js.hooks.pixels3daframe.
Position
Below the diagonal: octopus.assets.js.hooks uses a module listed above it, which is the healthy direction.
octopus.assets.js.hooks.shared uses octopus.assets.js.hooks.shared.frame, so a change to octopus.assets.js.hooks.shared.frame can break octopus.assets.js.hooks.shared, while a change to octopus.assets.js.hooks.shared can't break octopus.assets.js.hooks.shared.frame.
Position
Below the diagonal: octopus.assets.js.hooks.shared uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 42.9 · Weak · gated by R3, X5 ·
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
A03:2025 — Software Supply Chain Failures
24
High / Critical
A02:2025 — Security Misconfiguration
18
High / Critical
A01:2025 — Broken Access Control
1
Medium
Roadmap
Top priorities: Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene; Resolve the 1 Retired release finding(s) in Dependency Hygiene; Add a CI workflow that builds and runs the test suite on every push/PR.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Unbounded dependency requirement finding(s) in Dependency Hygiene.
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 40
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 — 330
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 — 108
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 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 — 58 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, 432 of 478 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 MEASURED: test source is present (.exs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
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) 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 an Elixir mix.exs/mix.lock (Hex), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Mix dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (octopus/native/octopus_webp/Cargo.toml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — 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.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
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 14 — a file the compose project references is missing) — env file octopus/deploy/redlady/.env not found: stat octopus/deploy/redlady/.env: no such file or directory; 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, Python, c, cpp 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, Python, c, cpp 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.
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.
X18 Disposal-pattern 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.
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.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Pixels3dHook.mounted at 38. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being AppModePresets.normalize_mode_id_for_app at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: octopus/lib/octopus/app_mode_presets.ex (AppModePresets.normalize_mode_id_for_app at 17). 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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with Pixels3dHook.mounted (cyclomatic 38). — Refactoring it lifts Cyclomatic Complexity from 8.3 to about 8.6/10.
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.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 15 down to 15 or less in Cognitive Complexity — start with Glowworms.handle_worm_phase (cognitive 35), Pixels3dHook.mounted (cognitive 31), mounted (cognitive 29). — 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 12 together lifts Cognitive Complexity from 8.2 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.6 / 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 23 FileTooLong finding(s) in God Classes — start with pixel_fun.ex, radar_live.ex, console_components.ex. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 7 TooManyFunctions finding(s) in God Classes — start with storm.ex, sim.ex, fire.ex. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with pixels3d.ts, nation.ts, pixels.ts. — One of this dimension's main actionable groups (4 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.
118 duplicated block group(s) detected. 8.9 % of the production lines (5,932 of 66,859) are in a reported copy. A further 70 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (8 corresponding lines) · ×8octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:341
Edited copy of a member (20 corresponding lines) · ×4octopus/lib/octopus/apps/supermario/game.ex:404
Edited copy of a member (1 corresponding lines) · ×4octopus/lib/octopus/apps/collective/animations/dots.ex:343
+ 108 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with fire.ex (2), lava_lamp.ex, world.ex. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with collective.ex (2), senso.ex, completed.ex. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (32 lines × 2) finding(s) in Code Duplication — start with level.ex (6). — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
3 production modules (Cargo+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether 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.
28 outdated, 1 retired direct Hex dependencies, 2 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 REDACTED there.
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.
Secret scan ran and found no leaked secrets. 4 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
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 40 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares an Elixir mix.exs/mix.lock (Hex), 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.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with installation_console_component.ex, pixel_fun.ex, pixels.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor6.1 / 10Adequate✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
73 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is octopus/lib/octopus_web/live/radar_live.ex. Counted over 187 of the 299 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
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).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 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.
8 deducted task-comment markers across 66859 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.
TodoComment · ×8octopus/lib/octopus/animator.ex:5
What to do
Resolve the 8 TodoComment finding(s) in Explicit Debt — start with game.ex (2), animator.ex, playlist.ex. — One of this dimension's main actionable groups (8 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.
1 of 1 documentation facets pass in full. 16 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
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.
1 of 4 build units (Cargo, Mix, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionoctopus/mix.exs:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with mix.exs. — One of this dimension's main actionable groups (1 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.
23 % of calls cross a namespace and 9 % 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).
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `blinkenleds/lib/ProtoBuf/schema.pb.h` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
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 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED (6). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 12 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (3). — One of this dimension's main actionable groups (12 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_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.
31 of 187 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is octopus/lib/octopus_web/components/core_components.ex. Counted over 187 of the 299 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with game.ex (2), core_components.ex, schema.pb.ex. — One of this dimension's main actionable groups (31 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge 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 8 Change coupling finding(s) in Change Coupling — start with pixels3daframe.ts (2), installation_transport.ex (2), pixel_fun.ex. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.6 / 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.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×4) — octopus/assets/js/hooks/pixels3daframe.ts:974, octopus/assets/js/hooks/pixels3daframe.ts:978, octopus/assets/js/hooks/pixels3daframe.ts:982, …
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. (×3) — octopus/lib/octopus_web/live/nation_live.ex:110, octopus/lib/octopus_web/live/pixels_live.ex:254, octopus/lib/octopus_web/live/proximity_live.ex:104
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels6.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×10) — octopus/lib/octopus_web/components/app_config_component.ex:311, octopus/lib/octopus_web/components/console_components.ex:1089, octopus/lib/octopus_web/components/console_components.ex:1169, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — octopus/lib/octopus_web/components/console_components.ex:1527, octopus/lib/octopus_web/components/console_components.ex:1560
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — octopus/lib/octopus_web/live/playlist_live.ex:30
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — octopus/lib/octopus_web/components/layouts/root.html.heex:2, octopus/lib/octopus_web/components/layouts/root_aframe.html.heex:2, octopus/lib/octopus_web/components/layouts/root_sim3d.html.heex:2
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×2) — octopus/lib/octopus_web/live/playlists_live.ex:32, octopus/lib/octopus_web/live/playlists_live.ex:87
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".
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×3) — octopus/lib/octopus_web/components/console_components.ex:1507, octopus/lib/octopus_web/components/console_components.ex:1537, octopus/lib/octopus_web/components/installation_console_component.ex:212
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — octopus/lib/octopus_web/live/radar_live.ex:1201, octopus/lib/octopus_web/live/radar_live.ex:1473
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.
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — octopus/lib/octopus_web/components/console_components.ex:1116, octopus/lib/octopus_web/components/console_components.ex:1208
<svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — octopus/lib/octopus_web/live/radar_live.ex:0
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.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
This repository serves requests — a server (use Phoenix.Endpoint) (octopus/lib/octopus_web/endpoint.ex:2) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — octopus/lib/octopus_web/endpoint.ex:2
What to do
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
`octopus/assets/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — octopus/assets/package.json:2
What to do
Run what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ 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.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.
Do you agree with this assessment?
R1 · Type Safety6.2 / 10Adequate✓ 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.
8 typed · 5 plain JS — the untyped files are octopus/assets/js/app.js, octopus/assets/js/app_sim3d.js, octopus/assets/js/app_sim3daframe.js, octopus/assets/js/hooks/index.js, octopus/assets/js/hooks/topbar.js.
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.
octopus/assets/js/app.js:26 · octopus/assets/js/app_sim3d.js:8 · octopus/assets/js/app_sim3daframe.js:8 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — octopus/assets/js/app.js:26
octopus/assets/js/app_sim3d.js:8 · octopus/assets/js/app_sim3daframe.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — octopus/assets/js/app_sim3d.js:8
octopus/assets/js/hooks/pixels3d.ts:499 · octopus/assets/js/hooks/pixels3d.ts:516 — 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. — octopus/assets/js/hooks/pixels3d.ts:499
octopus/assets/js/hooks/index.js:313 · octopus/assets/js/hooks/index.js:333 — 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. — octopus/assets/js/hooks/index.js:313
octopus/assets/js/hooks/pixels3daframe.ts:489 · octopus/assets/js/hooks/pixels3daframe.ts:942 — 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. — octopus/assets/js/hooks/pixels3daframe.ts:489
octopus/assets/js/hooks/pixels3d.ts:475 · octopus/assets/js/hooks/pixels3d.ts:496 · octopus/assets/js/hooks/pixels3d.ts:513 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — octopus/assets/js/hooks/pixels3d.ts:475
octopus/assets/js/hooks/nation.ts:60 · octopus/assets/js/hooks/pixels.ts:60 — 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. — octopus/assets/js/hooks/nation.ts:60
octopus/assets/js/hooks/humanComponents.ts:200 · octopus/assets/js/hooks/humanComponents.ts:212 — 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. — octopus/assets/js/hooks/humanComponents.ts:200
octopus/assets/js/hooks/pixels.ts:111 · octopus/assets/js/hooks/pixels.ts:354 — 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. — octopus/assets/js/hooks/pixels.ts:111
octopus/assets/js/hooks/pixels3daframe.ts:973 · octopus/assets/js/hooks/pixels3daframe.ts:981 — 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. — octopus/assets/js/hooks/pixels3daframe.ts:973
octopus/assets/js/hooks/pixels3daframe.ts:445 · octopus/assets/js/hooks/pixels3daframe.ts:1259 · octopus/assets/js/hooks/pixels3daframe.ts:1267 — 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. — octopus/assets/js/hooks/pixels3daframe.ts:445
octopus/assets/js/hooks/nation.ts:77 · octopus/assets/js/hooks/pixels.ts:32 — 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. — octopus/assets/js/hooks/nation.ts:77
octopus/assets/js/hooks/nation.ts:181 · octopus/assets/js/hooks/nation.ts:192 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — octopus/assets/js/hooks/nation.ts:181
octopus/assets/js/hooks/nation.ts:470 · octopus/assets/js/hooks/pixels.ts:395 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — octopus/assets/js/hooks/nation.ts:470
octopus/assets/js/hooks/pixels3daframe.ts:1001 · octopus/assets/js/hooks/pixels3daframe.ts:1008 — 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. — octopus/assets/js/hooks/pixels3daframe.ts:1001
octopus/assets/js/hooks/pixels3daframe.ts:1261 · octopus/assets/js/hooks/pixels3daframe.ts:1269 · octopus/assets/js/hooks/pixels3daframe.ts:1332 — 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. — octopus/assets/js/hooks/pixels3daframe.ts:1261
octopus/assets/js/hooks/pixels3daframe.ts:1486 · octopus/assets/js/hooks/pixels3daframe.ts:1492 — 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. — octopus/assets/js/hooks/pixels3daframe.ts:1486
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.
handleParams has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — octopus/assets/js/hooks/pixels3daframe.ts:1522
applyInstallationState has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — octopus/assets/js/hooks/pixels3daframe.ts:1571
Do you agree with this assessment?
R3 · Large Files0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
octopus/assets/js/hooks/pixels3daframe.ts has 1659 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — octopus/assets/js/hooks/pixels3daframe.ts:1
octopus/assets/js/hooks/pixels3d.ts has 648 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — octopus/assets/js/hooks/pixels3d.ts:1
octopus/assets/js/hooks/nation.ts has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — octopus/assets/js/hooks/nation.ts:1
octopus/assets/js/hooks/pixels.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — octopus/assets/js/hooks/pixels.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
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.
15 file(s) (~4945 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: octopus/assets/js/hooks/index.js imports '../../../deps/live_monaco_editor/priv/static/live_monaco_editor.esm', 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. — octopus/assets
This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — octopus/assets/js/hooks/humanWorld.ts:103
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.
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 (octopus/lib/octopus_web/endpoint.ex:2 — `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 `REDACTED` 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.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `Caddyfile` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — octopus/deploy/redlady/Caddyfile:3
This repository runs an HTTP server and nothing in its Elixir source or production configuration secures the transport: no HTTPS served (an endpoint's `https: [...]`, `scheme: :https`, `Plug.Cowboy.https`, SiteEncrypt), no `force_ssl:` or `plug Plug.SSL` redirecting to HTTPS and sending HSTS, no `strict-transport-security` header, no `rewrite_on: [:x_forwarded_proto]` or `x-forwarded-proto` read for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: octopus/lib/octopus_web/endpoint.ex:2 — `Phoenix.Endpoint`.
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Secure the server's transport: set `force_ssl: [rewrite_on: [:x_forwarded_proto], hsts: true]` on the endpoint in `config/prod.exs` (Plug.SSL redirects to HTTPS and sends `Strict-Transport-Security`; `rewrite_on` trusts the TLS-terminating proxy in front of it), or serve TLS itself with the endpoint's `https: [port: 443, cipher_suite: :strong, keyfile: …, certfile: …]`.
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.
0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.8 `!` null assertions per 1k TypeScript source lines — 8 assertion(s) across the 4335 source line(s) of the 8 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: octopus/assets/js/hooks/pixels3daframe.ts (7), octopus/assets/js/hooks/nation.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 68 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: 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 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; 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 — Not applicable: 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 14 — a file the compose project references is missing) — env file octopus/deploy/redlady/.env not found: stat octopus/deploy/redlady/.env: no such file or directory; 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.
D10 Test Quality — ~10070 lines of test source are present (.exs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
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 (11454 declarations, no unit with a dominant convention).
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 75 value object(s); 1 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 (6 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 — no CI workflow found
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for Benchee jobs (the entries of a `Benchee.run` job map) or Benchfella `bench "…"` blocks under `use Benchfella` in any `.ex`/`.exs` file, or benchee or benchfella in a mix.exs, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: Elixir has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (13 production file(s)) has no JavaScript/TypeScript test, but it is 6.32% of this repository's production source and the other 93.68% carries 10,070 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 6% of this repository's production lines — elixir (62,973 lines), cpp (2,456 lines), c (926 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 6% of this repository's production lines — elixir (62,973 lines), cpp (2,456 lines), c (926 lines), python (13 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 6% of this repository's production lines — elixir (62,973 lines), cpp (2,456 lines), c (926 lines), python (13 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 6% of this repository's production lines — elixir (62,973 lines), cpp (2,456 lines), c (926 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — X29 reached only 6% of this repository's production lines — elixir (62,973 lines), cpp (2,456 lines), c (926 lines), python (13 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X3 Exception handling — X3 reached only 6% of this repository's production lines — elixir (62,973 lines), cpp (2,456 lines), c (926 lines), rust (88 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <input> without a programmatic label · ×9
<input> without a programmatic label octopus/lib/octopus_web/components/app_config_component.ex:311— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/components/console_components.ex:1089— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/components/console_components.ex:1169— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/components/console_components.ex:1512— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/components/console_components.ex:1542— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/components/sim3d_params_component.ex:224— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/components/wood_config_component.ex:194— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label octopus/lib/octopus_web/live/playlist_live.ex:30— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label octopus/lib/octopus_web/live/radar_live.ex:1910— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC1 · Text alternatives· <img> without a text alternative · ×4
<img> without a text alternative octopus/assets/js/hooks/pixels3daframe.ts:974— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative octopus/assets/js/hooks/pixels3daframe.ts:978— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative octopus/assets/js/hooks/pixels3daframe.ts:982— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative octopus/assets/js/hooks/pixels3daframe.ts:986— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <select> without a programmatic label · ×2
<select> without a programmatic label octopus/lib/octopus_web/components/console_components.ex:1513— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label octopus/lib/octopus_web/live/pixels_live.ex:229— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text octopus/lib/octopus_web/components/console_components.ex:1527— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text octopus/lib/octopus_web/components/console_components.ex:1560— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×1
Click handler on a non-interactive <li> octopus/lib/octopus_web/live/radar_live.ex:1201— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <g> · ×1
Click handler on a non-interactive <g> octopus/lib/octopus_web/live/radar_live.ex:1473— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
FileTooLong: apps/pixel_fun.ex octopus/lib/octopus/apps/pixel_fun.ex— FileTooLong — 2476 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 143 functions. The bar is 500 significant lines; this is 1976 over it, 4.95× 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/radar_live.ex octopus/lib/octopus_web/live/radar_live.ex— FileTooLong — 2292 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 113 functions. The bar is 500 significant lines; this is 1792 over it, 4.58× 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/console_components.ex octopus/lib/octopus_web/components/console_components.ex— FileTooLong — 1560 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 66 functions. The bar is 500 significant lines; this is 1060 over it, 3.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: font/blinkenlights_regular.ex octopus/lib/octopus/font/blinkenlights_regular.ex— FileTooLong — 1501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1001 over it, 3.00× 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: font/blinkenlights_bold.ex octopus/lib/octopus/font/blinkenlights_bold.ex— FileTooLong — 1493 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 993 over it, 2.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: hooks/pixels3daframe.ts octopus/assets/js/hooks/pixels3daframe.ts— FileTooLong — 1320 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: Pixels3dAframeHook (680-1824). The bar is 500 significant lines; this is 820 over it, 2.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: apps/collective.ex octopus/lib/octopus/apps/collective.ex— FileTooLong — 1229 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 729 over it, 2.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: components/installation_console_component.ex octopus/lib/octopus_web/components/installation_console_component.ex— FileTooLong — 1075 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 51 functions. The bar is 500 significant lines; this is 575 over it, 2.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: octopus/installation_transport.ex octopus/lib/octopus/installation_transport.ex— FileTooLong — 1058 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 116 functions. The bar is 500 significant lines; this is 558 over it, 2.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: octopus/radar.ex octopus/lib/octopus/radar.ex— FileTooLong — 1006 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 126 functions. The bar is 500 significant lines; this is 506 over it, 2.01× 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: apps/sand.ex octopus/lib/octopus/apps/sand.ex— FileTooLong — 923 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 47 functions. The bar is 500 significant lines; this is 423 over it, 1.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: octopus/mixer.ex octopus/lib/octopus/mixer.ex— FileTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 41 functions. The bar is 500 significant lines; this is 336 over it, 1.67× 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: octopus/installation.ex octopus/lib/octopus/installation.ex— FileTooLong — 731 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 231 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: radar/sensor.ex octopus/lib/octopus/radar/sensor.ex— FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 48 functions. The bar is 500 significant lines; this is 226 over it, 1.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: apps/wood.ex octopus/lib/octopus/apps/wood.ex— FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 52 functions. 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: octopus/canvas.ex octopus/lib/octopus/canvas.ex— FileTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 37 functions. The bar is 500 significant lines; this is 104 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: apps/matrix.ex octopus/lib/octopus/apps/matrix.ex— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 31 functions. The bar is 500 significant lines; this is 99 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mock/world.ex octopus/lib/octopus/radar/mock/world.ex— FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 58 functions. The bar is 500 significant lines; this is 79 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: apps/pixie_debug.ex octopus/lib/octopus/apps/pixie_debug.ex— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 40 functions. The bar is 500 significant lines; this is 75 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: live/radar_debug_live.ex octopus/lib/octopus_web/live/radar_debug_live.ex— FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 31 functions. The bar is 500 significant lines; this is 69 over it, 1.14× 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/pixels_live.ex octopus/lib/octopus_web/live/pixels_live.ex— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 42 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: hooks/pixels3d.ts octopus/assets/js/hooks/pixels3d.ts— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: Pixels3dHook (127-769). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: apps/world_cup_final.ex octopus/lib/octopus/apps/world_cup_final.ex— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 51 functions. The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D30 · Dependency Vulnerabilities· Medium CVE · ×13
TodoComment octopus/lib/octopus/animator.ex:5— # 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 octopus/lib/octopus/playlist_scheduler/playlist.ex:53— # 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 octopus/lib/octopus/apps/bomber_person.ex:39— # @explosion_range 2 TODO: Implement — 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 octopus/lib/octopus/apps/supermario.ex:92— # TODO: show mario dying, then reset game, reduce level by 1, possibly game over — 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 octopus/lib/octopus/apps/supermario/game.ex:213— # TODO too many nested ifs, refactor, use case statement — 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 octopus/lib/octopus/apps/supermario/level.ex:11— # TODO cyclic dependency Game <-> Level — 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 octopus/lib/octopus/apps/supermario/png_file.ex:1— # TODO Find a better name for this module — 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 octopus/lib/octopus/apps/blocks/game.ex:321— ## todo needs a better place — 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.
Change coupling: pixels3daframe.ts ↔ sim3daframe_live.ex octopus/assets/js/hooks/pixels3daframe.ts:1— `octopus/assets/js/hooks/pixels3daframe.ts` and `octopus/lib/octopus_web/live/sim3daframe_live.ex` change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `cc4e51fd` feat: dots debug app with activity check, changed direction and velocity; `3f57bf58` feat: radar activity module, presence app modification; `db54aecb` feat: aframe sim data from installation config — run `git show` on any of them.
Change coupling: pixels3daframe.ts ↔ sim_3d.ex octopus/assets/js/hooks/pixels3daframe.ts:1— `octopus/assets/js/hooks/pixels3daframe.ts` and `octopus/lib/octopus/params/sim_3d.ex` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `cc4e51fd` feat: dots debug app with activity check, changed direction and velocity; `db54aecb` feat: aframe sim data from installation config; `e3fa93a6` feat: new panel diameter, orbital app — run `git show` on any of them.
Change coupling: installation_transport.ex ↔ installation_console_component.ex octopus/lib/octopus/installation_transport.ex:1— `octopus/lib/octopus/installation_transport.ex` and `octopus/lib/octopus_web/components/installation_console_component.ex` change together 64% of the time (14 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 14 shared commits counted here, the most recent 3 are `72e4ba4c` InstallationTransport: Playlist nach Neustart wieder starten; `2594a95d` feat: masks for playlist tracks; `0a8fdc3d` fix: show all apps in now playing card — run `git show` on any of them.
Change coupling: pixel_fun.ex ↔ app_config_component.ex octopus/lib/octopus/apps/pixel_fun.ex:1— `octopus/lib/octopus/apps/pixel_fun.ex` and `octopus/lib/octopus_web/components/app_config_component.ex` change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — 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 11 shared commits counted here, the most recent 3 are `f2af7a94` make bleeding an app parameter, set for pixel_fun, include in tweakab…; `a4e72800` feat/wip: pixelfun config for scenes; `aa904d14` feat: pixelfun config ui — run `git show` on any of them.
Change coupling: nation2024.ex ↔ nation2025.ex octopus/lib/octopus/installation/nation2024.ex:1— `octopus/lib/octopus/installation/nation2024.ex` and `octopus/lib/octopus/installation/nation2025.ex` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `afc2992c` add geo location and auto_brightness flag to installation files; `8ba1af05` add global speed default value to installation files; `542b191a` add num_joysticks option to installation — run `git show` on any of them.
Change coupling: manager_live.ex ↔ router.ex octopus/lib/octopus_web/live/manager_live.ex:1— `octopus/lib/octopus_web/live/manager_live.ex` and `octopus/lib/octopus_web/router.ex` change together 55% of the time (11 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 11 shared commits counted here, the most recent 3 are `3651883e` feat: ui improvements; `cda8693d` wip: queues for all apps; `957f0dbd` radar state improvement — run `git show` on any of them.
Change coupling: installation_transport.ex ↔ console_components.ex octopus/lib/octopus/installation_transport.ex:1— `octopus/lib/octopus/installation_transport.ex` and `octopus/lib/octopus_web/components/console_components.ex` change together 55% of the time (12 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 12 shared commits counted here, the most recent 3 are `72e4ba4c` InstallationTransport: Playlist nach Neustart wieder starten; `2594a95d` feat: masks for playlist tracks; `db507ee6` feat: fade through black when switching presets in playlist, add all … — run `git show` on any of them.
Change coupling: app_mode_presets.ex ↔ pixel_fun_config_component.ex octopus/lib/octopus/app_mode_presets.ex:1— `octopus/lib/octopus/app_mode_presets.ex` and `octopus/lib/octopus_web/components/pixel_fun_config_component.ex` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 9 shared commits counted here, the most recent 3 are `0e7d0d70` Combine PixelFun translate autos into 2D wander with interval.; `81d8c330` feat: improve pixelfun3d ui; `64e050da` feat: pixelfun 3 sliders and toggles — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×8
Edited copy of a member (8 corresponding lines) octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:341— octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:341-348 | octopus/lib/octopus/apps/pixel_fun/gradient_palettes.ex:114-121 — 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) octopus/lib/octopus/apps/fire.ex:214— octopus/lib/octopus/apps/fire.ex:214-221 | octopus/lib/octopus/apps/perlin_noise.ex:133-140 — 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) octopus/lib/octopus/apps/fire.ex:68— octopus/lib/octopus/apps/fire.ex:68-75 | octopus/lib/octopus/apps/world_cup_final.ex:89-96 — 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) octopus/lib/octopus/radar/mock/world.ex:716— octopus/lib/octopus/radar/mock/world.ex:716-723 | octopus/lib/octopus/radar/mock/world.ex:731-738 — 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) octopus/lib/octopus_web/components/console_components.ex:1479— octopus/lib/octopus_web/components/console_components.ex:1479-1488 | octopus/lib/octopus_web/components/pixel_fun_config_component.ex:400-407 — 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) octopus/lib/octopus/radar/read_response.ex:130— octopus/lib/octopus/radar/read_response.ex:130-137 | octopus/lib/octopus/radar/read_response.ex:141-149 — 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) octopus/lib/octopus/canvas.ex:641— octopus/lib/octopus/canvas.ex:641-649 | octopus/lib/octopus/canvas.ex:659-666 — 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) octopus/lib/octopus/radar.ex:1532— octopus/lib/octopus/radar.ex:1532-1539 | octopus/lib/octopus/radar/view_settings.ex:127-134 — 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.
TooManyFunctions: Storm octopus/lib/octopus/apps/collective/animations/storm.ex:1— TooManyFunctions — 47 functions. The bar is 30 functions; this is 17 over it, 1.57× 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: Sim octopus/lib/octopus/apps/sand/sim.ex:1— TooManyFunctions — 37 functions. The bar is 30 functions; this is 7 over it, 1.23× 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: Fire octopus/lib/octopus/apps/fire.ex:1— TooManyFunctions — 35 functions. The bar is 30 functions; this is 5 over it, 1.17× 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: AppModePresets octopus/lib/octopus/app_mode_presets.ex:1— TooManyFunctions — 34 functions. The bar is 30 functions; this is 4 over it, 1.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: Breath octopus/lib/octopus/apps/collective/animations/breath.ex:1— TooManyFunctions — 34 functions. The bar is 30 functions; this is 4 over it, 1.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: Broadcaster octopus/lib/octopus/broadcaster.ex:1— TooManyFunctions — 33 functions. The bar is 30 functions; this is 3 over it, 1.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: SparkleMist octopus/lib/octopus/apps/sparkle_mist.ex:1— TooManyFunctions — 32 functions. The bar is 30 functions; this is 2 over it, 1.07× 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.
Duplicated block (7 lines × 2) octopus/lib/octopus/apps/collective.ex:515— octopus/lib/octopus/apps/collective.ex:515-521 | octopus/lib/octopus/apps/collective/animations/glowworms.ex:164-170 — 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) octopus/lib/octopus/apps/senso.ex:153— octopus/lib/octopus/apps/senso.ex:153-159 | octopus/lib/octopus/apps/senso.ex:184-190 — 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) octopus/lib/octopus/apps/supermario/animation/completed.ex:26— octopus/lib/octopus/apps/supermario/animation/completed.ex:26-32 | octopus/lib/octopus/apps/supermario/animation/game_over.ex:26-32 — 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) octopus/lib/octopus/apps/collective.ex:1353— octopus/lib/octopus/apps/collective.ex:1353-1359 | octopus/lib/octopus/radar/panel_activity.ex:163-169 — 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 `octopus/lib/octopus/apps/collective.ex:1353` 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) octopus/lib/octopus/apps/collective/animations/fireflies.ex:280— octopus/lib/octopus/apps/collective/animations/fireflies.ex:280-286 | octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:273-281 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:284` calls `heat_at`, `map_size` and `octopus/lib/octopus/apps/collective/animations/fireflies.ex:289` 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 × 2) octopus/lib/octopus/apps/fire.ex:58— octopus/lib/octopus/apps/fire.ex:58-64 | octopus/lib/octopus/apps/world_cup_final.ex:79-85 — 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) octopus/lib/octopus/apps/sand/sim.ex:470— octopus/lib/octopus/apps/sand/sim.ex:470-476 | octopus/lib/octopus/apps/world_cup_final.ex:635-641 — 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 (32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:793— octopus/lib/octopus/apps/supermario/level.ex:793-824 | octopus/lib/octopus/apps/supermario/level.ex:1003-1034 — 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 (32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:941— octopus/lib/octopus/apps/supermario/level.ex:941-972 | octopus/lib/octopus/apps/supermario/level.ex:1064-1095 — 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 `octopus/lib/octopus/apps/supermario/level.ex:941` 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 (32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1295— octopus/lib/octopus/apps/supermario/level.ex:1295-1326 | octopus/lib/octopus/apps/supermario/level.ex:3273-3304 — 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 `octopus/lib/octopus/apps/supermario/level.ex:1295` 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 (32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1496— octopus/lib/octopus/apps/supermario/level.ex:1496-1527 | octopus/lib/octopus/apps/supermario/level.ex:2891-2922 — 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 (32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1635— octopus/lib/octopus/apps/supermario/level.ex:1635-1666 | octopus/lib/octopus/apps/supermario/level.ex:2748-2779 — 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 (32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:2704— octopus/lib/octopus/apps/supermario/level.ex:2704-2735 | octopus/lib/octopus/apps/supermario/level.ex:2864-2895 — 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.
MethodTooLong: Pixels3dHook.mounted octopus/assets/js/hooks/pixels3d.ts:128— MethodTooLong — mounted runs 452 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 352 over it, 4.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NationHook.mounted octopus/assets/js/hooks/nation.ts:238— MethodTooLong — mounted runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PixelsHook.mounted octopus/assets/js/hooks/pixels.ts:296— MethodTooLong — mounted runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Pixels3dAframeHook.registerComponents octopus/assets/js/hooks/pixels3daframe.ts:1636— MethodTooLong — registerComponents runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×4
Edited copy of a member (20 corresponding lines) octopus/lib/octopus/apps/supermario/game.ex:404— octopus/lib/octopus/apps/supermario/game.ex:404-423 | octopus/lib/octopus/apps/webpanimation.ex:125-151 — 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) octopus/lib/octopus/canvas.ex:824— octopus/lib/octopus/canvas.ex:824-843 | octopus/lib/octopus/canvas.ex:847-866 — 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) octopus/lib/octopus/apps/pixel_fun.ex:2877— octopus/lib/octopus/apps/pixel_fun.ex:2877-2899 | octopus/lib/octopus/apps/pixel_fun.ex:2903-2922 — 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) octopus/lib/octopus/apps/collective.ex:134— octopus/lib/octopus/apps/collective.ex:134-153 | octopus/lib/octopus/apps/collective.ex:375-394 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×4
Edited copy of a member (1 corresponding lines) octopus/lib/octopus/apps/collective/animations/dots.ex:343— octopus/lib/octopus/apps/collective/animations/dots.ex:343-343 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:171-171 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (1 corresponding lines) octopus/lib/octopus/apps/pixel_fun/merlin_zoom.ex:59— octopus/lib/octopus/apps/pixel_fun/merlin_zoom.ex:59-59 | octopus/lib/octopus/sphere.ex:244-244 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (1 corresponding lines) octopus/lib/octopus/apps/collective/animations/fireflies.ex:366— octopus/lib/octopus/apps/collective/animations/fireflies.ex:366-366 | octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:360-360 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (1 corresponding lines) octopus/lib/octopus_web/components/pixel_fun_config_component.ex:370— octopus/lib/octopus_web/components/pixel_fun_config_component.ex:370-370 | octopus/lib/octopus_web/components/wood_config_component.ex:298-298 — 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 (14 lines × 2) octopus/lib/octopus/apps/blocks.ex:61— octopus/lib/octopus/apps/blocks.ex:61-74 | octopus/lib/octopus/apps/snake.ex:60-73 — before extracting anything, compare `octopus/lib/octopus/apps/blocks.ex` and `octopus/lib/octopus/apps/snake.ex` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) octopus/lib/octopus/apps/collective/animations/glowworms.ex:138— octopus/lib/octopus/apps/collective/animations/glowworms.ex:138-151 | octopus/lib/octopus/apps/collective/animations/glowworms.ex:215-228 — 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 `octopus/lib/octopus/apps/collective/animations/glowworms.ex:138` 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 (14 lines × 2) octopus/lib/octopus/webp.ex:17— octopus/lib/octopus/webp.ex:17-30 | octopus/lib/octopus/webp.ex:76-89 — 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 lines × 2) octopus/lib/octopus/apps/ten_letters.ex:198— octopus/lib/octopus/apps/ten_letters.ex:198-213 | octopus/lib/octopus/apps/triple_tla.ex:281-294 — before extracting anything, compare `octopus/lib/octopus/apps/ten_letters.ex` and `octopus/lib/octopus/apps/triple_tla.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 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 (11 lines × 2) octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:195— octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:195-205 | octopus/lib/octopus/apps/collective/animations/ring_noise.ex:138-148 — 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 (11 lines × 2) octopus/lib/octopus/canvas.ex:824— octopus/lib/octopus/canvas.ex:824-834 | octopus/lib/octopus/canvas.ex:847-857 — 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) octopus/lib/octopus/installation_transport.ex:327— octopus/lib/octopus/installation_transport.ex:327-337 | octopus/lib/octopus/installation_transport.ex:357-367 — 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) octopus/lib/octopus/apps/blocks.ex:32— octopus/lib/octopus/apps/blocks.ex:32-42 | octopus/lib/octopus/apps/snake.ex:31-41 — before extracting anything, compare `octopus/lib/octopus/apps/blocks.ex` and `octopus/lib/octopus/apps/snake.ex` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) octopus/lib/octopus/apps/collective/animations/presence_panels.ex:66— octopus/lib/octopus/apps/collective/animations/presence_panels.ex:66-71 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:126-131 — 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) octopus/lib/octopus/apps/perlin_noise.ex:343— octopus/lib/octopus/apps/perlin_noise.ex:343-348 | octopus/lib/octopus/perlin_noise.ex:218-223 — before extracting anything, compare `octopus/lib/octopus/apps/perlin_noise.ex` and `octopus/lib/octopus/perlin_noise.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 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 (6 lines × 2) octopus/lib/octopus/apps/webpanimation.ex:155— octopus/lib/octopus/apps/webpanimation.ex:155-160 | octopus/lib/octopus/webp.ex:66-71 — 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) octopus/lib/octopus_web/live/nation_live.ex:150— octopus/lib/octopus_web/live/nation_live.ex:150-155 | octopus/lib/octopus_web/live/radar_live.ex:470-475 — 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 locations) octopus/assets/js/hooks/nation.ts:77— octopus/assets/js/hooks/nation.ts:77 · octopus/assets/js/hooks/pixels.ts:32 — 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 (6 lines × 2 locations) octopus/assets/js/hooks/nation.ts:181— octopus/assets/js/hooks/nation.ts:181 · octopus/assets/js/hooks/nation.ts:192 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (6 lines × 2 locations) octopus/assets/js/hooks/nation.ts:470— octopus/assets/js/hooks/nation.ts:470 · octopus/assets/js/hooks/pixels.ts:395 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (6 lines × 2 locations) octopus/assets/js/hooks/pixels3daframe.ts:1001— octopus/assets/js/hooks/pixels3daframe.ts:1001 · octopus/assets/js/hooks/pixels3daframe.ts:1008 — 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.
AC1 · Text alternatives· <canvas> without a text alternative · ×3
<canvas> without a text alternative octopus/lib/octopus_web/live/nation_live.ex:110— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative octopus/lib/octopus_web/live/pixels_live.ex:254— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative octopus/lib/octopus_web/live/proximity_live.ex:104— 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 · ×3
Page without a main landmark octopus/lib/octopus_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>.
Page without a main landmark octopus/lib/octopus_web/components/layouts/root_aframe.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>.
Page without a main landmark octopus/lib/octopus_web/components/layouts/root_sim3d.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>.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×3
Modal dialog does not manage focus octopus/lib/octopus_web/components/console_components.ex:1507— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus octopus/lib/octopus_web/components/console_components.ex:1537— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus octopus/lib/octopus_web/components/installation_console_component.ex:212— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Hotspot: octopus/lib/octopus_web/components/installation_console_component.ex octopus/lib/octopus_web/components/installation_console_component.ex:895— octopus/lib/octopus_web/components/installation_console_component.ex changed 42 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in InstallationConsoleComponent.assign_transport_view at line 895. 3 of those changes were fix/bug commits, and the other 39 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 21:28:47 +02:00' --until='2026-09-28 21:28:47 +02:00' --full-history --no-merges -- octopus/lib/octopus_web/components/installation_console_component.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: octopus/lib/octopus/apps/pixel_fun.ex octopus/lib/octopus/apps/pixel_fun.ex:392— octopus/lib/octopus/apps/pixel_fun.ex changed 44 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PixelFun.summary_for_preset at line 392. 9 of those changes were fix/bug commits, and the other 35 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 21:28:47 +02:00' --until='2026-09-28 21:28:47 +02:00' --full-history --no-merges -- octopus/lib/octopus/apps/pixel_fun.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: octopus/assets/js/hooks/pixels.ts octopus/assets/js/hooks/pixels.ts:296— octopus/assets/js/hooks/pixels.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in PixelsHook.mounted at line 296. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 21:28:47 +02:00' --until='2026-09-28 21:28:47 +02:00' --full-history --no-merges -- octopus/assets/js/hooks/pixels.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) octopus/lib/octopus/radar/track_merge.ex:101— octopus/lib/octopus/radar/track_merge.ex:101-123 | octopus/lib/octopus_web/live/radar_live.ex:2244-2264 — 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) octopus/lib/octopus/mixer.ex:1005— octopus/lib/octopus/mixer.ex:1005-1025 | octopus/lib/octopus/mixer.ex:1035-1056 — 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) octopus/lib/octopus/mixer.ex:191— octopus/lib/octopus/mixer.ex:191-211 | octopus/lib/octopus/mixer.ex:219-239 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) octopus/lib/octopus/apps/supermario/animation/completed.ex:17— octopus/lib/octopus/apps/supermario/animation/completed.ex:17-32 | octopus/lib/octopus/apps/supermario/animation/game_over.ex:17-32 — 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) octopus/lib/octopus/radar/stats.ex:81— octopus/lib/octopus/radar/stats.ex:81-101 | octopus/lib/octopus/radar/status_history.ex:54-69 — 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) octopus/lib/octopus_web/live/radar_debug_live.ex:159— octopus/lib/octopus_web/live/radar_debug_live.ex:159-174 | octopus/lib/octopus_web/live/radar_live.ex:414-430 — 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 (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) octopus/lib/octopus/apps/pixie_debug.ex:706— octopus/lib/octopus/apps/pixie_debug.ex:706-709 | octopus/lib/octopus/apps/wood.ex:759-762 — 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) octopus/lib/octopus/radar/status_history.ex:96— octopus/lib/octopus/radar/status_history.ex:96-99 | octopus/lib/octopus_web/live/radar_debug_live.ex:612-615 — 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) octopus/lib/octopus/apps/circular_clock.ex:145— octopus/lib/octopus/apps/circular_clock.ex:145-151 | octopus/lib/octopus/apps/slot_machine.ex:152-155 — 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 (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) octopus/lib/octopus/radar/sensor.ex:357— octopus/lib/octopus/radar/sensor.ex:357-374 | octopus/lib/octopus/radar/sensor.ex:378-389 — 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) octopus/lib/octopus/radar.ex:1117— octopus/lib/octopus/radar.ex:1117-1131 | octopus/lib/octopus/radar.ex:1142-1153 — 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) octopus/lib/octopus/apps/circular_clock.ex:350— octopus/lib/octopus/apps/circular_clock.ex:350-361 | octopus/lib/octopus/apps/one_word.ex:95-106 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×3
Edited copy of a member (2 corresponding lines) octopus/lib/octopus/apps/collective/animations/storm.ex:193— octopus/lib/octopus/apps/collective/animations/storm.ex:193-194 | octopus/lib/octopus/radar/panel_mapping.ex:43-44 — 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) octopus/lib/octopus/apps/collective/animations/fireflies.ex:349— octopus/lib/octopus/apps/collective/animations/fireflies.ex:349-350 | octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:319-320 — 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) octopus/lib/octopus/apps/collective/animations/fireflies.ex:301— octopus/lib/octopus/apps/collective/animations/fireflies.ex:301-302 | octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:298-299 — 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.
Duplicated block (30 lines × 3) octopus/lib/octopus/apps/supermario/level.ex:837— octopus/lib/octopus/apps/supermario/level.ex:837-867 | octopus/lib/octopus/apps/supermario/level.ex:872-901 | octopus/lib/octopus/apps/supermario/level.ex:3008-3037 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (30 lines × 3) octopus/lib/octopus/apps/supermario/level.ex:1213— octopus/lib/octopus/apps/supermario/level.ex:1213-1242 | octopus/lib/octopus/apps/supermario/level.ex:1262-1291 | octopus/lib/octopus/apps/supermario/level.ex:2209-2238 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (30 lines × 3) octopus/lib/octopus/apps/supermario/level.ex:1253— octopus/lib/octopus/apps/supermario/level.ex:1253-1282 | octopus/lib/octopus/apps/supermario/level.ex:1291-1320 | octopus/lib/octopus/apps/supermario/level.ex:3256-3285 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:241— octopus/lib/octopus/apps/supermario/level.ex:241-258 | octopus/lib/octopus/apps/supermario/level.ex:288-305 — 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 `octopus/lib/octopus/apps/supermario/level.ex:241` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) octopus/lib/octopus/mixer.ex:646— octopus/lib/octopus/mixer.ex:646-663 | octopus/lib/octopus/mixer.ex:706-723 — 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 (18 lines × 2) octopus/lib/octopus/mixer.ex:765— octopus/lib/octopus/mixer.ex:765-782 | octopus/lib/octopus/mixer.ex:787-804 — 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) octopus/lib/octopus/apps/pixel_fun.ex:2244— octopus/lib/octopus/apps/pixel_fun.ex:2244-2252 | octopus/lib/octopus/apps/pixel_fun.ex:2289-2297 — 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) octopus/lib/octopus_web/components/app_config_component.ex:155— octopus/lib/octopus_web/components/app_config_component.ex:155-163 | octopus/lib/octopus_web/components/wood_config_component.ex:133-141 — before extracting anything, compare `octopus/lib/octopus_web/components/app_config_component.ex` and `octopus/lib/octopus_web/components/wood_config_component.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 (9 lines × 2) octopus/lib/octopus/apps/perlin_noise.ex:312— octopus/lib/octopus/apps/perlin_noise.ex:312-320 | octopus/lib/octopus/perlin_noise.ex:187-195 — before extracting anything, compare `octopus/lib/octopus/apps/perlin_noise.ex` and `octopus/lib/octopus/perlin_noise.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 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 (7 lines × 3) octopus/lib/octopus/apps/collective.ex:1366— octopus/lib/octopus/apps/collective.ex:1366-1372 | octopus/lib/octopus/radar/panel_activity.ex:203-209 | octopus/lib/octopus/radar/panel_gravity.ex:364-370 — 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 (7 lines × 3) octopus/lib/octopus/apps/collective.ex:1376— octopus/lib/octopus/apps/collective.ex:1376-1382 | octopus/lib/octopus/radar/panel_activity.ex:193-199 | octopus/lib/octopus/radar/panel_gravity.ex:354-360 — 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 (7 lines × 3) octopus/lib/octopus/apps/collective/animations/dots.ex:50— octopus/lib/octopus/apps/collective/animations/dots.ex:50-56 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:30-36 | octopus/lib/octopus/apps/collective/animations/storm.ex:63-69 — before extracting anything, compare `octopus/lib/octopus/apps/collective/animations/dots.ex` and `octopus/lib/octopus/apps/collective/animations/presence_panels.ex` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (8 lines × 2) octopus/lib/octopus/apps/fairy_dust.ex:81— octopus/lib/octopus/apps/fairy_dust.ex:81-88 | octopus/lib/octopus/particles.ex:197-204 — 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 `octopus/lib/octopus/apps/fairy_dust.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.
Duplicated block (8 lines × 2) octopus/lib/octopus/radar.ex:1521— octopus/lib/octopus/radar.ex:1521-1528 | octopus/lib/octopus/radar/sensitivity.ex:20-27 — 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) octopus/lib/octopus/radar/track_merge.ex:127— octopus/lib/octopus/radar/track_merge.ex:127-134 | octopus/lib/octopus_web/live/radar_live.ex:2268-2275 — 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 `octopus/lib/octopus/radar/track_merge.ex:127` 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 × 3) octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:341— octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:341-345 | octopus/lib/octopus/apps/collective/animations/ring_noise.ex:221-225 | octopus/lib/octopus/apps/pixel_fun/gradient_palettes.ex:114-118 — 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) octopus/lib/octopus/apps/senso.ex:72— octopus/lib/octopus/apps/senso.ex:72-76 | octopus/lib/octopus/apps/senso.ex:157-161 | octopus/lib/octopus/apps/senso.ex:188-192 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) octopus/lib/octopus/apps/fireworks.ex:42— octopus/lib/octopus/apps/fireworks.ex:42-46 | octopus/lib/octopus/apps/sand.ex:985-989 | octopus/lib/octopus/apps/sparkle_mist.ex:390-394 — 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, `octopus/lib/octopus/apps/fireworks.ex:41` calls `num_panels` and `octopus/lib/octopus/apps/sparkle_mist.ex:389` 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 locations) octopus/assets/js/hooks/humanComponents.ts:200— octopus/assets/js/hooks/humanComponents.ts:200 · octopus/assets/js/hooks/humanComponents.ts:212 — 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) octopus/assets/js/hooks/pixels.ts:111— octopus/assets/js/hooks/pixels.ts:111 · octopus/assets/js/hooks/pixels.ts:354 — 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 locations) octopus/assets/js/hooks/pixels3daframe.ts:973— octopus/assets/js/hooks/pixels3daframe.ts:973 · octopus/assets/js/hooks/pixels3daframe.ts:981 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC3 · Page structure· Data table has no header cells · ×2
Data table has no header cells octopus/lib/octopus_web/live/playlists_live.ex:32— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells octopus/lib/octopus_web/live/playlists_live.ex:87— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Focus outline removed inline octopus/lib/octopus_web/components/console_components.ex:1116— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline octopus/lib/octopus_web/components/console_components.ex:1208— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Unbounded dependency requirement: ecto_sqlite3 — Runtime dependency `:ecto_sqlite3` is declared `">= 0.22.0"` in octopus/mix.exs, which has no upper bound — every future MAJOR release of `:ecto_sqlite3` satisfies it, so the next unlocked resolve can pull a breaking change. Use `~>` (e.g. `"~> 1.0"`) to bound the requirement to a compatible range.
Unbounded dependency requirement: gettext — Runtime dependency `:gettext` is declared `">= 0.0.0"` in octopus/mix.exs, which has no upper bound — every future MAJOR release of `:gettext` satisfies it, so the next unlocked resolve can pull a breaking change. Use `~>` (e.g. `"~> 1.0"`) to bound the requirement to a compatible range.
ClassTooLong: Pixels3dAframeHook octopus/assets/js/hooks/pixels3daframe.ts:680— ClassTooLong — 832 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 432 over it, 2.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Pixels3dHook octopus/assets/js/hooks/pixels3d.ts:127— ClassTooLong — 453 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 53 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) octopus/lib/octopus/mixer.ex:573— octopus/lib/octopus/mixer.ex:573-597 | octopus/lib/octopus/mixer.ex:602-630 | octopus/lib/octopus/mixer.ex:646-693 | octopus/lib/octopus/mixer.ex:706-739 — 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) octopus/lib/octopus_web/components/app_config_component.ex:99— octopus/lib/octopus_web/components/app_config_component.ex:99-147 | octopus/lib/octopus_web/components/global_params_component.ex:129-142 | octopus/lib/octopus_web/components/sim3d_params_component.ex:79-103 | octopus/lib/octopus_web/components/wood_config_component.ex:87-125 — 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 (49 corresponding lines) · ×2
Edited copy of a member (49 corresponding lines) octopus/lib/octopus/apps/pixel_fun.ex:2227— octopus/lib/octopus/apps/pixel_fun.ex:2227-2278 | octopus/lib/octopus/apps/pixel_fun.ex:2283-2331 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (49 corresponding lines) octopus/lib/octopus/apps/fire.ex:141— octopus/lib/octopus/apps/fire.ex:141-196 | octopus/lib/octopus/apps/world_cup_final.ex:128-176 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) octopus/lib/octopus/apps/whackamole/game.ex:558— octopus/lib/octopus/apps/whackamole/game.ex:558-583 | octopus/lib/octopus/apps/whackamole/game.ex:588-605 — 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) octopus/lib/octopus/playlist_scheduler.ex:118— octopus/lib/octopus/playlist_scheduler.ex:118-137 | octopus/lib/octopus/playlist_scheduler.ex:141-158 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) octopus/lib/octopus/apps/circular_clock.ex:432— octopus/lib/octopus/apps/circular_clock.ex:432-441 | octopus/lib/octopus/apps/circular_clock.ex:446-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) octopus/lib/octopus/apps/sand/sim.ex:244— octopus/lib/octopus/apps/sand/sim.ex:244-253 | octopus/lib/octopus/apps/sand/sim.ex:257-269 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) octopus/lib/octopus/apps/pixel_fun.ex:1535— octopus/lib/octopus/apps/pixel_fun.ex:1535-1547 | octopus/lib/octopus/apps/pixel_fun.ex:1581-1593 — 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) octopus/lib/octopus/apps/pixel_fun.ex:1551— octopus/lib/octopus/apps/pixel_fun.ex:1551-1563 | octopus/lib/octopus/apps/pixel_fun.ex:1597-1609 — 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 (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) octopus/lib/octopus/canvas.ex:64— octopus/lib/octopus/canvas.ex:64-70 | octopus/lib/octopus/canvas.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) octopus/lib/octopus/radar/sensor_transition.ex:57— octopus/lib/octopus/radar/sensor_transition.ex:57-63 | octopus/lib/octopus/radar/sensor_transition.ex:72-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.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) octopus/lib/octopus/apps/running_lights.ex:152— octopus/lib/octopus/apps/running_lights.ex:152-157 | octopus/lib/octopus/apps/senso.ex:248-252 — 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) octopus/lib/octopus/radar/clutter_filter.ex:234— octopus/lib/octopus/radar/clutter_filter.ex:234-238 | octopus/lib/octopus_web/live/radar_live.ex:2800-2804 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (37 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1965— octopus/lib/octopus/apps/supermario/level.ex:1965-2001 | octopus/lib/octopus/apps/supermario/level.ex:2758-2794 — 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 (37 lines × 2) octopus/lib/octopus/apps/ten_letters.ex:16— octopus/lib/octopus/apps/ten_letters.ex:16-52 | octopus/lib/octopus/apps/triple_tla.ex:17-53 — before extracting anything, compare `octopus/lib/octopus/apps/ten_letters.ex` and `octopus/lib/octopus/apps/triple_tla.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 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 (30 lines × 6) octopus/lib/octopus/apps/supermario/level.ex:989— octopus/lib/octopus/apps/supermario/level.ex:989-1018 | octopus/lib/octopus/apps/supermario/level.ex:1112-1141 | octopus/lib/octopus/apps/supermario/level.ex:1615-1644 | octopus/lib/octopus/apps/supermario/level.ex:1977-2006 | octopus/lib/octopus/apps/supermario/level.ex:2093-2122 | octopus/lib/octopus/apps/supermario/level.ex:2770-2799 — all 6 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 (30 lines × 6) octopus/lib/octopus/apps/supermario/level.ex:1582— octopus/lib/octopus/apps/supermario/level.ex:1582-1611 | octopus/lib/octopus/apps/supermario/level.ex:1632-1661 | octopus/lib/octopus/apps/supermario/level.ex:1876-1905 | octopus/lib/octopus/apps/supermario/level.ex:1980-2009 | octopus/lib/octopus/apps/supermario/level.ex:2103-2132 | octopus/lib/octopus/apps/supermario/level.ex:2745-2774 — all 6 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 (25 lines × 2) octopus/lib/octopus/apps/ocean.ex:366— octopus/lib/octopus/apps/ocean.ex:366-390 | octopus/lib/octopus/apps/ocean.ex:404-428 — 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 `octopus/lib/octopus/apps/ocean.ex:366` 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 (25 lines × 2) octopus/lib/octopus/apps/senso.ex:256— octopus/lib/octopus/apps/senso.ex:256-280 | octopus/lib/octopus/apps/senso.ex:284-308 — 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 `octopus/lib/octopus/apps/senso.ex:256` 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 (22–23 lines × 2) octopus/lib/octopus/apps/ten_letters.ex:259— octopus/lib/octopus/apps/ten_letters.ex:259-281 | octopus/lib/octopus/apps/triple_tla.ex:504-525 — before extracting anything, compare `octopus/lib/octopus/apps/ten_letters.ex` and `octopus/lib/octopus/apps/triple_tla.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 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 (22–23 lines × 2) octopus/lib/octopus/sunlight.ex:271— octopus/lib/octopus/sunlight.ex:271-292 | octopus/lib/octopus/sunlight.ex:329-351 — 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 `octopus/lib/octopus/sunlight.ex:271` 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 (18–19 lines × 2) octopus/lib/octopus/apps/slot_machine.ex:753— octopus/lib/octopus/apps/slot_machine.ex:753-770 | octopus/lib/octopus/apps/sprites_grouped.ex:317-335 — 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 (18–19 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:207— octopus/lib/octopus/apps/supermario/level.ex:207-224 | octopus/lib/octopus/apps/supermario/level.ex:317-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 `octopus/lib/octopus/apps/supermario/level.ex:207` 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 (17 lines × 2) octopus/lib/octopus/apps/perlin_noise.ex:244— octopus/lib/octopus/apps/perlin_noise.ex:244-260 | octopus/lib/octopus/perlin_noise.ex:118-134 — before extracting anything, compare `octopus/lib/octopus/apps/perlin_noise.ex` and `octopus/lib/octopus/perlin_noise.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `octopus/lib/octopus/perlin_noise.ex:135` calls `then` and `octopus/lib/octopus/apps/perlin_noise.ex:261` 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 (17 lines × 2) octopus/lib/octopus/installation_transport/persisted_state.ex:28— octopus/lib/octopus/installation_transport/persisted_state.ex:28-44 | octopus/lib/octopus/playlist_scheduler/persisted_state.ex:26-42 — 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 (16 lines × 2) octopus/lib/octopus/apps/rain.ex:83— octopus/lib/octopus/apps/rain.ex:83-98 | octopus/lib/octopus/apps/sparkle_mist.ex:195-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.
Duplicated block (16 lines × 2) octopus/lib/octopus/apps/supermario/game.ex:406— octopus/lib/octopus/apps/supermario/game.ex:406-421 | octopus/lib/octopus/apps/webpanimation.ex:130-145 — 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 (15–16 lines × 2) octopus/lib/octopus/mixer.ex:573— octopus/lib/octopus/mixer.ex:573-587 | octopus/lib/octopus/mixer.ex:602-617 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–16 lines × 2) octopus/lib/octopus_web/live/nation_live.ex:265— octopus/lib/octopus_web/live/nation_live.ex:265-280 | octopus/lib/octopus_web/live/radar_live.ex:2084-2098 — 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 `octopus/lib/octopus_web/live/nation_live.ex:265` 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 lines × 2) octopus/lib/octopus/apps/blocks/game.ex:497— octopus/lib/octopus/apps/blocks/game.ex:497-509 | octopus/lib/octopus/apps/snake/game.ex:183-195 — 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 (13 lines × 2) octopus/lib/octopus/apps/ten_letters.ex:139— octopus/lib/octopus/apps/ten_letters.ex:139-151 | octopus/lib/octopus/apps/triple_tla.ex:247-259 — before extracting anything, compare `octopus/lib/octopus/apps/ten_letters.ex` and `octopus/lib/octopus/apps/triple_tla.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 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 (12 lines × 2) octopus/lib/octopus/apps/perlin_noise.ex:326— octopus/lib/octopus/apps/perlin_noise.ex:326-337 | octopus/lib/octopus/perlin_noise.ex:201-212 — before extracting anything, compare `octopus/lib/octopus/apps/perlin_noise.ex` and `octopus/lib/octopus/perlin_noise.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 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 lines × 2) octopus/lib/octopus/apps/sample_app.ex:66— octopus/lib/octopus/apps/sample_app.ex:66-77 | octopus/lib/octopus/apps/sample_app.ex:81-92 — 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) octopus/lib/octopus/installation_transport.ex:1320— octopus/lib/octopus/installation_transport.ex:1320-1329 | octopus/lib/octopus_web/components/installation_console_component.ex:879-888 — 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) octopus/lib/octopus/radar/track_merge.ex:114— octopus/lib/octopus/radar/track_merge.ex:114-123 | octopus/lib/octopus_web/live/radar_live.ex:2255-2264 — 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 `octopus/lib/octopus/radar/track_merge.ex:114` 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) octopus/lib/octopus/apps/collective/animations/breath.ex:384— octopus/lib/octopus/apps/collective/animations/breath.ex:384-389 | octopus/lib/octopus/apps/collective/animations/dots.ex:315-320 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:145-150 — before extracting anything, compare `octopus/lib/octopus/apps/collective/animations/dots.ex` and `octopus/lib/octopus/apps/collective/animations/presence_panels.ex` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (6 lines × 3) octopus/lib/octopus/apps/collective/animations/fireflies.ex:290— octopus/lib/octopus/apps/collective/animations/fireflies.ex:290-295 | octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:287-292 | octopus/lib/octopus/apps/collective/animations/ring_noise.ex:195-200 — 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, `octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:284` calls `heat_at`, `map_size` and `octopus/lib/octopus/apps/collective/animations/fireflies.ex:287` 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 (5 lines × 2) octopus/lib/octopus/apps/circular_clock.ex:437— octopus/lib/octopus/apps/circular_clock.ex:437-441 | octopus/lib/octopus/apps/circular_clock.ex:452-456 — 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 `octopus/lib/octopus/apps/circular_clock.ex:437` 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) octopus/lib/octopus/apps/pixel_fun.ex:2255— octopus/lib/octopus/apps/pixel_fun.ex:2255-2259 | octopus/lib/octopus/apps/pixel_fun.ex:2302-2309 — 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 `octopus/lib/octopus/apps/pixel_fun.ex:2255` 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 locations) octopus/assets/js/app_sim3d.js:8— octopus/assets/js/app_sim3d.js:8 · octopus/assets/js/app_sim3daframe.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (13 lines × 2 locations) octopus/assets/js/hooks/pixels3d.ts:499— octopus/assets/js/hooks/pixels3d.ts:499 · octopus/assets/js/hooks/pixels3d.ts:516 — 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 locations) octopus/assets/js/hooks/index.js:313— octopus/assets/js/hooks/index.js:313 · octopus/assets/js/hooks/index.js:333 — 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 (12 lines × 2 locations) octopus/assets/js/hooks/pixels3daframe.ts:489— octopus/assets/js/hooks/pixels3daframe.ts:489 · octopus/assets/js/hooks/pixels3daframe.ts:942 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard octopus/lib/octopus_web/live/radar_live.ex— <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
No authorization octopus/lib/octopus_web/endpoint.ex:2— This repository serves requests — a server (use Phoenix.Endpoint) (octopus/lib/octopus_web/endpoint.ex:2) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
Pixels3dHook.mounted (cyclomatic 38) octopus/assets/js/hooks/pixels3d.ts:128— Pixels3dHook.mounted has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 5 of the 38 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 209, a function literal at line 233, a function literal at line 723, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
InstallationConsoleComponent.assign_transport_view (cyclomatic 30) octopus/lib/octopus_web/components/installation_console_component.ex:895— InstallationConsoleComponent.assign_transport_view has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Sphere.build_motion_params (cyclomatic 24) octopus/lib/octopus/apps/pixel_fun/transform/sphere.ex:32— Sphere.build_motion_params has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
mounted (cyclomatic 22) octopus/assets/js/hooks/index.js:256— mounted has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (_onPointerDown, a function literal at line 290, restoreSize, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PixelsHook.mounted (cyclomatic 20) octopus/assets/js/hooks/pixels.ts:296— PixelsHook.mounted has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (draw, onPointerMove, scheduleDraw, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
NationHook.mounted (cyclomatic 20) octopus/assets/js/hooks/nation.ts:238— NationHook.mounted has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 303, draw, a function literal at line 364, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
humanComponents.registerHumanComponents (cyclomatic 20) octopus/assets/js/hooks/humanComponents.ts:29— humanComponents.registerHumanComponents has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 44, 85, 154, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PixelFun.summary_for_preset (cyclomatic 18) octopus/lib/octopus/apps/pixel_fun.ex:392— PixelFun.summary_for_preset has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Mixer.build_display_info (cyclomatic 16) octopus/lib/octopus/mixer.ex:742— Mixer.build_display_info has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Retired release: circuits_gpio — `:circuits_gpio` is pinned to 2.1.2 in the committed REDACTED, and the publisher retired it as invalid on hex.pm — "Contains severe bug affecting interrupts. Upgrade to >=2.1.3". A retired release is one the publisher has asked you to stop using. The current stable release is 2.3.1. Move off it and commit the updated lockfile.
Glowworms.handle_worm_phase (cognitive 35) octopus/lib/octopus/apps/collective/animations/glowworms.ex:254— Glowworms.handle_worm_phase has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Pixels3dHook.mounted (cognitive 31) octopus/assets/js/hooks/pixels3d.ts:128— Pixels3dHook.mounted has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (18 pts), loops 8 (10 pts), match/switch 2, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (animate, a function literal at line 723, updateMeshes, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
mounted (cognitive 29) octopus/assets/js/hooks/index.js:256— mounted has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 7, ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 290, _onPointerDown, restoreSize, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PixelFun.summary_for_preset (cognitive 28) octopus/lib/octopus/apps/pixel_fun.ex:392— PixelFun.summary_for_preset has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (21 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Sphere.build_motion_params (cognitive 27) octopus/lib/octopus/apps/pixel_fun/transform/sphere.ex:32— Sphere.build_motion_params has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 20, if/else 6 (7 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Glowworms.check_gravity (cognitive 25) octopus/lib/octopus/apps/collective/animations/glowworms.ex:329— Glowworms.check_gravity has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstallationConsoleComponent.assign_transport_view (cognitive 22) octopus/lib/octopus_web/components/installation_console_component.ex:895— InstallationConsoleComponent.assign_transport_view has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 8, match/switch 5. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PixelFun.effective_transform_values (cognitive 21) octopus/lib/octopus/apps/pixel_fun.ex:2788— PixelFun.effective_transform_values has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, match/switch 2 (4 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.
NationHook.mounted (cognitive 21) octopus/assets/js/hooks/nation.ts:238— NationHook.mounted has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (18 pts), loops 2 (3 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 303, a function literal at line 364, draw, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
humanComponents.registerHumanComponents (cognitive 21) octopus/assets/js/hooks/humanComponents.ts:29— humanComponents.registerHumanComponents has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (6 pts), loops 4, boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 44, 85, 154, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Sim.move_grain (cognitive 19) octopus/lib/octopus/apps/sand/sim.ex:118— Sim.move_grain has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 4 (13 pts), if/else 5 (6 pts) (nesting depth added 10). 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.
PixelsHook.mounted (cognitive 19) octopus/assets/js/hooks/pixels.ts:296— PixelsHook.mounted has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 5, loops 1 (2 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function items inside it that branch (draw, onPointerMove, scheduleDraw, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FunctionTooLong: humanComponents.registerHumanComponents octopus/assets/js/hooks/humanComponents.ts:29— FunctionTooLong — registerHumanComponents runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Near-duplicate member family (4 members, 234 shared lines) · ×1
Near-duplicate member family (4 members, 234 shared lines) octopus/lib/octopus/apps/supermario/level.ex:343— octopus/lib/octopus/apps/supermario/level.ex:343-1326 | octopus/lib/octopus/apps/supermario/level.ex:1330-2315 | octopus/lib/octopus/apps/supermario/level.ex:2319-3304 | octopus/lib/octopus/apps/supermario/level.ex:3308-4293 — These 4 members are variants of one another: a block of 234 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) octopus/lib/octopus/apps/collective/animations/breath.ex:294— octopus/lib/octopus/apps/collective/animations/breath.ex:294-306 | octopus/lib/octopus/apps/collective/animations/dots.ex:191-203 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:56-78 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:124-135 | octopus/lib/octopus/apps/collective/animations/ring_noise.ex:177-189 | octopus/lib/octopus/apps/collective/animations/storm.ex:431-443 — These 6 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 6 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 6 times.
D4 · Code Duplication· Edited copy of a member (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) octopus/lib/octopus/apps/triple_tla.ex:344— octopus/lib/octopus/apps/triple_tla.ex:344-399 | octopus/lib/octopus/apps/triple_tla.ex:403-462 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) octopus/lib/octopus/hardware/untangle.ex:32— octopus/lib/octopus/hardware/untangle.ex:32-72 | octopus/lib/octopus/hardware/untangle.ex:80-119 — 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 copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) octopus/lib/octopus_web/live/nation_live.ex:261— octopus/lib/octopus_web/live/nation_live.ex:261-280 | octopus/lib/octopus_web/live/radar_live.ex:2080-2098 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) octopus/lib/octopus/apps/matrix.ex:454— octopus/lib/octopus/apps/matrix.ex:454-513 | octopus/lib/octopus/apps/shape_shifter.ex:58-117 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) octopus/lib/octopus/apps/collective/animations/glowworms.ex:130— octopus/lib/octopus/apps/collective/animations/glowworms.ex:130-159 | octopus/lib/octopus/apps/collective/animations/glowworms.ex:206-230 — 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 (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) octopus/lib/octopus/apps/whackamole.ex:139— octopus/lib/octopus/apps/whackamole.ex:139-161 | octopus/lib/octopus/apps/whackamole.ex:166-190 | octopus/lib/octopus/apps/whackamole/game.ex:64-86 | octopus/lib/octopus/apps/whackamole/game.ex:609-628 — 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 copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) octopus/lib/octopus/radar/sensor.ex:732— octopus/lib/octopus/radar/sensor.ex:732-754 | octopus/lib/octopus/radar/sensor.ex:812-838 — 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 (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) octopus/lib/octopus/apps/ten_letters.ex:217— octopus/lib/octopus/apps/ten_letters.ex:217-249 | octopus/lib/octopus/apps/triple_tla.ex:301-335 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) · ×1
Edited copy of a member (31 corresponding lines) octopus/lib/octopus/apps/ocean.ex:366— octopus/lib/octopus/apps/ocean.ex:366-397 | octopus/lib/octopus/apps/ocean.ex:404-434 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) octopus/lib/octopus/apps/whackamole/game.ex:158— octopus/lib/octopus/apps/whackamole/game.ex:158-187 | octopus/lib/octopus/apps/whackamole/game.ex:208-243 — 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 copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) octopus/lib/octopus/apps/collective/animations/breath.ex:384— octopus/lib/octopus/apps/collective/animations/breath.ex:384-394 | octopus/lib/octopus/apps/collective/animations/dots.ex:315-325 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:145-153 — 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 (4 members, 29+ corresponding lines) · ×1
Edited copies of one member (4 members, 29+ corresponding lines) octopus/lib/octopus/apps/collective.ex:61— octopus/lib/octopus/apps/collective.ex:61-96 | octopus/lib/octopus/apps/ocean.ex:77-105 | octopus/lib/octopus/apps/perlin_noise.ex:29-66 | octopus/lib/octopus/apps/sparkle_mist.ex:45-82 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) octopus/lib/octopus_web/components/app_config_component.ex:151— octopus/lib/octopus_web/components/app_config_component.ex:151-163 | octopus/lib/octopus_web/components/pixel_fun_config_component.ex:345-354 | octopus/lib/octopus_web/components/wood_config_component.ex:129-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) octopus/lib/octopus/canvas.ex:451— octopus/lib/octopus/canvas.ex:451-478 | octopus/lib/octopus/canvas.ex:482-509 — 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 copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) octopus/lib/octopus/radar/mock/world.ex:441— octopus/lib/octopus/radar/mock/world.ex:441-451 | octopus/lib/octopus/radar/mock/world.ex:458-471 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) octopus/lib/octopus/canvas.ex:212— octopus/lib/octopus/canvas.ex:212-222 | octopus/lib/octopus/canvas.ex:226-234 | octopus/lib/octopus/canvas.ex:242-250 | octopus/lib/octopus/canvas.ex:254-262 — 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 (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) octopus/lib/octopus/apps/whackamole.ex:311— octopus/lib/octopus/apps/whackamole.ex:311-332 | octopus/lib/octopus/apps/whackamole.ex:337-358 | octopus/lib/octopus/apps/whackamole.ex:430-453 — 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 (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) octopus/lib/octopus/font.ex:16— octopus/lib/octopus/font.ex:16-19 | octopus/lib/octopus/image.ex:8-11 | octopus/lib/octopus/sprite.ex:8-11 — 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 (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) octopus/lib/octopus/apps/collective.ex:618— octopus/lib/octopus/apps/collective.ex:618-627 | octopus/lib/octopus/radar/panel_activity.ex:86-94 — 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 (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) octopus/lib/octopus/radar/sensor.ex:647— octopus/lib/octopus/radar/sensor.ex:647-660 | octopus/lib/octopus/radar/sensor.ex:664-680 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) octopus/lib/octopus/apps/collective.ex:1386— octopus/lib/octopus/apps/collective.ex:1386-1388 | octopus/lib/octopus/apps/rain.ex:188-190 | octopus/lib/octopus/apps/sparkle_mist.ex:267-269 | octopus/lib/octopus/radar/panel_activity.ex:176-178 — 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 copies of one member (5 members, 3+ corresponding lines) · ×1
Edited copies of one member (5 members, 3+ corresponding lines) octopus/lib/octopus/app_mode_presets.ex:293— octopus/lib/octopus/app_mode_presets.ex:293-295 | octopus/lib/octopus/app_mode_presets/loader_support.ex:63-65 | octopus/lib/octopus/apps/matrix.ex:725-727 | octopus/lib/octopus/apps/sparkle_mist.ex:481-483 | octopus/lib/octopus/apps/wood.ex:814-816 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) octopus/lib/octopus/radar/track_merge.ex:138— octopus/lib/octopus/radar/track_merge.ex:138-140 | octopus/lib/octopus_web/live/radar_live.ex:2279-2281 — 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.
Duplicated block (54–59 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1190— octopus/lib/octopus/apps/supermario/level.ex:1190-1243 | octopus/lib/octopus/apps/supermario/level.ex:2181-2239 — 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 `octopus/lib/octopus/apps/supermario/level.ex:1190` 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 (40–46 lines × 2) octopus/lib/octopus/apps/whackamole/game.ex:387— octopus/lib/octopus/apps/whackamole/game.ex:387-426 | octopus/lib/octopus/apps/whackamole/game.ex:437-482 — 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 `octopus/lib/octopus/apps/whackamole/game.ex:387` 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 (45 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:615— octopus/lib/octopus/apps/supermario/level.ex:615-659 | octopus/lib/octopus/apps/supermario/level.ex:2568-2612 — 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 (39 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:974— octopus/lib/octopus/apps/supermario/level.ex:974-1012 | octopus/lib/octopus/apps/supermario/level.ex:1097-1135 — 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 (38 lines × 18) octopus/lib/octopus/apps/supermario/level.ex:437— octopus/lib/octopus/apps/supermario/level.ex:437-474 | octopus/lib/octopus/apps/supermario/level.ex:559-596 | octopus/lib/octopus/apps/supermario/level.ex:681-718 | octopus/lib/octopus/apps/supermario/level.ex:1425-1462 | octopus/lib/octopus/apps/supermario/level.ex:1548-1585 | octopus/lib/octopus/apps/supermario/level.ex:2414-2451 | octopus/lib/octopus/apps/supermario/level.ex:2537-2574 | octopus/lib/octopus/apps/supermario/level.ex:2660-2697 | octopus/lib/octopus/apps/supermario/level.ex:2783-2820 | octopus/lib/octopus/apps/supermario/level.ex:2906-2943 | octopus/lib/octopus/apps/supermario/level.ex:3029-3066 | octopus/lib/octopus/apps/supermario/level.ex:3403-3440 | octopus/lib/octopus/apps/supermario/level.ex:3526-3563 | octopus/lib/octopus/apps/supermario/level.ex:3649-3686 | octopus/lib/octopus/apps/supermario/level.ex:3772-3809 | octopus/lib/octopus/apps/supermario/level.ex:3895-3932 | octopus/lib/octopus/apps/supermario/level.ex:4018-4055 | octopus/lib/octopus/apps/supermario/level.ex:4141-4178 — all 18 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 `octopus/lib/octopus/apps/supermario/level.ex:437` 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 (38 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1244— octopus/lib/octopus/apps/supermario/level.ex:1244-1281 | octopus/lib/octopus/apps/supermario/level.ex:1282-1319 — 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 (36 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:873— octopus/lib/octopus/apps/supermario/level.ex:873-908 | octopus/lib/octopus/apps/supermario/level.ex:3009-3044 — 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 (35 lines × 4) octopus/lib/octopus/apps/supermario/level.ex:654— octopus/lib/octopus/apps/supermario/level.ex:654-688 | octopus/lib/octopus/apps/supermario/level.ex:2585-2619 | octopus/lib/octopus/apps/supermario/level.ex:2728-2762 | octopus/lib/octopus/apps/supermario/level.ex:3132-3166 — 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 (34 lines × 19) octopus/lib/octopus/apps/supermario/level.ex:447— octopus/lib/octopus/apps/supermario/level.ex:447-480 | octopus/lib/octopus/apps/supermario/level.ex:569-602 | octopus/lib/octopus/apps/supermario/level.ex:691-724 | octopus/lib/octopus/apps/supermario/level.ex:1435-1468 | octopus/lib/octopus/apps/supermario/level.ex:1558-1591 | octopus/lib/octopus/apps/supermario/level.ex:1681-1714 | octopus/lib/octopus/apps/supermario/level.ex:1927-1960 | octopus/lib/octopus/apps/supermario/level.ex:2424-2457 | octopus/lib/octopus/apps/supermario/level.ex:2547-2580 | octopus/lib/octopus/apps/supermario/level.ex:2670-2703 | octopus/lib/octopus/apps/supermario/level.ex:2793-2826 | octopus/lib/octopus/apps/supermario/level.ex:2916-2949 | octopus/lib/octopus/apps/supermario/level.ex:3413-3446 | octopus/lib/octopus/apps/supermario/level.ex:3536-3569 | octopus/lib/octopus/apps/supermario/level.ex:3659-3692 | octopus/lib/octopus/apps/supermario/level.ex:3782-3815 | octopus/lib/octopus/apps/supermario/level.ex:3905-3938 | octopus/lib/octopus/apps/supermario/level.ex:4028-4061 | octopus/lib/octopus/apps/supermario/level.ex:4151-4184 — all 19 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 `octopus/lib/octopus/apps/supermario/level.ex:447` 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 (34 lines × 16) octopus/lib/octopus/apps/supermario/level.ex:455— octopus/lib/octopus/apps/supermario/level.ex:455-488 | octopus/lib/octopus/apps/supermario/level.ex:577-610 | octopus/lib/octopus/apps/supermario/level.ex:699-732 | octopus/lib/octopus/apps/supermario/level.ex:944-977 | octopus/lib/octopus/apps/supermario/level.ex:1443-1476 | octopus/lib/octopus/apps/supermario/level.ex:1566-1599 | octopus/lib/octopus/apps/supermario/level.ex:1689-1722 | octopus/lib/octopus/apps/supermario/level.ex:2432-2465 | octopus/lib/octopus/apps/supermario/level.ex:2555-2588 | octopus/lib/octopus/apps/supermario/level.ex:3421-3454 | octopus/lib/octopus/apps/supermario/level.ex:3544-3577 | octopus/lib/octopus/apps/supermario/level.ex:3667-3700 | octopus/lib/octopus/apps/supermario/level.ex:3790-3823 | octopus/lib/octopus/apps/supermario/level.ex:3913-3946 | octopus/lib/octopus/apps/supermario/level.ex:4036-4069 | octopus/lib/octopus/apps/supermario/level.ex:4159-4192 — all 16 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 `octopus/lib/octopus/apps/supermario/level.ex:455` 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 (33–34 lines × 5) octopus/lib/octopus/apps/supermario/level.ex:984— octopus/lib/octopus/apps/supermario/level.ex:984-1017 | octopus/lib/octopus/apps/supermario/level.ex:1107-1140 | octopus/lib/octopus/apps/supermario/level.ex:1973-2005 | octopus/lib/octopus/apps/supermario/level.ex:2089-2121 | octopus/lib/octopus/apps/supermario/level.ex:2766-2798 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (34 lines × 2) octopus/lib/octopus/apps/collective.ex:638— octopus/lib/octopus/apps/collective.ex:638-671 | octopus/lib/octopus/apps/collective.ex:1220-1253 — 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 lines × 19) octopus/lib/octopus/apps/supermario/level.ex:444— octopus/lib/octopus/apps/supermario/level.ex:444-476 | octopus/lib/octopus/apps/supermario/level.ex:566-598 | octopus/lib/octopus/apps/supermario/level.ex:688-720 | octopus/lib/octopus/apps/supermario/level.ex:1432-1464 | octopus/lib/octopus/apps/supermario/level.ex:1555-1587 | octopus/lib/octopus/apps/supermario/level.ex:1678-1710 | octopus/lib/octopus/apps/supermario/level.ex:2421-2453 | octopus/lib/octopus/apps/supermario/level.ex:2544-2576 | octopus/lib/octopus/apps/supermario/level.ex:2667-2699 | octopus/lib/octopus/apps/supermario/level.ex:2790-2822 | octopus/lib/octopus/apps/supermario/level.ex:2913-2945 | octopus/lib/octopus/apps/supermario/level.ex:3036-3068 | octopus/lib/octopus/apps/supermario/level.ex:3410-3442 | octopus/lib/octopus/apps/supermario/level.ex:3533-3565 | octopus/lib/octopus/apps/supermario/level.ex:3656-3688 | octopus/lib/octopus/apps/supermario/level.ex:3779-3811 | octopus/lib/octopus/apps/supermario/level.ex:3902-3934 | octopus/lib/octopus/apps/supermario/level.ex:4025-4057 | octopus/lib/octopus/apps/supermario/level.ex:4148-4180 — all 19 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 `octopus/lib/octopus/apps/supermario/level.ex:444` 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 (32–33 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:834— octopus/lib/octopus/apps/supermario/level.ex:834-866 | octopus/lib/octopus/apps/supermario/level.ex:869-900 — 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 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1798— octopus/lib/octopus/apps/supermario/level.ex:1798-1830 | octopus/lib/octopus/apps/supermario/level.ex:1921-1953 — 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 `octopus/lib/octopus/apps/supermario/level.ex:1798` 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 (29–33 lines × 2) octopus/lib/octopus/apps/triple_tla.ex:363— octopus/lib/octopus/apps/triple_tla.ex:363-391 | octopus/lib/octopus/apps/triple_tla.ex:427-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `octopus/lib/octopus/apps/triple_tla.ex:427` 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 (32 lines × 20) octopus/lib/octopus/apps/supermario/level.ex:446— octopus/lib/octopus/apps/supermario/level.ex:446-477 | octopus/lib/octopus/apps/supermario/level.ex:568-599 | octopus/lib/octopus/apps/supermario/level.ex:690-721 | octopus/lib/octopus/apps/supermario/level.ex:1434-1465 | octopus/lib/octopus/apps/supermario/level.ex:1557-1588 | octopus/lib/octopus/apps/supermario/level.ex:1680-1711 | octopus/lib/octopus/apps/supermario/level.ex:1926-1957 | octopus/lib/octopus/apps/supermario/level.ex:2423-2454 | octopus/lib/octopus/apps/supermario/level.ex:2546-2577 | octopus/lib/octopus/apps/supermario/level.ex:2669-2700 | octopus/lib/octopus/apps/supermario/level.ex:2792-2823 | octopus/lib/octopus/apps/supermario/level.ex:2915-2946 | octopus/lib/octopus/apps/supermario/level.ex:3038-3069 | octopus/lib/octopus/apps/supermario/level.ex:3412-3443 | octopus/lib/octopus/apps/supermario/level.ex:3535-3566 | octopus/lib/octopus/apps/supermario/level.ex:3658-3689 | octopus/lib/octopus/apps/supermario/level.ex:3781-3812 | octopus/lib/octopus/apps/supermario/level.ex:3904-3935 | octopus/lib/octopus/apps/supermario/level.ex:4027-4058 | octopus/lib/octopus/apps/supermario/level.ex:4150-4181 — all 20 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 `octopus/lib/octopus/apps/supermario/level.ex:446` 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 (32 lines × 19) octopus/lib/octopus/apps/supermario/level.ex:436— octopus/lib/octopus/apps/supermario/level.ex:436-467 | octopus/lib/octopus/apps/supermario/level.ex:558-589 | octopus/lib/octopus/apps/supermario/level.ex:680-711 | octopus/lib/octopus/apps/supermario/level.ex:1424-1455 | octopus/lib/octopus/apps/supermario/level.ex:1547-1578 | octopus/lib/octopus/apps/supermario/level.ex:2413-2444 | octopus/lib/octopus/apps/supermario/level.ex:2536-2567 | octopus/lib/octopus/apps/supermario/level.ex:2659-2690 | octopus/lib/octopus/apps/supermario/level.ex:2782-2813 | octopus/lib/octopus/apps/supermario/level.ex:2905-2936 | octopus/lib/octopus/apps/supermario/level.ex:3028-3059 | octopus/lib/octopus/apps/supermario/level.ex:3151-3182 | octopus/lib/octopus/apps/supermario/level.ex:3402-3433 | octopus/lib/octopus/apps/supermario/level.ex:3525-3556 | octopus/lib/octopus/apps/supermario/level.ex:3648-3679 | octopus/lib/octopus/apps/supermario/level.ex:3771-3802 | octopus/lib/octopus/apps/supermario/level.ex:3894-3925 | octopus/lib/octopus/apps/supermario/level.ex:4017-4048 | octopus/lib/octopus/apps/supermario/level.ex:4140-4171 — all 19 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 `octopus/lib/octopus/apps/supermario/level.ex:436` 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 (32 lines × 4) octopus/lib/octopus/apps/supermario/level.ex:343— octopus/lib/octopus/apps/supermario/level.ex:343-374 | octopus/lib/octopus/apps/supermario/level.ex:1330-1361 | octopus/lib/octopus/apps/supermario/level.ex:2319-2350 | octopus/lib/octopus/apps/supermario/level.ex:3308-3339 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `octopus/lib/octopus/apps/supermario/level.ex:343` 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, `octopus/lib/octopus/apps/supermario/level.ex:339` calls `init_bad_guys` and `octopus/lib/octopus/apps/supermario/level.ex:1327` 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 (31–32 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:848— octopus/lib/octopus/apps/supermario/level.ex:848-879 | octopus/lib/octopus/apps/supermario/level.ex:2753-2783 — 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 (31 lines × 4) octopus/lib/octopus/apps/supermario/level.ex:1583— octopus/lib/octopus/apps/supermario/level.ex:1583-1613 | octopus/lib/octopus/apps/supermario/level.ex:1633-1663 | octopus/lib/octopus/apps/supermario/level.ex:1877-1907 | octopus/lib/octopus/apps/supermario/level.ex:2746-2776 — 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 (31 lines × 3) octopus/lib/octopus/apps/supermario/level.ex:625— octopus/lib/octopus/apps/supermario/level.ex:625-655 | octopus/lib/octopus/apps/supermario/level.ex:1948-1978 | octopus/lib/octopus/apps/supermario/level.ex:2578-2608 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (30–31 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:1741— octopus/lib/octopus/apps/supermario/level.ex:1741-1770 | octopus/lib/octopus/apps/supermario/level.ex:1791-1821 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (30 lines × 17) octopus/lib/octopus/apps/supermario/level.ex:345— octopus/lib/octopus/apps/supermario/level.ex:345-374 | octopus/lib/octopus/apps/supermario/level.ex:467-496 | octopus/lib/octopus/apps/supermario/level.ex:589-618 | octopus/lib/octopus/apps/supermario/level.ex:711-740 | octopus/lib/octopus/apps/supermario/level.ex:1332-1361 | octopus/lib/octopus/apps/supermario/level.ex:1455-1484 | octopus/lib/octopus/apps/supermario/level.ex:1578-1607 | octopus/lib/octopus/apps/supermario/level.ex:2321-2350 | octopus/lib/octopus/apps/supermario/level.ex:2444-2473 | octopus/lib/octopus/apps/supermario/level.ex:3310-3339 | octopus/lib/octopus/apps/supermario/level.ex:3433-3462 | octopus/lib/octopus/apps/supermario/level.ex:3556-3585 | octopus/lib/octopus/apps/supermario/level.ex:3679-3708 | octopus/lib/octopus/apps/supermario/level.ex:3802-3831 | octopus/lib/octopus/apps/supermario/level.ex:3925-3954 | octopus/lib/octopus/apps/supermario/level.ex:4048-4077 | octopus/lib/octopus/apps/supermario/level.ex:4171-4200 — all 17 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 `octopus/lib/octopus/apps/supermario/level.ex:345` 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, `octopus/lib/octopus/apps/supermario/level.ex:339` calls `init_bad_guys` and `octopus/lib/octopus/apps/supermario/level.ex:1327` 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 (30 lines × 15) octopus/lib/octopus/apps/supermario/level.ex:663— octopus/lib/octopus/apps/supermario/level.ex:663-692 | octopus/lib/octopus/apps/supermario/level.ex:882-911 | octopus/lib/octopus/apps/supermario/level.ex:991-1020 | octopus/lib/octopus/apps/supermario/level.ex:1114-1143 | octopus/lib/octopus/apps/supermario/level.ex:1377-1406 | octopus/lib/octopus/apps/supermario/level.ex:1500-1529 | octopus/lib/octopus/apps/supermario/level.ex:1617-1646 | octopus/lib/octopus/apps/supermario/level.ex:1752-1781 | octopus/lib/octopus/apps/supermario/level.ex:2095-2124 | octopus/lib/octopus/apps/supermario/level.ex:2594-2623 | octopus/lib/octopus/apps/supermario/level.ex:2737-2766 | octopus/lib/octopus/apps/supermario/level.ex:2772-2801 | octopus/lib/octopus/apps/supermario/level.ex:2895-2924 | octopus/lib/octopus/apps/supermario/level.ex:3018-3047 | octopus/lib/octopus/apps/supermario/level.ex:3141-3170 — all 15 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 (30 lines × 12) octopus/lib/octopus/apps/supermario/level.ex:609— octopus/lib/octopus/apps/supermario/level.ex:609-638 | octopus/lib/octopus/apps/supermario/level.ex:790-819 | octopus/lib/octopus/apps/supermario/level.ex:884-913 | octopus/lib/octopus/apps/supermario/level.ex:1000-1029 | octopus/lib/octopus/apps/supermario/level.ex:1128-1157 | octopus/lib/octopus/apps/supermario/level.ex:1335-1364 | octopus/lib/octopus/apps/supermario/level.ex:1457-1486 | octopus/lib/octopus/apps/supermario/level.ex:1580-1609 | octopus/lib/octopus/apps/supermario/level.ex:1630-1659 | octopus/lib/octopus/apps/supermario/level.ex:1769-1798 | octopus/lib/octopus/apps/supermario/level.ex:2101-2130 | octopus/lib/octopus/apps/supermario/level.ex:2743-2772 — all 12 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 (30 lines × 9) octopus/lib/octopus/apps/supermario/level.ex:661— octopus/lib/octopus/apps/supermario/level.ex:661-690 | octopus/lib/octopus/apps/supermario/level.ex:880-909 | octopus/lib/octopus/apps/supermario/level.ex:1375-1404 | octopus/lib/octopus/apps/supermario/level.ex:1750-1779 | octopus/lib/octopus/apps/supermario/level.ex:1873-1902 | octopus/lib/octopus/apps/supermario/level.ex:2592-2621 | octopus/lib/octopus/apps/supermario/level.ex:2735-2764 | octopus/lib/octopus/apps/supermario/level.ex:3016-3045 | octopus/lib/octopus/apps/supermario/level.ex:3139-3168 — all 9 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 (22–25 lines × 2) octopus/lib/octopus/apps/supermario/level.ex:177— octopus/lib/octopus/apps/supermario/level.ex:177-198 | octopus/lib/octopus/apps/supermario/level.ex:265-289 — 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 `octopus/lib/octopus/apps/supermario/level.ex:177` 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 (1–25 lines × 4) octopus/lib/octopus_web/components/app_config_component.ex:106— octopus/lib/octopus_web/components/app_config_component.ex:106-130 | octopus/lib/octopus_web/components/global_params_component.ex:133-134 | octopus/lib/octopus_web/components/sim3d_params_component.ex:86-86 | octopus/lib/octopus_web/components/wood_config_component.ex:94-113 — before extracting anything, compare `octopus/lib/octopus_web/components/app_config_component.ex` and `octopus/lib/octopus_web/components/wood_config_component.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 `octopus/lib/octopus_web/components/global_params_component.ex:133` 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 after the matched lines, `octopus/lib/octopus_web/components/app_config_component.ex:132` calls `config` and `octopus/lib/octopus_web/components/wood_config_component.ex:115` 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 (41 lines × 2) octopus/lib/octopus/apps/perlin_noise.ex:266— octopus/lib/octopus/apps/perlin_noise.ex:266-306 | octopus/lib/octopus/perlin_noise.ex:141-181 — before extracting anything, compare `octopus/lib/octopus/apps/perlin_noise.ex` and `octopus/lib/octopus/perlin_noise.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `octopus/lib/octopus/perlin_noise.ex:135` calls `then` and `octopus/lib/octopus/apps/perlin_noise.ex:260` 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 (21 lines × 3) octopus/lib/octopus/apps/supermario/level.ex:186— octopus/lib/octopus/apps/supermario/level.ex:186-206 | octopus/lib/octopus/apps/supermario/level.ex:226-246 | octopus/lib/octopus/apps/supermario/level.ex:312-332 — 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 `octopus/lib/octopus/apps/supermario/level.ex:186` 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 (19 lines × 2) octopus/lib/octopus/apps/ten_letters.ex:56— octopus/lib/octopus/apps/ten_letters.ex:56-74 | octopus/lib/octopus/apps/triple_tla.ex:57-75 — before extracting anything, compare `octopus/lib/octopus/apps/ten_letters.ex` and `octopus/lib/octopus/apps/triple_tla.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 108 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 (17–18 lines × 3) octopus/lib/octopus/apps/supermario/level.ex:176— octopus/lib/octopus/apps/supermario/level.ex:176-192 | octopus/lib/octopus/apps/supermario/level.ex:240-257 | octopus/lib/octopus/apps/supermario/level.ex:271-287 — 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 `octopus/lib/octopus/apps/supermario/level.ex:176` 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 (16–17 lines × 2) octopus/lib/octopus/apps/encounter.ex:56— octopus/lib/octopus/apps/encounter.ex:56-71 | octopus/lib/octopus/apps/encounter.ex:76-92 — 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 `octopus/lib/octopus/apps/encounter.ex:76` 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 (15–17 lines × 2) octopus/lib/octopus/apps/pixel_fun.ex:2877— octopus/lib/octopus/apps/pixel_fun.ex:2877-2891 | octopus/lib/octopus/apps/pixel_fun.ex:2903-2919 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–17 lines × 2) octopus/lib/octopus/apps/senso.ex:72— octopus/lib/octopus/apps/senso.ex:72-84 | octopus/lib/octopus/apps/senso.ex:157-173 — 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 `octopus/lib/octopus/apps/senso.ex:72` 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–16 lines × 2) octopus/lib/octopus/apps/triple_tla.ex:344— octopus/lib/octopus/apps/triple_tla.ex:344-356 | octopus/lib/octopus/apps/triple_tla.ex:403-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) octopus/lib/octopus/sunlight/solar_service.ex:66— octopus/lib/octopus/sunlight/solar_service.ex:66-80 | octopus/lib/octopus/sunlight/solar_service.ex:105-119 — 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 `octopus/lib/octopus/sunlight/solar_service.ex:66` 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–14 lines × 2) octopus/lib/octopus/apps/pixie_debug.ex:535— octopus/lib/octopus/apps/pixie_debug.ex:535-548 | octopus/lib/octopus/apps/wood.ex:141-153 — 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 `octopus/lib/octopus/apps/wood.ex:141` 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) octopus/lib/octopus/apps/collective/animations/breath.ex:398— octopus/lib/octopus/apps/collective/animations/breath.ex:398-409 | octopus/lib/octopus/apps/collective/animations/dots.ex:329-340 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:157-168 — before extracting anything, compare `octopus/lib/octopus/apps/collective/animations/dots.ex` and `octopus/lib/octopus/apps/collective/animations/presence_panels.ex` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (8–11 lines × 2) octopus/lib/octopus/apps/collective/animations/fireflies.ex:109— octopus/lib/octopus/apps/collective/animations/fireflies.ex:109-119 | octopus/lib/octopus/apps/collective/animations/lava_lamp.ex:113-120 — 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 (8–9 lines × 2) octopus/lib/octopus/apps/whackamole.ex:140— octopus/lib/octopus/apps/whackamole.ex:140-147 | octopus/lib/octopus/apps/whackamole/game.ex:64-72 — 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 `octopus/lib/octopus/apps/whackamole.ex:140` 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 × 4) octopus/lib/octopus/apps/collective/animations/breath.ex:294— octopus/lib/octopus/apps/collective/animations/breath.ex:294-302 | octopus/lib/octopus/apps/collective/animations/dots.ex:191-199 | octopus/lib/octopus/apps/collective/animations/ring_noise.ex:177-185 | octopus/lib/octopus/apps/collective/animations/storm.ex:431-439 — before extracting anything, compare `octopus/lib/octopus/apps/collective/animations/dots.ex` and `octopus/lib/octopus/apps/collective/animations/storm.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 × 3) octopus/lib/octopus/apps/collective/animations/dots.ex:171— octopus/lib/octopus/apps/collective/animations/dots.ex:171-178 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:104-111 | octopus/lib/octopus/apps/collective/animations/storm.ex:411-418 — before extracting anything, compare `octopus/lib/octopus/apps/collective/animations/dots.ex` and `octopus/lib/octopus/apps/collective/animations/presence_panels.ex` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (7 lines × 4) octopus/lib/octopus/mixer.ex:577— octopus/lib/octopus/mixer.ex:577-584 | octopus/lib/octopus/mixer.ex:606-613 | octopus/lib/octopus/mixer.ex:651-657 | octopus/lib/octopus/mixer.ex:711-717 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `octopus/lib/octopus/mixer.ex:649` calls `to_grayscale` and `octopus/lib/octopus/mixer.ex:574` 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–8 lines × 2) octopus/lib/octopus/apps/ocean.ex:475— octopus/lib/octopus/apps/ocean.ex:475-481 | octopus/lib/octopus/apps/ocean.ex:492-499 — 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 `octopus/lib/octopus/apps/ocean.ex:492` 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 (8 lines × 4) octopus/lib/octopus/apps/collective/animations/dots.ex:196— octopus/lib/octopus/apps/collective/animations/dots.ex:196-203 | octopus/lib/octopus/apps/collective/animations/presence_panels.ex:128-135 | octopus/lib/octopus/apps/collective/animations/ring_noise.ex:182-189 | octopus/lib/octopus/apps/collective/animations/storm.ex:436-443 — before extracting anything, compare `octopus/lib/octopus/apps/collective/animations/dots.ex` and `octopus/lib/octopus/apps/collective/animations/presence_panels.ex` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (4–6 lines × 4) octopus/lib/octopus_web/components/app_config_component.ex:99— octopus/lib/octopus_web/components/app_config_component.ex:99-104 | octopus/lib/octopus_web/components/global_params_component.ex:129-132 | octopus/lib/octopus_web/components/sim3d_params_component.ex:80-85 | octopus/lib/octopus_web/components/wood_config_component.ex:87-92 — before extracting anything, compare `octopus/lib/octopus_web/components/app_config_component.ex` and `octopus/lib/octopus_web/components/wood_config_component.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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, `octopus/lib/octopus_web/components/app_config_component.ex:95` calls `handle_config_change` and `octopus/lib/octopus_web/components/wood_config_component.ex:86` 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 (11 lines × 5) octopus/lib/octopus/layout/mildenberg.ex:22— octopus/lib/octopus/layout/mildenberg.ex:22-32 | octopus/lib/octopus/layout/mildenberg_narrow.ex:22-32 | octopus/lib/octopus/layout/mildenberg_zoom1.ex:21-31 | octopus/lib/octopus/layout/mildenberg_zoom2.ex:21-31 | octopus/lib/octopus/layout/nation.ex:22-32 — 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 5 call sites, so a change lands once.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplicated block (13 lines × 3 locations) octopus/assets/js/app.js:26— octopus/assets/js/app.js:26 · octopus/assets/js/app_sim3d.js:8 · octopus/assets/js/app_sim3daframe.js:8 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (11 lines × 3 locations) octopus/assets/js/hooks/pixels3d.ts:475— octopus/assets/js/hooks/pixels3d.ts:475 · octopus/assets/js/hooks/pixels3d.ts:496 · octopus/assets/js/hooks/pixels3d.ts:513 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) octopus/assets/js/hooks/nation.ts:60— octopus/assets/js/hooks/nation.ts:60 · octopus/assets/js/hooks/pixels.ts:60 — 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 (7 lines × 3 locations) octopus/assets/js/hooks/pixels3daframe.ts:445— octopus/assets/js/hooks/pixels3daframe.ts:445 · octopus/assets/js/hooks/pixels3daframe.ts:1259 · octopus/assets/js/hooks/pixels3daframe.ts:1267 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3 locations) octopus/assets/js/hooks/pixels3daframe.ts:1261— octopus/assets/js/hooks/pixels3daframe.ts:1261 · octopus/assets/js/hooks/pixels3daframe.ts:1269 · octopus/assets/js/hooks/pixels3daframe.ts:1332 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 2 locations) octopus/assets/js/hooks/pixels3daframe.ts:1486— octopus/assets/js/hooks/pixels3daframe.ts:1486 · octopus/assets/js/hooks/pixels3daframe.ts:1492 — 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.
Complex function handleParams (cyclomatic 14, cognitive 13) octopus/assets/js/hooks/pixels3daframe.ts:1522— handleParams has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function applyInstallationState (cyclomatic 12, cognitive 13) octopus/assets/js/hooks/pixels3daframe.ts:1571— applyInstallationState has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· octopus/assets/js/hooks/pixels3daframe.ts · ×1
octopus/assets/js/hooks/pixels3daframe.ts: 1659 lines of code octopus/assets/js/hooks/pixels3daframe.ts:1— octopus/assets/js/hooks/pixels3daframe.ts has 1659 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· octopus/assets/js/hooks/pixels3d.ts · ×1
octopus/assets/js/hooks/pixels3d.ts: 648 lines of code octopus/assets/js/hooks/pixels3d.ts:1— octopus/assets/js/hooks/pixels3d.ts has 648 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· octopus/assets/js/hooks/nation.ts · ×1
octopus/assets/js/hooks/nation.ts: 445 lines of code octopus/assets/js/hooks/nation.ts:1— octopus/assets/js/hooks/nation.ts has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· octopus/assets/js/hooks/pixels.ts · ×1
octopus/assets/js/hooks/pixels.ts: 410 lines of code octopus/assets/js/hooks/pixels.ts:1— octopus/assets/js/hooks/pixels.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· No test, lint or typecheck script · ×1
No test, lint or typecheck script — test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Orphaned file octopus/lib/octopus_web/components/core_components.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 octopus/lib/octopus/apps/blocks/game.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 joystick/lib/joystick/protobuf/schema.pb.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 octopus/lib/octopus/apps/space_invaders.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 octopus/lib/octopus/perlin_noise.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 octopus/lib/octopus/apps/encounter.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 octopus/lib/octopus/particles.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 octopus/assets/js/hooks/proximity_chart.ts: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 octopus/lib/octopus/events/event/proximity/generator.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 octopus/lib/octopus/apps/snake/game.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 octopus/lib/octopus/transitions.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 octopus/lib/octopus/apps/calibrator.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 octopus/lib/octopus/apps/text.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 octopus/lib/octopus/params.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 octopus/lib/octopus_web/live/proximity_live.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 octopus/lib/octopus/apps/starfield.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 octopus/lib/octopus/font.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 octopus/lib/octopus_web/live/playlist_live.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 octopus/lib/octopus/apps/diamonds.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 calibration/convert.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 octopus/lib/octopus/events/event/proximity/processor.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 octopus/lib/octopus/osc/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 joystick/lib/joystick/monitor.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 octopus/native/octopus_webp/src/lib.rs: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 octopus/lib/octopus_web/telemetry.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.
Silent fallback default on error octopus/lib/octopus/broadcaster.ex:413— `resolve_via_mdns` 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 octopus/lib/octopus/installation.ex:1017— `ring_layout_m` 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 octopus/lib/octopus/kiosk_mode_manager.ex:63— `init` matches `_` and answers `:noop` — 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 octopus/lib/octopus/radar.ex:792— `firmware_version` 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 octopus/lib/octopus/radar.ex:1527— `default_sensitivity_level` matches `_` and answers `6` — 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 octopus/lib/octopus/radar/deployment.ex:291— `resolve_usb_path` 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 octopus/lib/octopus/radar/deployment.ex:360— `log_discovered_adapter` 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 octopus/lib/octopus/radar/read_response.ex:106— `find_block` matches `:nomatch` and answers `:pending` — 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 octopus/lib/octopus/radar/read_response.ex:136— `check_int` 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 octopus/lib/octopus/radar/read_response.ex:148— `check_decisecs` 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 octopus/lib/octopus/radar/sensitivity.ex:26— `initial_level` matches `_` and answers `6` — 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 octopus/lib/octopus/events/router.ex:91— `handle_cast` matches `_` and answers `:noop` — 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 octopus/lib/octopus/apps/pixel_fun.ex:1090— `update_program` 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 joystick/lib/joystick/udp.ex:61— `handle_info` matches `_` and answers `:noop` — 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 in rescue octopus/lib/octopus_web/components/app_config_component.ex:184— `schema_key` rescues `ArgumentError` and answers `[]` — 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 octopus/lib/octopus_web/components/installation_console_component.ex:1253— `now_playing_schema_key` rescues `ArgumentError` and answers `[]` — 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 octopus/lib/octopus_web/components/pixel_fun_config_component.ex:377— `schema_key` rescues `ArgumentError` and answers `[]` — 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 octopus/lib/octopus_web/components/wood_config_component.ex:308— `schema_key` rescues `ArgumentError` and answers `[]` — 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 octopus/lib/octopus/app_supervisor.ex:44— `available_apps` rescues `_` and answers `false` — 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 octopus/lib/octopus/installation_transport.ex:1274— `load_queue` rescues `_` and answers `[]` — 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 octopus/lib/octopus/radar/panel_activity.ex:172— `mock_world_people` rescues `_` and answers `[]` — 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 octopus/lib/octopus/apps/collective.ex:1362— `mock_world_people` rescues `_` and answers `[]` — 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 octopus/lib/octopus/apps/pixel_fun.ex:1530— `installation_width_for_migration` rescues `_` and answers `312` — 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 octopus/lib/octopus/apps/pixel_fun.ex:1695— `coerce_gradient_palette` rescues `ArgumentError` and answers `:rainbow` — 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 octopus/lib/octopus/apps/pixel_fun/program.ex:18— `eval` rescues `_` and answers `0.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.
Duplicated predicate octopus/lib/octopus/apps/gravity_mask.ex:35— `apply(@mode_presets, :config_for, [__MODULE__, mode_id]) || default_config()` appears character-identically in 2 files — octopus/lib/octopus/apps/gravity_mask.ex, octopus/lib/octopus/apps/shape_shifter.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 octopus/lib/octopus/apps/blocks.ex:23— `installation_info.num_joysticks >= 1 and installation_info.panel_width == 8 and installation_info.panel_height == 8` appears character-identically in 3 files — octopus/lib/octopus/apps/blocks.ex, octopus/lib/octopus/apps/snake.ex, octopus/lib/octopus/apps/space_invaders.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 octopus/lib/octopus/apps/rain.ex:16— `installation_info.panel_width >= 8 and installation_info.panel_height >= 8` appears character-identically in 4 files — octopus/lib/octopus/apps/rain.ex, REDACTED, octopus/lib/octopus/apps/sprites_grouped.ex, octopus/lib/octopus/apps/twighlight_zone.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 octopus/lib/octopus/radar.ex:1102— `is_integer(device_id) and device_id > 0 and is_number(deg)` appears character-identically in 2 files — octopus/lib/octopus/radar.ex, octopus/lib/octopus/radar/pose_tweak.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 octopus/lib/octopus/radar.ex:149— `is_integer(device_id) and device_id >= 1` appears character-identically in 2 files — octopus/lib/octopus/radar.ex, octopus/lib/octopus/radar/log_format.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 octopus/lib/octopus/apps/gravity_mask.ex:225— `last_debug_ms == 0 or now - last_debug_ms >= @debug_log_interval_ms` appears character-identically in 2 files — octopus/lib/octopus/apps/gravity_mask.ex, octopus/lib/octopus/radar/panel_gravity.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 49 significant file(s) lose their only recent owner: octopus/lib/octopus_web/live/radar_live.ex, octopus/lib/octopus/radar.ex, octopus/lib/octopus/radar/sensor.ex, octopus/lib/octopus/apps/slot_machine.ex, octopus/lib/octopus_web/live/radar_debug_live.ex, octopus/lib/octopus/apps/world_cup_final.ex, octopus/assets/js/hooks/nation.ts, octopus/lib/octopus/apps/fire.ex (+41 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 23 significant file(s) lose their only recent owner: octopus/lib/octopus_web/components/console_components.ex, octopus/assets/js/hooks/pixels3daframe.ts, octopus/lib/octopus/apps/wood.ex, octopus/lib/octopus/apps/collective/animations/storm.ex, octopus/lib/octopus/apps/collective/animations/breath.ex, octopus/lib/octopus_web/components/pixel_fun_config_component.ex, octopus/lib/octopus_web/components/app_config_component.ex, octopus/lib/octopus/apps/collective/animations/dots.ex (+15 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (73 single-owned of 187 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; 187 of the 299 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: octopus/lib/octopus/apps/supermario/game.ex.
No ADRs found octopus/mix.exs:16— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `octopus/mix.exs` makes this repository a deployable product (line 16).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion octopus/mix.exs:1— `octopus` (60783 LoC, 353 module-visible types across 41 directories) overshoots its size bounds. 1 of 4 build unit(s) (Cargo, Mix, npm) overshoot their size bounds, lowering Project Cohesion to 5.0/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.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 31 of 187 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 187 of the 299 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: octopus/lib/octopus_web/components/core_components.ex, octopus/lib/octopus/apps/blocks/game.ex, joystick/lib/joystick/protobuf/schema.pb.ex, octopus/lib/octopus/apps/space_invaders.ex, octopus/lib/octopus/perlin_noise.ex, octopus/lib/octopus/apps/encounter.ex, octopus/lib/octopus/particles.ex, octopus/assets/js/hooks/proximity_chart.ts (and 23 more). 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST — No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation octopus/assets/package.json:2— `octopus/assets/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code· Write-only private field 'mockObjects' · ×1
Write-only private field 'mockObjects' octopus/assets/js/hooks/humanWorld.ts:103— This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
No security response headers detected octopus/deploy/redlady/Caddyfile:3— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `Caddyfile` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
No app-layer HTTPS enforcement detected — This repository runs an HTTP server and nothing in its Elixir source or production configuration secures the transport: no HTTPS served (an endpoint's `https: [...]`, `scheme: :https`, `Plug.Cowboy.https`, SiteEncrypt), no `force_ssl:` or `plug Plug.SSL` redirecting to HTTPS and sending HSTS, no `strict-transport-security` header, no `rewrite_on: [:x_forwarded_proto]` or `x-forwarded-proto` read for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: octopus/lib/octopus_web/endpoint.ex:2 — `Phoenix.Endpoint`.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~1.8 `!` null assertions per 1k TypeScript source lines — 8 assertion(s) across the 4335 source line(s) of the 8 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: octopus/assets/js/hooks/pixels3daframe.ts (7), octopus/assets/js/hooks/nation.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated: bandit — `:bandit` is locked at 1.12.5 but 1.14.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.10"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update bandit` and commit the updated REDACTED.
Outdated: circuits_uart — `:circuits_uart` is locked at 1.6.0 but 1.7.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.5"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update circuits_uart` and commit the updated REDACTED.
Outdated: ecto_sqlite3 — `:ecto_sqlite3` is locked at 0.25.0 but 0.26.0 is the current stable release on hex.pm, and it already satisfies the `">= 0.22.0"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ecto_sqlite3` and commit the updated REDACTED.
Outdated: esbuild — `:esbuild` is locked at 0.10.0 but 0.10.1 is the current stable release on hex.pm, and it already satisfies the `"~> 0.10"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update esbuild` and commit the updated REDACTED.
Outdated: finch — `:finch` is locked at 0.23.0 but 0.24.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.21"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update finch` and commit the updated REDACTED.
Outdated: igniter — `:igniter` is locked at 0.8.4 but 0.8.5 is the current stable release on hex.pm, and it already satisfies the `"~> 0.7"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update igniter` and commit the updated REDACTED.
Outdated: lazy_html — `:lazy_html` is locked at 0.1.13 but 0.1.14 is the current stable release on hex.pm, and it already satisfies the `">= 0.1.0"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update lazy_html` and commit the updated REDACTED.
Outdated: mdns_lite — `:mdns_lite` is locked at 0.9.2 but 0.9.3 is the current stable release on hex.pm, and it already satisfies the `"~> 0.9.1"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update mdns_lite` and commit the updated REDACTED.
Outdated: nerves — `:nerves` is locked at 1.11.3 but 1.15.1 is the current stable release on hex.pm, and it already satisfies the `"~> 1.10"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves` and commit the updated REDACTED.
Outdated: nerves_pack — `:nerves_pack` is locked at 0.7.1 but 0.7.2 is the current stable release on hex.pm, and it already satisfies the `"~> 0.7"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves_pack` and commit the updated REDACTED.
Outdated: nerves_runtime — `:nerves_runtime` is locked at 0.13.8 but 0.13.13 is the current stable release on hex.pm, and it already satisfies the `"~> 0.13"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves_runtime` and commit the updated REDACTED.
Outdated: nerves_system_bbb — `:nerves_system_bbb` is locked at 2.27.1 but 2.31.2 is the current stable release on hex.pm, and it already satisfies the `"~> 2.14"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves_system_bbb` and commit the updated REDACTED.
Outdated: nerves_system_grisp2 — `:nerves_system_grisp2` is locked at 0.15.1 but 0.18.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.3"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves_system_grisp2` and commit the updated REDACTED.
Outdated: nerves_system_osd32mp1 — `:nerves_system_osd32mp1` is locked at 0.22.1 but 0.25.0 is the current stable release on hex.pm, and it already satisfies the `"~> 0.10"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves_system_osd32mp1` and commit the updated REDACTED.
Outdated: nerves_system_x86_64 — `:nerves_system_x86_64` is locked at 1.31.1 but 1.35.2 is the current stable release on hex.pm, and it already satisfies the `"~> 1.19"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nerves_system_x86_64` and commit the updated REDACTED.
Outdated: nimble_options — `:nimble_options` is locked at 1.1.1 but 1.2.0 is the current stable release on hex.pm, and it already satisfies the `"~> 1.0"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update nimble_options` and commit the updated REDACTED.
Outdated: phoenix — `:phoenix` is locked at 1.8.15 but 1.8.16 is the current stable release on hex.pm, and it already satisfies the `"~> 1.8.0"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update phoenix` and commit the updated REDACTED.
Outdated: phoenix_html — `:phoenix_html` is locked at 4.3.0 but 4.4.0 is the current stable release on hex.pm, and it already satisfies the `"~> 4.3"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update phoenix_html` and commit the updated REDACTED.
Outdated: phoenix_live_view — `:phoenix_live_view` is locked at 1.2.12 but 1.2.13 is the current stable release on hex.pm, and it already satisfies the `"~> 1.1"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update phoenix_live_view` and commit the updated REDACTED.
Outdated: protobuf — `:protobuf` is locked at 0.17.0 but 0.17.1 is the current stable release on hex.pm, and it already satisfies the `"~> 0.15"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update protobuf` and commit the updated REDACTED.
Outdated: req — `:req` is locked at 0.7.4 but 0.7.5 is the current stable release on hex.pm, and it already satisfies the `"~> 0.5"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update req` and commit the updated REDACTED.
Outdated: ring_logger — `:ring_logger` is locked at 0.11.3 but 0.11.7 is the current stable release on hex.pm, and it already satisfies the `"~> 0.9"` requirement declared in joystick/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update ring_logger` and commit the updated REDACTED.
Outdated: swoosh — `:swoosh` is locked at 1.28.1 but 1.29.3 is the current stable release on hex.pm, and it already satisfies the `"~> 1.25"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update swoosh` and commit the updated REDACTED.
Outdated: tailwind — `:tailwind` is locked at 0.5.1 but 0.5.2 is the current stable release on hex.pm, and it already satisfies the `"~> 0.4"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update tailwind` and commit the updated REDACTED.
Outdated: tidewave — `:tidewave` is locked at 0.9.1 but 0.9.2 is the current stable release on hex.pm, and it already satisfies the `"~> 0.5"` requirement declared in octopus/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update tidewave` and commit the updated REDACTED.
+ 3 more in this group — see findings.md.
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.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e5dd-6a56-73fe-be93-7cf4993f00fd · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 40 · Warnings: 330 · Recommendations: 80 · Info: 28 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 19:37 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.