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

nsaintot/cdj3k-emu

Measured 16 November 2026, 17:22 UTC, at code version 9a1471a

First survey, so nothing to compare with yet
CAI score 62.7out of 100 Adequate
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: 70,926 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Production Readiness, 52.0

Findings by how serious they are

64 critical 295 serious 25 minor

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

This survey was produced by

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

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

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

52of 52 dimensions measured by tools.
362of 384 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
52dimensions across 6 lenses, read from 70,926 lines of product code in 10 projects.
Chapters

Executive summary

nsaintot/cdj3k-emu falls short of our standard for a preview release because we found no logging, tracing or health checks in the code. It scores 62.7 out of 100 and is rated Adequate, and all 64 of its critical findings are security problems.

Production Readiness, at 52.0, is the weakest lens and counts most in the score. The best first step is adopting a logging library, worth about 7.8 points. Recording design decisions comes next, worth about 3.0 points. Raising Production Readiness to 62 would lift the score to about 67.4.

Fifty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight settings leave the servers or containers unsafe, and three weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, correcting the unsafe settings and fixing the weaknesses the scanner points to would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first.

The product code is 70,926 lines, about €82,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 52.0 · counts for 46%Security and Compliance 66.9 · counts for 25%Maturity 67.1 · counts for 14%Code Health 77.4 · counts for 8%Architecture 93.5 · counts for 4%Event Sourcing 100.0 · counts for 2%

If Production Readiness rose from 52.0 to 62, the lowest score rated Strong, the score would rise from 62.7 to about 67.4.

Code composition: what the lines of code are
Product code 97%Tests 3%
Rebuild cost: about €82,000 · Estimate
Cost to rebuild€27,000 to €140,000, for 454 to 1,441 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 70,926 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run.
Raises the score by about 7.8 points · Medium effort · Observability
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Raises the score by about 3.0 points · Low effort · ADR Quality
3
Enable Dependabot/Renovate or a dependency-review gate.
Raises the score by about 4.6 points · Medium effort · Security & performance tooling

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 €82,000 to build again, about 0.6 person-years of work. Its weakest lens is Production Readiness, at 52.0 (Adequate). 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
Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run. Of all the actions in this report, it raises the score most for the work it takes: about 7.8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch cdj3k-emu cdj3k-emu cdj3k-emu-control cdj3k-emu-control cdj3k-emu->cdj3k-emu-control cdj3k-emu-panel cdj3k-emu-panel cdj3k-emu->cdj3k-emu-panel cdj3k-emu-platform cdj3k-emu-platform cdj3k-emu->cdj3k-emu-platform cdj3k-emu-runtime cdj3k-emu-runtime cdj3k-emu->cdj3k-emu-runtime cdj3k-emu-storage cdj3k-emu-storage cdj3k-emu->cdj3k-emu-storage cdj3k-emu-ui cdj3k-emu-ui cdj3k-emu->cdj3k-emu-ui cdj3k-emu-firmware cdj3k-emu-firmware cdj3k-emu-platform->cdj3k-emu-panel cdj3k-emu-runtime->cdj3k-emu-firmware cdj3k-emu-runtime->cdj3k-emu-panel cdj3k-emu-runtime->cdj3k-emu-platform cdj3k-emu-storage->cdj3k-emu-firmware cdj3k-emu-storage->cdj3k-emu-panel cdj3k-emu-storage->cdj3k-emu-platform cdj3k-emu-streams cdj3k-emu-streams cdj3k-emu-streams->cdj3k-emu-panel cdj3k-emu-streams->cdj3k-emu-platform cdj3k-emu-ui->cdj3k-emu-control cdj3k-emu-ui->cdj3k-emu-firmware cdj3k-emu-ui->cdj3k-emu-panel cdj3k-emu-ui->cdj3k-emu-platform cdj3k-emu-ui->cdj3k-emu-runtime cdj3k-emu-ui->cdj3k-emu-storage cdj3k-emu-ui->cdj3k-emu-streams cdj3k-emu-update cdj3k-emu-update cdj3k-emu-ui->cdj3k-emu-update cdj3k-emu-update->cdj3k-emu-platform cdj3k-emu-update->cdj3k-emu-storage

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.

325 modules, with 527 dependencies between them. 7 loops run through 17 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 cdj3k_emu_panel.lamp2 cdj3k_emu_panel.miso_frame3 cdj3k_emu_platform.audio4 cdj3k_emu_platform.desktop.aspect_fit5 cdj3k_emu_platform.desktop.frame_store6 cdj3k_emu_platform.menu.id7 cdj3k_emu_platform.net8 cdj3k_emu_platform.window_socket9 cdj3k_emu_runtime.cfg10 cdj3k_emu_runtime.net.linux_net11 cdj3k_emu_ui.app.theme12 cdj3k_emu_update.index13 cdj3k_emu_panel.mosi_frame14 cdj3k_emu_platform.menu.model15 cdj3k_emu_ui.app.picker.glyph16 cdj3k_emu_ui.app.ui.draw_cache17 cdj3k_emu_update18 cdj3k_emu_panel.model19 cdj3k_emu_platform.menu.muda_provider20 cdj3k_emu_ui.app.ui.draw_primitives21 cdj3k_emu_platform.desktop22 cdj3k_emu_platform.menu_state23 cdj3k_emu_runtime.config24 cdj3k_emu_storage.mods.boot25 cdj3k_emu_ui.app.firmware_wizard.provision26 cdj3k_emu_ui.app.ui27 cdj3k_emu_platform.menu.service28 cdj3k_emu_runtime.disk29 cdj3k_emu_ui.app.mods_view30 cdj3k_emu_ui.app.ui.tilt31 cdj3k_emu.runtime_worker32 cdj3k_emu_ui.app.mods_view.log_page33 cdj3k_emu_ui.app.picker34 cdj3k_emu_ui.app.ui.tilt.raised35 cdj3k_emu_ui.app36 cdj3k_emu_ui.app.shell.control.watch37 cdj3k_emu_ui.app.shell.control38 cdj3k_emu_ui.app.ui.slate.cdj1500x.draw_front39 cdj3k_emu_ui.app.shell40 cdj3k_emu.launch
1 cdj3k_emu_panel.lamp
2 cdj3k_emu_panel.miso_frame
3 cdj3k_emu_platform.audio
4 cdj3k_emu_platform.desktop.aspect_fit
5 cdj3k_emu_platform.desktop.frame_store
6 cdj3k_emu_platform.menu.id
7 cdj3k_emu_platform.net
8 cdj3k_emu_platform.window_socket
9 cdj3k_emu_runtime.cfg
10 cdj3k_emu_runtime.net.linux_net
11 cdj3k_emu_ui.app.theme
12 cdj3k_emu_update.index
13 cdj3k_emu_panel.mosi_frame2
14 cdj3k_emu_platform.menu.model1
15 cdj3k_emu_ui.app.picker.glyph21
16 cdj3k_emu_ui.app.ui.draw_cache241
17 cdj3k_emu_update4
18 cdj3k_emu_panel.model11
19 cdj3k_emu_platform.menu.muda_provider25
20 cdj3k_emu_ui.app.ui.draw_primitives11
21 cdj3k_emu_platform.desktop11
22 cdj3k_emu_platform.menu_state211
23 cdj3k_emu_runtime.config1
24 cdj3k_emu_storage.mods.boot1
25 cdj3k_emu_ui.app.firmware_wizard.provision2
26 cdj3k_emu_ui.app.ui11
27 cdj3k_emu_platform.menu.service1141
28 cdj3k_emu_runtime.disk11
29 cdj3k_emu_ui.app.mods_view111
30 cdj3k_emu_ui.app.ui.tilt12
31 cdj3k_emu.runtime_worker112132
32 cdj3k_emu_ui.app.mods_view.log_page113
33 cdj3k_emu_ui.app.picker1111
34 cdj3k_emu_ui.app.ui.tilt.raised11
35 cdj3k_emu_ui.app111112141111
36 cdj3k_emu_ui.app.shell.control.watch211
37 cdj3k_emu_ui.app.shell.control1111
38 cdj3k_emu_ui.app.ui.slate.cdj1500x.draw_front122251
39 cdj3k_emu_ui.app.shell1432121212
40 cdj3k_emu.launch32212
Uses a module listed above itPart of a loopThe module itself
1 cdj3k_emu_panel.lamp2 cdj3k_emu_panel.miso_frame3 cdj3k_emu_platform.audio4 cdj3k_emu_platform.desktop.aspect_fit5 cdj3k_emu_platform.desktop.frame_store6 cdj3k_emu_platform.menu.id7 cdj3k_emu_platform.net8 cdj3k_emu_platform.window_socket9 cdj3k_emu_runtime.cfg10 cdj3k_emu_runtime.net.linux_net11 cdj3k_emu_ui.app.theme12 cdj3k_emu_update.index13 cdj3k_emu_panel.mosi_frame14 cdj3k_emu_platform.menu.model15 cdj3k_emu_ui.app.picker.glyph16 cdj3k_emu_ui.app.ui.draw_cache17 cdj3k_emu_update18 cdj3k_emu_panel.model19 cdj3k_emu_platform.menu.muda_provider20 cdj3k_emu_ui.app.ui.draw_primitives21 cdj3k_emu_platform.desktop22 cdj3k_emu_platform.menu_state23 cdj3k_emu_runtime.config24 cdj3k_emu_storage.mods.boot25 cdj3k_emu_ui.app.firmware_wizard.provision26 cdj3k_emu_ui.app.ui27 cdj3k_emu_platform.menu.service28 cdj3k_emu_runtime.disk29 cdj3k_emu_ui.app.mods_view30 cdj3k_emu_ui.app.ui.tilt31 cdj3k_emu.runtime_worker32 cdj3k_emu_ui.app.mods_view.log_page33 cdj3k_emu_ui.app.picker34 cdj3k_emu_ui.app.ui.tilt.raised35 cdj3k_emu_ui.app36 cdj3k_emu_ui.app.shell.control.watch37 cdj3k_emu_ui.app.shell.control38 cdj3k_emu_ui.app.ui.slate.cdj1500x.draw_front39 cdj3k_emu_ui.app.shell40 cdj3k_emu.launchcdj3k_emu_panel.lamp1cdj3k_emu_panel.miso_frame2cdj3k_emu_platform.audio3cdj3k_emu_platform.desktop.aspect_fit4cdj3k_emu_platform.desktop.frame_store5cdj3k_emu_platform.menu.id6cdj3k_emu_platform.net7cdj3k_emu_platform.window_socket8cdj3k_emu_runtime.cfg9cdj3k_emu_runtime.net.linux_net10cdj3k_emu_ui.app.theme11cdj3k_emu_update.index12cdj3k_emu_panel.mosi_frame13cdj3k_emu_platform.menu.model14cdj3k_emu_ui.app.picker.glyph15cdj3k_emu_ui.app.ui.draw_cache16cdj3k_emu_update17cdj3k_emu_panel.model18cdj3k_emu_platform.menu.muda_provider19cdj3k_emu_ui.app.ui.draw_primitives20cdj3k_emu_platform.desktop21cdj3k_emu_platform.menu_state22cdj3k_emu_runtime.config23cdj3k_emu_storage.mods.boot24cdj3k_emu_ui.app.firmware_wizard.provision25cdj3k_emu_ui.app.ui26cdj3k_emu_platform.menu.service27cdj3k_emu_runtime.disk28cdj3k_emu_ui.app.mods_view29cdj3k_emu_ui.app.ui.tilt30cdj3k_emu.runtime_worker31cdj3k_emu_ui.app.mods_view.log_page32cdj3k_emu_ui.app.picker33cdj3k_emu_ui.app.ui.tilt.raised34cdj3k_emu_ui.app35cdj3k_emu_ui.app.shell.control.watch36cdj3k_emu_ui.app.shell.control37cdj3k_emu_ui.app.ui.slate.cdj1500x.draw_front38cdj3k_emu_ui.app.shell39cdj3k_emu.launch40212124141125111121111211114111111121121321131111111111121411112111111122251143212121232212+285 more modules (most-connected shown)

At a glance — Code Health · 77.4 · Strong ·

At a glance — Architecture · 93.5 · Exemplary ·

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

At a glance — Readiness · 52.0 · Adequate · gated by P2 ·

At a glance — Security · 66.9 · Adequate · gated by D29, D31, D36 ·

At a glance — Event Sourcing · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection56High / Critical
A02:2025 — Security Misconfiguration25High / Critical
A03:2025 — Software Supply Chain Failures24Medium

Roadmap

Top priorities: Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run; Enable Dependabot/Renovate or a dependency-review gate; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.

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

Do thisHelpsEffortDimension
Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run.+7.8 ptsMediumObservability
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.+3.0 ptsLowADR Quality
Enable Dependabot/Renovate or a dependency-review gate.+4.6 ptsMediumSecurity & performance tooling
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.+2.5 ptsMediumArchitecture documentation
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.+1.3 ptsMediumIncompleteness & stubs
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `crates/cdj3k-emu-firmware/src/extract.rs:67` (`md5::compute`), `crates/cdj3k-emu-firmware/src/luks/crypto.rs:137` (`Sha1::new`), `crates/cdj3k-emu-firmware/src/luks/crypto.rs:143` (`Sha1::new`). Each is a separate decision — fixing only the line this row cites leaves the others in place.+1.2 ptsMediumWeb-Security Posture
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.+1.0 ptsMediumRelease Hygiene
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.+0.9 ptsMediumDocumentation (README)

File quality

Per-file score 0–10 — a quality signature. Of 85 files carrying findings, judged against the Preview bar: 6% slop · 6% mixed · 88% near-clean.

FileScoreBandWorst signal
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedDependency Vulnerabilities: Medium advisory (unsound): REDACTED
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs7.0Near-cleanCode Duplication: Edited copy of a member (53 corresponding lines)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs7.0Near-cleanCode Duplication: Edited copy of a member (43 corresponding lines)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs7.0Near-cleanCode Duplication: Edited copy of a member (23 corresponding lines)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs7.0Near-cleanCode Duplication: Edited copy of a member (61 corresponding lines)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs7.0Near-cleanCode Duplication: Edited copy of a member (29 corresponding lines)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs7.0Near-cleanCode Duplication: Edited copy of a member (72 corresponding lines)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs7.0Near-cleanCode Duplication: Duplicated block (73 lines × 2)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs7.0Near-cleanCode Duplication: Duplicated block (58 lines × 2)
crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs7.1Near-cleanCode Duplication: Edited copy of a member (3 corresponding lines)
crates/cdj3k-emu-ui/src/app/buttons.rs7.1Near-cleanCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)

How the grades work

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

Critical — 64

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

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

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

Could not be resolved — 11

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.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 — 52 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D17D19D20D26D28D29D30D31D34D35D36D43D44AX10AX3AX4AX9ES1ES2GD1IC1M1M2M3M4P1P10P2P3P4P6S1X12X13X16X17X18X21X25X28X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 362 of 384 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a1e561-6612-7e67-b06f-4a57385375d9.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, 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 (.rs) and this repository declares a Cargo test suite (repository root, 110 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 87 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 2 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D31 IaC & Container Security — 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. Docker/Dockerfile.linux-host.dockerignore, REDACTED.dockerignore, REDACTED.dockerignore carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 5 of 8 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
  • IC1 Incompleteness & stubs — 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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
  • 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, 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.
  • X22 Contradicted release 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 reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's C, Rust 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.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
  • X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — 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. 34 further occurrence(s) are not listed individually; the score already reflects all 74.

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.
  • 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.
  • 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.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

0 function(s) exceeded the cyclomatic complexity threshold of 15. A further 1 function(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 CdjShell::apply_mods_action at 16 — 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: crates/cdj3k-emu-ui/src/app/shell/mods.rs (CdjShell::apply_mods_action at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity7.9 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

19 function(s) exceeded the cognitive complexity threshold of 15; the worst was cdj3k_emu_runtime::cfg::reader_loop at 25.

cdj3k_emu_ui::app::ui::draw_vinyl_speed::vinyl_speed_interact (cognitive 21) · ×4crates/cdj3k-emu-ui/src/app/ui/draw_vinyl_speed.rs:101
cdj3k_emu_runtime::cfg::reader_loop (cognitive 25) · ×3crates/cdj3k-emu-runtime/src/cfg.rs:293
cdj3k_emu_control::server::serve (cognitive 18) · ×3crates/cdj3k-emu-control/src/server.rs:223
CdjApp::paint_jog_adjust_interact (cognitive 17) · ×2crates/cdj3k-emu-ui/src/app/ui/draw_jog/interact.rs:188
cdj3k_emu_storage::mods::archive::unpack (cognitive 20)crates/cdj3k-emu-storage/src/mods/archive.rs:14

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

What to do

  1. Bring the 19 bodies over 15 down to 15 or less in Cognitive Complexity — start with cdj3k_emu_runtime::cfg::reader_loop (cognitive 25), cdj3k_emu_ui::app::ui::draw_vinyl_speed::vinyl_speed_interact (cognitive 21), cdj3k_emu_storage::mods::archive::unpack (cognitive 20). — 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 19 together lifts Cognitive Complexity from 7.9 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.

D3 · God Classes9.7 / 10Stronggated by 6 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

6 over-large unit(s) detected — types, modules or files that carry too much.

TooManyMethods: CdjShell · ×3crates/cdj3k-emu-ui/src/app/shell.rs:124
TooManyFields: CdjApp · ×2crates/cdj3k-emu-ui/src/app.rs:64
FileTooLong: shell/control.rscrates/cdj3k-emu-ui/src/app/shell/control.rs

What to do

  1. Resolve the 3 TooManyMethods finding(s) in God Classes — start with shell.rs, app.rs, runtime_worker.rs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 TooManyFields finding(s) in God Classes — start with app.rs, shell.rs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with control.rs. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication7.0 / 10Adequate✓ Tool-verified

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

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

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

85 duplicated block group(s) detected. 7.6 % of the production lines (5,395 of 70,926) are in a reported copy. A further 56 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 (11 corresponding lines) · ×6crates/cdj3k-emu-runtime/src/disk/windows_parse.rs:108
Duplicated block (9 lines × 2) · ×5crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:252
Duplicated block (7 lines × 2) · ×5crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:94
Edited copy of a member (21 corresponding lines) · ×4crates/cdj3k-emu-firmware/src/luks/crypto.rs:108
Duplicated block (10 lines × 2) · ×4crates/cdj3k-emu-ui/src/app/bloom.rs:457

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

What to do

  1. Resolve the 6 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with geometry.rs (2), windows_parse.rs, winbridge.rs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with draw_chassis.rs (2), draw_left.rs, nav_rotary.rs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with draw_left.rs (2), style.rs, portable.rs. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling6.8 / 10Adequate✓ Tool-verified

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

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

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

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

10 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence.

Off the main sequence: cdj3k-emu-control · ×4

What to do

  1. Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 103 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D12 · Dependency Hygiene9.5 9.2 / 10Exemplary✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 98% · ceiling Verified

11 outdated, 0 yanked direct Cargo dependencies. 43 of 44 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.

Outdated: bytemuck · ×11

✓ On the Gold path — maintain.

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

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 525 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. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

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

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

0 deducted task-comment markers across 70926 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs foundapp/cdj3k-emu/Cargo.toml:11

What to do

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

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

D26 · Project Cohesion6.3 / 10Adequate✓ Tool-verified

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

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

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

2 of 10 build units (Cargo) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×2crates/cdj3k-emu-ui/Cargo.toml:1

What to do

  1. Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

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

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)2.5 / 10Weak✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

56 finding(s): 0 critical, 56 high, 0 medium, 0 low. 48 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 6 file(s) — `REDACTED` (line 175), `docker/windows-qemu-deps.sh`, `initramfs-patch/patch-rootfs.sh` (line 28), `scripts/bundle-dlls.sh` (lines 15–116), `scripts/bundle-sos.sh`, … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 48 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (50 issue-level, 2 of them charged here).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D30 · Dependency Vulnerabilities6.8 / 10Adequate✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security5.6 3.5 / 10Weak✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 3.5 / 10 · rule-coverage 62% · ceiling Documented

25 finding(s): 0 critical, 8 high, 17 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 17 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (17 warning-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 261 of the 349 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

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

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • `run_elevated`'s whole body panics or returns an error whose message says it isn't finished — generated scaffolding that was never completed. Implement it or remove it. — crates/cdj3k-emu-runtime/src/elevate/unsupported.rs:5

What to do

  • Finish or delete the functions that are still `todo!()`/`unimplemented!()` or panic "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `print` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/cdj3k-emu-control/src/steps.rs:58
  • `permissions` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/cdj3k-emu-firmware/src/file_mode/unsupported.rs:5
  • `set_executable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/cdj3k-emu-firmware/src/file_mode/unsupported.rs:10
  • `quiet` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — crates/cdj3k-emu-platform/src/child/unix.rs:4, crates/cdj3k-emu-platform/src/child/unsupported.rs:4
  • `set_runnable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/cdj3k-emu-platform/src/child/unsupported.rs:14, crates/cdj3k-emu-platform/src/child/windows.rs:20
  • `open_url` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×3) — crates/cdj3k-emu-platform/src/desktop/linux.rs:106, crates/cdj3k-emu-platform/src/desktop/macos.rs:554, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:79
  • `set_caption_area` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×3) — crates/cdj3k-emu-platform/src/desktop/linux.rs:209, crates/cdj3k-emu-platform/src/desktop/macos.rs:581, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:26
  • `enter_picker_window` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — crates/cdj3k-emu-platform/src/desktop/macos.rs:457, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:43
  • `run_picker` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — crates/cdj3k-emu-platform/src/desktop/macos.rs:481, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:61
  • `run_mod_picker` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — crates/cdj3k-emu-platform/src/desktop/macos.rs:492, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:69
  • `reveal_in_file_manager` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — crates/cdj3k-emu-platform/src/desktop/macos.rs:546, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:77
  • `set_app_name` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/cdj3k-emu-platform/src/desktop/mod.rs:185
  • `activate_process` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/cdj3k-emu-platform/src/desktop/portable.rs:16, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:5
  • `set_app_name` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/cdj3k-emu-platform/src/desktop/portable.rs:21, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:28
  • `on_creation_context` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — crates/cdj3k-emu-platform/src/desktop/portable.rs:25, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:32
  • `answer_quit_request` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/cdj3k-emu-platform/src/desktop/portable.rs:35, crates/cdj3k-emu-platform/src/desktop/unsupported.rs:18
  • `enter_panel_window` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/cdj3k-emu-platform/src/desktop/unsupported.rs:34
  • `open_file_picker` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/cdj3k-emu-platform/src/desktop/unsupported.rs:57
  • `actuate` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/cdj3k-emu-platform/src/haptic/unsupported.rs:11
  • `show_net_error_alert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/cdj3k-emu-platform/src/menu/launch.rs:58
  • `show_usb_error_alert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/cdj3k-emu-platform/src/menu/launch.rs:68
  • `exists` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/cdj3k-emu-platform/src/net/unsupported.rs:14
  • `tighten` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/cdj3k-emu-platform/src/runtime_paths/unsupported.rs:16, crates/cdj3k-emu-platform/src/runtime_paths/windows.rs:15
  • `allow_holes` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/cdj3k-emu-platform/src/sparse_file/unix.rs:4, crates/cdj3k-emu-platform/src/sparse_file/unsupported.rs:4

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

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

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

What to do

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

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

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

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

What to do

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

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

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

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

  • No logging call was found in the 349 Rust production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (Rust: the log and tracing crates (info!/warn!/error!, #[instrument]), slog, env_logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run.
  • Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • `app/cdj3k-emu/Cargo.toml` 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`. — app/cdj3k-emu/Cargo.toml:15

What to do

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

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

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

P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified

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

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

  • The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's Rust 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 serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker.

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

  • MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — crates/cdj3k-emu-firmware/src/extract.rs:67, crates/cdj3k-emu-firmware/src/luks/crypto.rs:137, crates/cdj3k-emu-firmware/src/luks/crypto.rs:143

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `crates/cdj3k-emu-firmware/src/extract.rs:67` (`md5::compute`), `crates/cdj3k-emu-firmware/src/luks/crypto.rs:137` (`Sha1::new`), `crates/cdj3k-emu-firmware/src/luks/crypto.rs:143` (`Sha1::new`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X12 · Unreachable branch8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

  • `let process = info.hProcess;` follows `{ return Err(if e.code() == ERROR_CANCELLED.to_hresult() { io::Error::new(io:…` (line 30) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/cdj3k-emu-runtime/src/elevate/windows.rs:40

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

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

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

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

  • `panel` is public and takes `nodes: &[MenuNode]` from its caller, and it recurses at line 31 through `submenu_row`, `node` and back with a piece of the document (and at line 91, line 128) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `panel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/cdj3k-emu-platform/src/menu/egui_provider/panel.rs:31

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

X5 · Nullable reference types9.6 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.

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

  • `gl.create_vertex_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:111
  • `self.copy_tex` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:179
  • `self.copy_fbo` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:180
  • `self.blur_tex` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:181
  • `self.blur_fbo` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:182
  • `self.blur_tex` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `composite` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:238
  • `gl.create_texture()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_fbo` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:433
  • `gl.create_framebuffer()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_fbo` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:456
  • `gl.create_shader(glow::VERTEX_SHADER)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_program` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:471
  • `gl.create_shader(glow::FRAGMENT_SHADER)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_program` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:480
  • `gl.create_program()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_program` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/bloom.rs:489
  • `std::thread::Builder::new().name("cdj3k-emu-provision".into()).spawn(move||provision(upd,key,target,model,ssh,status,log,ctx))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start_provision` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/firmware_wizard.rs:405
  • `gl.create_texture()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `resize_if_needed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/frame_cache.rs:48
  • `gl.create_framebuffer()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `resize_if_needed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/frame_cache.rs:71
  • `gl.create_texture()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `allocate_lcd_texture` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/lcd_texture.rs:180
  • `resp` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `filled` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/theme.rs:283
  • `self.jog_static_cache.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `draw_jog_wheel_section` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/ui/draw_jog.rs:185
  • `cur.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `clip_polygon_to_rect` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:100
  • `out.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `inner_lcd_silhouette_polygon` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:170
  • `self.sample.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `sample` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/shell/guest_monitor.rs:89
  • `event.as_object_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `poll` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-ui/src/app/shell/control/watch.rs:127
  • `thread::Builder::new().name("ctrl-stream".into()).spawn(move||stream_loop(path,link))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-streams/src/ctrl_stream.rs:71
  • `thread::Builder::new().name("jog-lcd-stream".into()).spawn(move||stream_loop(&path,slot_clone,connected_clone,gate))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-streams/src/jog_stream.rs:109
  • `Arc::get_mut(&mut self.bufs[self.next])` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `writable` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-streams/src/jog_stream.rs:267
  • `thread::Builder::new().name("main-lcd-shm".into()).spawn(move||shm_loop(&path,slot_clone,connected_clone,frames_seen_clone,gate))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-streams/src/main_stream.rs:92
  • `thread::Builder::new().name("repaint-gate".into()).spawn(move||metronome(pending_clone,ctx,min_interval))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-streams/src/repaint_gate.rs:52
  • `stored.try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `read_uboot_env` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-storage/src/emmc.rs:118
  • `self.emmc.parent()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `dir` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-storage/src/lib.rs:57
  • `head[20..24].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `read_at` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-storage/src/qcow2.rs:32
  • `head[36..40].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `read_at` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-storage/src/qcow2.rs:37
  • `head[40..48].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `read_at` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-storage/src/qcow2.rs:38
  • `std::env::var("CARGO_MANIFEST_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/build.rs:15
  • `thread::Builder::new().name("cfg-stream".into()).spawn(move||reader_loop(path,weak))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/cfg.rs:118
  • `thread::Builder::new().name("cfg-ping".into()).spawn(move||ping_loop(weak))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/cfg.rs:124
  • `thread::Builder::new().name("dev-client".into()).spawn(move||reader_loop(&sock,&shared,&up,&stop))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/dev.rs:93
  • `std::thread::Builder::new().name(format!("qemu-monitor-{}",config.instance_id)).spawn(move||{let code=child.wait_with_output().map(|o|o.status.code().unwrap_or(-1)).unwrap_or(-1);eprintln!("cdj3k-emu: the QEMU child process exited with code {code}.");running_clone.store(false,Ordering::Release);code})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start_qemu` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/instance.rs:341
  • `format!("127.0.0.1:{}",qmp_port).parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `kill_stale` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/instance.rs:363
  • `CString::new(s.as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `run_worker_if_asked` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/qemu_exec/macos.rs:75
  • `self.ready.wait_timeout(q,WRITE_TIMEOUT)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `pop` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/pc_link/midi_driver.rs:78
  • `thread::Builder::new().name("pc-link-midi-writer".into()).spawn(move||write_loop(&write_client,&write_outbox,&write_stop))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/cdj3k-emu-runtime/src/pc_link/midi_driver.rs:297

What to do

  • Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health77.4StrongSolid.
Architecture93.5ExemplarySolid.
Maturity67.1Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness52.0Adequate — gated by P2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security66.9Adequate — gated by D29, D31, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event Sourcing100.0ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 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.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: 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.
  • AX2 Stateful singletons — Not applicable: 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.
  • 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 interface, protocol or abstract type declares an operation an implementer must write
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — #1 DONE 0.0s REDACTED.dockerignore:4 -------------------- 2 | # the guest image and excludes everything this needs, so BuildKit uses this 3 | # file instead (it prefers <dockerfile>.dockerignore). 4 | >>> .git/ 5 | target/ 6 | dist/ -------------------- ERROR: failed to solve: dockerfile parse error on line 4: unknown instruction: .git/; likely cause (the repository): the REDACTED does not parse: docker reports an instruction or option it does not know; runtime evidence skipped The cause is in the repository, not in our sandbox: the REDACTED does not parse: docker reports an instruction or option it does not know. 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 a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • 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 a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) 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 a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) 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 a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~1836 lines of test source are present (.rs) 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 — the .rs suite was found but not re-run
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • 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 (9488 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (cdj3k-emu-ui), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Rust suite
  • DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 22 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
  • 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
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • 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
  • 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
  • X19 Unrestored process-global state — 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
  • X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not 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
  • 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 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
  • X26 Unsynchronised callback handoff — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — 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
  • 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.

Critical — 64 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 25 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 295 finding(s)
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×40
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:111 — `gl.create_vertex_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:179 — `self.copy_tex` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:180 — `self.copy_fbo` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:181 — `self.blur_tex` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:182 — `self.blur_fbo` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `blur_scene` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:238 — `self.blur_tex` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `composite` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:433 — `gl.create_texture()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_fbo` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:456 — `gl.create_framebuffer()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_fbo` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:471 — `gl.create_shader(glow::VERTEX_SHADER)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_program` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:480 — `gl.create_shader(glow::FRAGMENT_SHADER)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_program` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/bloom.rs:489 — `gl.create_program()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_program` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/firmware_wizard.rs:405 — `std::thread::Builder::new().name("cdj3k-emu-provision".into()).spawn(move||provision(upd,key,target,model,ssh,status,log,ctx))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start_provision` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/frame_cache.rs:48 — `gl.create_texture()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `resize_if_needed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/frame_cache.rs:71 — `gl.create_framebuffer()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `resize_if_needed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/lcd_texture.rs:180 — `gl.create_texture()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `allocate_lcd_texture` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/theme.rs:283 — `resp` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `filled` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/ui/draw_jog.rs:185 — `self.jog_static_cache.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `draw_jog_wheel_section` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:100 — `cur.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `clip_polygon_to_rect` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:170 — `out.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `inner_lcd_silhouette_polygon` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/shell/guest_monitor.rs:89 — `self.sample.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `sample` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-ui/src/app/shell/control/watch.rs:127 — `event.as_object_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `poll` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-streams/src/ctrl_stream.rs:71 — `thread::Builder::new().name("ctrl-stream".into()).spawn(move||stream_loop(path,link))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-streams/src/jog_stream.rs:109 — `thread::Builder::new().name("jog-lcd-stream".into()).spawn(move||stream_loop(&path,slot_clone,connected_clone,gate))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-streams/src/jog_stream.rs:267 — `Arc::get_mut(&mut self.bufs[self.next])` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `writable` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • Symbol treated as nullable, then dereferenced unguarded crates/cdj3k-emu-streams/src/main_stream.rs:92 — `thread::Builder::new().name("main-lcd-shm".into()).spawn(move||shm_loop(&path,slot_clone,connected_clone,frames_seen_clone,gate))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
  • + 15 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Empty method body · ×24
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-control/src/steps.rs:58 — `print` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/child/unix.rs:4 — `quiet` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/child/unsupported.rs:4 — `quiet` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/linux.rs:106 — `open_url` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/linux.rs:209 — `set_caption_area` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/macos.rs:457 — `enter_picker_window` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/macos.rs:481 — `run_picker` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/macos.rs:492 — `run_mod_picker` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/macos.rs:546 — `reveal_in_file_manager` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/macos.rs:554 — `open_url` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/macos.rs:581 — `set_caption_area` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/mod.rs:185 — `set_app_name` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/portable.rs:25 — `on_creation_context` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:26 — `set_caption_area` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:32 — `on_creation_context` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:34 — `enter_panel_window` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:43 — `enter_picker_window` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:61 — `run_picker` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:69 — `run_mod_picker` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:77 — `reveal_in_file_manager` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/desktop/unsupported.rs:79 — `open_url` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/haptic/unsupported.rs:11 — `actuate` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/menu/launch.rs:58 — `show_net_error_alert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs crates/cdj3k-emu-platform/src/menu/launch.rs:68 — `show_usb_error_alert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
D31 · IaC & Container Security · Medium IaC · ×17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Hollow method · ×16
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-firmware/src/file_mode/unsupported.rs:5 — `permissions` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-firmware/src/file_mode/unsupported.rs:10 — `set_executable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/child/unsupported.rs:14 — `set_runnable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/child/windows.rs:20 — `set_runnable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/portable.rs:16 — `activate_process` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/portable.rs:21 — `set_app_name` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/portable.rs:35 — `answer_quit_request` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/unsupported.rs:5 — `activate_process` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/unsupported.rs:18 — `answer_quit_request` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/unsupported.rs:28 — `set_app_name` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/desktop/unsupported.rs:57 — `open_file_picker` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/net/unsupported.rs:14 — `exists` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/runtime_paths/unsupported.rs:16 — `tighten` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/runtime_paths/windows.rs:15 — `tighten` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/sparse_file/unix.rs:4 — `allow_holes` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
  • Hollow method — returns a constant without doing the work crates/cdj3k-emu-platform/src/sparse_file/unsupported.rs:4 — `allow_holes` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×6
  • Edited copy of a member (11 corresponding lines) crates/cdj3k-emu-runtime/src/disk/windows_parse.rs:108 — crates/cdj3k-emu-runtime/src/disk/windows_parse.rs:108-121 | crates/cdj3k-emu-runtime/src/net/winbridge.rs:28-38 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/cdj3k-emu-runtime/src/net/winbridge.rs:63 — crates/cdj3k-emu-runtime/src/net/winbridge.rs:63-73 | crates/cdj3k-emu-runtime/src/net/winbridge.rs:76-93 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:265 — crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:265-276 | crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:286-296 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/cdj3k-emu-panel/src/cdj3k.rs:105 — crates/cdj3k-emu-panel/src/cdj3k.rs:105-115 | crates/cdj3k-emu-panel/src/cdj3kx.rs:64-75 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/cdj3k-emu-platform/src/menu/egui_provider/paint.rs:56 — crates/cdj3k-emu-platform/src/menu/egui_provider/paint.rs:56-66 | crates/cdj3k-emu-platform/src/menu/egui_provider/paint.rs:69-79 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:12 — crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:12-22 | crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:24-34 — 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 · Duplicated block (9 lines × 2) · ×5
  • Duplicated block (9 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:252 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:252-260 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:248-256 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:371 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:371-379 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:302-310 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:111 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:111-119 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:108-116 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 127 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:111` 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 (9 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:323 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:323-331 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:348-356 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 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 (9 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:21 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:21-29 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:21-29 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×5
  • Duplicated block (7 lines × 2) crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:94 — crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:94-100 | crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:135-141 — 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 `crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) crates/cdj3k-emu-platform/src/desktop/portable.rs:114 — crates/cdj3k-emu-platform/src/desktop/portable.rs:114-120 | crates/cdj3k-emu-platform/src/desktop/portable.rs:139-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-platform/src/desktop/portable.rs:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:99 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:99-105 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:98-104 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 127 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (7 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:252 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:252-258 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:222-228 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:260` calls `draw_on_air_bar` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:231` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:144 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:144-150 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:119-125 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 127 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D2 · Cognitive Complexity · cdj3k_emu_ui · ×4
  • cdj3k_emu_ui::app::ui::draw_vinyl_speed::vinyl_speed_interact (cognitive 21) crates/cdj3k-emu-ui/src/app/ui/draw_vinyl_speed.rs:101 — cdj3k_emu_ui::app::ui::draw_vinyl_speed::vinyl_speed_interact has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (3 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • cdj3k_emu_ui::app::mods_view::log_page::draw_meta (cognitive 19) crates/cdj3k-emu-ui/src/app/mods_view/log_page.rs:227 — cdj3k_emu_ui::app::mods_view::log_page::draw_meta has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • cdj3k_emu_ui::app::ui::draw_jog::statics::collect_clipped_circle_arcs (cognitive 19) crates/cdj3k-emu-ui/src/app/ui/draw_jog/statics.rs:416 — cdj3k_emu_ui::app::ui::draw_jog::statics::collect_clipped_circle_arcs has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 3 (6 pts), boolean chains 4 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
  • cdj3k_emu_ui::app::ui::draw_jog::geometry::inner_lcd_push_curved_label (cognitive 18) crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:351 — cdj3k_emu_ui::app::ui::draw_jog::geometry::inner_lcd_push_curved_label has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) crates/cdj3k-emu-firmware/src/luks/crypto.rs:108 — crates/cdj3k-emu-firmware/src/luks/crypto.rs:108-128 | crates/cdj3k-emu-firmware/src/luks/crypto.rs:130-150 — 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) crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:84 — crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:84-108 | crates/cdj3k-emu-platform/src/menu/egui_provider/style.rs:129-149 — 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) crates/cdj3k-emu-ui/src/app/mods_view/dialogs.rs:25 — crates/cdj3k-emu-ui/src/app/mods_view/dialogs.rs:25-45 | crates/cdj3k-emu-ui/src/app/mods_view/dialogs.rs:53-73 — 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) crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:111 — crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:111-131 | crates/cdj3k-emu-ui/src/app/picker/cards.rs:249-270 — 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 · Duplicated block (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) crates/cdj3k-emu-ui/src/app/bloom.rs:457 — crates/cdj3k-emu-ui/src/app/bloom.rs:457-466 | crates/cdj3k-emu-ui/src/app/frame_cache.rs:72-81 — 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 (10 lines × 2) crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:115 — crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:115-124 | crates/cdj3k-emu-ui/src/app/picker/cards.rs:254-263 — 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 `crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:115` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:311 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:311-320 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:281-290 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (10 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:224 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:224-233 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:214-223 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:224` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) crates/cdj3k-emu-firmware/src/luks/crypto.rs:116 — crates/cdj3k-emu-firmware/src/luks/crypto.rs:116-120 | crates/cdj3k-emu-firmware/src/luks/crypto.rs:138-142 — 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 `crates/cdj3k-emu-firmware/src/luks/crypto.rs:116` 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) crates/cdj3k-emu-ui/src/app/buttons.rs:88 — crates/cdj3k-emu-ui/src/app/buttons.rs:88-92 | crates/cdj3k-emu-ui/src/app/buttons.rs:184-188 — 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 `crates/cdj3k-emu-ui/src/app/buttons.rs:88` 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 (5 lines × 2) crates/cdj3k-emu-ui/src/app/mods_view/list.rs:194 — crates/cdj3k-emu-ui/src/app/mods_view/list.rs:194-198 | crates/cdj3k-emu-ui/src/app/mods_view/log_page.rs:162-166 — 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 `crates/cdj3k-emu-ui/src/app/mods_view/list.rs:194` 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 (5 lines × 2) crates/cdj3k-emu-ui/src/app/updater/notes.rs:20 — crates/cdj3k-emu-ui/src/app/updater/notes.rs:20-24 | crates/cdj3k-emu-ui/src/app/updater/view.rs:489-493 — 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 `crates/cdj3k-emu-ui/src/app/updater/notes.rs:20` 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.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: cdj3k-emu-control — cdj3k-emu-control: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: cdj3k-emu-firmware — cdj3k-emu-firmware: abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: cdj3k-emu-panel — cdj3k-emu-panel: abstractness 0.13, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: cdj3k-emu-platform — cdj3k-emu-platform: abstractness 0.05, instability 0.14, distance 0.81 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
D2 · Cognitive Complexity · cdj3k_emu_runtime · ×3
  • cdj3k_emu_runtime::cfg::reader_loop (cognitive 25) crates/cdj3k-emu-runtime/src/cfg.rs:293 — cdj3k_emu_runtime::cfg::reader_loop has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • cdj3k_emu_runtime::instance::cleanup_qemu_files_inner (cognitive 19) crates/cdj3k-emu-runtime/src/instance.rs:455 — cdj3k_emu_runtime::instance::cleanup_qemu_files_inner has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • cdj3k_emu_runtime::disk::macos_disk::list_removable (cognitive 18) crates/cdj3k-emu-runtime/src/disk/macos_disk.rs:309 — cdj3k_emu_runtime::disk::macos_disk::list_removable has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cdj3k_emu_control · ×3
  • cdj3k_emu_control::server::serve (cognitive 18) crates/cdj3k-emu-control/src/server.rs:223 — cdj3k_emu_control::server::serve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • cdj3k_emu_control::diff::compare (cognitive 16) crates/cdj3k-emu-control/src/diff.rs:129 — cdj3k_emu_control::diff::compare has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • cdj3k_emu_control::steps::screen::watch_region (cognitive 16) crates/cdj3k-emu-control/src/steps/screen.rs:119 — cdj3k_emu_control::steps::screen::watch_region has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: CdjShell crates/cdj3k-emu-ui/src/app/shell.rs:124 — TooManyMethods — 116 methods, declared across 9 files: shell/control.rs (35), shell/mods.rs (17), shell/slots.rs (14), app/shell.rs (13), +5 more file(s). The bar is 30 methods; this is 86 over it, 3.87× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CdjApp crates/cdj3k-emu-ui/src/app.rs:64 — TooManyMethods — 104 methods, declared across 15 files: app/api_input.rs (23), app/jog_physics.rs (16), app/update.rs (14), app/frame_inject.rs (11), +11 more file(s). The bar is 30 methods; this is 74 over it, 3.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Worker app/cdj3k-emu/src/runtime_worker.rs:69 — TooManyMethods — 38 methods, declared across 6 files: runtime_worker/usb.rs (11), src/runtime_worker.rs (9), runtime_worker/qemu.rs (8), runtime_worker/net.rs (5), +2 more file(s). The bar is 30 methods; this is 8 over it, 1.27× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) crates/cdj3k-emu-platform/src/menu_state.rs:402 — crates/cdj3k-emu-platform/src/menu_state.rs:402-414 | crates/cdj3k-emu-platform/src/menu_state.rs:433-446 — 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) crates/cdj3k-emu-ui/src/app/api_input.rs:80 — crates/cdj3k-emu-ui/src/app/api_input.rs:80-92 | crates/cdj3k-emu-ui/src/app/api_input.rs:96-108 — 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) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:232 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:232-244 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:169-189 — 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 · Duplicated block (58 lines × 2) · ×3
  • Duplicated block (58 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:254 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:254-311 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:252-309 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (58 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:294 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:294-351 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:282-339 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (58 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:480 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:480-537 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:406-463 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (48 lines × 2) · ×3
  • Duplicated block (48 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:378 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:378-425 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:323-370 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (48 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:380 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:380-427 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:434-481 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (48 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:314 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:314-361 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:240-287 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×3
  • Duplicated block (35 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:176 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:176-210 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:164-198 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:176` 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 (35 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:228 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:228-262 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:216-250 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (35 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:210 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:210-244 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:180-214 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×3
  • Duplicated block (27 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:110 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:110-136 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:110-136 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:112 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:112-138 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:100-126 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:221 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:221-247 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:217-243 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×3
  • Duplicated block (25 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:110 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:110-134 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:128-152 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (25 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:118 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:118-142 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:118-142 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:118` 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 (25 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:172 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:172-196 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:160-184 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×3
  • Duplicated block (24 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:224 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:224-247 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:243-266 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (24 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:33 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:33-56 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:33-56 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:83 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:83-106 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:83-106 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) crates/cdj3k-emu-platform/src/menu/muda_provider.rs:345 — crates/cdj3k-emu-platform/src/menu/muda_provider.rs:345-357 | crates/cdj3k-emu-platform/src/menu/muda_provider.rs:373-385 — 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 `crates/cdj3k-emu-platform/src/menu/muda_provider.rs:345` 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 first that the copies are not typed on the same thing: the declarations holding them bind `item` to `&MenuItem` in one and `&CheckMenuItem` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:87 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:87-99 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs:81-93 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 196 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:540 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:540-552 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:466-478 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) crates/cdj3k-emu-firmware/src/luks/crypto.rs:186 — crates/cdj3k-emu-firmware/src/luks/crypto.rs:186-197 | crates/cdj3k-emu-firmware/src/luks/crypto.rs:224-235 — 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 `crates/cdj3k-emu-firmware/src/luks/crypto.rs: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/cdj3k-emu-firmware/src/luks/crypto.rs:238` calls `Some`, `essiv_iv` and `crates/cdj3k-emu-firmware/src/luks/crypto.rs:199` 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 (12 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:78 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:78-89 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:96-107 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:105 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:105-116 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:105-116 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) crates/cdj3k-emu-ui/src/app/picker/dialogs.rs:215 — crates/cdj3k-emu-ui/src/app/picker/dialogs.rs:215-225 | crates/cdj3k-emu-ui/src/app/picker/header.rs:150-160 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/picker/dialogs.rs:215` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/cdj3k-emu-ui/src/app/picker/dialogs.rs:253 — crates/cdj3k-emu-ui/src/app/picker/dialogs.rs:253-263 | crates/cdj3k-emu-ui/src/app/table.rs:232-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/cdj3k-emu-ui/src/app/table.rs:243` calls `proportional`, `iter`, `zip` and `crates/cdj3k-emu-ui/src/app/picker/dialogs.rs:264` 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 × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:266 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:266-276 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:235-245 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:266` 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.
S1 · Web-Security Posture · Weak hash algorithm · ×3
  • Weak hash algorithm crates/cdj3k-emu-firmware/src/extract.rs:67 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm crates/cdj3k-emu-firmware/src/luks/crypto.rs:137 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm crates/cdj3k-emu-firmware/src/luks/crypto.rs:143 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
D2 · Cognitive Complexity · CdjApp · ×2
  • CdjApp::paint_jog_adjust_interact (cognitive 17) crates/cdj3k-emu-ui/src/app/ui/draw_jog/interact.rs:188 — CdjApp::paint_jog_adjust_interact has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CdjApp::apply_lcd_touch (cognitive 16) crates/cdj3k-emu-ui/src/app/lcd_touch.rs:23 — CdjApp::apply_lcd_touch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · TooManyFields · ×2
  • TooManyFields: CdjApp crates/cdj3k-emu-ui/src/app.rs:64 — TooManyFields — 69 stored fields beside 104 methods. The bar is 30 stored fields; this is 39 over it, 2.30× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: CdjShell crates/cdj3k-emu-ui/src/app/shell.rs:124 — TooManyFields — 39 stored fields beside 116 methods. The bar is 30 stored fields; this is 9 over it, 1.30× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×2
  • Edited copy of a member (44 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:261 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:261-312 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/media.rs:335-378 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) crates/cdj3k-emu-ui/src/app/lcd_texture.rs:53 — crates/cdj3k-emu-ui/src/app/lcd_texture.rs:53-96 | crates/cdj3k-emu-ui/src/app/lcd_texture.rs:100-157 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×2
  • Edited copy of a member (20 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:98 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:98-119 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:97-116 — 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) crates/cdj3k-emu-streams/src/jog_stream.rs:97 — crates/cdj3k-emu-streams/src/jog_stream.rs:97-116 | crates/cdj3k-emu-streams/src/main_stream.rs:79-100 — 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 (23 corresponding lines) · ×2
  • Edited copy of a member (23 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:364 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:364-386 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:290-312 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) crates/cdj3k-emu-runtime/src/net/linux_net.rs:150 — crates/cdj3k-emu-runtime/src/net/linux_net.rs:150-172 | crates/cdj3k-emu-runtime/src/net/linux_net.rs:175-198 — 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 (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:15 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:15-38 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:15-40 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:482 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:482-515 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:427-450 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×2
  • Edited copy of a member (14 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:207 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:207-220 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:196-210 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:134 — crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:134-147 | crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:150-163 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×2
  • Edited copy of a member (10 corresponding lines) crates/cdj3k-emu-ui/src/app/api_input.rs:314 — crates/cdj3k-emu-ui/src/app/api_input.rs:314-323 | crates/cdj3k-emu-ui/src/app/debug_view.rs:391-400 — 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) crates/cdj3k-emu-streams/src/main_stream.rs:261 — crates/cdj3k-emu-streams/src/main_stream.rs:261-277 | crates/cdj3k-emu-streams/src/main_stream.rs:281-290 — 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 (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) crates/cdj3k-emu-firmware/src/initramfs.rs:305 — crates/cdj3k-emu-firmware/src/initramfs.rs:305-316 | crates/cdj3k-emu-firmware/src/initramfs_guest.rs:348-356 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) crates/cdj3k-emu-runtime/src/net/linux.rs:29 — crates/cdj3k-emu-runtime/src/net/linux.rs:29-37 | crates/cdj3k-emu-runtime/src/net/windows.rs:27-35 — 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 (5 corresponding lines) · ×2
  • Edited copy of a member (5 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_top.rs:124 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_top.rs:124-128 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_transport.rs:176-180 — 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) crates/cdj3k-emu-firmware/src/file_mode/unix.rs:10 — crates/cdj3k-emu-firmware/src/file_mode/unix.rs:10-14 | crates/cdj3k-emu-platform/src/child/unix.rs:15-20 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_top.rs:85 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_top.rs:85-87 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_transport.rs:59-61 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:138 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:138-140 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs:132-134 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×2
  • Duplicated block (50 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:430 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:430-479 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:375-424 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (50 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:390 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:390-439 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:316-365 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:144 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:144-161 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:143-160 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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, `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:143` calls `height` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:142` 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 (18 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:188 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:188-205 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:184-201 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:156 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:156-171 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs:148-163 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 196 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) crates/cdj3k-emu-runtime/src/mods_report.rs:174 — crates/cdj3k-emu-runtime/src/mods_report.rs:174-189 | crates/cdj3k-emu-storage/src/mods/manifest.rs:194-209 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D2 · Cognitive Complexity · cdj3k_emu_storage · ×1
  • cdj3k_emu_storage::mods::archive::unpack (cognitive 20) crates/cdj3k-emu-storage/src/mods/archive.rs:14 — cdj3k_emu_storage::mods::archive::unpack has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cdj3k_emu_streams · ×1
  • cdj3k_emu_streams::ctrl_stream::read_loop (cognitive 19) crates/cdj3k-emu-streams/src/ctrl_stream.rs:183 — cdj3k_emu_streams::ctrl_stream::read_loop has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FirmwareWizard · ×1
  • FirmwareWizard::path_row (cognitive 19) crates/cdj3k-emu-ui/src/app/firmware_wizard/form.rs:125 — FirmwareWizard::path_row has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (19 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cdj3k_emu_update · ×1
  • cdj3k_emu_update::slots::close_other_slots (cognitive 18) crates/cdj3k-emu-update/src/slots.rs:24 — cdj3k_emu_update::slots::close_other_slots has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Watch · ×1
  • Watch::poll (cognitive 17) crates/cdj3k-emu-ui/src/app/shell/control/watch.rs:104 — Watch::poll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · EguiProvider · ×1
  • EguiProvider::bar (cognitive 16) crates/cdj3k-emu-platform/src/menu/egui_provider/strip.rs:36 — EguiProvider::bar has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3, boolean chains 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PartialFrame · ×1
  • PartialFrame::read (cognitive 16) crates/cdj3k-emu-runtime/src/pc_link/transport.rs:240 — PartialFrame::read has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: shell/control.rs crates/cdj3k-emu-ui/src/app/shell/control.rs — FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: CdjShell (138-712). The bar is 500 significant lines; this is 16 over it, 1.03× 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) crates/cdj3k-emu-ui/src/app/buttons.rs:70 — crates/cdj3k-emu-ui/src/app/buttons.rs:70-116 | crates/cdj3k-emu-ui/src/app/buttons.rs:131-151 | crates/cdj3k-emu-ui/src/app/buttons.rs:172-211 | crates/cdj3k-emu-ui/src/app/buttons.rs:237-283 — 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 (72 corresponding lines) · ×1
  • Edited copy of a member (72 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:152 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:152-223 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:128-199 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (53 corresponding lines) · ×1
  • Edited copy of a member (53 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:140 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:140-204 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:140-192 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:140 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:140-178 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/media.rs:154-206 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (61 corresponding lines) · ×1
  • Edited copy of a member (61 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:212 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:212-286 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:230-290 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:100 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:100-142 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:100-142 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (50 corresponding lines) · ×1
  • Edited copy of a member (50 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:54 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:54-103 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:68-121 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) crates/cdj3k-emu-runtime/src/mods_report.rs:171 — crates/cdj3k-emu-runtime/src/mods_report.rs:171-189 | crates/cdj3k-emu-storage/src/mods/manifest.rs:191-209 — 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 (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:166 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:166-197 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:167-195 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/draw_jog/statics.rs:253 — crates/cdj3k-emu-ui/src/app/ui/draw_jog/statics.rs:253-294 | crates/cdj3k-emu-ui/src/app/ui/draw_vinyl_speed.rs:152-193 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:106 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:106-146 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:124-164 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 54+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 54+ corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:150 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:150-209 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:168-227 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/transport.rs:42-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 54 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:341 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:341-367 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:385-421 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) crates/cdj3k-emu-platform/src/desktop/portable.rs:113 — crates/cdj3k-emu-platform/src/desktop/portable.rs:113-130 | crates/cdj3k-emu-platform/src/desktop/portable.rs:138-156 — 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 (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:251 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:251-266 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:221-236 — 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 (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) crates/cdj3k-emu-platform/src/menu/muda_provider.rs:334 — crates/cdj3k-emu-platform/src/menu/muda_provider.rs:334-358 | crates/cdj3k-emu-platform/src/menu/muda_provider.rs:360-389 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) crates/cdj3k-emu-platform/src/audio/coreaudio.rs:167 — crates/cdj3k-emu-platform/src/audio/coreaudio.rs:167-189 | crates/cdj3k-emu-platform/src/audio/coreaudio.rs:235-257 | crates/cdj3k-emu-platform/src/audio/coreaudio.rs:259-283 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 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, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:344 — crates/cdj3k-emu-ui/src/app/mods_view/pieces.rs:344-347 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_jog.rs:221-229 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_tempo.rs:214-217 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:419-423 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) app/cdj3k-emu/src/runtime_worker/usb.rs:33 — app/cdj3k-emu/src/runtime_worker/usb.rs:33-46 | app/cdj3k-emu/src/runtime_worker/usb.rs:48-55 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) crates/cdj3k-emu-platform/src/desktop/macos.rs:54 — crates/cdj3k-emu-platform/src/desktop/macos.rs:54-68 | crates/cdj3k-emu-platform/src/desktop/macos.rs:75-86 — 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 (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) crates/cdj3k-emu-ui/src/app/lcd_texture.rs:243 — crates/cdj3k-emu-ui/src/app/lcd_texture.rs:243-259 | crates/cdj3k-emu-ui/src/app/lcd_texture.rs:261-275 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 4+ corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_front/tray.rs:50 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_front/tray.rs:50-53 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_front/tray.rs:57-60 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/key.rs:31-38 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:145-148 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:123-126 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) crates/cdj3k-emu-firmware/src/luks.rs:491 — crates/cdj3k-emu-firmware/src/luks.rs:491-494 | crates/cdj3k-emu-firmware/src/luks/rekey.rs:474-477 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×1
  • Edited copy of a member (7 corresponding lines) crates/cdj3k-emu-storage/src/lib.rs:46 — crates/cdj3k-emu-storage/src/lib.rs:46-53 | crates/cdj3k-emu-storage/src/staging.rs:39-45 — 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 copies of one member (3 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 3+ corresponding lines) crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_knobs.rs:46 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_knobs.rs:46-48 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_tempo.rs:59-61 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj1500x/draw_top.rs:80-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (73 lines × 2) · ×1
  • Duplicated block (73 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:111 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:111-183 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:107-179 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (62 lines × 2) · ×1
  • Duplicated block (62 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:162 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:162-223 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:138-199 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 127 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:162` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (60 lines × 2) · ×1
  • Duplicated block (60 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:176 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:176-235 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs:168-227 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 196 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×1
  • Duplicated block (54 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:281 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:281-334 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:226-279 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:270 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:270-312 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/media.rs:336-378 — 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 `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/media.rs:270` 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.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:229 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs:229-270 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs:205-246 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 127 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:159 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:159-199 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:177-217 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:159` 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:201 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:201-240 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:199-238 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:168 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:168-205 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:138-175 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:339 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:339-374 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:284-319 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:443 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:443-476 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:369-402 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:104 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:104-134 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs:98-128 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 196 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:248 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:248-277 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:193-222 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:143 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:143-171 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:131-159 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:143` 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/transport.rs:133 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/transport.rs:133-160 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/transport.rs:148-175 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×1
  • Duplicated block (23–25 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:345 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:345-367 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:397-421 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:345` 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.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×1
  • Duplicated block (21–23 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:493 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:493-515 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:430-450 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:493` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:287 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:287-308 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:256-277 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (76 lines × 2) · ×1
  • Duplicated block (76 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:239 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs:239-314 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs:231-306 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 196 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:60 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs:60-79 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs:60-79 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/statics.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 190 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:368 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs:368-386 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs:294-312 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_top.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_top.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 9 separate duplicated blocks between them, totalling at least 302 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17–18 lines × 3) · ×1
  • Duplicated block (17–18 lines × 3) crates/cdj3k-emu-ui/src/app/buttons.rs:96 — crates/cdj3k-emu-ui/src/app/buttons.rs:96-113 | crates/cdj3k-emu-ui/src/app/buttons.rs:192-208 | crates/cdj3k-emu-ui/src/app/buttons.rs:263-280 — 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 `crates/cdj3k-emu-ui/src/app/buttons.rs:96` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/transport.rs:44 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/transport.rs:44-59 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/transport.rs:54-70 — 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 `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/transport.rs:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/transport.rs:61` calls `mosi`, `lit` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/transport.rs:72` 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.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:63 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:63-76 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:110-123 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs:128-141 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/loops.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/loops.rs:63` 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:167 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs:167-180 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs:168-181 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/nav_rotary.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/nav_rotary.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:267 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:267-283 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:255-271 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:25 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:25-35 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs:27-38 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_left/statics.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 290 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_left/statics.rs:25` 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) crates/cdj3k-emu-runtime/src/disk/windows_parse.rs:111 — crates/cdj3k-emu-runtime/src/disk/windows_parse.rs:111-121 | crates/cdj3k-emu-runtime/src/net/winbridge.rs:30-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-runtime/src/disk/windows_parse.rs:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) crates/cdj3k-emu-platform/src/menu/egui_provider/strip.rs:180 — crates/cdj3k-emu-platform/src/menu/egui_provider/strip.rs:180-188 | crates/cdj3k-emu-platform/src/menu/egui_provider/strip.rs:234-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) crates/cdj3k-emu-ui/src/app/buttons.rs:301 — crates/cdj3k-emu-ui/src/app/buttons.rs:301-307 | crates/cdj3k-emu-ui/src/app/ui/draw_primitives/buttons.rs:240-247 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) crates/cdj3k-emu-ui/src/app/buttons.rs:111 — crates/cdj3k-emu-ui/src/app/buttons.rs:111-116 | crates/cdj3k-emu-ui/src/app/buttons.rs:145-151 | crates/cdj3k-emu-ui/src/app/buttons.rs:206-211 | crates/cdj3k-emu-ui/src/app/buttons.rs:278-283 — 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 `crates/cdj3k-emu-ui/src/app/buttons.rs:111` 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:246 — crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:246-250 | crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:256-260 | crates/cdj3k-emu-ui/src/app/ui/draw_jog/geometry.rs:307-311 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:209 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs:209-216 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs:205-212 — `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_chassis.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_chassis.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 154 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:218 — crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:218-223 | crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs:206-211 — before extracting anything, compare `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs` and `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3kx/draw_right/tempo.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/cdj3k-emu-ui/src/app/ui/slate/cdj3k/draw_right/tempo.rs:218` 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — panics or fails with a "not implemented" message crates/cdj3k-emu-runtime/src/elevate/unsupported.rs:5 — `run_elevated`'s whole body panics or returns an error whose message says it isn't finished — generated scaffolding that was never completed. Implement it or remove it.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 349 Rust production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (Rust: the log and tracing crates (info!/warn!/error!, #[instrument]), slog, env_logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
X12 · Unreachable branch · Statement is unreachable · ×1
  • Statement is unreachable — control never gets past the statement before it crates/cdj3k-emu-runtime/src/elevate/windows.rs:40 — `let process = info.hProcess;` follows `{ return Err(if e.code() == ERROR_CANCELLED.to_hresult() { io::Error::new(io:…` (line 30) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap crates/cdj3k-emu-platform/src/menu/egui_provider/panel.rs:31 — `panel` is public and takes `nodes: &[MenuNode]` from its caller, and it recurses at line 31 through `submenu_row`, `node` and back with a piece of the document (and at line 91, line 128) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `panel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Minor — 14 finding(s)
X7 · Silent fallback defaults · Silent fallback default on Err · ×3
  • Silent fallback default on Err crates/cdj3k-emu-platform/src/net/linux.rs:43 — `bridgeable_without_address` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/cdj3k-emu-runtime/src/net/tapbridge.rs:40 — `djpl_bridge` turns every `Err` into `"bridge99".to_string()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/cdj3k-emu-runtime/src/net/windows_tap.rs:66 — `present_taps` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×2
  • Projects may be oversized for their cohesion crates/cdj3k-emu-ui/Cargo.toml:1 — `crates/cdj3k-emu-ui` (30443 LoC, 120 module-visible types across 22 directories) overshoots its size bounds. 2 of 10 build unit(s) (Cargo) overshoot their size bounds, lowering Project Cohesion to 6.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion crates/cdj3k-emu-platform/Cargo.toml:1 — `crates/cdj3k-emu-platform` (9729 LoC, 110 module-visible types across 14 directories) overshoots its size bounds. 2 of 10 build unit(s) (Cargo) overshoot their size bounds, lowering Project Cohesion to 6.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate crates/cdj3k-emu-ui/src/app/shell/setup.rs:87 — `first_frame || (root.content_rect().size() - size).length() > 1.0` appears character-identically in 2 files — crates/cdj3k-emu-ui/src/app/shell/setup.rs, crates/cdj3k-emu-ui/src/app/updater/mod.rs. 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 crates/cdj3k-emu-platform/src/desktop/frame_store.rs:81 — `v.maximized == Some(true) || v.fullscreen == Some(true)` appears character-identically in 2 files — crates/cdj3k-emu-platform/src/desktop/frame_store.rs, crates/cdj3k-emu-platform/src/desktop/mod.rs. 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.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found app/cdj3k-emu/Cargo.toml:11 — 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 `app/cdj3k-emu/Cargo.toml` makes this repository a deployable product (line 11).
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation app/cdj3k-emu/Cargo.toml:15 — `app/cdj3k-emu/Cargo.toml` 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`.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
Minor — 11 finding(s)
D12 · Dependency Hygiene · Outdated · ×11
  • Outdated: bytemuck — `bytemuck` is locked at 1.25.0 but 1.25.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/cdj3k-emu-ui/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytemuck` and commit the updated REDACTED.
  • Outdated: ed25519-compact — `ed25519-compact` is locked at 2.6.0 but 2.6.1 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/cdj3k-emu-update/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ed25519-compact` and commit the updated REDACTED.
  • Outdated: flate2 — `flate2` is locked at 1.1.9 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/cdj3k-emu-firmware/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
  • Outdated: getrandom — `getrandom` is locked at 0.4.2 but 0.4.3 is the current stable release on crates.io, and it already satisfies the `"0.4.2"` requirement declared in crates/cdj3k-emu-firmware/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p getrandom` and commit the updated REDACTED.
  • Outdated: libc — `libc` is locked at 0.2.186 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in app/cdj3k-emu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
  • Outdated: memmap2 — `memmap2` is locked at 0.9.10 but 0.9.12 is the current stable release on crates.io, and it already satisfies the `"0.9"` requirement declared in crates/cdj3k-emu-streams/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p memmap2` and commit the updated REDACTED.
  • Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/cdj3k-emu-update/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
  • Outdated: serde_json — `serde_json` is locked at 1.0.149 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/cdj3k-emu-control/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
  • Outdated: tar — `tar` is locked at 0.4.45 but 0.4.46 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in crates/cdj3k-emu-firmware/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tar` and commit the updated REDACTED.
  • Outdated: ureq — `ureq` is locked at 3.4.2 but 3.5.2 is the current stable release on crates.io, and it already satisfies the `"3.4"` requirement declared in crates/cdj3k-emu-update/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ureq` and commit the updated REDACTED.
  • Outdated: uuid — `uuid` is locked at 1.23.1 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/cdj3k-emu-storage/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-99c59eb5baa247bda3c778281afaf82b/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-99c59eb5baa247bda3c778281afaf82b/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .56artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .17artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .25artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1e561-6612-7e67-b06f-4a57385375d9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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