wasmerio/wasmer

Executive summary

wasmerio/wasmer falls short of our standard for production because we found no access checks on the code's endpoints or handlers and it has pipeline tools referenced by a changeable name. It scores 46 out of 100 and is rated Weak, and 143 of its 159 critical findings are security problems.

Security and Compliance, at 35, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 8 points. Adding text alternatives comes next, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 54.

Ninety-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eighteen secrets can leak from the build pipeline, and ten pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Fixing the weaknesses the scanner points to would fix the eight security weaknesses in the code, and the six unsafe settings in infrastructure or container files need changing to safe values. The seven parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.

The product code is 275,299 lines, about €270,000 to rebuild.

Code Health 68 Adequate, capped by Structured logging Architecture 86 Strong Maturity 62 Adequate Production Readiness 78 Strong Security and Compliance 35 Weak, capped by Static Analysis (SAST), Supply-chain Provenance & Signing and Access Controls Event Sourcing 100 ★ Exemplary Accessibility 36 Weak, capped by Text alternatives and Page structure Performance 94 ★ Exemplary

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.

Security and Compliance 35 · counts for 45%Accessibility 36 · counts for 25%Maturity 62 · counts for 14%Code Health 68 · counts for 8%Production Readiness 78 · counts for 4%Architecture 86 · counts for 2%Performance 94 · counts for 1%Event Sourcing 100 · counts for 1%

If Security and Compliance rose from 35 to 70, the lowest score rated Strong, the score would rise from 46 to about 54.

Code composition: what the lines of code are

Product code 91%Tests 9%

New since the last survey: 447 findings

These 447 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-llvm/src/translator/intrinsics.rs
Code Duplication · Duplicated block (5 lines × 2) lib/api/src/utils/polyfill.rs
Churn × Complexity Hotspots · Hotspot: lib/cli/src/commands/app/deploy.rs lib/cli/src/commands/app/deploy.rs
Churn × Complexity Hotspots · Hotspot: lib/cli/src/commands/app/create.rs lib/cli/src/commands/app/create.rs
Churn × Complexity Hotspots · Hotspot: lib/compiler/src/translator/module.rs lib/compiler/src/translator/module.rs
Boundary Type-Coupling · Cross-context type FunctionType (types → api) lib/api/src/backend/js/entities/function/mod.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/backend/js/entities/memory/mod.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/backend/js/entities/memory/view.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/handle.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/handle.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/handle.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type Iter (types → api) lib/api/src/backend/js/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/backend/sys/entities/memory/view.rs
Boundary Type-Coupling · Cross-context type FunctionType (types → api) lib/api/src/backend/v8/entities/function/mod.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/backend/v8/entities/memory/mod.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/backend/v8/entities/memory/view.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type Iter (types → api) lib/api/src/backend/v8/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type IntoIter (types → api) lib/api/src/entities/exports.rs
Boundary Type-Coupling · Cross-context type IntoIter (types → api) lib/api/src/entities/exports.rs
Boundary Type-Coupling · Cross-context type FunctionType (types → api) lib/api/src/entities/function/mod.rs
Boundary Type-Coupling · Cross-context type IntoIter (types → api) lib/api/src/entities/imports.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/entities/memory/mod.rs
Boundary Type-Coupling · Cross-context type Pages (types → api) lib/api/src/entities/memory/view/mod.rs
Boundary Type-Coupling · Cross-context type StoreId (types → api) lib/api/src/entities/store/obj.rs
Boundary Type-Coupling · Cross-context type Iter (types → api) lib/api/src/utils/mem/access.rs
Boundary Type-Coupling · Cross-context type IterMut (types → api) lib/api/src/utils/mem/access.rs
Boundary Type-Coupling · Cross-context type ExportsIterator (api → types) lib/types/src/module.rs
Boundary Type-Coupling · Cross-context type ImportsIterator (api → types) lib/types/src/module.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/bin_factory/mod.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/memory_and_snapshot.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/memory_and_snapshot.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/process_exit.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/chdir.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/chdir.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/clock_time.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/clock_time.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_create.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_create.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_ctl.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_ctl.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_advise.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_advise.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_allocate.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_allocate.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_close.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_close.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_duplicate.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_duplicate.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_event.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_event.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_pipe.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_pipe.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_renumber.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_renumber.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_seek.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_seek.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_fdflags.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_fdflags.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_flags.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_flags.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_rights.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_rights.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_size.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_size.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_times.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_set_times.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_write.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_write.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_create_directory.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_create_directory.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_link.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_link.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_open.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_open.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_remove_directory.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_remove_directory.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_rename.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_rename.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_set_times.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_set_times.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_symlink.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_symlink.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_unlink.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/path_unlink.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_addr_add.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_addr_add.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_addr_clear.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_addr_clear.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_addr_remove.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_addr_remove.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_bridge.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_bridge.rs
Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/port_dhcp_acquire.rs

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 15 findings

These 15 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one.

Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-llvm/src/translator/intrinsics.rs
Code Duplication · Duplicated block (11 lines × 2) lib/api/src/utils/polyfill.rs
Churn × Complexity Hotspots · Hotspot: lib/compiler-llvm/src/object_file.rs lib/compiler-llvm/src/object_file.rs
Churn × Complexity Hotspots · Hotspot: lib/compiler-cranelift/src/eh.rs lib/compiler-cranelift/src/eh.rs
Boundary Type-Coupling · Cross-context type FunctionType (types → api)
Boundary Type-Coupling · Cross-context type Pages (types → api)
Boundary Type-Coupling · Cross-context type Pages (types → api)
Boundary Type-Coupling · Cross-context type StoreId (types → api)
Boundary Type-Coupling · Cross-context type StoreId (types → api)
Boundary Type-Coupling · Cross-context type StoreId (types → api)
Boundary Type-Coupling · Cross-context type StoreId (types → api)
Boundary Type-Coupling · Cross-context type StoreId (types → api)
Supply-chain Provenance & Signing · Dependency source pinned to a moving git ref
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED

Rebuild cost: about €270,000 · Estimate

Cost to rebuild	€89,000 to €450,000, for 1,485 to 4,711 hours of work, about 1.8 person-years for 1 to 4 engineers
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 46. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Large: 275,299 lines of product code
What it is not	Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: Watchdog prices 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.

Raises the score by about 8 points · Medium effort · Access Controls

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Raises the score by about 5 points · Medium effort · Text alternatives

Resolve the 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 2 points · Low effort · ADR Quality

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €270,000 to build again, about 1.8 person-years of work. Its weakest lens is Security and Compliance, at 35 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.

Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts

What to do: Start with the Security and Compliance actions in Top priorities.

If you do one thing first · First action

Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. Of all the actions in this report, it raises the score most for the work it takes: about 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

What hard-to-read code costs each year · Cost

Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.8 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 29,330 lines over the last 90 days, which is about 118,949 lines a year. At that pace, the extra work comes to an estimated 8.7 to 52.1 engineer-days a year, and it grows as more code changes.

How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.

Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history

What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

Architecture: which parts of the code depend on which

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

813 modules, with 2505 dependencies between them. 10 loops run through 172 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 773 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 virtual_fs	3 wasmer_cli.commands	4 wasmer_cli.config.env	6 wasmer_types.entity.primary_map	7 wasmer_types.indexes	8 wasmer_types.progress	9 wasmer_types.units	10 virtual_fs.host_fs	11 wasmer.backend.js.entities.store.obj	12 wasmer.entities.exports	13 wasmer_wasix_types.wasi.wasix_manual	14 wasmer.backend.js.entities.store.handle	15 wasmer.entities.store.store_ref	16 wasmer_wasix.fs	17 wasmer.backend.js.entities.function.env	18 wasmer_wasix_types.wasi.bindings	19 wasmer_types.types	20 wasmer.backend.js.entities.memory	21 wasmer.entities.external	22 wasmer.backend.js.vm.external	23 wasmer.entities.imports	24 wasmer.backend.js.entities.function	25 wasmer_types.module	26 wasmer.backend.js.entities.module	27 wasmer.entities.value	28 wasmer.backend.js.entities.instance	29 wasmer_backend_api.types.queries	30 wasmer_backend_api.client	32 wasmer_vm.instance	34 wasmer_cli.commands.add	36 wasmer.backend.js.entities.engine	37 wasmer_compiler.compiler	39 wasmer_compiler.engine.inner
1 virtual_fs
2 wasmer.utils.mem.ptr
3 wasmer_cli.commands
4 wasmer_cli.config.env
5 wasmer_journal.entry
6 wasmer_types.entity.primary_map
7 wasmer_types.indexes
8 wasmer_types.progress
9 wasmer_types.units
10 virtual_fs.host_fs	8						1
11 wasmer.backend.js.entities.store.obj												1
12 wasmer.entities.exports																			3
13 wasmer_wasix_types.wasi.wasix_manual																9
14 wasmer.backend.js.entities.store.handle									2
15 wasmer.entities.store.store_ref									3																						2
16 wasmer_wasix.fs	4							2								8														1
17 wasmer.backend.js.entities.function.env									2			1	10
18 wasmer_wasix_types.wasi.bindings											1			4			1
19 wasmer_types.types							1									1
20 wasmer.backend.js.entities.memory							2										1			1
21 wasmer.entities.external										1							1	1		1		1
22 wasmer.backend.js.vm.external																			2
23 wasmer.entities.imports										1									1					1
24 wasmer.backend.js.entities.function													1		1		3			1					1
25 wasmer_types.module				2	12					1							2				1
26 wasmer.backend.js.entities.module							1			1							2				2		1			1
27 wasmer.entities.value																	1					1
28 wasmer.backend.js.entities.instance																					1			1
29 wasmer_backend_api.types.queries																									1
30 wasmer_backend_api.client																											1
31 wasmer_config.package.package_source																											1
32 wasmer_vm.instance					14		1		4			1					1			1	2		3			2
33 wasmer_wasix.state.env											1			2	1	1	1	1						1		1
34 wasmer_cli.commands.add		1	1																								2	2
35 wasmer_cli.commands.app.util			1																									2
36 wasmer.backend.js.entities.engine						1																								1
37 wasmer_compiler.compiler				2		1		1															1							3
38 wasmer_compiler_singlepass.machine					2	2											2								1					1
39 wasmer_compiler.engine.inner				1		1		1									1						1							1		1
40 wasmer_compiler.engine.artifact				3	2	1		2	1								1						2						1	1	1		1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 68% · Adequate · gated by X4 ·

The Good

D3 · Rust God Classes 8.1 D4 · Rust Code Duplication 8.5 D17 · Rust Explicit Debt 9.7 X1 · Repo Async correctness 8.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

D2 · Rust Cognitive Complexity 5.1

The Ugly

D1 · Rust Cyclomatic Complexity 4.5 X4 · Repo Structured logging 4.0

At a glance — Architecture · 86% · Strong ·

The Good

D5 · Rust Coupling 8.6 D6 · Rust Cohesion (LCOM4) 9.2 D35 · Rust Change Coupling 9.6 AX10 · Repo Code composition 9.5 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX8 · Repo Test isolation 7.5 AX9 · Repo CQS / query purity 10.0

The Bad

D23 · Rust Boundary Type-Coupling 6.6 D26 · Rust Project Cohesion 5.7

At a glance — Maturity · 62% · Adequate ·

The Good

D15 · Rust Churn × Complexity Hotspots 8.7 D16 · Rust Bus Factor 9.1 D19 · Rust Documentation Quality 10.0 D34 · Rust Knowledge Freshness 7.4 M1 · Repo Documentation (README) 7.9 M3 · Repo Folder & project structure 10.0

The Bad

M2 · Repo Architecture documentation 5.0

The Ugly

D20 · Rust ADR Quality 0.0 M4 · Repo Documentation accuracy 4.0

At a glance — Readiness · 78% · Strong ·

The Good

D9 · Rust Test Distribution 10.0 D12 · Rust Dependency Hygiene 9.7 D13 · Rust Secret Scanning 10.0 D14 · Rust License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 7.0 P6 · Repo Release Hygiene 10.0

The Bad

P2 · Repo Observability 6.7 P3 · Repo Security & performance tooling 6.0

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

The Good

D28 · Rust Secrets (history) 10.0 D30 · Rust Dependency Vulnerabilities 8.5 D31 · Rust IaC & Container Security 7.7 D37 · Rust Vulnerability-disclosure Policy 10.0 D43 · Rust Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D44 · Rust Platform End-of-Life 6.0 S1 · Repo Web-Security Posture 6.0

The Ugly

D29 · Rust Static Analysis (SAST) 0.0 D36 · Rust Supply-chain Provenance & Signing 0.0 C2 · Repo Access Controls 0.0

At a glance — Event Sourcing · 100% · Exemplary ·

The Good

ES1 · Repo Fold determinism 10.0 ES2 · Repo Immutable events 10.0

At a glance — Accessibility · 36% · Weak · gated by AC1, AC3 ·

The Good

AC6 · Repo Visual & motion safety 10.0

The Ugly

AC1 · Repo Text alternatives 1.0 AC2 · Repo Forms & labels 4.8 AC3 · Repo Page structure 3.5 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 94% · Exemplary ·

The Good

PF1 · Repo Benchmark discipline 9.0 PF3 · Repo Async & latency hygiene 10.0

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 category	Findings	Severity
A05:2025 — Injection	149	High / Critical
A03:2025 — Software Supply Chain Failures	26	Medium
A02:2025 — Security Misconfiguration	9	High / Critical

Roadmap

First, secure the application by implementing a global authentication guard with explicit role-based permissions and ensuring all server traffic is served over TLS with proper HSTS headers. Next, improve accessibility by adding text alternatives for all media elements and ensuring the page structure includes proper language declarations, titles, and semantic landmarks. Finally, enforce these accessibility standards by integrating automated checks into the existing UI test suite and gating merges on CI to prevent regressions.

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

Do this	Helps	Effort	Dimension
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.	+7.9 pts	Medium	Access Controls
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.	+4.5 pts	Medium	Text alternatives
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+2.1 pts	Low	ADR Quality
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml.	+1.4 pts	Low	Platform End-of-Life
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.	+2.7 pts	Medium	Web-Security Posture
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.	+2.5 pts	Medium	Page structure
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.	+2.2 pts	Medium	A11y enforcement
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.	+1.8 pts	Medium	Forms & labels

File quality

Per-file score 0–10 — a quality signature. Of 525 files carrying findings, judged against the Production bar: 2% slop · 59% mixed · 39% near-clean.

File	Score	Band	Worst signal
REDACTED	0.2	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	0.5	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	0.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	1.6	Slop	Static Analysis (SAST): High: REDACTED
lib/compiler-llvm/src/translator/code.rs	1.6	Slop	Change Coupling: Boundary-crossing change coupling: code.rs ↔ tunables.rs
REDACTED	2.0	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.4	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.0	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.0	Slop	IaC & Container Security: High IaC: REDACTED
lib/compiler-cranelift/src/config.rs	4.3	Mixed	Change Coupling: Boundary-crossing change coupling: config.rs ↔ config.rs
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
lib/compiler/src/translator/environ.rs	4.7	Mixed	Change Coupling: Boundary-crossing change coupling: environ.rs ↔ mod.rs
REDACTED	4.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): High: REDACTED
lib/api/src/backend/v8/entities/function/mod.rs	4.8	Mixed	Code Duplication: Near-duplicate member pair (34 shared lines)
lib/wasix/src/syscalls/wasix/sock_send.rs	4.8	Mixed	Code Duplication: Near-duplicate member pair (47 shared lines)
lib/wasix/src/syscalls/wasi/path_rename.rs	4.8	Mixed	Cyclomatic Complexity: wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal (cyclomatic 31)
lib/wasix/src/syscalls/wasi/poll_oneoff.rs	5.1	Mixed	Cyclomatic Complexity: wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal (cyclomatic 31)
lib/api/src/backend/js/entities/store/handle.rs	5.1	Mixed	Code Duplication: Duplicated block (6 lines × 3)

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

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

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

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

Could not be resolved — 12

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

Watchdog 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. 74 of 74 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 74 dimensions across the health lenses

D1D2D3D4D5D6D9D12D13D14D15D16D17D19D20D23D26D28D29D30D31D34D35D36D37D43D44AC1AC2AC3AC6AC7AX10AX3AX4AX8AX9C2ES1ES2M1M2M3M4P1P10P2P3P4P6PF1PF3S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X26X27X28X29X3X30X4

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17689-b662-7c50-89b9-d011ab7611a4.

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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog 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, 222 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.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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.
D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog 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 on C# first (docs/plans/deterministic-engine.md, P5): 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 — Watchdog 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 — Watchdog 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.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — -------------------- 1 | >>> FROM debian:stable AS openssl_riscv64 2 | #FROM ghcr.io/cross-rs/riscv64gc-unknown-linux-gnu:edge AS openssl_riscv64 3 | -------------------- ERROR: failed to solve: debian:stable: failed to resolve source metadata for docker.io/library/debian:stable: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/stable": Forbidden; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 360 further occurrence(s) are not listed individually; the score already reflects all 400.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Python, 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.

Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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 Complexity4.5 / 10Weak✓ 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 4.5 / 10 · rule-coverage 100% · ceiling Prevented

86 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was wasmer_compiler_cranelift::translator::code_translator::translate_operator at 403. A further 58 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being wasmer_parser_operator_t::from at 528 — they are counted neither in the figure above nor in this dimension's score. 20 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: lib/c-api/src/wasm_c_api/unstable/parser/operator.rs (wasmer_parser_operator_t::from at 528), lib/wasi-types/src/wasi/bindings.rs (SockProto::from_native at 265), lib/wasix/src/os/posix_err.rs (wasmer_wasix::os::posix_err::exit_code_to_message at 126), lib/types/src/libcalls.rs (LibCall::to_function_name at 89), lib/vm/src/libcalls.rs (wasmer_vm::libcalls::function_pointer at 89), and 15 more not listed here. 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.

wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth (cyclomatic 60) · ×10lib/wasix/src/syscalls/wasix/path_open2.rs:186

LLVMFunctionCodeGenerator::translate_integer_arithmetic_operator (cyclomatic 118) · ×8lib/compiler-llvm/src/translator/code.rs:4031

InodeSocket::bind_internal (cyclomatic 28) · ×6lib/wasix/src/net/socket.rs:309

wasmer_compiler_cranelift::translator::code_translator::translate_operator (cyclomatic 403) · ×3lib/compiler-cranelift/src/translator/code_translator.rs:157

FuncGen::feed_operator (cyclomatic 369) · ×2lib/compiler-singlepass/src/codegen.rs:1170

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

What to do

Bring the 3 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with wasmer_compiler_cranelift::translator::code_translator::translate_operator (cyclomatic 403), FuncGen::feed_operator (cyclomatic 369), RemoteNetworkingServerDriver::process_socket (cyclomatic 125). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 4.5 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity5.1 / 10Adequate✓ Tool-verified

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

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

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

156 method(s) exceeded the cognitive complexity threshold of 15; the worst was FuncGen::feed_operator at 228.

wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal (cognitive 128) · ×21lib/wasix/src/syscalls/wasi/fd_write.rs:243

LLVMFunctionCodeGenerator::translate_basic_operator (cognitive 83) · ×7lib/compiler-llvm/src/translator/code.rs:3217

wasmer_compiler::object::module::emit_compilation (cognitive 39) · ×6lib/compiler/src/object/module.rs:139

wasmer_compiler_cranelift::translator::code_translator::translate_operator (cognitive 87) · ×5lib/compiler-cranelift/src/translator/code_translator.rs:157

InodeSocket::bind_internal (cognitive 53) · ×5lib/wasix/src/net/socket.rs:309

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

What to do

Bring the 4 bodies over 120 down to 120 or less in Cognitive Complexity — start with FuncGen::feed_operator (cognitive 228), JournalSyscallPlayer::play_event (cognitive 137), make-release.make_release (cognitive 132). — 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 4 together lifts Cognitive Complexity from 5.1 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.1 / 10Strong✓ Tool-verified

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

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

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

226 god class(es) detected.

MethodTooLong: FuncGen.feed_operator · ×70lib/compiler-singlepass/src/codegen.rs:1170

FileTooLong: translator/code.rs · ×62lib/compiler-llvm/src/translator/code.rs

FunctionTooLong: wasmer_compiler_cranelift::translator::code_translator::translate_operator · ×39lib/compiler-cranelift/src/translator/code_translator.rs:157

ClassTooLong: LLVMFunctionCodeGenerator · ×37lib/compiler-llvm/src/translator/code.rs:2517

TooManyMethods: JournalEffector · ×16lib/wasix/src/journal/effector/mod.rs:104

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

What to do

Resolve the 70 MethodTooLong finding(s) in God Classes — start with code.rs (15), mod.rs (5), machine_arm64.rs (4). — One of this dimension's main actionable groups (70 warning-level).
Resolve the 62 FileTooLong finding(s) in God Classes — start with mod.rs (10), lib.rs (3), compiler.rs (2). — One of this dimension's main actionable groups (62 warning-level).
Resolve the 39 FunctionTooLong finding(s) in God Classes — start with emitter_arm64.rs (3), emitter_riscv.rs (3), code_translator.rs (2). — One of this dimension's main actionable groups (39 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication8.5 / 10Strong✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

844 duplicated block group(s) detected. A further 44 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 888 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (5 lines × 2) · ×70lib/api/src/backend/sys/entities/function/mod.rs:871

Duplicated block (7 lines × 2) · ×52lib/api/src/backend/js/entities/function/typed.rs:176

Duplicated block (9 lines × 2) · ×50lib/api/src/backend/sys/entities/function/mod.rs:73

Duplicated block (10 lines × 2) · ×45lib/api/src/backend/js/entities/function/mod.rs:378

Duplicated block (6 lines × 2) · ×40lib/api/src/backend/js/entities/function/mod.rs:314

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

What to do

Resolve the 70 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with code.rs (12), arc_box_file.rs (10), machine_arm64.rs (7). — One of this dimension's main actionable groups (70 warning-level).
Resolve the 52 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with code.rs (7), machine_x64.rs (6), memories.rs (5). — One of this dimension's main actionable groups (52 warning-level).
Resolve the 50 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with machine_arm64.rs (10), mod.rs (5), code.rs (5). — One of this dimension's main actionable groups (50 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling8.6 / 10Strong✓ Tool-verified

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

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

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

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

31 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 25 of the 31 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: wasmer-config · ×4

Unstable project wasmer-journal

What to do

Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Unstable project wasmer-journal finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.2 / 10Stronggated by 29 serious findings✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Verified

29 of 421 classes have LCOM4 above 3.

Low cohesion: AssemblerX64 (LCOM4 64) · ×29lib/compiler-singlepass/src/machine_x64.rs:39

What to do

Resolve the 29 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (7), module.rs (3), table.rs (3). — One of this dimension's main actionable groups (29 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

1106 test methods: 912 unit, 194 integration, 0 BDD, 0 e2e. The Rust suite contributes 1106 `#[test]` function(s) across 222 file(s) declaring at least one; its unit/integration split is Cargo's own — 36 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene~~9.8~~ 9.7 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

5 outdated, 0 yanked direct Cargo dependencies. 199 of 200 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: cc · ×5

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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 750 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, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: lib/compiler-singlepass/src/codegen.rs (16×369=5904); lib/compiler-cranelift/src/translator/code_translator.rs (5×403=2015); lib/compiler-llvm/src/translator/code.rs (18×66=1188) Repeated repair below the complexity floor: lib/wasix/src/bin_factory/mod.rs (7 of 9 changes were fixes); lib/wasix/src/state/env.rs (6 of 8 changes were fixes); lib/compiler-singlepass/src/machine_x64.rs (5 of 7 changes were fixes)

Hotspot: lib/compiler-singlepass/src/codegen.rs · ×20lib/compiler-singlepass/src/codegen.rs:1170

Repeated repair: lib/wasix/src/bin_factory/mod.rs · ×7lib/wasix/src/bin_factory/mod.rs:210

What to do

Resolve the 20 Hotspot finding(s) in Churn × Complexity Hotspots — start with compiler.rs (3), module.rs (2), codegen.rs. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 7 Repeated repair finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), env.rs, machine_x64.rs. — One of this dimension's main actionable groups (7 warning-level).

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

Do you agree with this assessment?

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

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

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

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

53 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/compiler-singlepass/src/machine_x64.rs. Counted over 567 of the 977 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×3

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

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

TodoComment · ×368tests/lib/wast/src/wast.rs:409

FixmeComment · ×39tests/integration/cli/tests/snapshot.rs:960

HackComment · ×12lib/wasix/src/state/linker/linker_state.rs:39

What to do

Resolve the 368 TodoComment finding(s) in Explicit Debt — start with mod.rs (57), bindings.rs (55), bindings_manual.rs (15). — One of this dimension's main actionable groups (368 warning-level).
Resolve the 39 FixmeComment finding(s) in Explicit Debt — start with mod.rs (4), compiler_builtins.rs (4), func_env.rs (3). — One of this dimension's main actionable groups (39 warning-level).
Resolve the 12 HackComment finding(s) in Explicit Debt — start with mod.rs (2), linker_state.rs, load_package_tree.rs. — One of this dimension's main actionable groups (12 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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. 54 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

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

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

Do you agree with this assessment?

D23 · Boundary Type-Coupling6.6 / 10Adequate✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

473 domain type(s) cross context boundaries across 3 contexts.

Cross-context type FunctionEnvMut (api → wasix) · ×305lib/wasix/src/bin_factory/mod.rs:190

Cross-context type Module (api → wasix) · ×36lib/wasix/src/runners/wasi.rs:352

Cross-context type ModuleHash (types → wasix) · ×27lib/wasix/src/bin_factory/binary_package.rs:46

Cross-context type StoreMut (api → wasix) · ×16lib/wasix/src/runtime/mod.rs:123

Cross-context type StoreId (types → api) · ×14lib/api/src/backend/js/entities/store/handle.rs:75

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

What to do

Resolve the 305 Cross-context type FunctionEnvMut (api → wasix) finding(s) in Boundary Type-Coupling — start with mod.rs (20), epoll_create.rs (4), fd_event.rs (4). — One of this dimension's main actionable groups (305 warning-level).
Resolve the 36 Cross-context type Module (api → wasix) finding(s) in Boundary Type-Coupling — start with mod.rs (22), func_env.rs (3), builder.rs (2). — One of this dimension's main actionable groups (36 warning-level).
Resolve the 27 Cross-context type ModuleHash (types → wasix) finding(s) in Boundary Type-Coupling — start with types.rs (5), binary_package.rs (3), fallback.rs (3). — One of this dimension's main actionable groups (27 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D26 · Project Cohesion5.7 / 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, LLM-independent.

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

6 of 27 build units (Cargo) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

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

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

149 finding(s): 0 critical, 137 high, 12 medium, 0 low. 92 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 7 file(s) — `REDACTED` (line 55, line 56, line 57, …), `REDACTED` (line 12), `lib/c-api/examples/early-exit.c`, `REDACTED` (line 11), `lib/c-api/examples/wasi.c` (line 105), … (+2 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 6 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

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

What to do

Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
No action in Static Analysis (SAST) — all 92 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (92 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities8.5 / 10Strong✓ 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.

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security7.7 / 10Adequategated by 6 critical findings✓ 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 7.7 / 10 · rule-coverage 100% · ceiling Documented

9 finding(s): 0 critical, 6 high, 3 medium, 0 low.

REDACTED

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge Freshness7.4 / 10Adequategated by 7 critical findings✓ 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 7.4 / 10 · rule-coverage 100% · ceiling Documented

139 of 567 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/journal/src/concrete/archived.rs. Counted over 567 of the 977 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×7lib/journal/src/concrete/archived.rs:1

Orphaned file · ×132lib/journal/src/concrete/log_file.rs:1

Further orphaned files (smaller)

What to do

Resolve the 132 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (11), instance.rs (5), inner.rs (4). — One of this dimension's main actionable groups (132 recommendation-level).
Resolve the 7 Orphaned knowledge finding(s) in Knowledge Freshness — start with archived.rs, play_event.rs, operator.rs. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling9.6 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: filesystem_source.rs↔web_source.rs 82%; inspect.rs↔validate.rs 80%; sock_send.rs↔sock_send_to.rs 77%

Boundary-crossing change coupling: environ.rs ↔ mod.rs · ×3lib/compiler/src/translator/environ.rs:1

Change coupling: filesystem_source.rs ↔ web_source.rs · ×18lib/wasix/src/runtime/resolver/filesystem_source.rs:1

Change-coupling hub: proc_fork.rs → proc_exit.rs, stack_checkpoint.rs, thread_spawn.rs · ×3lib/wasix/src/syscalls/wasix/proc_fork.rs

Change coupling clique: context_create.rs, context_destroy.rs, context_switch.rslib/wasix/src/syscalls/wasix/context_create.rs

What to do

Resolve the 3 Boundary-crossing change coupling finding(s) in Change Coupling — start with environ.rs, config.rs, code.rs. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 18 Change coupling finding(s) in Change Coupling — start with exec.rs (2), filesystem_source.rs, inspect.rs. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with proc_fork.rs, mod.rs, fd_write.rs. — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

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

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

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

A vulnerability-disclosure policy (docs/SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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. Scored 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. SCORED, not informational.

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.

Do you agree with this assessment?

D44 · Platform End-of-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

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

End-of-life runtime: Rust 1.96rust-toolchain.toml:1

What to do

Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified

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

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

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

An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — lib/cli/src/utils/package_wizard/templates/static-site/index.html:422, lib/cli/src/utils/package_wizard/templates/static-site/index.html:442

What to do

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Do you agree with this assessment?

AC2 · Forms & labels4.8 / 10Weak✓ Tool-verified

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

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

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

A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — lib/cli/src/utils/package_wizard/templates/static-site/index.html:332

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure3.5 / 10Weak✓ Tool-verified

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

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

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

The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — lib/cli/src/utils/package_wizard/templates/static-site/index.html:1
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — lib/cli/src/utils/package_wizard/templates/static-site/index.html:3

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.

Do you agree with this assessment?

AX10 · Code composition9.5 / 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.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

AX8 · Test isolation7.5 / 10Strong✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

`wasmer-workspace` (production) references the test project `test-generator`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

What to do

Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.

Do you agree with this assessment?

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.

Do you agree with this assessment?

C2 · Access Controls0.0 / 10Critical✓ Tool-verified

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

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

This repository serves requests — a server (.serve_connection) (lib/cli/src/commands/auth/login/mod.rs:132) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — lib/cli/src/commands/auth/login/mod.rs:132

What to do

Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

M1 · Documentation (README)7.9 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 11 of 29 project(s) that lack one — worth up to 0.8 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ 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.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

Do you agree with this assessment?

M4 · Documentation accuracy4.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

lib/c-api/README.md links to `./wasmer.hh`, but `lib/c-api/wasmer.hh` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — lib/c-api/README.md:202
lib/config/README.md links to `.github/workflows/release-please.yml`, but `lib/config/.github/workflows/release-please.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — lib/config/README.md:17
lib/wasix/tests/wasm_tests/README.md links to `../wasm_tests.rs`, but `lib/wasix/tests/wasm_tests.rs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — lib/wasix/tests/wasm_tests/README.md:31

What to do

Reconcile the README with reality: lib/c-api/README.md links to `./wasmer.hh`, but `lib/c-api/wasmer.hh` does not exist; lib/config/README.md links to `.github/workflows/release-please.yml`, but `lib/config/.github/workflows/release-please.yml` does not exist; lib/wasix/tests/wasm_tests/README.md links to `../wasm_tests.rs`, but `lib/wasix/tests/wasm_tests.rs` does not exist.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language 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.

Do you agree with this assessment?

P2 · Observability6.7 / 10Adequate✓ 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.

Only 16/18 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `lib/config`.

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.

Do you agree with this assessment?

P3 · Security & performance tooling6.0 / 10Adequate✓ 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.

What to do

Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

PF1 · Benchmark discipline9.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

Do you agree with this assessment?

S1 · Web-Security Posture6.0 / 10Adequate✓ 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 HTTP itself (`.serve_connection(` (lib/cli/src/commands/auth/login/mod.rs:132)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.

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.

This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `.serve_connection(` (lib/cli/src/commands/auth/login/mod.rs:132).
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (lib/cli/src/commands/auth/login/mod.rs:132).

What to do

Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.

Do you agree with this assessment?

X1 · Async correctness8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`. — lib/backend-api/src/query.rs:2356

What to do

Blocking `thread::sleep` inside an `async` body

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

X4 · Structured logging4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

`warn!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/utils/mod.rs:44
`debug!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:391
`trace!` at line 469 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:469
`warn!` at line 778 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:778
`warn!` at line 811 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:811
`warn!` at line 824 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:824
`trace!` at line 1109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:1109
`warn!` at line 1198 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:1198
`trace!` at line 1243 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:1243
`trace!` at line 1268 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:1268
`warn!` at line 1374 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:1374
`trace!` at line 1541 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/mod.rs:1541
`debug!` at line 41 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/windows.rs:41
`warn!` at line 21 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/callback_signal.rs:21
`error!` at line 25 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — lib/wasix/src/syscalls/wasix/chdir.rs:25, lib/wasix/src/syscalls/wasix/closure_allocate.rs:25
`trace!` at line 22 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_create.rs:22
`trace!` at line 36 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — lib/wasix/src/syscalls/wasix/context_create.rs:36, lib/wasix/src/syscalls/wasix/futex_wake_all.rs:36
`trace!` at line 40 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_destroy.rs:40
`trace!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_destroy.rs:48
`trace!` at line 62 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_destroy.rs:62
`trace!` at line 49 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_switch.rs:49
`trace!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_switch.rs:59
`trace!` at line 68 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_switch.rs:68
`trace!` at line 72 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_switch.rs:72
`trace!` at line 74 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/context_switch.rs:74
`error!` at line 29 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/epoll_create.rs:29
`error!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/epoll_ctl.rs:56
`trace!` at line 119 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/epoll_wait.rs:119
`warn!` at line 132 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/epoll_wait.rs:132
`error!` at line 34 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — lib/wasix/src/syscalls/wasix/fd_dup2.rs:34, lib/wasix/src/syscalls/wasix/fd_pipe.rs:34
`error!` at line 27 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/fd_fdflags_set.rs:27
`trace!` at line 164 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/futex_wait.rs:164
`trace!` at line 39 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/futex_wake.rs:39
`trace!` at line 42 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/futex_wake.rs:42
`trace!` at line 33 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/futex_wake_all.rs:33
`error!` at line 100 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/path_open2.rs:100
`error!` at line 30 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lib/wasix/src/syscalls/wasix/port_addr_add.rs:30

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	68%	Adequate — gated by X4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	86%	Strong	Solid.
Maturity	62%	Adequate	Acceptable, with room to improve.
Readiness	78%	Strong	Solid.
Security	35%	Weak — gated by D29, D36, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event Sourcing	100%	Exemplary	Strongest area.
Accessibility	36%	Weak — gated by AC1, AC3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	94%	Exemplary	Solid.

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 — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 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 — 44 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.

AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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 | >>> FROM debian:stable AS openssl_riscv64 2 | #FROM ghcr.io/cross-rs/riscv64gc-unknown-linux-gnu:edge AS openssl_riscv64 3 | -------------------- ERROR: failed to solve: debian:stable: failed to resolve source metadata for docker.io/library/debian:stable: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/stable": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in 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.
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 — ~25644 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
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 — Naming consistency is measured on C# only; JavaScript, Python, Rust not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (4 signals for this style, 3 needed — the count is met but a required primary signal is absent): 65 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 83 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a Rust domain-layer crate (a .../domain/ clean-architecture layer); a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; 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.
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.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 159 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
+ 67 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D34 · Knowledge Freshness · Orphaned knowledge · ×7

Orphaned knowledge lib/journal/src/concrete/archived.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/wasix/src/syscalls/journal/play_event.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/c-api/src/wasm_c_api/unstable/parser/operator.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/c-api/src/wasm_c_api/module.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge lib/journal/src/entry.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/middlewares/src/metering.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge lib/cli/src/commands/init.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.

D31 · IaC & Container Security · High IaC · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Boundary-crossing change coupling · ×3

Boundary-crossing change coupling: environ.rs ↔ mod.rs lib/compiler/src/translator/environ.rs:1 — `lib/compiler/src/translator/environ.rs` (context compiler) and `lib/vm/src/instance/mod.rs` (context vm) sit in DIFFERENT parts of the tree yet change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `fbeb9a63` fix(vm): share module passive data across instances instead of deep-c…; `75c34bc1` feat: use hash-based signature checks for indirect calls (#6293); `3641981e` feat: support Extended constant expressions WA feature (#6242) — run `git show` on any of them.
Boundary-crossing change coupling: config.rs ↔ config.rs lib/compiler-cranelift/src/config.rs:1 — `lib/compiler-cranelift/src/config.rs` (context compiler-cranelift) and `lib/compiler-llvm/src/config.rs` (context compiler-llvm) sit in DIFFERENT parts of the tree yet change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `9303735a` fix(Table): add resource allocation tracking for local Tables (#16); `27af3341` fix(deterministic_id): include all code-sensitive config flags (#6871); `1276e846` feat(experimental-artifact): replace Cargo feature with a config opti… — run `git show` on any of them.
Boundary-crossing change coupling: code.rs ↔ tunables.rs lib/compiler-llvm/src/translator/code.rs:1 — `lib/compiler-llvm/src/translator/code.rs` (context compiler-llvm) and `lib/compiler/src/engine/tunables.rs` (context compiler) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `9303735a` fix(Table): add resource allocation tracking for local Tables (#16); `aa495eb7` feat(MemoryStyle::static): adjust API and require mmap of 8GiB (#13) …; `eb0fcf69` feat(LLVM,Cranelift,Singlepass): fully support multi-memory WA propos… — run `git show` on any of them.

AC1 · Text alternatives · <img> without a text alternative · ×2

<img> without a text alternative lib/cli/src/utils/package_wizard/templates/static-site/index.html:422 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative lib/cli/src/utils/package_wizard/templates/static-site/index.html:442 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

AC2 · Forms & labels · Link with no accessible name · ×1

Link with no accessible name lib/cli/src/utils/package_wizard/templates/static-site/index.html:332 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.

AC3 · Page structure · <html> without a lang · ×1

<html> without a lang lib/cli/src/utils/package_wizard/templates/static-site/index.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

AC3 · Page structure · Viewport restricts zoom · ×1

Viewport restricts zoom lib/cli/src/utils/package_wizard/templates/static-site/index.html:3 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.

AX8 · Test isolation · Production project references a test project · ×1

Production project references a test project: wasmer-workspace → test-generator — `wasmer-workspace` (production) references the test project `test-generator`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

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 — 2371 finding(s)

D17 · Explicit Debt · TodoComment · ×368

TodoComment tests/lib/wast/src/wast.rs:409 — // // TODO: when memory64 merges into the proper spec then this should be — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/integration/cli/tests/publish.rs:27 — // <-- TODO! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/integration/cli/tests/publish.rs:89 — // <-- TODO! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/integration/cli/tests/snapshot.rs:73 — // TODO: show hash of code? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/integration/cli/tests/snapshot.rs:229 — // TODO: figure out why snapshot exit code is 79 on macos — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/integration/cli/tests/snapshot.rs:488 — // TODO: figure out why this hangs on Windows and Mac OS — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/compilers/issues.rs:461 — // TODO: the tests fails on RISC-V as the `j` instruction can reach only +- 1MiB offset. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/compilers/issues.rs:479 — // TODO: the tests fails on RISC-V as the `j` instruction can reach only +- 1MiB offset. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/compilers/issues.rs:770 — // TODO: V8 appears to handle this differently — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/compilers/traps.rs:122 — // TODO: Reenable this (disabled as it was not working with llvm/singlepass) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/compilers/traps.rs:362 — // TODO: Reenable this (disabled as it was not working with llvm/singlepass) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/compilers/wast.rs:113 — // TODO: remove once added for Cranelift — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/tests/wasm_tests/wasi_wast/path_rename.rs:52 — // TODO: add temp directory support for native execution... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/tests/wasm_tests/wasi_wast/path_rename.rs:131 — // TODO: add temp directory support for native execution... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/lib.rs:63 — // TODO: should this be pub? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/lib.rs:65 — // TODO: should this be pub? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/lib.rs:815 — // TODO: split function into two variants, one for JS and one for sys. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/utils/thread_parker.rs:51 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/mod.rs:92 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/mod.rs:99 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/mod.rs:107 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/handles/mod.rs:54 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/handles/mod.rs:80 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/handles/mod.rs:91 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment lib/wasix/src/state/handles/mod.rs:99 — // TODO: review allow... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
+ 343 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Cross-context type FunctionEnvMut (api → wasix) · ×305

Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/bin_factory/mod.rs:190 — FunctionEnvMut (context api) is exposed in wasix's public surface via BinFactory.try_built_in — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/memory_and_snapshot.rs:38 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_memory_and_snapshot — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/memory_and_snapshot.rs:202 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_compressed_memory — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/process_exit.rs:18 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_process_exit — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/chdir.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_chdir — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/chdir.rs:8 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_chdir — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/clock_time.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_clock_time_set — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/clock_time.rs:12 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_clock_time_set — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_create.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_epoll_create — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_create.rs:8 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_epoll_create — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_ctl.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_epoll_ctl — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/epoll_ctl.rs:22 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_epoll_ctl — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_advise.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_advise — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_advise.rs:22 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_fd_advise — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_allocate.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_allocate — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_allocate.rs:16 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_fd_allocate — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_close.rs:5 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_close — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_close.rs:9 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_fd_close — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_duplicate.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_duplicate — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_duplicate.rs:20 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_fd_duplicate — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_event.rs:6 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_event — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_event.rs:22 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_fd_event — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_pipe.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_pipe — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_pipe.rs:12 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.apply_fd_pipe — couples the contexts.
Cross-context type FunctionEnvMut (api → wasix) lib/wasix/src/journal/effector/syscalls/fd_renumber.rs:4 — FunctionEnvMut (context api) is exposed in wasix's public surface via JournalEffector.save_fd_renumber — couples the contexts.
+ 280 more in this group — see findings.md.

D3 · God Classes · MethodTooLong · ×70

MethodTooLong: FuncGen.feed_operator lib/compiler-singlepass/src/codegen.rs:1170 — MethodTooLong — feed_operator runs 3972 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3872 over it, 39.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_integer_arithmetic_operator lib/compiler-llvm/src/translator/code.rs:4031 — MethodTooLong — translate_integer_arithmetic_operator runs 1702 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1602 over it, 17.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_floating_point_arithmetic_operator lib/compiler-llvm/src/translator/code.rs:6146 — MethodTooLong — translate_floating_point_arithmetic_operator runs 1075 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 975 over it, 10.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_conversion_operator lib/compiler-llvm/src/translator/code.rs:8575 — MethodTooLong — translate_conversion_operator runs 976 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 876 over it, 9.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Intrinsics.declare lib/compiler-llvm/src/translator/intrinsics.rs:305 — MethodTooLong — declare runs 856 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 756 over it, 8.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_memory_operator lib/compiler-llvm/src/translator/code.rs:9871 — MethodTooLong — translate_memory_operator runs 831 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 731 over it, 8.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JournalSyscallPlayer.play_event lib/wasix/src/syscalls/journal/play_event.rs:7 — MethodTooLong — play_event runs 709 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 609 over it, 7.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_integer_comparison_operator lib/compiler-llvm/src/translator/code.rs:7450 — MethodTooLong — translate_integer_comparison_operator runs 624 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 524 over it, 6.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_basic_operator lib/compiler-llvm/src/translator/code.rs:3217 — MethodTooLong — translate_basic_operator runs 622 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 522 over it, 6.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_operator lib/compiler-llvm/src/translator/code.rs:12277 — MethodTooLong — translate_operator runs 556 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 456 over it, 5.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SockProto.fmt lib/wasi-types/src/wasi/bindings.rs:1668 — MethodTooLong — fmt runs 548 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 448 over it, 5.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: wasmer_parser_operator_t.from lib/c-api/src/wasm_c_api/unstable/parser/operator.rs:543 — MethodTooLong — from runs 532 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 432 over it, 5.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_atomic_memory_operator lib/compiler-llvm/src/translator/code.rs:10886 — MethodTooLong — translate_atomic_memory_operator runs 527 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 427 over it, 5.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JournalEntry.try_from lib/journal/src/concrete/archived_from.rs:654 — MethodTooLong — try_from runs 488 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 388 over it, 4.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JournalEntry.serialize_archive lib/journal/src/concrete/archived.rs:412 — MethodTooLong — serialize_archive runs 477 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 377 over it, 4.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CraneliftCompiler.compile_module_internal lib/compiler-cranelift/src/compiler.rs:107 — MethodTooLong — compile_module_internal runs 469 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 369 over it, 4.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_eh_operator lib/compiler-llvm/src/translator/code.rs:11684 — MethodTooLong — translate_eh_operator runs 378 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RemoteNetworkingServerDriver.process_socket lib/virtual-net/src/server.rs:860 — MethodTooLong — process_socket runs 346 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: JournalEntry.into_owned lib/journal/src/entry.rs:399 — MethodTooLong — into_owned runs 334 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 234 over it, 3.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CmdAppDeploy.run_async lib/cli/src/commands/app/deploy.rs:565 — MethodTooLong — run_async runs 324 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMCompiler.compile_module lib/compiler-llvm/src/compiler.rs:249 — MethodTooLong — compile_module runs 303 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 203 over it, 3.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FuncTranslator.translate_to_module lib/compiler-llvm/src/translator/code.rs:186 — MethodTooLong — translate_to_module runs 301 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 201 over it, 3.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LLVMFunctionCodeGenerator.translate_control_flow_operator lib/compiler-llvm/src/translator/code.rs:2786 — MethodTooLong — translate_control_flow_operator runs 297 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 197 over it, 2.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SinglepassCompiler.compile_module_internal lib/compiler-singlepass/src/compiler.rs:67 — MethodTooLong — compile_module_internal runs 289 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 189 over it, 2.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Artifact.from_parts_with_module_file lib/compiler/src/engine/artifact.rs:448 — MethodTooLong — from_parts_with_module_file runs 279 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
+ 45 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×70

Duplicated block (5 lines × 2) lib/api/src/backend/sys/entities/function/mod.rs:871 — lib/api/src/backend/sys/entities/function/mod.rs:871-875 | lib/api/src/backend/sys/entities/function/mod.rs:883-887 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/api/src/utils/polyfill.rs:517 — lib/api/src/utils/polyfill.rs:517-521 | lib/compiler/src/translator/sections.rs:310-314 — before extracting anything, compare `lib/api/src/utils/polyfill.rs` and `lib/compiler/src/translator/sections.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 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 (5 lines × 2) lib/c-api-imports/src/lib.rs:2176 — lib/c-api-imports/src/lib.rs:2176-2180 | lib/c-api/src/wasm_c_api/types/reference.rs:98-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/cli/src/commands/app/deploy.rs:1115 — lib/cli/src/commands/app/deploy.rs:1115-1119 | lib/cli/src/commands/run/wasi.rs:301-305 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1795 — lib/compiler-cranelift/src/func_environ.rs:1795-1799 | lib/compiler-cranelift/src/func_environ.rs:1835-1839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:215 — lib/compiler-cranelift/src/translator/code_translator.rs:215-219 | lib/compiler-cranelift/src/translator/code_translator.rs:233-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:1690 — lib/compiler-cranelift/src/translator/code_translator.rs:1690-1694 | lib/compiler-cranelift/src/translator/code_translator.rs:1698-1702 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:2138 — lib/compiler-cranelift/src/translator/code_translator.rs:2138-2142 | lib/compiler-cranelift/src/translator/code_translator.rs:2147-2151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:2886 — lib/compiler-llvm/src/translator/code.rs:2886-2893 | lib/compiler-llvm/src/translator/code.rs:2915-2919 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:5109 — lib/compiler-llvm/src/translator/code.rs:5109-5113 | lib/compiler-llvm/src/translator/code.rs:10474-10478 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:5545 — lib/compiler-llvm/src/translator/code.rs:5545-5549 | lib/compiler-llvm/src/translator/code.rs:5561-5565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:7412 — lib/compiler-llvm/src/translator/code.rs:7412-7416 | lib/compiler-llvm/src/translator/code.rs:7428-7432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:10023 — lib/compiler-llvm/src/translator/code.rs:10023-10027 | lib/compiler-llvm/src/translator/code.rs:10045-10049 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:10034 — lib/compiler-llvm/src/translator/code.rs:10034-10038 | lib/compiler-llvm/src/translator/code.rs:10056-10060 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:10079 — lib/compiler-llvm/src/translator/code.rs:10079-10083 | lib/compiler-llvm/src/translator/code.rs:10101-10105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:10090 — lib/compiler-llvm/src/translator/code.rs:10090-10094 | lib/compiler-llvm/src/translator/code.rs:10112-10116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/code.rs:10123 — lib/compiler-llvm/src/translator/code.rs:10123-10127 | lib/compiler-llvm/src/translator/code.rs:10699-10703 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/intrinsics.rs:415 — lib/compiler-llvm/src/translator/intrinsics.rs:415-420 | lib/compiler-llvm/src/translator/intrinsics.rs:430-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-llvm/src/translator/intrinsics.rs:1616 — lib/compiler-llvm/src/translator/intrinsics.rs:1616-1620 | lib/compiler-llvm/src/translator/intrinsics.rs:1652-1656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-singlepass/src/codegen.rs:1693 — lib/compiler-singlepass/src/codegen.rs:1693-1697 | lib/compiler-singlepass/src/codegen.rs:1732-1737 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:895 — lib/compiler-singlepass/src/machine_arm64.rs:895-899 | lib/compiler-singlepass/src/machine_x64.rs:347-351 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:900 — lib/compiler-singlepass/src/machine_arm64.rs:900-904 | lib/compiler-singlepass/src/machine_arm64.rs:928-932 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:923 — lib/compiler-singlepass/src/machine_arm64.rs:923-927 | lib/compiler-singlepass/src/machine_x64.rs:424-428 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2260 — lib/compiler-singlepass/src/machine_arm64.rs:2260-2264 | lib/compiler-singlepass/src/machine_riscv.rs:2619-2623 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:3033 — lib/compiler-singlepass/src/machine_riscv.rs:3033-3037 | lib/compiler-singlepass/src/machine_riscv.rs:4357-4361 — 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.
+ 45 more in this group — see findings.md.

D3 · God Classes · FileTooLong · ×62

FileTooLong: translator/code.rs lib/compiler-llvm/src/translator/code.rs — FileTooLong — 10258 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: LLVMFunctionCodeGenerator (3 blocks, 676-12889). The bar is 500 significant lines; this is 9758 over it, 20.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/machine_arm64.rs lib/compiler-singlepass/src/machine_arm64.rs — FileTooLong — 7029 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: MachineARM64 (3 blocks, 36-8494). The bar is 500 significant lines; this is 6529 over it, 14.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/machine_x64.rs lib/compiler-singlepass/src/machine_x64.rs — FileTooLong — 6800 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: MachineX86_64 (3 blocks, 94-8395). The bar is 500 significant lines; this is 6300 over it, 13.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/machine_riscv.rs lib/compiler-singlepass/src/machine_riscv.rs — FileTooLong — 5312 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: MachineRiscv (3 blocks, 76-6612). The bar is 500 significant lines; this is 4812 over it, 10.62× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/codegen.rs lib/compiler-singlepass/src/codegen.rs — FileTooLong — 4828 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 97% of them inside a single declaration: FuncGen (2 blocks, 93-6223). The bar is 500 significant lines; this is 4328 over it, 9.66× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: wasi/bindings.rs lib/wasi-types/src/wasi/bindings.rs — FileTooLong — 3281 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 2781 over it, 6.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: translator/code_translator.rs lib/compiler-cranelift/src/translator/code_translator.rs — FileTooLong — 2809 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 33 free functions. The bar is 500 significant lines; this is 2309 over it, 5.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/emitter_arm64.rs lib/compiler-singlepass/src/emitter_arm64.rs — FileTooLong — 2519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: Assembler (504-2805). The bar is 500 significant lines; this is 2019 over it, 5.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/types.rs lib/backend-api/src/types.rs — FileTooLong — 2367 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1867 over it, 4.73× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/machine.rs lib/compiler-singlepass/src/machine.rs — FileTooLong — 2139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: Machine (105-2352). The bar is 500 significant lines; this is 1639 over it, 4.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/query.rs lib/backend-api/src/query.rs — FileTooLong — 1913 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 108 free functions. The bar is 500 significant lines; this is 1413 over it, 3.83× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: fs/mod.rs lib/wasix/src/fs/mod.rs — FileTooLong — 1830 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: WasiFs (3 blocks, 569-2773). The bar is 500 significant lines; this is 1330 over it, 3.66× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: translator/intrinsics.rs lib/compiler-llvm/src/translator/intrinsics.rs — FileTooLong — 1783 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1283 over it, 3.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/emitter_x64.rs lib/compiler-singlepass/src/emitter_x64.rs — FileTooLong — 1735 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 61% of them inside a single declaration: AssemblerX64 (901-2390). The bar is 500 significant lines; this is 1235 over it, 3.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/func_environ.rs lib/compiler-cranelift/src/func_environ.rs — FileTooLong — 1677 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 97% of them inside a single declaration: FuncEnvironment (3 blocks, 89-2406). The bar is 500 significant lines; this is 1177 over it, 3.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/emitter_riscv.rs lib/compiler-singlepass/src/emitter_riscv.rs — FileTooLong — 1606 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 61% of them inside a single declaration: Assembler (352-1748). The bar is 500 significant lines; this is 1106 over it, 3.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs lib/c-api-imports/src/lib.rs — FileTooLong — 1595 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 128 free functions. The bar is 500 significant lines; this is 1095 over it, 3.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: concrete/archived.rs lib/journal/src/concrete/archived.rs — FileTooLong — 1592 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1092 over it, 3.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: net/socket.rs lib/wasix/src/net/socket.rs — FileTooLong — 1365 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: InodeSocket (2 blocks, 237-1695). The bar is 500 significant lines; this is 865 over it, 2.73× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: engine/artifact.rs lib/compiler/src/engine/artifact.rs — FileTooLong — 1332 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: Artifact (6 blocks, 159-1878). The bar is 500 significant lines; this is 832 over it, 2.66× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/server.rs lib/virtual-net/src/server.rs — FileTooLong — 1220 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 720 over it, 2.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/client.rs lib/virtual-net/src/client.rs — FileTooLong — 1184 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 684 over it, 2.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: syscalls/mod.rs lib/wasix/src/syscalls/mod.rs — FileTooLong — 1075 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 44 free functions. The bar is 500 significant lines; this is 575 over it, 2.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: parser/operator.rs lib/c-api/src/wasm_c_api/unstable/parser/operator.rs — FileTooLong — 1071 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 100% of them inside a single declaration: wasmer_parser_operator_t (2 blocks, 5-1080). The bar is 500 significant lines; this is 571 over it, 2.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: instance/mod.rs lib/vm/src/instance/mod.rs — FileTooLong — 1026 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 526 over it, 2.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
+ 37 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×52

Duplicated block (7 lines × 2) lib/api/src/backend/js/entities/function/typed.rs:176 — lib/api/src/backend/js/entities/function/typed.rs:176-183 | lib/api/src/backend/sys/entities/function/typed.rs:319-325 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/api/src/backend/js/entities/module.rs:406 — lib/api/src/backend/js/entities/module.rs:406-412 | lib/api/src/backend/js/entities/module.rs:419-425 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/api/src/backend/js/entities/module.rs:483 — lib/api/src/backend/js/entities/module.rs:483-489 | lib/api/src/backend/js/entities/module.rs:594-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/api/src/backend/v8/entities/module.rs:42 — lib/api/src/backend/v8/entities/module.rs:42-48 | lib/api/src/backend/v8/entities/module.rs:74-80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/api/src/utils/polyfill.rs:802 — lib/api/src/utils/polyfill.rs:802-808 | lib/compiler/src/translator/sections.rs:417-423 — before extracting anything, compare `lib/api/src/utils/polyfill.rs` and `lib/compiler/src/translator/sections.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) lib/c-api/src/wasm_c_api/types/frame.rs:64 — lib/c-api/src/wasm_c_api/types/frame.rs:64-70 | lib/c-api/src/wasm_c_api/types/frame.rs:77-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-cranelift/src/eh.rs:550 — lib/compiler-cranelift/src/eh.rs:550-556 | lib/compiler-cranelift/src/eh.rs:575-581 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-cranelift/src/elf.rs:98 — lib/compiler-cranelift/src/elf.rs:98-104 | lib/compiler/src/dwarf.rs:117-123 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler/src/dwarf.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1188 — lib/compiler-cranelift/src/func_environ.rs:1188-1194 | lib/compiler-cranelift/src/func_environ.rs:1255-1261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:584 — lib/compiler-cranelift/src/translator/code_translator.rs:584-590 | lib/compiler-cranelift/src/translator/code_translator.rs:594-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:1764 — lib/compiler-llvm/src/translator/code.rs:1764-1770 | lib/compiler-llvm/src/translator/code.rs:6093-6099 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:2432 — lib/compiler-llvm/src/translator/code.rs:2432-2438 | lib/compiler-llvm/src/translator/code.rs:3564-3570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:2798 — lib/compiler-llvm/src/translator/code.rs:2798-2804 | lib/compiler-llvm/src/translator/code.rs:2998-3004 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:4512 — lib/compiler-llvm/src/translator/code.rs:4512-4518 | lib/compiler-llvm/src/translator/code.rs:4522-4528 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:8835 — lib/compiler-llvm/src/translator/code.rs:8835-8841 | lib/compiler-llvm/src/translator/code.rs:9669-9675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:10292 — lib/compiler-llvm/src/translator/code.rs:10292-10298 | lib/compiler-llvm/src/translator/code.rs:10314-10320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-llvm/src/translator/code.rs:10303 — lib/compiler-llvm/src/translator/code.rs:10303-10309 | lib/compiler-llvm/src/translator/code.rs:10325-10331 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/codegen.rs:2706 — lib/compiler-singlepass/src/codegen.rs:2706-2713 | lib/compiler-singlepass/src/codegen.rs:2716-2722 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:774 — lib/compiler-singlepass/src/machine_arm64.rs:774-780 | lib/compiler-singlepass/src/machine_arm64.rs:804-810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1003 — lib/compiler-singlepass/src/machine_arm64.rs:1003-1009 | lib/compiler-singlepass/src/machine_riscv.rs:2467-2473 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2886 — lib/compiler-singlepass/src/machine_arm64.rs:2886-2892 | lib/compiler-singlepass/src/machine_arm64.rs:5069-5075 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:6060 — lib/compiler-singlepass/src/machine_riscv.rs:6060-6066 | lib/compiler-singlepass/src/machine_x64.rs:7174-7180 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:343 — lib/compiler-singlepass/src/machine_x64.rs:343-349 | lib/compiler-singlepass/src/machine_x64.rs:420-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:6926 — lib/compiler-singlepass/src/machine_x64.rs:6926-6932 | lib/compiler-singlepass/src/machine_x64.rs:7026-7032 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:7362 — lib/compiler-singlepass/src/machine_x64.rs:7362-7368 | lib/compiler-singlepass/src/machine_x64.rs:7482-7488 — 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.
+ 27 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×50

Duplicated block (9 lines × 2) lib/api/src/backend/sys/entities/function/mod.rs:73 — lib/api/src/backend/sys/entities/function/mod.rs:73-81 | lib/api/src/backend/sys/entities/function/mod.rs:176-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/api/src/entities/function/env/inner.rs:339 — lib/api/src/entities/function/env/inner.rs:339-347 | lib/api/src/entities/function/env/inner.rs:395-403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/api/src/utils/polyfill.rs:531 — lib/api/src/utils/polyfill.rs:531-539 | lib/compiler/src/translator/sections.rs:38-46 — before extracting anything, compare `lib/api/src/utils/polyfill.rs` and `lib/compiler/src/translator/sections.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 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) lib/c-api/src/wasm_c_api/wasi/mod.rs:92 — lib/c-api/src/wasm_c_api/wasi/mod.rs:92-100 | lib/c-api/src/wasm_c_api/wasi/mod.rs:126-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/c-api/src/wasm_c_api/wasi/mod.rs:92 — lib/c-api/src/wasm_c_api/wasi/mod.rs:92-100 | lib/c-api/src/wasm_c_api/wasi/mod.rs:116-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/cli/src/commands/app/secrets/create.rs:74 — lib/cli/src/commands/app/secrets/create.rs:74-82 | lib/cli/src/commands/app/secrets/update.rs:79-87 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/update.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/cli/src/commands/app/secrets/export.rs:50 — lib/cli/src/commands/app/secrets/export.rs:50-58 | lib/cli/src/commands/app/secrets/reveal.rs:70-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) lib/cli/src/commands/app/secrets/utils/render.rs:28 — lib/cli/src/commands/app/secrets/utils/render.rs:28-36 | lib/cli/src/commands/app/secrets/utils/render.rs:69-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/cli/src/commands/package/common/mod.rs:178 — lib/cli/src/commands/package/common/mod.rs:178-186 | lib/package/src/convert/webc_to_package.rs:29-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) lib/compiler-cranelift/src/compiler.rs:458 — lib/compiler-cranelift/src/compiler.rs:458-466 | lib/compiler-cranelift/src/compiler.rs:495-503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1196 — lib/compiler-cranelift/src/func_environ.rs:1196-1204 | lib/compiler-cranelift/src/func_environ.rs:1263-1271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1930 — lib/compiler-cranelift/src/func_environ.rs:1930-1938 | lib/compiler-cranelift/src/func_environ.rs:1983-1991 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:186 — lib/compiler-cranelift/src/translator/code_translator.rs:186-194 | lib/compiler-cranelift/src/translator/code_translator.rs:199-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:3056 — lib/compiler-cranelift/src/translator/code_translator.rs:3056-3064 | lib/compiler-cranelift/src/translator/code_translator.rs:3141-3149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:3244 — lib/compiler-cranelift/src/translator/code_translator.rs:3244-3252 | lib/compiler-cranelift/src/translator/code_translator.rs:3293-3301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-llvm/src/translator/code.rs:3004 — lib/compiler-llvm/src/translator/code.rs:3004-3012 | lib/compiler-llvm/src/translator/code.rs:11706-11714 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-llvm/src/translator/code.rs:4089 — lib/compiler-llvm/src/translator/code.rs:4089-4097 | lib/compiler-llvm/src/translator/code.rs:4149-4157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-llvm/src/translator/code.rs:5981 — lib/compiler-llvm/src/translator/code.rs:5981-5989 | lib/compiler-llvm/src/translator/code.rs:6018-6026 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-llvm/src/translator/code.rs:10624 — lib/compiler-llvm/src/translator/code.rs:10624-10632 | lib/compiler-llvm/src/translator/code.rs:10643-10651 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-llvm/src/translator/code.rs:10662 — lib/compiler-llvm/src/translator/code.rs:10662-10670 | lib/compiler-llvm/src/translator/code.rs:10681-10689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-singlepass/src/codegen.rs:1844 — lib/compiler-singlepass/src/codegen.rs:1844-1852 | lib/compiler-singlepass/src/codegen.rs:1995-2003 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:437 — lib/compiler-singlepass/src/machine_arm64.rs:437-445 | lib/compiler-singlepass/src/machine_riscv.rs:287-295 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:478 — lib/compiler-singlepass/src/machine_arm64.rs:478-486 | lib/compiler-singlepass/src/machine_riscv.rs:310-318 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1004 — lib/compiler-singlepass/src/machine_arm64.rs:1004-1012 | lib/compiler-singlepass/src/machine_arm64.rs:2162-2170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1032 — lib/compiler-singlepass/src/machine_arm64.rs:1032-1040 | lib/compiler-singlepass/src/machine_riscv.rs:977-985 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
+ 25 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×45

Duplicated block (10 lines × 2) lib/api/src/backend/js/entities/function/mod.rs:378 — lib/api/src/backend/js/entities/function/mod.rs:378-387 | lib/api/src/backend/js/entities/function/mod.rs:410-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/api/src/backend/v8/entities/function/mod.rs:168 — lib/api/src/backend/v8/entities/function/mod.rs:168-177 | lib/api/src/backend/v8/entities/function/mod.rs:244-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/cli/src/backend.rs:623 — lib/cli/src/backend.rs:623-632 | lib/cli/src/backend.rs:662-671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/cli/src/commands/app/util.rs:165 — lib/cli/src/commands/app/util.rs:165-174 | lib/cli/src/commands/app/util.rs:191-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/cli/src/commands/init.rs:202 — lib/cli/src/commands/init.rs:202-212 | lib/cli/src/commands/init.rs:220-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-cranelift/src/func_environ.rs:743 — lib/compiler-cranelift/src/func_environ.rs:743-752 | lib/compiler-cranelift/src/func_environ.rs:873-882 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:1454 — lib/compiler-llvm/src/translator/code.rs:1454-1463 | lib/compiler-llvm/src/translator/code.rs:1535-1544 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:6410 — lib/compiler-llvm/src/translator/code.rs:6410-6419 | lib/compiler-llvm/src/translator/code.rs:6443-6452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:6517 — lib/compiler-llvm/src/translator/code.rs:6517-6526 | lib/compiler-llvm/src/translator/code.rs:6550-6559 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:6739 — lib/compiler-llvm/src/translator/code.rs:6739-6748 | lib/compiler-llvm/src/translator/code.rs:6909-6918 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:6762 — lib/compiler-llvm/src/translator/code.rs:6762-6771 | lib/compiler-llvm/src/translator/code.rs:6932-6941 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:7333 — lib/compiler-llvm/src/translator/code.rs:7333-7342 | lib/compiler-llvm/src/translator/code.rs:7353-7362 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-llvm/src/translator/code.rs:11952 — lib/compiler-llvm/src/translator/code.rs:11952-11961 | lib/compiler-llvm/src/translator/code.rs:12019-12028 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/codegen.rs:3206 — lib/compiler-singlepass/src/codegen.rs:3206-3215 | lib/compiler-singlepass/src/codegen.rs:3505-3514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/compiler.rs:305 — lib/compiler-singlepass/src/compiler.rs:305-315 | lib/compiler-singlepass/src/compiler.rs:345-354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:223 — lib/compiler-singlepass/src/machine_arm64.rs:223-232 | lib/compiler-singlepass/src/machine_arm64.rs:242-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2590 — lib/compiler-singlepass/src/machine_arm64.rs:2590-2599 | lib/compiler-singlepass/src/machine_riscv.rs:2989-2998 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2671 — lib/compiler-singlepass/src/machine_arm64.rs:2671-2680 | lib/compiler-singlepass/src/machine_arm64.rs:2709-2718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:4773 — lib/compiler-singlepass/src/machine_arm64.rs:4773-4782 | lib/compiler-singlepass/src/machine_riscv.rs:4312-4321 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:4854 — lib/compiler-singlepass/src/machine_arm64.rs:4854-4863 | lib/compiler-singlepass/src/machine_arm64.rs:4892-4901 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:4877 — lib/compiler-singlepass/src/machine_arm64.rs:4877-4886 | lib/compiler-singlepass/src/machine_arm64.rs:5100-5109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:2817 — lib/compiler-singlepass/src/machine_x64.rs:2817-2826 | lib/compiler-singlepass/src/machine_x64.rs:2883-2892 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3020 — lib/compiler-singlepass/src/machine_x64.rs:3020-3029 | lib/compiler-singlepass/src/machine_x64.rs:3075-3084 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4600 — lib/compiler-singlepass/src/machine_x64.rs:4600-4609 | lib/compiler-singlepass/src/machine_x64.rs:4666-4675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4803 — lib/compiler-singlepass/src/machine_x64.rs:4803-4812 | lib/compiler-singlepass/src/machine_x64.rs:4858-4867 — 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.
+ 20 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×40

Duplicated block (6 lines × 2) lib/api/src/backend/js/entities/function/mod.rs:314 — lib/api/src/backend/js/entities/function/mod.rs:314-319 | lib/api/src/backend/js/entities/function/mod.rs:330-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/api/src/entities/function/inner.rs:264 — lib/api/src/entities/function/inner.rs:264-269 | lib/api/src/entities/function/inner.rs:320-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/cli/src/commands/app/deploy.rs:356 — lib/cli/src/commands/app/deploy.rs:356-361 | lib/cli/src/commands/app/deploy.rs:1025-1030 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-cranelift/src/func_environ.rs:309 — lib/compiler-cranelift/src/func_environ.rs:309-314 | lib/compiler-cranelift/src/func_environ.rs:1567-1572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-llvm/src/translator/code.rs:3395 — lib/compiler-llvm/src/translator/code.rs:3395-3400 | lib/compiler-llvm/src/translator/code.rs:3456-3461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-llvm/src/translator/code.rs:6086 — lib/compiler-llvm/src/translator/code.rs:6086-6091 | lib/compiler-llvm/src/translator/code.rs:6133-6138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-llvm/src/translator/code.rs:11912 — lib/compiler-llvm/src/translator/code.rs:11912-11917 | lib/compiler-llvm/src/translator/code.rs:11979-11984 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:893 — lib/compiler-singlepass/src/machine_arm64.rs:893-898 | lib/compiler-singlepass/src/machine_arm64.rs:921-926 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1985 — lib/compiler-singlepass/src/machine_arm64.rs:1985-1990 | lib/compiler-singlepass/src/machine_riscv.rs:2403-2408 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2916 — lib/compiler-singlepass/src/machine_arm64.rs:2916-2921 | lib/compiler-singlepass/src/machine_arm64.rs:5099-5104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:4697 — lib/compiler-singlepass/src/machine_arm64.rs:4697-4702 | lib/compiler-singlepass/src/machine_riscv.rs:4231-4236 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:8110 — lib/compiler-singlepass/src/machine_arm64.rs:8110-8115 | lib/compiler-singlepass/src/machine_x64.rs:7596-7601 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:1381 — lib/compiler-singlepass/src/machine_riscv.rs:1381-1386 | lib/compiler-singlepass/src/machine_x64.rs:478-483 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:1413 — lib/compiler-singlepass/src/machine_riscv.rs:1413-1418 | lib/compiler-singlepass/src/machine_riscv.rs:1584-1589 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:353 — lib/compiler-singlepass/src/machine_x64.rs:353-358 | lib/compiler-singlepass/src/machine_x64.rs:430-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:674 — lib/compiler-singlepass/src/machine_x64.rs:674-679 | lib/compiler-singlepass/src/machine_x64.rs:820-825 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler/src/abi.rs:123 — lib/compiler/src/abi.rs:123-128 | lib/compiler/src/abi.rs:170-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/compiler/src/engine/artifact.rs:540 — lib/compiler/src/engine/artifact.rs:540-545 | lib/compiler/src/engine/artifact.rs:560-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/package/src/package/package.rs:321 — lib/package/src/package/package.rs:321-326 | lib/package/src/package/package.rs:330-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/package/src/package/volume/fs.rs:436 — lib/package/src/package/volume/fs.rs:436-441 | lib/package/src/package/volume/fs.rs:444-449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/virtual-fs/src/mem_fs/file.rs:1160 — lib/virtual-fs/src/mem_fs/file.rs:1160-1165 | lib/virtual-fs/src/mem_fs/file.rs:1180-1185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/virtual-net/src/host.rs:418 — lib/virtual-net/src/host.rs:418-423 | lib/virtual-net/src/host.rs:434-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/wasix/src/http/web_http_client.rs:167 — lib/wasix/src/http/web_http_client.rs:167-173 | lib/wasix/src/http/web_http_client.rs:194-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/wasix/src/lib.rs:453 — lib/wasix/src/lib.rs:453-458 | lib/wasix/src/lib.rs:510-515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/wasix/src/net/mod.rs:140 — lib/wasix/src/net/mod.rs:140-145 | lib/wasix/src/net/mod.rs:303-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
+ 15 more in this group — see findings.md.

D17 · Explicit Debt · FixmeComment · ×39

FixmeComment tests/integration/cli/tests/snapshot.rs:960 — // FIXME: re-enable - hangs on windows and macos — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/compilers/metering.rs:167 — // FIXME: Since now a metering error is signaled with an `unreachable`, it is impossible to verify — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/lib.rs:1 — // FIXME: merge with ./lib.rs_upstream — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/syscalls/wasix/closure_prepare.rs:208 — // FIXME: Look into replacing this with the wasm start function — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/syscalls/wasix/fd_pipe.rs:61 — // FIXME: since a hash of the inode name is used to calculate the inode number, this may — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/syscalls/wasix/sock_pair.rs:9 — // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/syscalls/wasix/sock_pair.rs:57 — // FIXME: currently, socket properties are ignored outright, since they — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/syscalls/wasi/fd_seek.rs:132 — // FIXME: implement this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/syscalls/journal/restore_snapshot.rs:33 — // FIXME: if the stdout/stderr FDs were closed as a result of replaying the journal, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/builder.rs:1143 — // FIXME: use a proper custom error type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/env.rs:494 — // FIXME: use custom error type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/env.rs:518 — // FIXME: should we be storing envs as raw byte arrays? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/func_env.rs:85 — // FIXME: shouldn't this happen _before_ instantiating, so the startup code in the instance — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/func_env.rs:123 — // FIXME: this probably doesn't work with WASIX modules, since they import their memories? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/func_env.rs:160 — // FIXME: Move this code to somewhere that makes sense (in WasiEnv?) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/linker/mod.rs:705 — // FIXME: this needs to become a parameter if we ever decouple the linker from WASIX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/state/linker/mod.rs:1114 — // FIXME: If we fail at an intermediate step, we should reset the linker's state, a la: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/runtime/resolver/backend_source.rs:224 — // FIXME: implementing caching! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/runtime/resolver/inputs.rs:131 — // FIXME: is this still needed? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/runtime/resolver/resolve.rs:791 — // FIXME: This code is all super naive and will break the moment there — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/runtime/resolver/web_source.rs:157 — // FIXME: This will all block the main thread — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/runtime/package_loader/builtin_loader.rs:535 — // FIXME: This implementation will block the async runtime and should use — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/os/task/control_plane.rs:132 — // FIXME: De-register terminated processes! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/wasix/src/os/task/process.rs:864 — // FIXME: this is wrong, threads might still be running! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/vm/src/trap/traphandlers.rs:711 — // FIXME: this is what the previous C++ did to make sure that TLS — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
+ 14 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×39

FunctionTooLong: wasmer_compiler_cranelift::translator::code_translator::translate_operator lib/compiler-cranelift/src/translator/code_translator.rs:157 — FunctionTooLong — wasmer_compiler_cranelift::translator::code_translator::translate_operator runs 1836 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1736 over it, 18.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_compiler_llvm::object_file::load_object_file lib/compiler-llvm/src/object_file.rs:194 — FunctionTooLong — wasmer_compiler_llvm::object_file::load_object_file runs 506 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 406 over it, 5.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth lib/wasix/src/syscalls/wasix/path_open2.rs:186 — FunctionTooLong — wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth runs 378 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: virtual_fs::overlay_fs::open_copy_on_write lib/virtual-fs/src/overlay_fs.rs:741 — FunctionTooLong — virtual_fs::overlay_fs::open_copy_on_write runs 374 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 274 over it, 3.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_compiler::engine::link::apply_relocation lib/compiler/src/engine/link.rs:21 — FunctionTooLong — wasmer_compiler::engine::link::apply_relocation runs 350 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 250 over it, 3.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_compiler::object::module::emit_compilation lib/compiler/src/object/module.rs:139 — FunctionTooLong — wasmer_compiler::object::module::emit_compilation runs 297 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 197 over it, 2.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal lib/wasix/src/syscalls/wasi/fd_write.rs:243 — FunctionTooLong — wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal runs 294 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasi::fd_read::fd_read_internal lib/wasix/src/syscalls/wasi/fd_read.rs:135 — FunctionTooLong — wasmer_wasix::syscalls::wasi::fd_read::fd_read_internal runs 237 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 137 over it, 2.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_compiler_cranelift::translator::code_translator::type_of lib/compiler-cranelift/src/translator/code_translator.rs:3475 — FunctionTooLong — wasmer_compiler_cranelift::translator::code_translator::type_of runs 215 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal lib/wasix/src/syscalls/wasi/path_rename.rs:56 — FunctionTooLong — wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal runs 191 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_package_sdk::package::publish::publish_package_directory lib/package-sdk/src/package/publish.rs:131 — FunctionTooLong — wasmer_package_sdk::package::publish::publish_package_directory runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal lib/wasix/src/syscalls/wasi/poll_oneoff.rs:232 — FunctionTooLong — wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal runs 161 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl lib/wasix/src/syscalls/wasix/proc_exec4.rs:78 — FunctionTooLong — wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasix::sock_send_file::sock_send_file_internal lib/wasix/src/syscalls/wasix/sock_send_file.rs:52 — FunctionTooLong — wasmer_wasix::syscalls::wasix::sock_send_file::sock_send_file_internal runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasix::proc_fork::proc_fork lib/wasix/src/syscalls/wasix/proc_fork.rs:23 — FunctionTooLong — wasmer_wasix::syscalls::wasix::proc_fork::proc_fork runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 lib/compiler-singlepass/src/emitter_arm64.rs:3108 — FunctionTooLong — wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 runs 146 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::wasix_exports_32 lib/wasix/src/lib.rs:517 — FunctionTooLong — wasmer_wasix::wasix_exports_32 runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::wasix_exports_64 lib/wasix/src/lib.rs:666 — FunctionTooLong — wasmer_wasix::wasix_exports_64 runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_package_sdk::app::deploy_remote_build::deploy_app_remote lib/package-sdk/src/app/deploy_remote_build.rs:101 — FunctionTooLong — wasmer_package_sdk::app::deploy_remote_build::deploy_app_remote runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::syscalls::wasix::closure_prepare::build_closure_wasm_bytes lib/wasix/src/syscalls/wasix/closure_prepare.rs:119 — FunctionTooLong — wasmer_wasix::syscalls::wasix::closure_prepare::build_closure_wasm_bytes runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_vm::libcalls::function_pointer lib/vm/src/libcalls.rs:939 — FunctionTooLong — wasmer_vm::libcalls::function_pointer runs 141 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_cli::commands::init::construct_manifest lib/cli/src/commands/init.rs:362 — FunctionTooLong — wasmer_cli::commands::init::construct_manifest runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_package::convert::webc_to_package::webc_to_package_dir lib/package/src/convert/webc_to_package.rs:11 — FunctionTooLong — wasmer_package::convert::webc_to_package::webc_to_package_dir runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_wasix::os::posix_err::exit_code_to_message lib/wasix/src/os/posix_err.rs:133 — FunctionTooLong — wasmer_wasix::os::posix_err::exit_code_to_message runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wasmer_vm::libcalls::eh::dwarf::eh::find_eh_action lib/vm/src/libcalls/eh/dwarf/eh.rs:72 — FunctionTooLong — wasmer_vm::libcalls::eh::dwarf::eh::find_eh_action runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
+ 14 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×38

Duplicated block (8 lines × 2) lib/api/src/backend/js/entities/function/mod.rs:194 — lib/api/src/backend/js/entities/function/mod.rs:194-201 | lib/api/src/backend/sys/entities/function/mod.rs:303-311 — before extracting anything, compare `lib/api/src/backend/js/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 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 (8 lines × 2) lib/api/src/backend/js/entities/function/mod.rs:250 — lib/api/src/backend/js/entities/function/mod.rs:250-257 | lib/api/src/backend/sys/entities/function/mod.rs:357-365 — before extracting anything, compare `lib/api/src/backend/js/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 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 (8 lines × 2) lib/c-api-imports/src/lib.rs:1092 — lib/c-api-imports/src/lib.rs:1092-1099 | lib/c-api-imports/src/lib.rs:1116-1123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/c-api-imports/src/lib.rs:1315 — lib/c-api-imports/src/lib.rs:1315-1322 | lib/c-api-imports/src/lib.rs:1348-1355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/cli/src/utils/prompts.rs:8 — lib/cli/src/utils/prompts.rs:8-19 | lib/cli/src/utils/prompts.rs:32-39 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-cranelift/src/func_environ.rs:593 — lib/compiler-cranelift/src/func_environ.rs:593-600 | lib/compiler-cranelift/src/func_environ.rs:630-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1415 — lib/compiler-cranelift/src/func_environ.rs:1415-1422 | lib/compiler-cranelift/src/func_environ.rs:2101-2108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-cranelift/src/func_environ.rs:2117 — lib/compiler-cranelift/src/func_environ.rs:2117-2124 | lib/compiler-cranelift/src/func_environ.rs:2229-2236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:265 — lib/compiler-cranelift/src/translator/code_translator.rs:265-272 | lib/compiler-cranelift/src/translator/code_translator.rs:278-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:1066 — lib/compiler-llvm/src/translator/code.rs:1066-1073 | lib/compiler-llvm/src/translator/code.rs:5011-5018 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:4524 — lib/compiler-llvm/src/translator/code.rs:4524-4531 | lib/compiler-llvm/src/translator/code.rs:4576-4583 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5574 — lib/compiler-llvm/src/translator/code.rs:5574-5581 | lib/compiler-llvm/src/translator/code.rs:5590-5597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:9795 — lib/compiler-llvm/src/translator/code.rs:9795-9802 | lib/compiler-llvm/src/translator/code.rs:9823-9830 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:9809 — lib/compiler-llvm/src/translator/code.rs:9809-9816 | lib/compiler-llvm/src/translator/code.rs:9837-9844 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:10391 — lib/compiler-llvm/src/translator/code.rs:10391-10398 | lib/compiler-llvm/src/translator/code.rs:10406-10413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-llvm/src/translator/code.rs:10588 — lib/compiler-llvm/src/translator/code.rs:10588-10595 | lib/compiler-llvm/src/translator/code.rs:10606-10613 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/emitter_arm64.rs:2988 — lib/compiler-singlepass/src/emitter_arm64.rs:2988-2995 | lib/compiler-singlepass/src/machine_x64.rs:8123-8130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1089 — lib/compiler-singlepass/src/machine_arm64.rs:1089-1096 | lib/compiler-singlepass/src/machine_x64.rs:587-594 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1587 — lib/compiler-singlepass/src/machine_arm64.rs:1587-1594 | lib/compiler-singlepass/src/machine_arm64.rs:1604-1611 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1654 — lib/compiler-singlepass/src/machine_arm64.rs:1654-1661 | lib/compiler-singlepass/src/machine_riscv.rs:2195-2202 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:7663 — lib/compiler-singlepass/src/machine_arm64.rs:7663-7670 | lib/compiler-singlepass/src/machine_arm64.rs:7702-7709 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:7741 — lib/compiler-singlepass/src/machine_arm64.rs:7741-7748 | lib/compiler-singlepass/src/machine_arm64.rs:7780-7787 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:1189 — lib/compiler-singlepass/src/machine_x64.rs:1189-1196 | lib/compiler-singlepass/src/machine_x64.rs:1602-1609 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3150 — lib/compiler-singlepass/src/machine_x64.rs:3150-3157 | lib/compiler-singlepass/src/machine_x64.rs:4933-4940 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:6890 — lib/compiler-singlepass/src/machine_x64.rs:6890-6897 | lib/compiler-singlepass/src/machine_x64.rs:6990-6997 — 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.
+ 13 more in this group — see findings.md.

D3 · God Classes · ClassTooLong · ×37

ClassTooLong: LLVMFunctionCodeGenerator lib/compiler-llvm/src/translator/code.rs:2517 — ClassTooLong — 9752 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 54 methods, 3 blocks, lines 676-12889. The bar is 400 significant lines; this is 9352 over it, 24.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MachineARM64 lib/compiler-singlepass/src/machine_arm64.rs:36 — ClassTooLong — 6974 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 42 methods, 3 blocks, lines 36-8494. The bar is 400 significant lines; this is 6574 over it, 17.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MachineX86_64 lib/compiler-singlepass/src/machine_x64.rs:94 — ClassTooLong — 6736 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 50 methods, 3 blocks, lines 94-8395. The bar is 400 significant lines; this is 6336 over it, 16.84× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MachineRiscv lib/compiler-singlepass/src/machine_riscv.rs:76 — ClassTooLong — 5243 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 36 methods, 3 blocks, lines 76-6612. The bar is 400 significant lines; this is 4843 over it, 13.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FuncGen lib/compiler-singlepass/src/codegen.rs:93 — ClassTooLong — 4699 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 2 blocks, lines 93-6223. The bar is 400 significant lines; this is 4299 over it, 11.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Machine lib/compiler-singlepass/src/machine.rs:105 — ClassTooLong — 1939 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 276 methods. The bar is 400 significant lines; this is 1539 over it, 4.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FuncEnvironment lib/compiler-cranelift/src/func_environ.rs:89 — ClassTooLong — 1623 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 99 methods, 3 blocks, lines 89-2406. The bar is 400 significant lines; this is 1223 over it, 4.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WasiFs lib/wasix/src/fs/mod.rs:569 — ClassTooLong — 1422 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 62 methods, 3 blocks, lines 569-2773. The bar is 400 significant lines; this is 1022 over it, 3.56× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Artifact lib/compiler/src/engine/artifact.rs:159 — ClassTooLong — 1094 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 30 methods, 6 blocks, lines 159-1878. The bar is 400 significant lines; this is 694 over it, 2.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SockProto lib/wasi-types/src/wasi/bindings.rs:1401 — ClassTooLong — 1092 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods, 4 blocks, lines 1401-3757. The bar is 400 significant lines; this is 692 over it, 2.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: wasmer_parser_operator_t lib/c-api/src/wasm_c_api/unstable/parser/operator.rs:5 — ClassTooLong — 1068 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods, 2 blocks, lines 5-1080. The bar is 400 significant lines; this is 668 over it, 2.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InodeSocket lib/wasix/src/net/socket.rs:237 — ClassTooLong — 1058 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods, 2 blocks, lines 237-1695. The bar is 400 significant lines; this is 658 over it, 2.65× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Intrinsics lib/compiler-llvm/src/translator/intrinsics.rs:71 — ClassTooLong — 1037 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 2 blocks, lines 71-1399. The bar is 400 significant lines; this is 637 over it, 2.59× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RemoteNetworkingServerDriver lib/virtual-net/src/server.rs:316 — ClassTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 2 blocks, lines 325-1324. The bar is 400 significant lines; this is 313 over it, 1.78× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FileHandle lib/virtual-fs/src/mem_fs/file.rs:29 — ClassTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 9 blocks, lines 29-1674. The bar is 400 significant lines; this is 312 over it, 1.78× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WasiEnv lib/wasix/src/state/env.rs:182 — ClassTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 60 methods, 4 blocks, lines 182-1382. The bar is 400 significant lines; this is 307 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Linker lib/wasix/src/state/linker/mod.rs:316 — ClassTooLong — 677 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 3 blocks, lines 316-1337. The bar is 400 significant lines; this is 277 over it, 1.69× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CmdAppDeploy lib/cli/src/commands/app/deploy.rs:41 — ClassTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 3 blocks, lines 41-1031. The bar is 400 significant lines; this is 274 over it, 1.69× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JournalEntry lib/journal/src/entry.rs:83 — ClassTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 2 blocks, lines 83-861. The bar is 400 significant lines; this is 269 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CtxType lib/compiler-llvm/src/translator/intrinsics.rs:1438 — ClassTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 2 blocks, lines 1438-2240. The bar is 400 significant lines; this is 217 over it, 1.54× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Instance lib/vm/src/instance/mod.rs:55 — ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 76 methods, 3 blocks, lines 55-1090. The bar is 400 significant lines; this is 179 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WasiEnvBuilder lib/wasix/src/state/builder.rs:51 — ClassTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 84 methods, 3 blocks, lines 51-1174. The bar is 400 significant lines; this is 176 over it, 1.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CmdAppCreate lib/cli/src/commands/app/create.rs:80 — ClassTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 3 blocks, lines 80-947. The bar is 400 significant lines; this is 167 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RemoteSocket lib/virtual-net/src/client.rs:905 — ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 12 blocks, lines 905-1693. The bar is 400 significant lines; this is 134 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CraneliftCompiler lib/compiler-cranelift/src/compiler.rs:90 — ClassTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 3 blocks, lines 90-792. The bar is 400 significant lines; this is 125 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
+ 12 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Cross-context type Module (api → wasix) · ×36

Cross-context type Module (api → wasix) lib/wasix/src/runners/wasi.rs:352 — Module (context api) is exposed in wasix's public surface via WasiRunner.run_wasm — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:123 — Module (context api) is exposed in wasix's public surface via InstantiationHook.additional_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:143 — Module (context api) is exposed in wasix's public surface via InstantiationHook.prepare_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:159 — Module (context api) is exposed in wasix's public surface via InstantiationHook.configure_new_instance — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:397 — Module (context api) is exposed in wasix's public surface via Runtime.additional_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:411 — Module (context api) is exposed in wasix's public surface via Runtime.prepare_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:427 — Module (context api) is exposed in wasix's public surface via Runtime.configure_new_instance — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:917 — Module (context api) is exposed in wasix's public surface via PluggableRuntime.additional_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:930 — Module (context api) is exposed in wasix's public surface via PluggableRuntime.prepare_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:943 — Module (context api) is exposed in wasix's public surface via PluggableRuntime.configure_new_instance — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:1170 — Module (context api) is exposed in wasix's public surface via OverriddenRuntime.additional_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:1189 — Module (context api) is exposed in wasix's public surface via OverriddenRuntime.prepare_imports — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/mod.rs:1206 — Module (context api) is exposed in wasix's public surface via OverriddenRuntime.configure_new_instance — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/module_cache/fallback.rs:96 — Module (context api) is exposed in wasix's public surface via FallbackCache.save — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/module_cache/filesystem.rs:161 — Module (context api) is exposed in wasix's public surface via FileSystemCache.save — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/module_cache/shared.rs:56 — Module (context api) is exposed in wasix's public surface via SharedCache.save — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/module_cache/thread_local.rs:49 — Module (context api) is exposed in wasix's public surface via ThreadLocalCache.save — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/module_cache/types.rs:54 — Module (context api) is exposed in wasix's public surface via ModuleCache.save — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:98 — Module (context api) is exposed in wasix's public surface via TaskWasm.module — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:106 — Module (context api) is exposed in wasix's public surface via TaskWasm.new — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:271 — Module (context api) is exposed in wasix's public surface via VirtualTaskManager.spawn_with_module — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/state/builder.rs:1145 — Module (context api) is exposed in wasix's public surface via WasiEnvBuilder.instantiate — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/state/builder.rs:1154 — Module (context api) is exposed in wasix's public surface via WasiEnvBuilder.instantiate_ext — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/state/func_env.rs:39 — Module (context api) is exposed in wasix's public surface via WasiFunctionEnv.new_with_store — couples the contexts.
Cross-context type Module (api → wasix) lib/wasix/src/state/func_env.rs:96 — Module (context api) is exposed in wasix's public surface via WasiFunctionEnv.import_object — couples the contexts.
+ 11 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×29

Duplicated block (13 lines × 2) lib/api/src/backend/js/entities/memory/buffer.rs:15 — lib/api/src/backend/js/entities/memory/buffer.rs:15-27 | lib/api/src/backend/js/entities/memory/buffer.rs:44-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/api/src/backend/sys/entities/function/mod.rs:262 — lib/api/src/backend/sys/entities/function/mod.rs:262-274 | lib/api/src/backend/sys/entities/function/mod.rs:415-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/api/src/backend/v8/entities/function/mod.rs:119 — lib/api/src/backend/v8/entities/function/mod.rs:119-131 | lib/api/src/backend/v8/entities/function/mod.rs:269-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/api/src/backend/v8/entities/function/mod.rs:179 — lib/api/src/backend/v8/entities/function/mod.rs:179-191 | lib/api/src/backend/v8/entities/function/mod.rs:255-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:887 — lib/compiler-llvm/src/translator/code.rs:887-899 | lib/compiler-llvm/src/translator/code.rs:900-912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:3629 — lib/compiler-llvm/src/translator/code.rs:3629-3641 | lib/compiler-llvm/src/translator/code.rs:3653-3665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:6454 — lib/compiler-llvm/src/translator/code.rs:6454-6466 | lib/compiler-llvm/src/translator/code.rs:6561-6573 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:8892 — lib/compiler-llvm/src/translator/code.rs:8892-8904 | lib/compiler-llvm/src/translator/code.rs:8966-8978 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:9041 — lib/compiler-llvm/src/translator/code.rs:9041-9053 | lib/compiler-llvm/src/translator/code.rs:9107-9119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:9286 — lib/compiler-llvm/src/translator/code.rs:9286-9298 | lib/compiler-llvm/src/translator/code.rs:9722-9734 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:9334 — lib/compiler-llvm/src/translator/code.rs:9334-9346 | lib/compiler-llvm/src/translator/code.rs:9348-9360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:9390 — lib/compiler-llvm/src/translator/code.rs:9390-9402 | lib/compiler-llvm/src/translator/code.rs:9404-9416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:9446 — lib/compiler-llvm/src/translator/code.rs:9446-9458 | lib/compiler-llvm/src/translator/code.rs:9460-9472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:9502 — lib/compiler-llvm/src/translator/code.rs:9502-9514 | lib/compiler-llvm/src/translator/code.rs:9516-9528 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-llvm/src/translator/code.rs:10494 — lib/compiler-llvm/src/translator/code.rs:10494-10506 | lib/compiler-llvm/src/translator/code.rs:10559-10571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-singlepass/src/codegen.rs:1100 — lib/compiler-singlepass/src/codegen.rs:1100-1112 | lib/compiler-singlepass/src/codegen.rs:1131-1143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-singlepass/src/codegen.rs:5556 — lib/compiler-singlepass/src/codegen.rs:5556-5568 | lib/compiler-singlepass/src/codegen.rs:5681-5693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-singlepass/src/emitter_arm64.rs:2849 — lib/compiler-singlepass/src/emitter_arm64.rs:2849-2861 | lib/compiler-singlepass/src/emitter_riscv.rs:1792-1804 — 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 (13 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:150 — lib/compiler-singlepass/src/machine_arm64.rs:150-162 | lib/compiler-singlepass/src/machine_arm64.rs:190-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:310 — lib/compiler-singlepass/src/machine_arm64.rs:310-322 | lib/compiler-singlepass/src/machine_arm64.rs:348-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:2348 — lib/compiler-singlepass/src/machine_riscv.rs:2348-2360 | lib/compiler-singlepass/src/machine_riscv.rs:2373-2385 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:6909 — lib/compiler-singlepass/src/machine_x64.rs:6909-6921 | lib/compiler-singlepass/src/machine_x64.rs:7009-7021 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/sys-utils/src/memory/fd_memory/memories.rs:166 — lib/sys-utils/src/memory/fd_memory/memories.rs:166-178 | lib/vm/src/memory.rs:168-180 — before extracting anything, compare `lib/sys-utils/src/memory/fd_memory/memories.rs` and `lib/vm/src/memory.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/vm/src/vmcontext.rs:426 — lib/vm/src/vmcontext.rs:426-438 | lib/vm/src/vmcontext.rs:465-477 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/wasix/src/syscalls/mod.rs:713 — lib/wasix/src/syscalls/mod.rs:713-725 | lib/wasix/src/syscalls/mod.rs:748-760 — 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.
+ 4 more in this group — see findings.md.

D6 · Cohesion (LCOM4) · Low cohesion · ×29

Low cohesion: AssemblerX64 (LCOM4 64) lib/compiler-singlepass/src/machine_x64.rs:39 — AssemblerX64's methods fall into 64 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 64 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PluggableRuntime (LCOM4 10) lib/wasix/src/runtime/mod.rs:669 — PluggableRuntime's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: StoreObjects (LCOM4 8) lib/api/src/backend/js/entities/store/obj.rs:51 — StoreObjects's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Cranelift (LCOM4 7) lib/compiler-cranelift/src/config.rs:113 — Cranelift's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LLVM (LCOM4 7) lib/compiler-llvm/src/config.rs:113 — LLVM's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MachineX86_64 (LCOM4 7) lib/compiler-singlepass/src/machine_x64.rs:94 — MachineX86_64's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Memory (LCOM4 6) lib/api/src/backend/v8/entities/memory/mod.rs:21 — Memory's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Function (LCOM4 5) lib/api/src/backend/js/entities/function/mod.rs:65 — Function's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Module (LCOM4 5) lib/api/src/backend/js/entities/module.rs:45 — Module's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Function (LCOM4 5) lib/api/src/backend/sys/entities/function/mod.rs:41 — Function's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Module (LCOM4 5) lib/api/src/backend/sys/entities/module.rs:25 — Module's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Table (LCOM4 5) lib/api/src/backend/v8/entities/table.rs:18 — Table's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WasmCapiRuntimeHooks (LCOM4 5) lib/c-api-imports/src/lib.rs:271 — WasmCapiRuntimeHooks's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MachineARM64 (LCOM4 5) lib/compiler-singlepass/src/machine_arm64.rs:36 — MachineARM64's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MachineRiscv (LCOM4 5) lib/compiler-singlepass/src/machine_riscv.rs:76 — MachineRiscv's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FunctionEnv (LCOM4 4) lib/api/src/backend/js/entities/function/env.rs:19 — FunctionEnv's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Global (LCOM4 4) lib/api/src/backend/js/entities/global.rs:13 — Global's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Memory (LCOM4 4) lib/api/src/backend/js/entities/memory/mod.rs:25 — Memory's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Table (LCOM4 4) lib/api/src/backend/js/entities/table.rs:10 — Table's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FunctionEnv (LCOM4 4) lib/api/src/backend/sys/entities/function/env.rs:16 — FunctionEnv's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Memory (LCOM4 4) lib/api/src/backend/sys/entities/memory/mod.rs:32 — Memory's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Table (LCOM4 4) lib/api/src/backend/sys/entities/table.rs:15 — Table's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FunctionEnv (LCOM4 4) lib/api/src/backend/v8/entities/function/env.rs:13 — FunctionEnv's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Function (LCOM4 4) lib/api/src/backend/v8/entities/function/mod.rs:37 — Function's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Module (LCOM4 4) lib/api/src/backend/v8/entities/module.rs:159 — Module's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
+ 4 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×28

Duplicated block (11 lines × 2) lib/api/src/entities/store/local_rwlock.rs:197 — lib/api/src/entities/store/local_rwlock.rs:197-207 | lib/api/src/entities/store/local_rwlock.rs:247-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/cli/src/backend.rs:607 — lib/cli/src/backend.rs:607-617 | lib/cli/src/backend.rs:646-656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-llvm/src/translator/code.rs:1193 — lib/compiler-llvm/src/translator/code.rs:1193-1203 | lib/compiler-llvm/src/translator/code.rs:1294-1304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-llvm/src/translator/code.rs:11538 — lib/compiler-llvm/src/translator/code.rs:11538-11548 | lib/compiler-llvm/src/translator/code.rs:11628-11638 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-llvm/src/translator/code.rs:11940 — lib/compiler-llvm/src/translator/code.rs:11940-11950 | lib/compiler-llvm/src/translator/code.rs:12007-12017 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:203 — lib/compiler-singlepass/src/machine_arm64.rs:203-213 | lib/compiler-singlepass/src/machine_riscv.rs:147-157 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2088 — lib/compiler-singlepass/src/machine_arm64.rs:2088-2098 | lib/compiler-singlepass/src/machine_arm64.rs:2112-2122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2632 — lib/compiler-singlepass/src/machine_arm64.rs:2632-2642 | lib/compiler-singlepass/src/machine_riscv.rs:3036-3046 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:4815 — lib/compiler-singlepass/src/machine_arm64.rs:4815-4825 | lib/compiler-singlepass/src/machine_riscv.rs:4360-4370 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:7559 — lib/compiler-singlepass/src/machine_arm64.rs:7559-7569 | lib/compiler-singlepass/src/machine_arm64.rs:7586-7596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:7613 — lib/compiler-singlepass/src/machine_arm64.rs:7613-7623 | lib/compiler-singlepass/src/machine_arm64.rs:7640-7650 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:7679 — lib/compiler-singlepass/src/machine_arm64.rs:7679-7689 | lib/compiler-singlepass/src/machine_arm64.rs:7757-7767 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:7718 — lib/compiler-singlepass/src/machine_arm64.rs:7718-7728 | lib/compiler-singlepass/src/machine_arm64.rs:7796-7806 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:1168 — lib/compiler-singlepass/src/machine_x64.rs:1168-1178 | lib/compiler-singlepass/src/machine_x64.rs:1581-1591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:1200 — lib/compiler-singlepass/src/machine_x64.rs:1200-1210 | lib/compiler-singlepass/src/machine_x64.rs:1613-1623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/wasix/src/bin_factory/exec.rs:268 — lib/wasix/src/bin_factory/exec.rs:268-278 | lib/wasix/src/bin_factory/exec.rs:281-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/wasix/src/syscalls/journal/maybe_snapshot_many.rs:17 — lib/wasix/src/syscalls/journal/maybe_snapshot_many.rs:17-27 | lib/wasix/src/syscalls/journal/maybe_snapshot_once.rs:17-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) lib/wasix/src/syscalls/wasix/closure_prepare.rs:334 — lib/wasix/src/syscalls/wasix/closure_prepare.rs:334-344 | lib/wasix/src/syscalls/wasix/closure_prepare.rs:348-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/wasix/src/syscalls/wasix/proc_exec4.rs:247 — lib/wasix/src/syscalls/wasix/proc_exec4.rs:247-257 | lib/wasix/src/syscalls/wasix/proc_exit2.rs:58-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) lib/wasix/src/syscalls/wasix/sock_send.rs:101 — lib/wasix/src/syscalls/wasix/sock_send.rs:101-111 | lib/wasix/src/syscalls/wasix/sock_send_to.rs:111-121 — before extracting anything, compare `lib/wasix/src/syscalls/wasix/sock_send.rs` and `lib/wasix/src/syscalls/wasix/sock_send_to.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/compiler-cranelift/src/dwarf.rs:44 — lib/compiler-cranelift/src/dwarf.rs:44-54 | lib/compiler-singlepass/src/dwarf.rs:32-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:2324 — lib/compiler-singlepass/src/machine_riscv.rs:2324-2334 | lib/compiler-singlepass/src/machine_x64.rs:2328-2338 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/compiler-cranelift/src/compiler.rs:167 — lib/compiler-cranelift/src/compiler.rs:167-177 | lib/compiler-singlepass/src/compiler.rs:123-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/compiler-llvm/src/translator/code.rs:3788 — lib/compiler-llvm/src/translator/code.rs:3788-3798 | lib/compiler-llvm/src/translator/code.rs:3859-3869 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/cli/src/commands/app/secrets/create.rs:161 — lib/cli/src/commands/app/secrets/create.rs:161-171 | lib/cli/src/commands/app/secrets/update.rs:155-165 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/update.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
+ 3 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Cross-context type ModuleHash (types → wasix) · ×27

Cross-context type ModuleHash (types → wasix) lib/wasix/src/bin_factory/binary_package.rs:46 — ModuleHash (context types) is exposed in wasix's public surface via BinaryPackageCommand.new — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/bin_factory/binary_package.rs:86 — ModuleHash (context types) is exposed in wasix's public surface via BinaryPackageCommand.hash — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/bin_factory/binary_package.rs:320 — ModuleHash (context types) is exposed in wasix's public surface via BinaryPackage.hash — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/os/task/control_plane.rs:134 — ModuleHash (context types) is exposed in wasix's public surface via WasiControlPlane.new_process — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/os/task/process.rs:422 — ModuleHash (context types) is exposed in wasix's public surface via WasiProcess.new — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runners/wasi.rs:352 — ModuleHash (context types) is exposed in wasix's public surface via WasiRunner.run_wasm — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/mod.rs:305 — ModuleHash (context types) is exposed in wasix's public surface via ModuleInput.hash — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/fallback.rs:65 — ModuleHash (context types) is exposed in wasix's public surface via FallbackCache.load — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/fallback.rs:88 — ModuleHash (context types) is exposed in wasix's public surface via FallbackCache.contains — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/fallback.rs:96 — ModuleHash (context types) is exposed in wasix's public surface via FallbackCache.save — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/filesystem.rs:135 — ModuleHash (context types) is exposed in wasix's public surface via FileSystemCache.load — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/filesystem.rs:148 — ModuleHash (context types) is exposed in wasix's public surface via FileSystemCache.contains — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/filesystem.rs:161 — ModuleHash (context types) is exposed in wasix's public surface via FileSystemCache.save — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/hashed_module.rs:40 — ModuleHash (context types) is exposed in wasix's public surface via HashedModuleData.hash — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/shared.rs:37 — ModuleHash (context types) is exposed in wasix's public surface via SharedCache.load — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/shared.rs:50 — ModuleHash (context types) is exposed in wasix's public surface via SharedCache.contains — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/shared.rs:56 — ModuleHash (context types) is exposed in wasix's public surface via SharedCache.save — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/thread_local.rs:33 — ModuleHash (context types) is exposed in wasix's public surface via ThreadLocalCache.load — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/thread_local.rs:43 — ModuleHash (context types) is exposed in wasix's public surface via ThreadLocalCache.contains — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/thread_local.rs:49 — ModuleHash (context types) is exposed in wasix's public surface via ThreadLocalCache.save — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/types.rs:27 — ModuleHash (context types) is exposed in wasix's public surface via ModuleCache.load — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/types.rs:32 — ModuleHash (context types) is exposed in wasix's public surface via ModuleCache.load_with_progress — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/types.rs:44 — ModuleHash (context types) is exposed in wasix's public surface via ModuleCache.contains — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/runtime/module_cache/types.rs:54 — ModuleHash (context types) is exposed in wasix's public surface via ModuleCache.save — couples the contexts.
Cross-context type ModuleHash (types → wasix) lib/wasix/src/state/builder.rs:400 — ModuleHash (context types) is exposed in wasix's public surface via WasiEnvBuilder.set_module_hash — couples the contexts.
+ 2 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×25

Duplicated block (12 lines × 2) lib/api/src/backend/sys/entities/memory/mod.rs:217 — lib/api/src/backend/sys/entities/memory/mod.rs:217-228 | lib/api/src/backend/sys/entities/memory/mod.rs:240-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/api/src/utils/mem/mod.rs:343 — lib/api/src/utils/mem/mod.rs:343-354 | lib/api/src/utils/mem/mod.rs:361-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/cli/src/commands/app/deploy.rs:894 — lib/cli/src/commands/app/deploy.rs:894-905 | lib/cli/src/commands/app/deploy.rs:907-918 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/cli/src/commands/app/secrets/create.rs:60 — lib/cli/src/commands/app/secrets/create.rs:60-71 | lib/cli/src/commands/app/secrets/delete.rs:62-73 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/delete.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) lib/cli/src/commands/app/secrets/reveal.rs:51 — lib/cli/src/commands/app/secrets/reveal.rs:51-62 | lib/cli/src/commands/app/secrets/update.rs:65-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/cli/src/utils/unpack.rs:89 — lib/cli/src/utils/unpack.rs:89-100 | lib/cli/src/utils/unpack.rs:114-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:953 — lib/compiler-singlepass/src/machine_arm64.rs:953-964 | lib/compiler-singlepass/src/machine_riscv.rs:912-923 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2273 — lib/compiler-singlepass/src/machine_arm64.rs:2273-2284 | lib/compiler-singlepass/src/machine_riscv.rs:2632-2643 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4443 — lib/compiler-singlepass/src/machine_x64.rs:4443-4454 | lib/compiler-singlepass/src/machine_x64.rs:4503-4514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/compiler/src/engine/artifact.rs:651 — lib/compiler/src/engine/artifact.rs:651-662 | lib/compiler/src/engine/artifact.rs:678-689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/compiler/src/object/module.rs:257 — lib/compiler/src/object/module.rs:257-268 | lib/compiler/src/object/module.rs:277-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/virtual-fs/src/mount_fs.rs:709 — lib/virtual-fs/src/mount_fs.rs:709-720 | lib/virtual-fs/src/mount_fs.rs:734-745 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/virtual-net/src/client.rs:115 — lib/virtual-net/src/client.rs:115-126 | lib/virtual-net/src/server.rs:88-99 — before extracting anything, compare `lib/virtual-net/src/client.rs` and `lib/virtual-net/src/server.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) lib/virtual-net/src/host.rs:404 — lib/virtual-net/src/host.rs:404-415 | lib/virtual-net/src/host.rs:859-870 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/virtual-net/src/ruleset.rs:454 — lib/virtual-net/src/ruleset.rs:454-465 | lib/virtual-net/src/ruleset.rs:485-496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/virtual-net/src/rx_tx.rs:402 — lib/virtual-net/src/rx_tx.rs:402-413 | lib/virtual-net/src/rx_tx.rs:464-475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/fs/fd_list.rs:255 — lib/wasix/src/fs/fd_list.rs:255-266 | lib/wasix/src/fs/fd_list.rs:278-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/net/socket.rs:744 — lib/wasix/src/net/socket.rs:744-755 | lib/wasix/src/net/socket.rs:776-787 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/os/task/process.rs:694 — lib/wasix/src/os/task/process.rs:694-705 | lib/wasix/src/os/task/process.rs:734-745 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/os/task/process.rs:708 — lib/wasix/src/os/task/process.rs:708-719 | lib/wasix/src/os/task/process.rs:748-759 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/syscalls/mod.rs:666 — lib/wasix/src/syscalls/mod.rs:666-677 | lib/wasix/src/syscalls/mod.rs:742-753 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/syscalls/wasix/proc_exec4.rs:89 — lib/wasix/src/syscalls/wasix/proc_exec4.rs:89-100 | lib/wasix/src/syscalls/wasix/proc_spawn3.rs:105-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/wasix/src/syscalls/wasix/sock_open.rs:31 — lib/wasix/src/syscalls/wasix/sock_open.rs:31-42 | lib/wasix/src/syscalls/wasix/sock_pair.rs:44-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/wasix/src/syscalls/wasix/sock_send_file.rs:165 — lib/wasix/src/syscalls/wasix/sock_send_file.rs:165-176 | lib/wasix/src/syscalls/wasix/sock_send_file.rs:178-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/wasix/src/fs/mod.rs:2419 — lib/wasix/src/fs/mod.rs:2419-2430 | lib/wasix/src/fs/mod.rs:2537-2548 — 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.

D2 · Cognitive Complexity · wasmer_wasix · ×21

wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal (cognitive 128) lib/wasix/src/syscalls/wasi/fd_write.rs:243 — wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal has cognitive complexity 128 (threshold 15). Drivers by points: if/else 26 (65 pts), match/switch 12 (34 pts), loops 8 (25 pts), boolean chains 4 (nesting depth added 78). 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.
wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth (cognitive 117) lib/wasix/src/syscalls/wasix/path_open2.rs:186 — wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth has cognitive complexity 117 (threshold 15). Drivers by points: if/else 38 (84 pts), match/switch 10 (24 pts), boolean chains 9 (nesting depth added 60). Of this number, 115 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasi::fd_read::fd_read_internal (cognitive 76) lib/wasix/src/syscalls/wasi/fd_read.rs:135 — wasmer_wasix::syscalls::wasi::fd_read::fd_read_internal has cognitive complexity 76 (threshold 15). Drivers by points: if/else 20 (38 pts), match/switch 11 (28 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 39). 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.
wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal (cognitive 53) lib/wasix/src/syscalls/wasi/poll_oneoff.rs:232 — wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal has cognitive complexity 53 (threshold 15). Drivers by points: if/else 22 (42 pts), match/switch 4 (5 pts), boolean chains 3, loops 3 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl (cognitive 44) lib/wasix/src/syscalls/wasix/proc_exec4.rs:78 — wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl has cognitive complexity 44 (threshold 15). Drivers by points: match/switch 10 (22 pts), if/else 12 (19 pts), boolean chains 3 (nesting depth added 19). 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.
wasmer_wasix::syscalls::wasix::epoll_ctl::epoll_ctl_internal (cognitive 38) lib/wasix/src/syscalls/wasix/epoll_ctl.rs:64 — wasmer_wasix::syscalls::wasix::epoll_ctl::epoll_ctl_internal has cognitive complexity 38 (threshold 15). Drivers by points: if/else 5 (19 pts), match/switch 7 (19 pts) (nesting depth added 26). 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.
wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal (cognitive 35) lib/wasix/src/syscalls/wasi/path_rename.rs:56 — wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (27 pts), match/switch 5 (6 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::bin_factory::exec::call_module (cognitive 29) lib/wasix/src/bin_factory/exec.rs:250 — wasmer_wasix::bin_factory::exec::call_module has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::runners::wasi_common::prepare_filesystem (cognitive 23) lib/wasix/src/runners/wasi_common.rs:226 — wasmer_wasix::runners::wasi_common::prepare_filesystem has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 3 (6 pts), loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasix::epoll_wait::epoll_wait (cognitive 22) lib/wasix/src/syscalls/wasix/epoll_wait.rs:17 — wasmer_wasix::syscalls::wasix::epoll_wait::epoll_wait has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 3 (4 pts), loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
wasmer_wasix::syscalls::journal::restore_snapshot::restore_snapshot (cognitive 21) lib/wasix/src/syscalls/journal/restore_snapshot.rs:9 — wasmer_wasix::syscalls::journal::restore_snapshot::restore_snapshot has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 6 (8 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasix::proc_spawn::proc_spawn_internal (cognitive 21) lib/wasix/src/syscalls/wasix/proc_spawn.rs:100 — wasmer_wasix::syscalls::wasix::proc_spawn::proc_spawn_internal has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 7 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasi::path_link::path_link_internal (cognitive 20) lib/wasix/src/syscalls/wasi/path_link.rs:73 — wasmer_wasix::syscalls::wasi::path_link::path_link_internal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 5 (9 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasix::proc_join::proc_join_internal (cognitive 19) lib/wasix/src/syscalls/wasix/proc_join.rs:35 — wasmer_wasix::syscalls::wasix::proc_join::proc_join_internal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 6 (8 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.
wasmer_wasix::syscalls::wasix::proc_spawn3::proc_spawn3_impl (cognitive 19) lib/wasix/src/syscalls/wasix/proc_spawn3.rs:89 — wasmer_wasix::syscalls::wasix::proc_spawn3::proc_spawn3_impl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 4 (5 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::runtime::resolver::resolve::resolve_package (cognitive 17) lib/wasix/src/runtime/resolver/resolve.rs:790 — wasmer_wasix::runtime::resolver::resolve::resolve_package has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 2 (6 pts), if/else 3 (5 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::bin_factory::exec::resume_vfork (cognitive 16) lib/wasix/src/bin_factory/exec.rs:410 — wasmer_wasix::bin_factory::exec::resume_vfork has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (5 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.
wasmer_wasix::runtime::resolver::resolve::discover_dependencies_once (cognitive 16) lib/wasix/src/runtime/resolver/resolve.rs:177 — wasmer_wasix::runtime::resolver::resolve::discover_dependencies_once has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (8 pts), loops 3 (5 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::state::linker::locator::locate_module (cognitive 16) lib/wasix/src/state/linker/locator.rs:17 — wasmer_wasix::state::linker::locator::locate_module has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 3 (6 pts), loops 1 (2 pts) (nesting depth added 6). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_wasix::syscalls::wasi::fd_filestat_set_times::fd_filestat_set_times_internal (cognitive 16) lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs:43 — wasmer_wasix::syscalls::wasi::fd_filestat_set_times::fd_filestat_set_times_internal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
wasmer_wasix::syscalls::wasix::proc_fork::proc_fork (cognitive 16) lib/wasix/src/syscalls/wasix/proc_fork.rs:23 — wasmer_wasix::syscalls::wasix::proc_fork::proc_fork has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 5 (6 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×21

Duplicated block (14 lines × 2) lib/api/src/backend/mod.rs:46 — lib/api/src/backend/mod.rs:46-59 | lib/api/src/backend/mod.rs:73-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/api/src/utils/polyfill.rs:845 — lib/api/src/utils/polyfill.rs:845-858 | lib/compiler/src/translator/sections.rs:589-602 — before extracting anything, compare `lib/api/src/utils/polyfill.rs` and `lib/compiler/src/translator/sections.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 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 (14 lines × 2) lib/compiler-cranelift/src/elf.rs:121 — lib/compiler-cranelift/src/elf.rs:121-134 | lib/compiler/src/dwarf.rs:140-153 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler/src/dwarf.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/compiler-llvm/src/translator/code.rs:4102 — lib/compiler-llvm/src/translator/code.rs:4102-4115 | lib/compiler-llvm/src/translator/code.rs:4158-4171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler-llvm/src/translator/code.rs:7368 — lib/compiler-llvm/src/translator/code.rs:7368-7381 | lib/compiler-llvm/src/translator/code.rs:7387-7400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler-llvm/src/translator/code.rs:8619 — lib/compiler-llvm/src/translator/code.rs:8619-8632 | lib/compiler-llvm/src/translator/code.rs:8647-8660 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1115 — lib/compiler-singlepass/src/machine_arm64.rs:1115-1128 | lib/compiler-singlepass/src/machine_arm64.rs:1133-1146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2066 — lib/compiler-singlepass/src/machine_arm64.rs:2066-2079 | lib/compiler-singlepass/src/machine_riscv.rs:2444-2457 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:1126 — lib/compiler-singlepass/src/machine_riscv.rs:1126-1139 | lib/compiler-singlepass/src/machine_riscv.rs:1243-1256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:2785 — lib/compiler-singlepass/src/machine_x64.rs:2785-2798 | lib/compiler-singlepass/src/machine_x64.rs:2841-2854 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4568 — lib/compiler-singlepass/src/machine_x64.rs:4568-4581 | lib/compiler-singlepass/src/machine_x64.rs:4624-4637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/compiler/src/engine/artifact.rs:500 — lib/compiler/src/engine/artifact.rs:500-513 | lib/compiler/src/engine/artifact.rs:516-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/virtual-net/src/client.rs:1331 — lib/virtual-net/src/client.rs:1331-1344 | lib/virtual-net/src/client.rs:1575-1588 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/wasix/src/net/socket.rs:1343 — lib/wasix/src/net/socket.rs:1343-1356 | lib/wasix/src/net/socket.rs:1427-1440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/wasix/src/syscalls/journal/restore_snapshot.rs:39 — lib/wasix/src/syscalls/journal/restore_snapshot.rs:39-52 | lib/wasix/src/syscalls/journal/restore_snapshot.rs:56-69 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/wasix/src/syscalls/wasi/fd_write.rs:50 — lib/wasix/src/syscalls/wasi/fd_write.rs:50-63 | lib/wasix/src/syscalls/wasi/fd_write.rs:104-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/wasix/src/syscalls/wasix/proc_exec3.rs:34 — lib/wasix/src/syscalls/wasix/proc_exec3.rs:34-47 | lib/wasix/src/syscalls/wasix/proc_exec4.rs:29-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) lib/wasix/src/syscalls/wasix/sock_send.rs:70 — lib/wasix/src/syscalls/wasix/sock_send.rs:70-83 | lib/wasix/src/syscalls/wasix/sock_send_to.rs:67-80 — before extracting anything, compare `lib/wasix/src/syscalls/wasix/sock_send.rs` and `lib/wasix/src/syscalls/wasix/sock_send_to.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/wasix/src/syscalls/wasix/path_open2.rs:91 — lib/wasix/src/syscalls/wasix/path_open2.rs:91-105 | lib/wasix/src/syscalls/wasix/sock_accept.rs:87-100 — 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 (14 lines × 2) lib/wasix/src/net/socket.rs:529 — lib/wasix/src/net/socket.rs:529-542 | lib/wasix/src/net/socket.rs:551-564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/virtual-fs/src/mem_fs/file.rs:393 — lib/virtual-fs/src/mem_fs/file.rs:393-406 | lib/virtual-fs/src/mem_fs/file.rs:449-462 — 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×20

Hotspot: lib/compiler-singlepass/src/codegen.rs lib/compiler-singlepass/src/codegen.rs:1170 — lib/compiler-singlepass/src/codegen.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 369 in FuncGen::feed_operator at line 1170. 7 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-singlepass/src/codegen.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler-cranelift/src/translator/code_translator.rs lib/compiler-cranelift/src/translator/code_translator.rs:157 — lib/compiler-cranelift/src/translator/code_translator.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 403 in wasmer_compiler_cranelift::translator::code_translator::translate_operator at line 157. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-cranelift/src/translator/code_translator.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler-llvm/src/translator/code.rs lib/compiler-llvm/src/translator/code.rs:10886 — lib/compiler-llvm/src/translator/code.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in LLVMFunctionCodeGenerator::translate_atomic_memory_operator at line 10886. 7 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-llvm/src/translator/code.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler-cranelift/src/compiler.rs lib/compiler-cranelift/src/compiler.rs:107 — lib/compiler-cranelift/src/compiler.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in CraneliftCompiler::compile_module_internal at line 107. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-cranelift/src/compiler.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler-llvm/src/compiler.rs lib/compiler-llvm/src/compiler.rs:249 — lib/compiler-llvm/src/compiler.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in LLVMCompiler::compile_module at line 249. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-llvm/src/compiler.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler-singlepass/src/compiler.rs lib/compiler-singlepass/src/compiler.rs:67 — lib/compiler-singlepass/src/compiler.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in SinglepassCompiler::compile_module_internal at line 67. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-singlepass/src/compiler.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/cli/src/commands/app/deploy.rs lib/cli/src/commands/app/deploy.rs:565 — lib/cli/src/commands/app/deploy.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in CmdAppDeploy::run_async at line 565. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/cli/src/commands/app/deploy.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/cli/src/backend.rs lib/cli/src/backend.rs:594 — lib/cli/src/backend.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in BackendType::get_engine at line 594. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/cli/src/backend.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/wasix/src/syscalls/wasi/fd_write.rs lib/wasix/src/syscalls/wasi/fd_write.rs:243 — lib/wasix/src/syscalls/wasi/fd_write.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal at line 243. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/syscalls/wasi/fd_write.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/make-release.py scripts/make-release.py:78 — scripts/make-release.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in make-release.make_release at line 78. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- scripts/make-release.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler/src/engine/artifact.rs lib/compiler/src/engine/artifact.rs:448 — lib/compiler/src/engine/artifact.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Artifact::from_parts_with_module_file at line 448. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler/src/engine/artifact.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler/src/engine/mapped_binary.rs lib/compiler/src/engine/mapped_binary.rs:275 — lib/compiler/src/engine/mapped_binary.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in MemoryMappedBinary::try_from_source at line 275. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler/src/engine/mapped_binary.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/api/src/backend/js/entities/module.rs lib/api/src/backend/js/entities/module.rs:324 — lib/api/src/backend/js/entities/module.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Module::annotate_table_functions at line 324. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/api/src/backend/js/entities/module.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/wasix/src/syscalls/wasix/proc_exec4.rs lib/wasix/src/syscalls/wasix/proc_exec4.rs:78 — lib/wasix/src/syscalls/wasix/proc_exec4.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl at line 78. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/syscalls/wasix/proc_exec4.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/wasix/src/syscalls/wasix/proc_spawn3.rs lib/wasix/src/syscalls/wasix/proc_spawn3.rs:89 — lib/wasix/src/syscalls/wasix/proc_spawn3.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in wasmer_wasix::syscalls::wasix::proc_spawn3::proc_spawn3_impl at line 89. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/syscalls/wasix/proc_spawn3.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/wasix/src/state/builder.rs lib/wasix/src/state/builder.rs:884 — lib/wasix/src/state/builder.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in WasiEnvBuilder::build_init at line 884. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/state/builder.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler-singlepass/src/emitter_arm64.rs lib/compiler-singlepass/src/emitter_arm64.rs:3108 — lib/compiler-singlepass/src/emitter_arm64.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 at line 3108. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-singlepass/src/emitter_arm64.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/cli/src/commands/app/create.rs lib/cli/src/commands/app/create.rs:645 — lib/cli/src/commands/app/create.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in CmdAppCreate::create_from_template at line 645. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/cli/src/commands/app/create.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/compiler/src/translator/module.rs lib/compiler/src/translator/module.rs:137 — lib/compiler/src/translator/module.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in wasmer_compiler::translator::module::translate_module at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler/src/translator/module.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/wasix/src/syscalls/wasix/proc_spawn.rs lib/wasix/src/syscalls/wasix/proc_spawn.rs:100 — lib/wasix/src/syscalls/wasix/proc_spawn.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in wasmer_wasix::syscalls::wasix::proc_spawn::proc_spawn_internal at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/syscalls/wasix/proc_spawn.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D35 · Change Coupling · Change coupling · ×18

Change coupling: filesystem_source.rs ↔ web_source.rs lib/wasix/src/runtime/resolver/filesystem_source.rs:1 — `lib/wasix/src/runtime/resolver/filesystem_source.rs` and `lib/wasix/src/runtime/resolver/web_source.rs` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `c454c2a7` fix warnings; `8d74bf12` add utils for Container creation; `d3ada875` move container, volume and migration back to webc — run `git show` on any of them.
Change coupling: inspect.rs ↔ validate.rs lib/cli/src/commands/inspect.rs:1 — `lib/cli/src/commands/inspect.rs` and `lib/cli/src/commands/validate.rs` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `83822b2e` fix(cli): Fix `Target` imports; `c8ddde53` remove unncessary hash options for validate and inspect; `22c1935f` fix jsc build — run `git show` on any of them.
Change coupling: sock_send.rs ↔ sock_send_to.rs lib/wasix/src/syscalls/wasix/sock_send.rs:1 — `lib/wasix/src/syscalls/wasix/sock_send.rs` and `lib/wasix/src/syscalls/wasix/sock_send_to.rs` change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `03165a20` Connected udp peer state (#6738); `68604f18` More linting fixes; `61c68250` Split the port and socket syscalls so they can be invokes seperately — run `git show` on any of them.
Change coupling: client.rs ↔ server.rs lib/virtual-net/src/client.rs:1 — `lib/virtual-net/src/client.rs` and `lib/virtual-net/src/server.rs` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e4244c1f` Various fixes to get wasmer-js compiling; `f5bee5d4` Upgrade hyper to 1.0 across the repo; `ba9e62b4` - Added more methods to the interest handler for expanded functionali… — run `git show` on any of them.
Change coupling: create.rs ↔ mod.rs lib/cli/src/commands/app/create.rs:1 — `lib/cli/src/commands/app/create.rs` and `lib/cli/src/utils/package_wizard/mod.rs` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `fc6471e4` feat(cli): Use registry templates to create new apps; `af177546` Improved Confirm dialog theme; `1a3a6521` Improved prompting — run `git show` on any of them.
Change coupling: exec.rs ↔ mod.rs lib/wasix/src/bin_factory/exec.rs:1 — `lib/wasix/src/bin_factory/exec.rs` and `lib/wasix/src/os/command/mod.rs` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `83a75a02` Refactor how `InlineWaker::block_on` works, while also refactoring `I…; `752f9ad2` Rename WasiRuntime to Runtime (at that commit the files were still `lib/wasi/src/bin_factory/exec.rs` and `lib/wasi/src/os/command/mod.rs`); `a41bf19d` Refactored the exit codes so they can be strongly typed and arbitary (at that commit the files were still `lib/wasi/src/bin_factory/exec.rs` and `lib/wasi/src/os/command/mod.rs`) — run `git show` on any of them.
Change coupling: sock_recv.rs ↔ sock_send.rs lib/wasix/src/syscalls/wasix/sock_recv.rs:1 — `lib/wasix/src/syscalls/wasix/sock_recv.rs` and `lib/wasix/src/syscalls/wasix/sock_send.rs` change together 60% of the time (12 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `db310f1e` fix(wasix): make sock_send/sock_recv handle PipeTx/PipeRx like pipe-b…; `de25a3ec` Fix calling sock_send with an FD from a socket pair; `387a89c3` Fix calling sock_send with an FD from a socket pair — run `git show` on any of them.
Change coupling: exec.rs ↔ proc_exit.rs lib/wasix/src/bin_factory/exec.rs:1 — `lib/wasix/src/bin_factory/exec.rs` and `lib/wasix/src/syscalls/wasi/proc_exit.rs` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `b92cd508` Adjust WasiVFork; `d2f7f787` Implement proc_vfork; `83a75a02` Refactor how `InlineWaker::block_on` works, while also refactoring `I… — run `git show` on any of them.
Change coupling: codegen.rs ↔ machine_x64.rs lib/compiler-singlepass/src/codegen.rs:1 — `lib/compiler-singlepass/src/codegen.rs` and `lib/compiler-singlepass/src/machine_x64.rs` change together 59% of the time (52 of the 88 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 52 shared commits counted here, the most recent 3 are `61105679` fix(VMOffsets): handle gracefully u32 -> i32 casting (#6904); `8cd62574` fix(Singlepass): simplify stack rounding logic (#6895); `7f49134d` feat(Singlepass): correct wasmer_vm_x function types, use RISC-V call… — run `git show` on any of them.
Change coupling: task_join_handle.rs ↔ env.rs lib/wasix/src/os/task/task_join_handle.rs:1 — `lib/wasix/src/os/task/task_join_handle.rs` and `lib/wasix/src/state/env.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `68fedb87` Fixed an issue where ctrl-c was not triggering during deep threading …; `9e3f3c03` Now reusing DCGI instances but not the memory associated with them; `a41bf19d` Refactored the exit codes so they can be strongly typed and arbitary (at that commit the files were still `lib/wasi/src/os/task/task_join_handle.rs` and `lib/wasi/src/state/env.rs`) — run `git show` on any of them.
Change coupling: mod.rs ↔ mod.rs lib/wasix/src/os/command/mod.rs:1 — `lib/wasix/src/os/command/mod.rs` and `lib/wasix/src/os/console/mod.rs` change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `da6d38a1` Apply review comments; `83a75a02` Refactor how `InlineWaker::block_on` works, while also refactoring `I…; `c04fffcb` fix: Remove top level constructions of `stores` — run `git show` on any of them.
Change coupling: futex_wait.rs ↔ thread_sleep.rs lib/wasix/src/syscalls/wasix/futex_wait.rs:1 — `lib/wasix/src/syscalls/wasix/futex_wait.rs` and `lib/wasix/src/syscalls/wasix/thread_sleep.rs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3713f1c6` Implemented an exponential CPU backoff that kicks in when a run token…; `45d98097` DProxy now correctly snapshots threads to the journal; `24368b50` More wiring of the snapshot options and the intercepts — run `git show` on any of them.
Change coupling: epoll_ctl.rs ↔ epoll_wait.rs lib/wasix/src/syscalls/wasix/epoll_ctl.rs:1 — `lib/wasix/src/syscalls/wasix/epoll_ctl.rs` and `lib/wasix/src/syscalls/wasix/epoll_wait.rs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `06082328` fix(wasix): Refactor EPOLL implementation; `94f2b9c0` Rework how pipes and event FDs interact with the epoll system; `31bf65dd` Fixed an issue where the notifications were not renewed on epoll enab… — run `git show` on any of them.
Change coupling: poll_oneoff.rs ↔ thread_sleep.rs lib/wasix/src/syscalls/wasi/poll_oneoff.rs:1 — `lib/wasix/src/syscalls/wasi/poll_oneoff.rs` and `lib/wasix/src/syscalls/wasix/thread_sleep.rs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3713f1c6` Implemented an exponential CPU backoff that kicks in when a run token…; `45d98097` DProxy now correctly snapshots threads to the journal; `24368b50` More wiring of the snapshot options and the intercepts — run `git show` on any of them.
Change coupling: stack_checkpoint.rs ↔ thread_spawn.rs lib/wasix/src/syscalls/wasix/stack_checkpoint.rs:1 — `lib/wasix/src/syscalls/wasix/stack_checkpoint.rs` and `lib/wasix/src/syscalls/wasix/thread_spawn.rs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `13203fde` Renamed InstanceSnapshot to StoreSnapshot which better reflects its p…; `31c4a61f` Refactored the snapshot feature toggle; `e2fd1daa` Removed the default stack size as its unreliable (at that commit the files were still `lib/wasi/src/syscalls/wasix/stack_checkpoint.rs` and `lib/wasi/src/syscalls/wasix/thread_spawn.rs`) — run `git show` on any of them.
Change coupling: push.rs ↔ tag.rs lib/cli/src/commands/package/push.rs:1 — `lib/cli/src/commands/package/push.rs` and `lib/cli/src/commands/package/tag.rs` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `e8c35d76` fix(cli): Actively wait for packages only after tag; `ba4b735e` fix(cli): More fixes on final user-facing messages; `6944f370` feat(cli): Better final messages for `push`, `tag` and `publish` — run `git show` on any of them.
Change coupling: binary_package.rs ↔ outputs.rs lib/wasix/src/bin_factory/binary_package.rs:1 — `lib/wasix/src/bin_factory/binary_package.rs` and `lib/wasix/src/runtime/resolver/outputs.rs` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d3f235f0` Partially resolve compilation errors after merge; `f4b1f202` catch up to latest webc changes; `c06e2cb4` wasmer can now run unnamed packages — run `git show` on any of them.
Change coupling: deploy.rs ↔ mod.rs lib/cli/src/commands/app/deploy.rs:1 — `lib/cli/src/commands/app/deploy.rs` and `lib/cli/src/utils/package_wizard/mod.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `fc6471e4` feat(cli): Use registry templates to create new apps; `af177546` Improved Confirm dialog theme; `1a3a6521` Improved prompting — run `git show` on any of them.

D23 · Boundary Type-Coupling · Cross-context type StoreMut (api → wasix) · ×16

Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:123 — StoreMut (context api) is exposed in wasix's public surface via InstantiationHook.additional_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:143 — StoreMut (context api) is exposed in wasix's public surface via InstantiationHook.prepare_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:159 — StoreMut (context api) is exposed in wasix's public surface via InstantiationHook.configure_new_instance — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:397 — StoreMut (context api) is exposed in wasix's public surface via Runtime.additional_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:411 — StoreMut (context api) is exposed in wasix's public surface via Runtime.prepare_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:427 — StoreMut (context api) is exposed in wasix's public surface via Runtime.configure_new_instance — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:917 — StoreMut (context api) is exposed in wasix's public surface via PluggableRuntime.additional_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:930 — StoreMut (context api) is exposed in wasix's public surface via PluggableRuntime.prepare_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:943 — StoreMut (context api) is exposed in wasix's public surface via PluggableRuntime.configure_new_instance — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:1170 — StoreMut (context api) is exposed in wasix's public surface via OverriddenRuntime.additional_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:1189 — StoreMut (context api) is exposed in wasix's public surface via OverriddenRuntime.prepare_imports — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/mod.rs:1206 — StoreMut (context api) is exposed in wasix's public surface via OverriddenRuntime.configure_new_instance — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:186 — StoreMut (context api) is exposed in wasix's public surface via VirtualTaskManager.build_memory — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/state/linker/mod.rs:332 — StoreMut (context api) is exposed in wasix's public surface via Linker.new — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/state/linker/mod.rs:673 — StoreMut (context api) is exposed in wasix's public surface via Linker.create_instance_group — couples the contexts.
Cross-context type StoreMut (api → wasix) lib/wasix/src/syscalls/wasix/context_create.rs:11 — StoreMut (context api) is exposed in wasix's public surface via context_create$module.lookup_typechecked_entrypoint — couples the contexts.

D3 · God Classes · TooManyMethods · ×16

TooManyMethods: JournalEffector lib/wasix/src/journal/effector/mod.rs:104 — TooManyMethods — 117 methods, declared across 59 files: effector/memory_and_snapshot.rs (2), effector/process_exit.rs (2), syscalls/chdir.rs (2), syscalls/clock_time.rs (2), +55 more file(s). The bar is 30 methods; this is 87 over it, 3.90× 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: TypedFunction lib/api/src/utils/native/typed_func.rs:23 — TooManyMethods — 110 methods, declared across 4 files: function/typed.rs (43), function/typed.rs (43), function/typed.rs (22), native/typed_func.rs (2). The bar is 30 methods; this is 80 over it, 3.67× 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: FuncEnvironment lib/compiler-cranelift/src/func_environ.rs:89 — TooManyMethods — 99 methods. The bar is 30 methods; this is 69 over it, 3.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasiEnvBuilder lib/wasix/src/state/builder.rs:51 — TooManyMethods — 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Instance lib/vm/src/instance/mod.rs:55 — TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VMOffsets lib/types/src/vmoffsets.rs:204 — TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasiFs lib/wasix/src/fs/mod.rs:569 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasiEnv lib/wasix/src/state/env.rs:182 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LLVMFunctionCodeGenerator lib/compiler-llvm/src/translator/code.rs:2517 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MachineX86_64 lib/compiler-singlepass/src/machine_x64.rs:94 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MachineARM64 lib/compiler-singlepass/src/machine_arm64.rs:36 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ModuleEnvironment lib/compiler/src/translator/environ.rs:62 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InodeSocket lib/wasix/src/net/socket.rs:237 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MachineRiscv lib/compiler-singlepass/src/machine_riscv.rs:76 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasiRunner lib/wasix/src/runners/wasi.rs:26 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WasiThread lib/wasix/src/os/task/thread.rs:98 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×15

Members sharing a duplicated core (4 members, 50+ identical tokens) lib/api/src/backend/js/entities/memory/view.rs:254 — lib/api/src/backend/js/entities/memory/view.rs:254-267 | lib/api/src/backend/sys/entities/memory/view.rs:177-190 | lib/api/src/backend/v8/entities/memory/view.rs:172-185 | lib/api/src/entities/memory/view/inner.rs:207-220 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/api/src/backend/sys/entities/memory/mod.rs:288 — lib/api/src/backend/sys/entities/memory/mod.rs:288-318 | lib/api/src/backend/sys/entities/memory/mod.rs:320-349 | lib/api/src/backend/v8/entities/memory/mod.rs:342-376 | lib/api/src/backend/v8/entities/memory/mod.rs:379-413 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/api/src/entities/function/inner.rs:223 — lib/api/src/entities/function/inner.rs:223-236 | lib/api/src/entities/function/inner.rs:258-275 | lib/api/src/entities/function/inner.rs:288-301 | lib/api/src/entities/function/inner.rs:315-332 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/cli/src/commands/app/secrets/create.rs:58 — lib/cli/src/commands/app/secrets/create.rs:58-71 | lib/cli/src/commands/app/secrets/delete.rs:60-73 | lib/cli/src/commands/app/secrets/reveal.rs:49-62 | lib/cli/src/commands/app/secrets/update.rs:63-76 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-cranelift/src/elf.rs:231 — lib/compiler-cranelift/src/elf.rs:231-381 | lib/compiler-singlepass/src/elf.rs:37-106 | lib/compiler/src/elf.rs:329-347 | lib/compiler/src/elf.rs:354-372 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-cranelift/src/func_environ.rs:2163 — lib/compiler-cranelift/src/func_environ.rs:2163-2178 | lib/compiler-cranelift/src/func_environ.rs:2190-2206 | lib/compiler-cranelift/src/func_environ.rs:2246-2272 | lib/compiler-cranelift/src/func_environ.rs:2282-2299 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-llvm/src/translator/intrinsics.rs:1493 — lib/compiler-llvm/src/translator/intrinsics.rs:1493-1587 | lib/compiler-llvm/src/translator/intrinsics.rs:1597-1658 | lib/compiler-llvm/src/translator/intrinsics.rs:1786-1859 | lib/compiler-llvm/src/translator/trampoline.rs:459-602 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/emitter_x64.rs:2035 — lib/compiler-singlepass/src/emitter_x64.rs:2035-2044 | lib/compiler-singlepass/src/emitter_x64.rs:2065-2074 | lib/compiler-singlepass/src/emitter_x64.rs:2095-2104 | lib/compiler-singlepass/src/emitter_x64.rs:2125-2134 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/emitter_x64.rs:2050 — lib/compiler-singlepass/src/emitter_x64.rs:2050-2059 | lib/compiler-singlepass/src/emitter_x64.rs:2080-2089 | lib/compiler-singlepass/src/emitter_x64.rs:2110-2119 | lib/compiler-singlepass/src/emitter_x64.rs:2140-2149 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_arm64.rs:2065 — lib/compiler-singlepass/src/machine_arm64.rs:2065-2146 | lib/compiler-singlepass/src/machine_riscv.rs:1109-1178 | lib/compiler-singlepass/src/machine_riscv.rs:1221-1280 | lib/compiler-singlepass/src/machine_riscv.rs:2443-2509 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_arm64.rs:7658 — lib/compiler-singlepass/src/machine_arm64.rs:7658-7689 | lib/compiler-singlepass/src/machine_arm64.rs:7697-7728 | lib/compiler-singlepass/src/machine_arm64.rs:7736-7767 | lib/compiler-singlepass/src/machine_arm64.rs:7775-7806 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_arm64.rs:7886 — lib/compiler-singlepass/src/machine_arm64.rs:7886-7898 | lib/compiler-singlepass/src/machine_arm64.rs:7924-7936 | lib/compiler-singlepass/src/machine_arm64.rs:8171-8183 | lib/compiler-singlepass/src/machine_arm64.rs:8209-8221 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_arm64.rs:7905 — lib/compiler-singlepass/src/machine_arm64.rs:7905-7917 | lib/compiler-singlepass/src/machine_arm64.rs:7943-7955 | lib/compiler-singlepass/src/machine_arm64.rs:8190-8202 | lib/compiler-singlepass/src/machine_arm64.rs:8228-8240 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_x64.rs:6888 — lib/compiler-singlepass/src/machine_x64.rs:6888-6944 | lib/compiler-singlepass/src/machine_x64.rs:6951-6981 | lib/compiler-singlepass/src/machine_x64.rs:6988-7044 | lib/compiler-singlepass/src/machine_x64.rs:7051-7081 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/wasix/src/net/socket.rs:1252 — lib/wasix/src/net/socket.rs:1252-1263 | lib/wasix/src/net/socket.rs:1265-1276 | lib/wasix/src/net/socket.rs:1278-1289 | lib/wasix/src/net/socket.rs:1291-1302 — 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 · Duplicated block (16 lines × 2) · ×15

Duplicated block (16 lines × 2) lib/api/src/backend/js/entities/memory/view.rs:118 — lib/api/src/backend/js/entities/memory/view.rs:118-133 | lib/api/src/backend/js/entities/memory/view.rs:171-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/api/src/utils/mem/access.rs:243 — lib/api/src/utils/mem/access.rs:243-258 | lib/api/src/utils/mem/access.rs:293-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/cli/src/commands/app/create.rs:61 — lib/cli/src/commands/app/create.rs:61-76 | lib/cli/src/commands/app/create.rs:164-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-llvm/src/translator/code.rs:8774 — lib/compiler-llvm/src/translator/code.rs:8774-8789 | lib/compiler-llvm/src/translator/code.rs:8798-8813 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-llvm/src/translator/code.rs:11373 — lib/compiler-llvm/src/translator/code.rs:11373-11388 | lib/compiler-llvm/src/translator/code.rs:11401-11416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/codegen.rs:2315 — lib/compiler-singlepass/src/codegen.rs:2315-2330 | lib/compiler-singlepass/src/codegen.rs:2378-2393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/codegen.rs:5575 — lib/compiler-singlepass/src/codegen.rs:5575-5590 | lib/compiler-singlepass/src/codegen.rs:5619-5634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:727 — lib/compiler-singlepass/src/machine_x64.rs:727-742 | lib/compiler-singlepass/src/machine_x64.rs:872-887 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:1128 — lib/compiler-singlepass/src/machine_x64.rs:1128-1143 | lib/compiler-singlepass/src/machine_x64.rs:1541-1556 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4371 — lib/compiler-singlepass/src/machine_x64.rs:4371-4386 | lib/compiler-singlepass/src/machine_x64.rs:6714-6729 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4425 — lib/compiler-singlepass/src/machine_x64.rs:4425-4440 | lib/compiler-singlepass/src/machine_x64.rs:6594-6609 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4485 — lib/compiler-singlepass/src/machine_x64.rs:4485-4500 | lib/compiler-singlepass/src/machine_x64.rs:6654-6669 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/compiler/src/engine/artifact.rs:590 — lib/compiler/src/engine/artifact.rs:590-605 | lib/compiler/src/engine/artifact.rs:607-622 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/vm/src/table.rs:300 — lib/vm/src/table.rs:300-315 | lib/vm/src/table.rs:349-364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/wasix/src/net/socket.rs:1483 — lib/wasix/src/net/socket.rs:1483-1498 | lib/wasix/src/net/socket.rs:1576-1591 — 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 (9 lines × 3) · ×15

Duplicated block (9 lines × 3) lib/compiler-llvm/src/translator/code.rs:5292 — lib/compiler-llvm/src/translator/code.rs:5292-5300 | lib/compiler-llvm/src/translator/code.rs:5394-5402 | lib/compiler-llvm/src/translator/code.rs:5496-5504 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/compiler-llvm/src/translator/code.rs:5785 — lib/compiler-llvm/src/translator/code.rs:5785-5793 | lib/compiler-llvm/src/translator/code.rs:5845-5853 | lib/compiler-llvm/src/translator/code.rs:5905-5913 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/compiler-llvm/src/translator/code.rs:5800 — lib/compiler-llvm/src/translator/code.rs:5800-5808 | lib/compiler-llvm/src/translator/code.rs:5860-5868 | lib/compiler-llvm/src/translator/code.rs:5920-5928 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/compiler-llvm/src/translator/code.rs:5815 — lib/compiler-llvm/src/translator/code.rs:5815-5823 | lib/compiler-llvm/src/translator/code.rs:5875-5883 | lib/compiler-llvm/src/translator/code.rs:5935-5943 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/compiler-llvm/src/translator/code.rs:5830 — lib/compiler-llvm/src/translator/code.rs:5830-5838 | lib/compiler-llvm/src/translator/code.rs:5890-5898 | lib/compiler-llvm/src/translator/code.rs:5950-5958 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/compiler-singlepass/src/machine_riscv.rs:1381 — lib/compiler-singlepass/src/machine_riscv.rs:1381-1389 | lib/compiler-singlepass/src/machine_riscv.rs:1433-1441 | lib/compiler-singlepass/src/machine_riscv.rs:1490-1498 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:7403 — lib/compiler-singlepass/src/machine_x64.rs:7403-7411 | lib/compiler-singlepass/src/machine_x64.rs:7805-7813 | lib/compiler-singlepass/src/machine_x64.rs:7920-7928 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/virtual-net/src/client.rs:782 — lib/virtual-net/src/client.rs:782-790 | lib/virtual-net/src/client.rs:813-821 | lib/virtual-net/src/client.rs:863-871 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/wasix/src/syscalls/mod.rs:663 — lib/wasix/src/syscalls/mod.rs:663-671 | lib/wasix/src/syscalls/mod.rs:702-710 | lib/wasix/src/syscalls/mod.rs:739-747 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/api/src/backend/js/entities/function/env.rs:146 — lib/api/src/backend/js/entities/function/env.rs:146-154 | lib/api/src/backend/sys/entities/function/env.rs:160-168 | lib/api/src/backend/v8/entities/function/env.rs:140-148 — before extracting anything, compare `lib/api/src/backend/js/entities/function/env.rs` and `lib/api/src/backend/sys/entities/function/env.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) lib/api/src/backend/js/entities/store/handle.rs:128 — lib/api/src/backend/js/entities/store/handle.rs:128-136 | lib/api/src/backend/v8/entities/store/obj.rs:258-266 | lib/vm/src/store.rs:271-279 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) lib/api/src/backend/js/entities/function/env.rs:29 — lib/api/src/backend/js/entities/function/env.rs:29-37 | lib/api/src/backend/sys/entities/function/env.rs:23-31 | lib/api/src/backend/v8/entities/function/env.rs:23-31 — before extracting anything, compare `lib/api/src/backend/js/entities/function/env.rs` and `lib/api/src/backend/sys/entities/function/env.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) lib/wasix/src/syscalls/wasix/sock_send.rs:68 — lib/wasix/src/syscalls/wasix/sock_send.rs:68-76 | lib/wasix/src/syscalls/wasix/sock_send_file.rs:36-44 | lib/wasix/src/syscalls/wasix/sock_send_to.rs:64-73 — before extracting anything, compare `lib/wasix/src/syscalls/wasix/sock_send.rs` and `lib/wasix/src/syscalls/wasix/sock_send_to.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) lib/wasix/src/lib.rs:424 — lib/wasix/src/lib.rs:424-432 | lib/wasix/src/lib.rs:480-488 | lib/wasix/src/lib.rs:545-553 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) fuzz/fuzz_targets/cranelift.rs:16 — fuzz/fuzz_targets/cranelift.rs:16-24 | fuzz/fuzz_targets/llvm.rs:16-24 | fuzz/fuzz_targets/misc.rs:10-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (7 lines × 3) · ×15

Duplicated block (7 lines × 3) lib/api/src/backend/js/entities/function/typed.rs:92 — lib/api/src/backend/js/entities/function/typed.rs:92-98 | lib/api/src/backend/sys/entities/function/typed.rs:96-102 | lib/api/src/backend/sys/entities/function/typed.rs:234-240 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) lib/compiler-cranelift/src/elf.rs:241 — lib/compiler-cranelift/src/elf.rs:241-247 | lib/compiler-singlepass/src/elf.rs:45-51 | lib/compiler/src/elf.rs:336-342 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler-singlepass/src/elf.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) lib/compiler-llvm/src/translator/code.rs:4391 — lib/compiler-llvm/src/translator/code.rs:4391-4397 | lib/compiler-llvm/src/translator/code.rs:4402-4408 | lib/compiler-llvm/src/translator/code.rs:4413-4419 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/compiler-llvm/src/translator/code.rs:4716 — lib/compiler-llvm/src/translator/code.rs:4716-4722 | lib/compiler-llvm/src/translator/code.rs:4819-4825 | lib/compiler-llvm/src/translator/code.rs:4973-4979 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/compiler-llvm/src/translator/code.rs:9912 — lib/compiler-llvm/src/translator/code.rs:9912-9918 | lib/compiler-llvm/src/translator/code.rs:10366-10372 | lib/compiler-llvm/src/translator/code.rs:10379-10385 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/compiler-llvm/src/translator/code.rs:9926 — lib/compiler-llvm/src/translator/code.rs:9926-9932 | lib/compiler-llvm/src/translator/code.rs:9940-9946 | lib/compiler-llvm/src/translator/code.rs:9954-9960 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:381 — lib/compiler-singlepass/src/machine_arm64.rs:381-387 | lib/compiler-singlepass/src/machine_arm64.rs:523-529 | lib/compiler-singlepass/src/machine_arm64.rs:561-567 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:2352 — lib/compiler-singlepass/src/machine_x64.rs:2352-2358 | lib/compiler-singlepass/src/machine_x64.rs:2363-2369 | lib/compiler-singlepass/src/machine_x64.rs:2374-2380 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/wasix/src/syscalls/wasix/port_addr_remove.rs:15 — lib/wasix/src/syscalls/wasix/port_addr_remove.rs:15-21 | lib/wasix/src/syscalls/wasix/port_gateway_set.rs:15-21 | lib/wasix/src/syscalls/wasix/port_route_remove.rs:11-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (7 lines × 3) lib/compiler-llvm/src/translator/code.rs:11362 — lib/compiler-llvm/src/translator/code.rs:11362-11368 | lib/compiler-llvm/src/translator/code.rs:11390-11396 | lib/compiler-llvm/src/translator/code.rs:11417-11423 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1550 — lib/compiler-singlepass/src/machine_arm64.rs:1550-1556 | lib/compiler-singlepass/src/machine_riscv.rs:2092-2098 | lib/compiler-singlepass/src/machine_x64.rs:2143-2149 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) lib/api/src/backend/js/entities/function/env.rs:43 — lib/api/src/backend/js/entities/function/env.rs:43-49 | lib/api/src/backend/sys/entities/function/env.rs:52-58 | lib/api/src/backend/v8/entities/function/env.rs:37-43 — before extracting anything, compare `lib/api/src/backend/js/entities/function/env.rs` and `lib/api/src/backend/sys/entities/function/env.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) lib/api/src/backend/js/entities/function/env.rs:62 — lib/api/src/backend/js/entities/function/env.rs:62-68 | lib/api/src/backend/sys/entities/function/env.rs:61-67 | lib/api/src/backend/v8/entities/function/env.rs:56-62 — before extracting anything, compare `lib/api/src/backend/js/entities/function/env.rs` and `lib/api/src/backend/sys/entities/function/env.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) lib/wasix/src/syscalls/wasix/sock_join_multicast_v4.rs:48 — lib/wasix/src/syscalls/wasix/sock_join_multicast_v4.rs:48-54 | lib/wasix/src/syscalls/wasix/sock_join_multicast_v6.rs:47-53 | lib/wasix/src/syscalls/wasix/sock_leave_multicast_v4.rs:48-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (7 lines × 3) lib/wasix/src/syscalls/wasix/fd_pipe.rs:34 — lib/wasix/src/syscalls/wasix/fd_pipe.rs:34-40 | lib/wasix/src/syscalls/wasix/sock_open.rs:49-55 | lib/wasix/src/syscalls/wasix/sock_pair.rs:64-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.

D23 · Boundary Type-Coupling · Cross-context type StoreId (types → api) · ×14

Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/handle.rs:75 — StoreId (context types) is exposed in api's public surface via StoreHandle.store_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/handle.rs:81 — StoreId (context types) is exposed in api's public surface via StoreHandle.set_store_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/handle.rs:89 — StoreId (context types) is exposed in api's public surface via StoreHandle.from_internal — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/obj.rs:60 — StoreId (context types) is exposed in api's public surface via StoreObjects.id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/js/entities/store/obj.rs:65 — StoreId (context types) is exposed in api's public surface via StoreObjects.set_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/sys/entities/store/mod.rs:113 — StoreId (context types) is exposed in api's public surface via Interrupter.new — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs:81 — StoreId (context types) is exposed in api's public surface via StoreObjects.id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs:86 — StoreId (context types) is exposed in api's public surface via StoreObjects.set_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs:205 — StoreId (context types) is exposed in api's public surface via StoreHandle.store_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs:211 — StoreId (context types) is exposed in api's public surface via StoreHandle.set_store_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/backend/v8/entities/store/obj.rs:219 — StoreId (context types) is exposed in api's public surface via StoreHandle.from_internal — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/entities/store/async_.rs:93 — StoreId (context types) is exposed in api's public surface via AsStoreAsync.store_id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/entities/store/mod.rs:120 — StoreId (context types) is exposed in api's public surface via Store.id — couples the contexts.
Cross-context type StoreId (types → api) lib/api/src/entities/store/obj.rs:44 — StoreId (context types) is exposed in api's public surface via StoreObjects.id — couples the contexts.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×14

Duplicated block (15 lines × 2) lib/api/src/backend/v8/entities/memory/mod.rs:265 — lib/api/src/backend/v8/entities/memory/mod.rs:265-279 | lib/api/src/backend/v8/entities/memory/mod.rs:291-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:3251 — lib/compiler-cranelift/src/translator/code_translator.rs:3251-3265 | lib/compiler-cranelift/src/translator/code_translator.rs:3304-3318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-llvm/src/translator/code.rs:6196 — lib/compiler-llvm/src/translator/code.rs:6196-6210 | lib/compiler-llvm/src/translator/code.rs:6465-6479 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-llvm/src/translator/code.rs:6222 — lib/compiler-llvm/src/translator/code.rs:6222-6236 | lib/compiler-llvm/src/translator/code.rs:6572-6586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-llvm/src/translator/code.rs:8675 — lib/compiler-llvm/src/translator/code.rs:8675-8689 | lib/compiler-llvm/src/translator/code.rs:8703-8717 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-llvm/src/translator/code.rs:9175 — lib/compiler-llvm/src/translator/code.rs:9175-9189 | lib/compiler-llvm/src/translator/code.rs:9233-9247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-llvm/src/translator/code.rs:11963 — lib/compiler-llvm/src/translator/code.rs:11963-11977 | lib/compiler-llvm/src/translator/code.rs:12032-12046 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:966 — lib/compiler-singlepass/src/machine_arm64.rs:966-980 | lib/compiler-singlepass/src/machine_riscv.rs:924-938 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2923 — lib/compiler-singlepass/src/machine_arm64.rs:2923-2937 | lib/compiler-singlepass/src/machine_arm64.rs:5106-5120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4232 — lib/compiler-singlepass/src/machine_x64.rs:4232-4246 | lib/compiler-singlepass/src/machine_x64.rs:6483-6497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/virtual-fs/src/mem_fs/file.rs:1736 — lib/virtual-fs/src/mem_fs/file.rs:1736-1750 | lib/virtual-fs/src/mem_fs/offloaded_file.rs:164-178 — 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 (15 lines × 2) lib/virtual-net/src/server.rs:1585 — lib/virtual-net/src/server.rs:1585-1599 | lib/virtual-net/src/server.rs:1606-1620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/wasix/src/syscalls/journal/maybe_snapshot_many.rs:30 — lib/wasix/src/syscalls/journal/maybe_snapshot_many.rs:30-44 | lib/wasix/src/syscalls/journal/maybe_snapshot_once.rs:30-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) lib/wasix/src/syscalls/wasix/proc_exec3.rs:67 — lib/wasix/src/syscalls/wasix/proc_exec3.rs:67-81 | lib/wasix/src/syscalls/wasix/proc_exec4.rs:62-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (7 lines × 4) · ×13

Duplicated block (7 lines × 4) lib/compiler-llvm/src/translator/code.rs:4045 — lib/compiler-llvm/src/translator/code.rs:4045-4051 | lib/compiler-llvm/src/translator/code.rs:4056-4062 | lib/compiler-llvm/src/translator/code.rs:4120-4126 | lib/compiler-llvm/src/translator/code.rs:4176-4182 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-llvm/src/translator/code.rs:4267 — lib/compiler-llvm/src/translator/code.rs:4267-4273 | lib/compiler-llvm/src/translator/code.rs:4278-4284 | lib/compiler-llvm/src/translator/code.rs:4289-4295 | lib/compiler-llvm/src/translator/code.rs:4300-4306 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-llvm/src/translator/code.rs:5364 — lib/compiler-llvm/src/translator/code.rs:5364-5370 | lib/compiler-llvm/src/translator/code.rs:5385-5391 | lib/compiler-llvm/src/translator/code.rs:5403-5409 | lib/compiler-llvm/src/translator/code.rs:5425-5431 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-llvm/src/translator/code.rs:5466 — lib/compiler-llvm/src/translator/code.rs:5466-5472 | lib/compiler-llvm/src/translator/code.rs:5487-5493 | lib/compiler-llvm/src/translator/code.rs:5505-5511 | lib/compiler-llvm/src/translator/code.rs:5527-5533 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-llvm/src/translator/code.rs:5729 — lib/compiler-llvm/src/translator/code.rs:5729-5735 | lib/compiler-llvm/src/translator/code.rs:5744-5750 | lib/compiler-llvm/src/translator/code.rs:5759-5765 | lib/compiler-llvm/src/translator/code.rs:5774-5780 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-llvm/src/translator/code.rs:10185 — lib/compiler-llvm/src/translator/code.rs:10185-10191 | lib/compiler-llvm/src/translator/code.rs:10195-10201 | lib/compiler-llvm/src/translator/code.rs:10205-10211 | lib/compiler-llvm/src/translator/code.rs:10215-10221 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:975 — lib/compiler-singlepass/src/machine_x64.rs:975-981 | lib/compiler-singlepass/src/machine_x64.rs:1170-1176 | lib/compiler-singlepass/src/machine_x64.rs:1583-1589 | lib/compiler-singlepass/src/machine_x64.rs:2511-2517 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:3032 — lib/compiler-singlepass/src/machine_x64.rs:3032-3038 | lib/compiler-singlepass/src/machine_x64.rs:3087-3093 | lib/compiler-singlepass/src/machine_x64.rs:4815-4821 | lib/compiler-singlepass/src/machine_x64.rs:4870-4876 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:3046 — lib/compiler-singlepass/src/machine_x64.rs:3046-3052 | lib/compiler-singlepass/src/machine_x64.rs:3101-3107 | lib/compiler-singlepass/src/machine_x64.rs:4829-4835 | lib/compiler-singlepass/src/machine_x64.rs:4884-4890 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:6889 — lib/compiler-singlepass/src/machine_x64.rs:6889-6895 | lib/compiler-singlepass/src/machine_x64.rs:6952-6958 | lib/compiler-singlepass/src/machine_x64.rs:6989-6995 | lib/compiler-singlepass/src/machine_x64.rs:7052-7058 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/wasix/src/net/socket.rs:1257 — lib/wasix/src/net/socket.rs:1257-1263 | lib/wasix/src/net/socket.rs:1270-1276 | lib/wasix/src/net/socket.rs:1283-1289 | lib/wasix/src/net/socket.rs:1296-1302 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/wasix/src/net/socket.rs:1356 — lib/wasix/src/net/socket.rs:1356-1362 | lib/wasix/src/net/socket.rs:1440-1446 | lib/wasix/src/net/socket.rs:1532-1538 | lib/wasix/src/net/socket.rs:1623-1629 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 4) lib/wasix/src/state/linker/instance_group/imports.rs:435 — lib/wasix/src/state/linker/instance_group/imports.rs:435-442 | lib/wasix/src/state/linker/instance_group/imports.rs:452-459 | lib/wasix/src/state/linker/instance_group/imports.rs:469-475 | lib/wasix/src/state/linker/instance_group/imports.rs:482-488 — 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.

D17 · Explicit Debt · HackComment · ×12

HackComment lib/wasix/src/state/linker/linker_state.rs:39 — // hack from back then. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/wasix/src/state/linker/mod.rs:498 — // HACK: The main module doesn't have to exist in the virtual FS at all; e.g. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/wasix/src/runtime/package_loader/load_package_tree.rs:265 — /// HACK: Some older packages like `sharrattj/bash` and `sharrattj/coreutils` — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/wasix/src/runners/wasi_common.rs:353 — /// HACK: We need this so users can mount host directories at relative paths. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/wasix/src/http/web_http_client.rs:55 — /// # Hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/wasix/src/bin_factory/binary_package.rs:210 — // HACK: webc has no way to return its deserialized manifest to us, so we need to do it again here — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/virtual-fs/src/overlay_fs.rs:1334 — // HACK: We shouldn't really be ignoring FsError::BaseNotDirectory, but — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/virtual-fs/src/webc_volume_fs.rs:421 — // HACK: WebC v2 doesn't have timestamps, and WebC v3 files sometimes — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/derive/tests/compiletest.rs:31 — // hack to make this work on OSX: we probably don't need it though — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/compiler-llvm/src/config.rs:284 — // Hack: we're using is_pic to determine whether this is a native — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/cli/src/commands/package/common/mod.rs:25 — // HACK: We want to invalidate the cache used for GraphQL queries so — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment lib/api/src/entities/exports.rs:151 — /// Hack to get this working with nativefunc too — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.

D23 · Boundary Type-Coupling · Cross-context type Bytes (types → wasix) · ×12

Cross-context type Bytes (types → wasix) lib/wasix/src/journal/effector/thread_state.rs:14 — Bytes (context types) is exposed in wasix's public surface via JournalEffector.save_thread_state — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/journal/effector/thread_state.rs:41 — Bytes (context types) is exposed in wasix's public surface via JournalEffector.apply_thread_state — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/lib.rs:356 — Bytes (context types) is exposed in wasix's public surface via WasiVForkAsyncify.store_data — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/rewind.rs:21 — Bytes (context types) is exposed in wasix's public surface via RewindPostProcess.finish — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/rewind.rs:26 — Bytes (context types) is exposed in wasix's public surface via RewindState.memory_stack — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/rewind.rs:28 — Bytes (context types) is exposed in wasix's public surface via RewindState.rewind_stack — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/rewind.rs:30 — Bytes (context types) is exposed in wasix's public surface via RewindState.store_data — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/runtime/package_loader/builtin_loader.rs:802 — Bytes (context types) is exposed in wasix's public surface via FileSystemCache.save — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/runtime/package_loader/builtin_loader.rs:549 — Bytes (context types) is exposed in wasix's public surface via PackageCache.save — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/runtime/resolver/backend_source.rs:457 — Bytes (context types) is exposed in wasix's public surface via QueryCache.save — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/syscalls/mod.rs:1313 — Bytes (context types) is exposed in wasix's public surface via syscalls$module.rewind — couples the contexts.
Cross-context type Bytes (types → wasix) lib/wasix/src/syscalls/mod.rs:1337 — Bytes (context types) is exposed in wasix's public surface via syscalls$module.rewind_ext — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Memory (api → wasix) · ×12

Cross-context type Memory (api → wasix) lib/wasix/src/runtime/mod.rs:159 — Memory (context api) is exposed in wasix's public surface via InstantiationHook.configure_new_instance — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/runtime/mod.rs:427 — Memory (context api) is exposed in wasix's public surface via Runtime.configure_new_instance — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/runtime/mod.rs:943 — Memory (context api) is exposed in wasix's public surface via PluggableRuntime.configure_new_instance — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/runtime/mod.rs:1206 — Memory (context api) is exposed in wasix's public surface via OverriddenRuntime.configure_new_instance — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:80 — Memory (context api) is exposed in wasix's public surface via TaskWasmRecycleProperties.memory — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/handles/mod.rs:119 — Memory (context api) is exposed in wasix's public surface via WasiModuleInstanceHandles.new — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/handles/mod.rs:198 — Memory (context api) is exposed in wasix's public surface via WasiModuleInstanceHandles.memory — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/handles/mod.rs:204 — Memory (context api) is exposed in wasix's public surface via WasiModuleInstanceHandles.memory_clone — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/handles/mod.rs:311 — Memory (context api) is exposed in wasix's public surface via WasiModuleTreeHandles.memory — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/handles/mod.rs:317 — Memory (context api) is exposed in wasix's public surface via WasiModuleTreeHandles.memory_clone — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/linker/mod.rs:332 — Memory (context api) is exposed in wasix's public surface via Linker.new — couples the contexts.
Cross-context type Memory (api → wasix) lib/wasix/src/state/linker/types.rs:38 — Memory (context api) is exposed in wasix's public surface via LinkedMainModule.memory — couples the contexts.

D4 · Code Duplication · Duplicated block (6–8 lines × 2) · ×12

Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5783 — lib/compiler-llvm/src/translator/code.rs:5783-5788 | lib/compiler-llvm/src/translator/code.rs:7622-7629 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5798 — lib/compiler-llvm/src/translator/code.rs:5798-5803 | lib/compiler-llvm/src/translator/code.rs:7709-7716 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5813 — lib/compiler-llvm/src/translator/code.rs:5813-5818 | lib/compiler-llvm/src/translator/code.rs:7943-7950 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5828 — lib/compiler-llvm/src/translator/code.rs:5828-5833 | lib/compiler-llvm/src/translator/code.rs:8033-8040 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5843 — lib/compiler-llvm/src/translator/code.rs:5843-5848 | lib/compiler-llvm/src/translator/code.rs:7640-7647 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5858 — lib/compiler-llvm/src/translator/code.rs:5858-5863 | lib/compiler-llvm/src/translator/code.rs:7727-7734 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5873 — lib/compiler-llvm/src/translator/code.rs:5873-5878 | lib/compiler-llvm/src/translator/code.rs:7961-7968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5888 — lib/compiler-llvm/src/translator/code.rs:5888-5893 | lib/compiler-llvm/src/translator/code.rs:8051-8058 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5903 — lib/compiler-llvm/src/translator/code.rs:5903-5908 | lib/compiler-llvm/src/translator/code.rs:7658-7665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5918 — lib/compiler-llvm/src/translator/code.rs:5918-5923 | lib/compiler-llvm/src/translator/code.rs:7745-7752 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5933 — lib/compiler-llvm/src/translator/code.rs:5933-5938 | lib/compiler-llvm/src/translator/code.rs:7979-7986 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–8 lines × 2) lib/compiler-llvm/src/translator/code.rs:5948 — lib/compiler-llvm/src/translator/code.rs:5948-5953 | lib/compiler-llvm/src/translator/code.rs:8069-8076 — 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 (6 lines × 3) · ×12

Duplicated block (6 lines × 3) lib/api/src/backend/js/entities/store/obj.rs:81 — lib/api/src/backend/js/entities/store/obj.rs:81-86 | lib/api/src/backend/v8/entities/store/obj.rs:102-107 | lib/vm/src/store.rs:112-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 3) lib/api/src/backend/v8/entities/function/mod.rs:319 — lib/api/src/backend/v8/entities/function/mod.rs:319-324 | lib/api/src/backend/v8/entities/function/mod.rs:327-332 | lib/api/src/backend/v8/entities/tag.rs:64-69 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/codegen.rs:5556 — lib/compiler-singlepass/src/codegen.rs:5556-5561 | lib/compiler-singlepass/src/codegen.rs:5601-5606 | lib/compiler-singlepass/src/codegen.rs:5681-5686 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:2067 — lib/compiler-singlepass/src/machine_arm64.rs:2067-2073 | lib/compiler-singlepass/src/machine_riscv.rs:1236-1241 | lib/compiler-singlepass/src/machine_riscv.rs:2445-2451 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:2530 — lib/compiler-singlepass/src/machine_x64.rs:2530-2535 | lib/compiler-singlepass/src/machine_x64.rs:7799-7804 | lib/compiler-singlepass/src/machine_x64.rs:7914-7919 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) lib/virtual-fs/src/mem_fs/mod.rs:157 — lib/virtual-fs/src/mem_fs/mod.rs:157-162 | lib/virtual-fs/src/mem_fs/mod.rs:183-188 | lib/virtual-fs/src/mem_fs/mod.rs:207-212 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) lib/api/src/backend/js/entities/store/handle.rs:39 — lib/api/src/backend/js/entities/store/handle.rs:39-44 | lib/api/src/backend/v8/entities/store/obj.rs:169-174 | lib/vm/src/store.rs:169-174 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/arm64_decl.rs:145 — lib/compiler-singlepass/src/arm64_decl.rs:145-150 | lib/compiler-singlepass/src/riscv_decl.rs:99-104 | lib/compiler-singlepass/src/x64_decl.rs:70-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1372 — lib/compiler-singlepass/src/machine_arm64.rs:1372-1377 | lib/compiler-singlepass/src/machine_riscv.rs:1949-1954 | lib/compiler-singlepass/src/machine_x64.rs:1981-1986 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1531 — lib/compiler-singlepass/src/machine_arm64.rs:1531-1536 | lib/compiler-singlepass/src/machine_riscv.rs:2073-2078 | lib/compiler-singlepass/src/machine_x64.rs:2124-2129 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) lib/compiler-singlepass/src/machine_riscv.rs:1787 — lib/compiler-singlepass/src/machine_riscv.rs:1787-1792 | lib/compiler-singlepass/src/machine_x64.rs:1168-1173 | lib/compiler-singlepass/src/machine_x64.rs:1581-1586 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) lib/virtual-fs/src/mem_fs/filesystem.rs:883 — lib/virtual-fs/src/mem_fs/filesystem.rs:883-888 | lib/virtual-fs/src/mem_fs/filesystem.rs:930-935 | lib/virtual-fs/src/mem_fs/filesystem.rs:971-976 — 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 (17 lines × 2) · ×11

Duplicated block (17 lines × 2) lib/api/src/backend/sys/entities/function/mod.rs:276 — lib/api/src/backend/sys/entities/function/mod.rs:276-292 | lib/api/src/backend/sys/entities/function/mod.rs:429-445 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/api/src/backend/sys/entities/memory/mod.rs:261 — lib/api/src/backend/sys/entities/memory/mod.rs:261-277 | lib/api/src/backend/v8/entities/memory/mod.rs:315-331 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) lib/compiler-llvm/src/translator/code.rs:10421 — lib/compiler-llvm/src/translator/code.rs:10421-10437 | lib/compiler-llvm/src/translator/code.rs:10449-10465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/compiler-singlepass/src/emitter_riscv.rs:1916 — lib/compiler-singlepass/src/emitter_riscv.rs:1916-1932 | lib/compiler-singlepass/src/emitter_riscv.rs:2074-2090 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/compiler-singlepass/src/emitter_riscv.rs:2003 — lib/compiler-singlepass/src/emitter_riscv.rs:2003-2019 | lib/compiler-singlepass/src/emitter_riscv.rs:2138-2154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/compiler/src/compiler.rs:523 — lib/compiler/src/compiler.rs:523-539 | lib/compiler/src/compiler.rs:565-581 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/virtual-fs/src/mem_fs/file.rs:936 — lib/virtual-fs/src/mem_fs/file.rs:936-952 | lib/virtual-fs/src/mem_fs/file.rs:1124-1140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/virtual-net/src/client.rs:320 — lib/virtual-net/src/client.rs:320-336 | lib/virtual-net/src/server.rs:379-395 — before extracting anything, compare `lib/virtual-net/src/client.rs` and `lib/virtual-net/src/server.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) lib/wasix/src/syscalls/wasi/fd_read.rs:297 — lib/wasix/src/syscalls/wasi/fd_read.rs:297-313 | lib/wasix/src/syscalls/wasi/fd_read.rs:351-367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/wasix/src/syscalls/wasix/sock_send.rs:137 — lib/wasix/src/syscalls/wasix/sock_send.rs:137-153 | lib/wasix/src/syscalls/wasix/sock_send_to.rs:149-165 — before extracting anything, compare `lib/wasix/src/syscalls/wasix/sock_send.rs` and `lib/wasix/src/syscalls/wasix/sock_send_to.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) lib/api/src/backend/v8/entities/module.rs:55 — lib/api/src/backend/v8/entities/module.rs:55-71 | lib/api/src/backend/v8/entities/module.rs:84-101 — 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 (12 lines × 3) · ×11

Duplicated block (12 lines × 3) lib/compiler-llvm/src/translator/code.rs:5250 — lib/compiler-llvm/src/translator/code.rs:5250-5261 | lib/compiler-llvm/src/translator/code.rs:5352-5363 | lib/compiler-llvm/src/translator/code.rs:5454-5465 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/compiler-llvm/src/translator/code.rs:5271 — lib/compiler-llvm/src/translator/code.rs:5271-5282 | lib/compiler-llvm/src/translator/code.rs:5373-5384 | lib/compiler-llvm/src/translator/code.rs:5475-5486 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/compiler-singlepass/src/emitter_arm64.rs:3288 — lib/compiler-singlepass/src/emitter_arm64.rs:3288-3299 | lib/compiler-singlepass/src/emitter_riscv.rs:2179-2190 | lib/compiler-singlepass/src/machine_x64.rs:8324-8335 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (12 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1884 — lib/compiler-singlepass/src/machine_arm64.rs:1884-1895 | lib/compiler-singlepass/src/machine_arm64.rs:1899-1910 | lib/compiler-singlepass/src/machine_arm64.rs:1914-1925 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:2655 — lib/compiler-singlepass/src/machine_arm64.rs:2655-2666 | lib/compiler-singlepass/src/machine_arm64.rs:2693-2704 | lib/compiler-singlepass/src/machine_arm64.rs:4838-4849 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:4554 — lib/compiler-singlepass/src/machine_arm64.rs:4554-4565 | lib/compiler-singlepass/src/machine_arm64.rs:4617-4628 | lib/compiler-singlepass/src/machine_arm64.rs:4680-4691 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:6612 — lib/compiler-singlepass/src/machine_x64.rs:6612-6623 | lib/compiler-singlepass/src/machine_x64.rs:6672-6683 | lib/compiler-singlepass/src/machine_x64.rs:6732-6743 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/virtual-fs/src/overlay_fs.rs:286 — lib/virtual-fs/src/overlay_fs.rs:286-297 | lib/virtual-fs/src/overlay_fs.rs:533-544 | lib/virtual-fs/src/overlay_fs.rs:562-573 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/wasix/src/syscalls/wasi/fd_read.rs:219 — lib/wasix/src/syscalls/wasi/fd_read.rs:219-230 | lib/wasix/src/syscalls/wasi/fd_read.rs:334-346 | lib/wasix/src/syscalls/wasi/fd_read.rs:388-400 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/wasix/src/syscalls/wasi/fd_read.rs:246 — lib/wasix/src/syscalls/wasi/fd_read.rs:246-257 | lib/wasix/src/syscalls/wasi/fd_read.rs:302-313 | lib/wasix/src/syscalls/wasi/fd_read.rs:356-367 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/wasix/src/syscalls/wasi/fd_write.rs:421 — lib/wasix/src/syscalls/wasi/fd_write.rs:421-432 | lib/wasix/src/syscalls/wasi/fd_write.rs:480-491 | lib/wasix/src/syscalls/wasi/fd_write.rs:598-609 — 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.

D1 · Cyclomatic Complexity · wasmer_wasix · ×10

wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth (cyclomatic 60) lib/wasix/src/syscalls/wasix/path_open2.rs:186 — wasmer_wasix::syscalls::wasix::path_open2::path_open_internal_with_symlink_depth has cyclomatic complexity 60 (threshold 15). Of this number, 58 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal (cyclomatic 59) lib/wasix/src/syscalls/wasi/fd_write.rs:243 — wasmer_wasix::syscalls::wasi::fd_write::fd_write_internal has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_wasix::syscalls::wasi::fd_read::fd_read_internal (cyclomatic 40) lib/wasix/src/syscalls/wasi/fd_read.rs:135 — wasmer_wasix::syscalls::wasi::fd_read::fd_read_internal has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal (cyclomatic 31) lib/wasix/src/syscalls/wasi/path_rename.rs:56 — wasmer_wasix::syscalls::wasi::path_rename::path_rename_internal has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal (cyclomatic 31) lib/wasix/src/syscalls/wasi/poll_oneoff.rs:232 — wasmer_wasix::syscalls::wasi::poll_oneoff::poll_oneoff_internal has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl (cyclomatic 28) lib/wasix/src/syscalls/wasix/proc_exec4.rs:78 — wasmer_wasix::syscalls::wasix::proc_exec4::proc_exec4_impl has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
wasmer_wasix::bin_factory::exec::call_module (cyclomatic 20) lib/wasix/src/bin_factory/exec.rs:250 — wasmer_wasix::bin_factory::exec::call_module has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_wasix::syscalls::wasi::path_link::path_link_internal (cyclomatic 18) lib/wasix/src/syscalls/wasi/path_link.rs:73 — wasmer_wasix::syscalls::wasi::path_link::path_link_internal has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
wasmer_wasix::syscalls::wasix::proc_spawn::proc_spawn_internal (cyclomatic 18) lib/wasix/src/syscalls/wasix/proc_spawn.rs:100 — wasmer_wasix::syscalls::wasix::proc_spawn::proc_spawn_internal has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
wasmer_wasix::syscalls::wasix::proc_spawn3::proc_spawn3_impl (cyclomatic 16) lib/wasix/src/syscalls/wasix/proc_spawn3.rs:89 — wasmer_wasix::syscalls::wasix::proc_spawn3::proc_spawn3_impl has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D23 · Boundary Type-Coupling · Cross-context type Instance (api → wasix) · ×10

Cross-context type Instance (api → wasix) lib/wasix/src/runtime/mod.rs:159 — Instance (context api) is exposed in wasix's public surface via InstantiationHook.configure_new_instance — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/runtime/mod.rs:427 — Instance (context api) is exposed in wasix's public surface via Runtime.configure_new_instance — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/runtime/mod.rs:943 — Instance (context api) is exposed in wasix's public surface via PluggableRuntime.configure_new_instance — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/runtime/mod.rs:1206 — Instance (context api) is exposed in wasix's public surface via OverriddenRuntime.configure_new_instance — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/state/env.rs:978 — Instance (context api) is exposed in wasix's public surface via WasiEnv.try_clone_instance — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/state/func_env.rs:124 — Instance (context api) is exposed in wasix's public surface via WasiFunctionEnv.initialize — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/state/func_env.rs:161 — Instance (context api) is exposed in wasix's public surface via WasiFunctionEnv.initialize_handles_and_layout — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/state/handles/mod.rs:119 — Instance (context api) is exposed in wasix's public surface via WasiModuleInstanceHandles.new — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/state/handles/mod.rs:208 — Instance (context api) is exposed in wasix's public surface via WasiModuleInstanceHandles.instance — couples the contexts.
Cross-context type Instance (api → wasix) lib/wasix/src/state/linker/types.rs:37 — Instance (context api) is exposed in wasix's public surface via LinkedMainModule.instance — couples the contexts.

D29 · Static Analysis (SAST) · REDACTED · ×10

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (27 lines × 2) · ×10

Duplicated block (27 lines × 2) lib/api/src/backend/v8/entities/memory/mod.rs:350 — lib/api/src/backend/v8/entities/memory/mod.rs:350-376 | lib/api/src/backend/v8/entities/memory/mod.rs:387-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-llvm/src/translator/code.rs:778 — lib/compiler-llvm/src/translator/code.rs:778-804 | lib/compiler-llvm/src/translator/code.rs:916-942 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-llvm/src/translator/code.rs:1099 — lib/compiler-llvm/src/translator/code.rs:1099-1125 | lib/compiler-llvm/src/translator/code.rs:1149-1175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:778 — lib/compiler-singlepass/src/machine_x64.rs:778-804 | lib/compiler-singlepass/src/machine_x64.rs:920-946 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3717 — lib/compiler-singlepass/src/machine_x64.rs:3717-3743 | lib/compiler-singlepass/src/machine_x64.rs:3850-3876 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3764 — lib/compiler-singlepass/src/machine_x64.rs:3764-3790 | lib/compiler-singlepass/src/machine_x64.rs:3897-3923 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:5659 — lib/compiler-singlepass/src/machine_x64.rs:5659-5685 | lib/compiler-singlepass/src/machine_x64.rs:5839-5865 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:5706 — lib/compiler-singlepass/src/machine_x64.rs:5706-5732 | lib/compiler-singlepass/src/machine_x64.rs:5886-5912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:5753 — lib/compiler-singlepass/src/machine_x64.rs:5753-5779 | lib/compiler-singlepass/src/machine_x64.rs:5933-5959 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) lib/virtual-fs/src/mem_fs/filesystem.rs:230 — lib/virtual-fs/src/mem_fs/filesystem.rs:230-256 | lib/virtual-fs/src/mem_fs/filesystem.rs:435-461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×10

Duplicated block (21 lines × 2) lib/api/src/backend/sys/entities/memory/mod.rs:298 — lib/api/src/backend/sys/entities/memory/mod.rs:298-318 | lib/api/src/backend/sys/entities/memory/mod.rs:329-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/api/src/backend/sys/entities/memory/view.rs:206 — lib/api/src/backend/sys/entities/memory/view.rs:206-226 | lib/api/src/backend/v8/entities/memory/view.rs:201-221 — before extracting anything, compare `lib/api/src/backend/sys/entities/memory/view.rs` and `lib/api/src/backend/v8/entities/memory/view.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 (21 lines × 2) lib/cli/src/commands/app/util.rs:308 — lib/cli/src/commands/app/util.rs:308-328 | lib/cli/src/commands/package/common/mod.rs:210-230 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (21 lines × 2) lib/compiler-cranelift/src/elf.rs:136 — lib/compiler-cranelift/src/elf.rs:136-156 | lib/compiler/src/dwarf.rs:155-175 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler/src/dwarf.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) lib/compiler-llvm/src/translator/code.rs:2618 — lib/compiler-llvm/src/translator/code.rs:2618-2638 | lib/compiler-llvm/src/translator/code.rs:2644-2664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/compiler-singlepass/src/codegen.rs:1210 — lib/compiler-singlepass/src/codegen.rs:1210-1230 | lib/compiler-singlepass/src/codegen.rs:1240-1260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3679 — lib/compiler-singlepass/src/machine_x64.rs:3679-3699 | lib/compiler-singlepass/src/machine_x64.rs:3812-3832 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:7789 — lib/compiler-singlepass/src/machine_x64.rs:7789-7809 | lib/compiler-singlepass/src/machine_x64.rs:7904-7924 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/sys-utils/src/memory/fd_memory/memories.rs:65 — lib/sys-utils/src/memory/fd_memory/memories.rs:65-85 | lib/vm/src/memory.rs:59-79 — before extracting anything, compare `lib/sys-utils/src/memory/fd_memory/memories.rs` and `lib/vm/src/memory.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 156 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 (21 lines × 2) lib/vm/src/libcalls.rs:81 — lib/vm/src/libcalls.rs:81-101 | lib/vm/src/libcalls.rs:138-158 — 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 (10 lines × 3) · ×10

Duplicated block (10 lines × 3) lib/cli/src/backend.rs:451 — lib/cli/src/backend.rs:451-460 | lib/cli/src/backend.rs:481-490 | lib/cli/src/backend.rs:524-533 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/cli/src/commands/app/deploy.rs:805 — lib/cli/src/commands/app/deploy.rs:805-814 | lib/cli/src/commands/app/deploy.rs:943-952 | lib/cli/src/commands/app/deploy.rs:956-965 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/compiler-llvm/src/translator/code.rs:4658 — lib/compiler-llvm/src/translator/code.rs:4658-4667 | lib/compiler-llvm/src/translator/code.rs:4755-4764 | lib/compiler-llvm/src/translator/code.rs:4874-4883 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/compiler-llvm/src/translator/code.rs:8681 — lib/compiler-llvm/src/translator/code.rs:8681-8690 | lib/compiler-llvm/src/translator/code.rs:8709-8718 | lib/compiler-llvm/src/translator/code.rs:10612-10621 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/compiler-llvm/src/translator/code.rs:8781 — lib/compiler-llvm/src/translator/code.rs:8781-8790 | lib/compiler-llvm/src/translator/code.rs:8805-8814 | lib/compiler-llvm/src/translator/code.rs:10650-10659 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:486 — lib/compiler-singlepass/src/machine_x64.rs:486-495 | lib/compiler-singlepass/src/machine_x64.rs:522-531 | lib/compiler-singlepass/src/machine_x64.rs:550-559 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/wasix/src/net/socket.rs:1352 — lib/wasix/src/net/socket.rs:1352-1361 | lib/wasix/src/net/socket.rs:1436-1445 | lib/wasix/src/net/socket.rs:1528-1537 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/api/src/backend/sys/entities/global.rs:80 — lib/api/src/backend/sys/entities/global.rs:80-89 | lib/api/src/backend/sys/entities/memory/mod.rs:95-104 | lib/api/src/backend/sys/entities/table.rs:162-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1809 — lib/compiler-singlepass/src/machine_arm64.rs:1809-1818 | lib/compiler-singlepass/src/machine_riscv.rs:2310-2319 | lib/compiler-singlepass/src/machine_x64.rs:2317-2326 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) lib/cli/src/commands/app/secrets/create.rs:152 — lib/cli/src/commands/app/secrets/create.rs:152-161 | lib/cli/src/commands/app/secrets/import.rs:142-151 | lib/cli/src/commands/app/secrets/update.rs:146-155 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/update.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D23 · Boundary Type-Coupling · Cross-context type Pages (types → api) · ×9

Cross-context type Pages (types → api) lib/api/src/backend/js/entities/memory/mod.rs:134 — Pages (context types) is exposed in api's public surface via Memory.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/backend/js/entities/memory/view.rs:98 — Pages (context types) is exposed in api's public surface via MemoryView.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/backend/sys/entities/memory/view.rs:100 — Pages (context types) is exposed in api's public surface via MemoryView.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/backend/v8/entities/memory/mod.rs:100 — Pages (context types) is exposed in api's public surface via Memory.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/backend/v8/entities/memory/view.rs:95 — Pages (context types) is exposed in api's public surface via MemoryView.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/entities/memory/mod.rs:99 — Pages (context types) is exposed in api's public surface via Memory.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/entities/memory/view/mod.rs:76 — Pages (context types) is exposed in api's public surface via MemoryView.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/entities/memory/inner.rs:97 — Pages (context types) is exposed in api's public surface via BackendMemory.size — couples the contexts.
Cross-context type Pages (types → api) lib/api/src/entities/memory/view/inner.rs:110 — Pages (context types) is exposed in api's public surface via BackendMemoryView.size — couples the contexts.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×9

Duplicated block (8 lines × 3) lib/compiler-cranelift/src/compiler.rs:159 — lib/compiler-cranelift/src/compiler.rs:159-166 | lib/compiler-llvm/src/compiler.rs:270-278 | lib/compiler-singlepass/src/compiler.rs:115-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 3) lib/compiler-cranelift/src/config.rs:45 — lib/compiler-cranelift/src/config.rs:45-52 | lib/compiler-llvm/src/config.rs:50-57 | lib/compiler-singlepass/src/config.rs:44-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 3) lib/compiler-singlepass/src/codegen.rs:5562 — lib/compiler-singlepass/src/codegen.rs:5562-5569 | lib/compiler-singlepass/src/codegen.rs:5606-5613 | lib/compiler-singlepass/src/codegen.rs:5687-5694 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) lib/compiler-singlepass/src/codegen.rs:5882 — lib/compiler-singlepass/src/codegen.rs:5882-5889 | lib/compiler-singlepass/src/codegen.rs:5932-5939 | lib/compiler-singlepass/src/codegen.rs:5981-5988 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:1059 — lib/compiler-singlepass/src/machine_x64.rs:1059-1066 | lib/compiler-singlepass/src/machine_x64.rs:1214-1221 | lib/compiler-singlepass/src/machine_x64.rs:1398-1405 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) lib/wasix/src/net/socket.rs:1440 — lib/wasix/src/net/socket.rs:1440-1447 | lib/wasix/src/net/socket.rs:1532-1539 | lib/wasix/src/net/socket.rs:1623-1630 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:2187 — lib/compiler-singlepass/src/machine_arm64.rs:2187-2194 | lib/compiler-singlepass/src/machine_riscv.rs:2527-2534 | lib/compiler-singlepass/src/machine_x64.rs:2465-2472 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) lib/types/src/entity/boxed_slice.rs:33 — lib/types/src/entity/boxed_slice.rs:33-40 | lib/types/src/entity/primary_map.rs:51-58 | lib/types/src/entity/secondary_map.rs:47-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) lib/compiler-singlepass/src/machine_riscv.rs:1393 — lib/compiler-singlepass/src/machine_riscv.rs:1393-1400 | lib/compiler-singlepass/src/machine_riscv.rs:1444-1451 | lib/compiler-singlepass/src/machine_riscv.rs:1501-1508 — 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.

D1 · Cyclomatic Complexity · LLVMFunctionCodeGenerator · ×8

LLVMFunctionCodeGenerator::translate_integer_arithmetic_operator (cyclomatic 118) lib/compiler-llvm/src/translator/code.rs:4031 — LLVMFunctionCodeGenerator::translate_integer_arithmetic_operator has cyclomatic complexity 118 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
LLVMFunctionCodeGenerator::translate_memory_operator (cyclomatic 86) lib/compiler-llvm/src/translator/code.rs:9871 — LLVMFunctionCodeGenerator::translate_memory_operator has cyclomatic complexity 86 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
LLVMFunctionCodeGenerator::translate_conversion_operator (cyclomatic 67) lib/compiler-llvm/src/translator/code.rs:8575 — LLVMFunctionCodeGenerator::translate_conversion_operator has cyclomatic complexity 67 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
LLVMFunctionCodeGenerator::translate_basic_operator (cyclomatic 55) lib/compiler-llvm/src/translator/code.rs:3217 — LLVMFunctionCodeGenerator::translate_basic_operator has cyclomatic complexity 55 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
LLVMFunctionCodeGenerator::translate_control_flow_operator (cyclomatic 33) lib/compiler-llvm/src/translator/code.rs:2786 — LLVMFunctionCodeGenerator::translate_control_flow_operator has cyclomatic complexity 33 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
LLVMFunctionCodeGenerator::translate_eh_operator (cyclomatic 23) lib/compiler-llvm/src/translator/code.rs:11684 — LLVMFunctionCodeGenerator::translate_eh_operator has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
LLVMFunctionCodeGenerator::translate_operator (cyclomatic 20) lib/compiler-llvm/src/translator/code.rs:12277 — LLVMFunctionCodeGenerator::translate_operator has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
LLVMFunctionCodeGenerator::build_m0_indirect_call (cyclomatic 16) lib/compiler-llvm/src/translator/code.rs:2186 — LLVMFunctionCodeGenerator::build_m0_indirect_call has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×8

Duplicated block (20 lines × 2) lib/api/src/backend/sys/entities/function/typed.rs:46 — lib/api/src/backend/sys/entities/function/typed.rs:46-65 | lib/api/src/backend/sys/entities/function/typed.rs:183-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/compiler-cranelift/src/dwarf.rs:77 — lib/compiler-cranelift/src/dwarf.rs:77-96 | lib/compiler-singlepass/src/dwarf.rs:65-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4269 — lib/compiler-singlepass/src/machine_x64.rs:4269-4288 | lib/compiler-singlepass/src/machine_x64.rs:6393-6412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:4314 — lib/compiler-singlepass/src/machine_x64.rs:4314-4333 | lib/compiler-singlepass/src/machine_x64.rs:6438-6457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/virtual-fs/src/mem_fs/filesystem.rs:942 — lib/virtual-fs/src/mem_fs/filesystem.rs:942-961 | lib/virtual-fs/src/mem_fs/filesystem.rs:983-1002 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/virtual-net/src/host.rs:912 — lib/virtual-net/src/host.rs:912-931 | lib/virtual-net/src/host.rs:1225-1244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/virtual-net/src/rx_tx.rs:379 — lib/virtual-net/src/rx_tx.rs:379-398 | lib/virtual-net/src/rx_tx.rs:441-460 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/wasix/src/net/socket.rs:1314 — lib/wasix/src/net/socket.rs:1314-1333 | lib/wasix/src/net/socket.rs:1402-1421 — 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.

D15 · Churn × Complexity Hotspots · Repeated repair · ×7

Repeated repair: lib/wasix/src/bin_factory/mod.rs lib/wasix/src/bin_factory/mod.rs:210 — lib/wasix/src/bin_factory/mod.rs changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is BinFactory::get_executable at line 210), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(wasix): report a shebang chain that never ends as ELOOP”; “fix(wasix): leave the caller's argv alone when a script spawn fails”; “fix(wasix): find an executable that no preopen covers”; “fix(wasix): report an unusable shebang as ENOEXEC instead of compiling it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/bin_factory/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/wasix/src/state/env.rs lib/wasix/src/state/env.rs:496 — lib/wasix/src/state/env.rs changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is WasiEnv::instantiate at line 496), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix build”; “fix(wasix): deduplicate spawned command environment”; “fix(wasix): preserve package metadata when command alias installation fails (#7044)”; “fix(wasix): drain sibling signal copies”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/state/env.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/compiler-singlepass/src/machine_x64.rs lib/compiler-singlepass/src/machine_x64.rs:129 — lib/compiler-singlepass/src/machine_x64.rs changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is MachineX86_64::emit_relaxed_binop at line 129), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(Singlepass): use correct value_size for some memory ops (#7079)”; “fix(Singlepass): correctly narrow returned value for atomics (#7066)”; “fix(VMOffsets): handle gracefully u32 -> i32 casting (#6904)”; “fix(Singlepass): simplify stack rounding logic (#6895)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/compiler-singlepass/src/machine_x64.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/api/src/backend/js/entities/memory/mod.rs lib/api/src/backend/js/entities/memory/mod.rs:45 — lib/api/src/backend/js/entities/memory/mod.rs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is Memory::new at line 45), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(js): make module and shared-memory ownership worker-safe (#6979)”; “fix(api-js-backend): make memory maximum pages limit bigger”; “fix(api-js-backend): add copy_range_to_memory to the MemoryViews”; “fix(api-js-backend): Add support for ExternRefs in Wasmer JS backend”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/api/src/backend/js/entities/memory/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/vm/src/vmcontext.rs lib/vm/src/vmcontext.rs:418 — lib/vm/src/vmcontext.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is wasmer_vm::vmcontext::memory32_atomic_check32 at line 418), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(Table): add resource allocation tracking for local Tables (#16)”; “fix(memory.atomic): offset, add boundary and alignment checks (#6862)”; “fix: memory32_atomic_check miss off-by-width bounds check (#6853)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/vm/src/vmcontext.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/c-api-imports/src/lib.rs lib/c-api-imports/src/lib.rs:2270 — lib/c-api-imports/src/lib.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is wasmer_c_api_imports::wasm_val_vec_new_uninitialized at line 2270), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(api): preserve V8 externref boundaries”; “fix(api-js-backend): add copy_range_to_memory to the MemoryViews”; “refactor(wasix): thread per-instantiation state through runtime hooks (fixes WAX-600 cross-store panic) (#6804)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/c-api-imports/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/wasix/src/os/tty/tty_sys.rs lib/wasix/src/os/tty/tty_sys.rs:36 — lib/wasix/src/os/tty/tty_sys.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is SysTty::tty_set at line 36), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix function signature on macOS”; “fix(wasix): preserve CR and LF in noncanonical tty mode”; “fix(wasix): preserve carriage returns in raw tty mode”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 11:09:24 +00:00' --until='2026-10-23 11:09:24 +00:00' --full-history --no-merges -- lib/wasix/src/os/tty/tty_sys.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D2 · Cognitive Complexity · LLVMFunctionCodeGenerator · ×7

LLVMFunctionCodeGenerator::translate_basic_operator (cognitive 83) lib/compiler-llvm/src/translator/code.rs:3217 — LLVMFunctionCodeGenerator::translate_basic_operator has cognitive complexity 83 (threshold 15). Drivers by points: if/else 36 (61 pts), loops 4 (12 pts), match/switch 4 (7 pts), boolean chains 3 (nesting depth added 36). 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.
LLVMFunctionCodeGenerator::translate_eh_operator (cognitive 56) lib/compiler-llvm/src/translator/code.rs:11684 — LLVMFunctionCodeGenerator::translate_eh_operator has cognitive complexity 56 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 7 (23 pts), match/switch 4 (9 pts) (nesting depth added 35). 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.
LLVMFunctionCodeGenerator::translate_control_flow_operator (cognitive 51) lib/compiler-llvm/src/translator/code.rs:2786 — LLVMFunctionCodeGenerator::translate_control_flow_operator has cognitive complexity 51 (threshold 15). Drivers by points: loops 14 (32 pts), if/else 9 (16 pts), match/switch 2 (3 pts) (nesting depth added 26). 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.
LLVMFunctionCodeGenerator::build_m0_indirect_call (cognitive 34) lib/compiler-llvm/src/translator/code.rs:2186 — LLVMFunctionCodeGenerator::build_m0_indirect_call has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLVMFunctionCodeGenerator::translate_memory_operator (cognitive 22) lib/compiler-llvm/src/translator/code.rs:9871 — LLVMFunctionCodeGenerator::translate_memory_operator has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LLVMFunctionCodeGenerator::translate_integer_arithmetic_operator (cognitive 21) lib/compiler-llvm/src/translator/code.rs:4031 — LLVMFunctionCodeGenerator::translate_integer_arithmetic_operator has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 9 (17 pts), if/else 3 (4 pts) (nesting depth added 9). 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.
LLVMFunctionCodeGenerator::resolve_memory_ptr (cognitive 20) lib/compiler-llvm/src/translator/code.rs:1838 — LLVMFunctionCodeGenerator::resolve_memory_ptr has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (13 lines × 3) · ×7

Duplicated block (13 lines × 3) lib/compiler-llvm/src/translator/code.rs:5310 — lib/compiler-llvm/src/translator/code.rs:5310-5322 | lib/compiler-llvm/src/translator/code.rs:5412-5424 | lib/compiler-llvm/src/translator/code.rs:5514-5526 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/compiler-llvm/src/translator/code.rs:6158 — lib/compiler-llvm/src/translator/code.rs:6158-6170 | lib/compiler-llvm/src/translator/code.rs:6252-6264 | lib/compiler-llvm/src/translator/code.rs:6346-6358 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/compiler-llvm/src/translator/code.rs:6179 — lib/compiler-llvm/src/translator/code.rs:6179-6191 | lib/compiler-llvm/src/translator/code.rs:6273-6285 | lib/compiler-llvm/src/translator/code.rs:6367-6379 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:4374 — lib/compiler-singlepass/src/machine_arm64.rs:4374-4386 | lib/compiler-singlepass/src/machine_arm64.rs:4432-4444 | lib/compiler-singlepass/src/machine_arm64.rs:4490-4502 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/virtual-net/src/server.rs:883 — lib/virtual-net/src/server.rs:883-895 | lib/virtual-net/src/server.rs:913-925 | lib/virtual-net/src/server.rs:940-952 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/compiler-llvm/src/translator/code.rs:2009 — lib/compiler-llvm/src/translator/code.rs:2009-2021 | lib/compiler-llvm/src/translator/code.rs:3770-3783 | lib/compiler-llvm/src/translator/code.rs:3930-3944 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:811 — lib/compiler-singlepass/src/machine_arm64.rs:811-823 | lib/compiler-singlepass/src/machine_arm64.rs:839-851 | lib/compiler-singlepass/src/machine_arm64.rs:868-880 — 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 (11 lines × 3) · ×7

Duplicated block (11 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:305 — lib/compiler-singlepass/src/machine_arm64.rs:305-315 | lib/compiler-singlepass/src/machine_arm64.rs:324-334 | lib/compiler-singlepass/src/machine_arm64.rs:343-353 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:8435 — lib/compiler-singlepass/src/machine_arm64.rs:8435-8445 | lib/compiler-singlepass/src/machine_riscv.rs:6565-6575 | lib/compiler-singlepass/src/machine_x64.rs:8339-8349 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) lib/compiler-singlepass/src/machine_riscv.rs:1419 — lib/compiler-singlepass/src/machine_riscv.rs:1419-1429 | lib/compiler-singlepass/src/machine_riscv.rs:1476-1486 | lib/compiler-singlepass/src/machine_riscv.rs:1547-1557 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) lib/compiler/src/object/module.rs:715 — lib/compiler/src/object/module.rs:715-725 | lib/compiler/src/object/module.rs:739-749 | lib/compiler/src/object/module.rs:764-774 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) lib/vm/src/vmcontext.rs:396 — lib/vm/src/vmcontext.rs:396-406 | lib/vm/src/vmcontext.rs:425-435 | lib/vm/src/vmcontext.rs:464-474 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1566 — lib/compiler-singlepass/src/machine_arm64.rs:1566-1576 | lib/compiler-singlepass/src/machine_riscv.rs:2108-2118 | lib/compiler-singlepass/src/machine_x64.rs:2159-2169 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) lib/compiler-llvm/src/translator/code.rs:1167 — lib/compiler-llvm/src/translator/code.rs:1167-1177 | lib/compiler-llvm/src/translator/code.rs:1808-1818 | lib/compiler-llvm/src/translator/code.rs:2026-2036 — 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.

D1 · Cyclomatic Complexity · InodeSocket · ×6

InodeSocket::bind_internal (cyclomatic 28) lib/wasix/src/net/socket.rs:309 — InodeSocket::bind_internal has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InodeSocket::connect (cyclomatic 21) lib/wasix/src/net/socket.rs:692 — InodeSocket::connect has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: WasiSocketOption::try_from (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
InodeSocket::set_opt_flag (cyclomatic 19) lib/wasix/src/net/socket.rs:922 — InodeSocket::set_opt_flag has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: WasiSocketOption::try_from (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
InodeSocket::get_opt_flag (cyclomatic 17) lib/wasix/src/net/socket.rs:974 — InodeSocket::get_opt_flag has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: WasiSocketOption::try_from (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
InodeSocket::send (cyclomatic 16) lib/wasix/src/net/socket.rs:1304 — InodeSocket::send has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: WasiSocketOption::try_from (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
InodeSocket::recv (cyclomatic 16) lib/wasix/src/net/socket.rs:1475 — InodeSocket::recv has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: WasiSocketOption::try_from (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D2 · Cognitive Complexity · wasmer_compiler · ×6

wasmer_compiler::object::module::emit_compilation (cognitive 39) lib/compiler/src/object/module.rs:139 — wasmer_compiler::object::module::emit_compilation has cognitive complexity 39 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 5 (13 pts), loops 8 (9 pts), boolean chains 1 (nesting depth added 17). 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.
wasmer_compiler::engine::link::apply_relocation (cognitive 27) lib/compiler/src/engine/link.rs:21 — wasmer_compiler::engine::link::apply_relocation has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 2 (3 pts), boolean chains 2 (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.
wasmer_compiler::engine::resolver::resolve_imports (cognitive 21) lib/compiler/src/engine/resolver.rs:79 — wasmer_compiler::engine::resolver::resolve_imports has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 2 (8 pts), boolean chains 1, loops 1 (nesting depth added 13). 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.
wasmer_compiler::engine::resolver::resolve_tags (cognitive 21) lib/compiler/src/engine/resolver.rs:222 — wasmer_compiler::engine::resolver::resolve_tags has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (5 pts), loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_compiler::translator::sections::parse_name_section (cognitive 18) lib/compiler/src/translator/sections.rs:555 — wasmer_compiler::translator::sections::parse_name_section has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_compiler::compiler::translate_function_buckets (cognitive 17) lib/compiler/src/compiler.rs:348 — wasmer_compiler::compiler::translate_function_buckets has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 2 (7 pts), match/switch 1 (2 pts) (nesting depth added 9). 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.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×6

Duplicated block (5 lines × 3) lib/api/src/backend/js/entities/function/mod.rs:315 — lib/api/src/backend/js/entities/function/mod.rs:315-319 | lib/api/src/backend/js/entities/function/mod.rs:331-335 | lib/api/src/backend/js/entities/function/mod.rs:347-351 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) lib/compiler-cranelift/src/translator/code_translator.rs:2007 — lib/compiler-cranelift/src/translator/code_translator.rs:2007-2011 | lib/compiler-cranelift/src/translator/code_translator.rs:2016-2020 | lib/compiler-cranelift/src/translator/code_translator.rs:2025-2029 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) lib/virtual-fs/src/overlay_fs.rs:1132 — lib/virtual-fs/src/overlay_fs.rs:1132-1136 | lib/virtual-fs/src/overlay_fs.rs:1144-1148 | lib/virtual-fs/src/overlay_fs.rs:1279-1283 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) lib/wasix/src/syscalls/wasi/path_filestat_set_times.rs:32 — lib/wasix/src/syscalls/wasi/path_filestat_set_times.rs:32-37 | lib/wasix/src/syscalls/wasi/path_rename.rs:31-35 | lib/wasix/src/syscalls/wasi/path_symlink.rs:26-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1538 — lib/compiler-singlepass/src/machine_arm64.rs:1538-1542 | lib/compiler-singlepass/src/machine_riscv.rs:2080-2084 | lib/compiler-singlepass/src/machine_x64.rs:2131-2135 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) lib/compiler/src/serialize.rs:49 — lib/compiler/src/serialize.rs:49-53 | lib/compiler/src/serialize.rs:85-89 | lib/compiler/src/types/symbols.rs:96-100 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.

D2 · Cognitive Complexity · wasmer_compiler_cranelift · ×5

wasmer_compiler_cranelift::translator::code_translator::translate_operator (cognitive 87) lib/compiler-cranelift/src/translator/code_translator.rs:157 — wasmer_compiler_cranelift::translator::code_translator::translate_operator has cognitive complexity 87 (threshold 15). Drivers by points: if/else 21 (41 pts), match/switch 14 (31 pts), loops 6 (15 pts) (nesting depth added 46). 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.
wasmer_compiler_cranelift::eh::build_function_lsda (cognitive 27) lib/compiler-cranelift/src/eh.rs:43 — wasmer_compiler_cranelift::eh::build_function_lsda has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 2 (7 pts), loops 5 (6 pts) (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
wasmer_compiler_cranelift::eh::compact_unwind_encoding_aarch64 (cognitive 19) lib/compiler-cranelift/src/eh.rs:419 — wasmer_compiler_cranelift::eh::compact_unwind_encoding_aarch64 has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 3 (6 pts), loops 3, boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_compiler_cranelift::eh::encode_action_table (cognitive 17) lib/compiler-cranelift/src/eh.rs:600 — wasmer_compiler_cranelift::eh::encode_action_table has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_compiler_cranelift::translator::code_translator::translate_unreachable_operator (cognitive 16) lib/compiler-cranelift/src/translator/code_translator.rs:2654 — wasmer_compiler_cranelift::translator::code_translator::translate_unreachable_operator has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 2 (5 pts), boolean chains 2 (nesting depth added 8). 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 · InodeSocket · ×5

InodeSocket::bind_internal (cognitive 53) lib/wasix/src/net/socket.rs:309 — InodeSocket::bind_internal has cognitive complexity 53 (threshold 15). Drivers by points: if/else 9 (30 pts), match/switch 11 (23 pts) (nesting depth added 33). 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.
InodeSocket::connect (cognitive 28) lib/wasix/src/net/socket.rs:692 — InodeSocket::connect has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 6 (13 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InodeSocket::send (cognitive 17) lib/wasix/src/net/socket.rs:1304 — InodeSocket::send has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 5 (7 pts), loops 1 (nesting depth added 7). 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.
InodeSocket::recv (cognitive 16) lib/wasix/src/net/socket.rs:1475 — InodeSocket::recv has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 3, loops 1 (nesting depth added 7). 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.
InodeSocket::recv_from (cognitive 16) lib/wasix/src/net/socket.rs:1568 — InodeSocket::recv_from has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 3, loops 1 (nesting depth added 7). 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 · wasmer_compiler_singlepass · ×5

wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 (cognitive 47) lib/compiler-singlepass/src/emitter_arm64.rs:3108 — wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (26 pts), match/switch 4 (11 pts), loops 2 (6 pts), boolean chains 4 (nesting depth added 24). 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.
wasmer_compiler_singlepass::emitter_arm64::gen_std_dynamic_import_trampoline_arm64 (cognitive 29) lib/compiler-singlepass/src/emitter_arm64.rs:2949 — wasmer_compiler_singlepass::emitter_arm64::gen_std_dynamic_import_trampoline_arm64 has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 8 (10 pts), loops 1 (2 pts) (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
wasmer_compiler_singlepass::emitter_riscv::gen_import_call_trampoline_riscv (cognitive 27) lib/compiler-singlepass/src/emitter_riscv.rs:2036 — wasmer_compiler_singlepass::emitter_riscv::gen_import_call_trampoline_riscv has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (6 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_compiler_singlepass::emitter_riscv::gen_std_trampoline_riscv (cognitive 23) lib/compiler-singlepass/src/emitter_riscv.rs:1750 — wasmer_compiler_singlepass::emitter_riscv::gen_std_trampoline_riscv has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 2 (4 pts), loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_compiler_singlepass::emitter_arm64::gen_std_trampoline_arm64 (cognitive 21) lib/compiler-singlepass/src/emitter_arm64.rs:2807 — wasmer_compiler_singlepass::emitter_arm64::gen_std_trampoline_arm64 has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 4 (8 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · wasmer_cli · ×5

wasmer_cli::commands::app::deploy::wait_app (cognitive 40) lib/cli/src/commands/app/deploy.rs:1171 — wasmer_cli::commands::app::deploy::wait_app has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (33 pts), match/switch 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 24). 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.
wasmer_cli::commands::app::secrets::utils::get_app_id (cognitive 32) lib/cli/src/commands/app/secrets/utils/mod.rs:93 — wasmer_cli::commands::app::secrets::utils::get_app_id has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (32 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_cli::utils::prompts::prompt_for_package (cognitive 26) lib/cli/src/utils/prompts.rs:113 — wasmer_cli::utils::prompts::prompt_for_package has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_cli::commands::init::construct_manifest (cognitive 24) lib/cli/src/commands/init.rs:362 — wasmer_cli::commands::init::construct_manifest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 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.
wasmer_cli::utils::yaml::merge_into_mapping (cognitive 20) lib/cli/src/utils/yaml.rs:81 — wasmer_cli::utils::yaml::merge_into_mapping has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (4 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D23 · Boundary Type-Coupling · Cross-context type FunctionType (types → api) · ×5

Cross-context type FunctionType (types → api) lib/api/src/backend/js/entities/function/mod.rs:433 — FunctionType (context types) is exposed in api's public surface via Function.ty — couples the contexts.
Cross-context type FunctionType (types → api) lib/api/src/backend/js/entities/function/mod.rs:682 — FunctionType (context types) is exposed in api's public surface via WasmFunction.ty — couples the contexts.
Cross-context type FunctionType (types → api) lib/api/src/backend/v8/entities/function/mod.rs:313 — FunctionType (context types) is exposed in api's public surface via Function.ty — couples the contexts.
Cross-context type FunctionType (types → api) lib/api/src/entities/function/mod.rs:249 — FunctionType (context types) is exposed in api's public surface via Function.ty — couples the contexts.
Cross-context type FunctionType (types → api) lib/api/src/entities/function/inner.rs:353 — FunctionType (context types) is exposed in api's public surface via BackendFunction.ty — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Imports (api → wasix) · ×5

Cross-context type Imports (api → wasix) lib/wasix/src/runtime/mod.rs:143 — Imports (context api) is exposed in wasix's public surface via InstantiationHook.prepare_imports — couples the contexts.
Cross-context type Imports (api → wasix) lib/wasix/src/runtime/mod.rs:411 — Imports (context api) is exposed in wasix's public surface via Runtime.prepare_imports — couples the contexts.
Cross-context type Imports (api → wasix) lib/wasix/src/runtime/mod.rs:930 — Imports (context api) is exposed in wasix's public surface via PluggableRuntime.prepare_imports — couples the contexts.
Cross-context type Imports (api → wasix) lib/wasix/src/runtime/mod.rs:1189 — Imports (context api) is exposed in wasix's public surface via OverriddenRuntime.prepare_imports — couples the contexts.
Cross-context type Imports (api → wasix) lib/wasix/src/lib.rs:374 — Imports (context api) is exposed in wasix's public surface via wasmer_wasix$module.generate_import_object_from_env — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Store (api → wasix) · ×5

Cross-context type Store (api → wasix) lib/wasix/src/runtime/mod.rs:376 — Store (context api) is exposed in wasix's public surface via Runtime.new_store — couples the contexts.
Cross-context type Store (api → wasix) lib/wasix/src/runtime/mod.rs:901 — Store (context api) is exposed in wasix's public surface via PluggableRuntime.new_store — couples the contexts.
Cross-context type Store (api → wasix) lib/wasix/src/runtime/mod.rs:1162 — Store (context api) is exposed in wasix's public surface via OverriddenRuntime.new_store — couples the contexts.
Cross-context type Store (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:54 — Store (context api) is exposed in wasix's public surface via TaskWasmRunProperties.store — couples the contexts.
Cross-context type Store (api → wasix) lib/wasix/src/runtime/task_manager/mod.rs:81 — Store (context api) is exposed in wasix's public surface via TaskWasmRecycleProperties.store — couples the contexts.

D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×5

Members sharing a duplicated core (5 members, 50+ identical tokens) lib/backend-api/src/query.rs:266 — lib/backend-api/src/query.rs:266-303 | lib/backend-api/src/query.rs:644-679 | lib/backend-api/src/query.rs:698-735 | lib/backend-api/src/query.rs:1513-1554 | lib/backend-api/src/query.rs:1579-1619 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_x64.rs:2508 — lib/compiler-singlepass/src/machine_x64.rs:2508-2559 | lib/compiler-singlepass/src/machine_x64.rs:7308-7421 | lib/compiler-singlepass/src/machine_x64.rs:7428-7536 | lib/compiler-singlepass/src/machine_x64.rs:7710-7823 | lib/compiler-singlepass/src/machine_x64.rs:7830-7938 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/virtual-fs/src/mem_fs/filesystem.rs:186 — lib/virtual-fs/src/mem_fs/filesystem.rs:186-256 | lib/virtual-fs/src/mem_fs/filesystem.rs:258-314 | lib/virtual-fs/src/mem_fs/filesystem.rs:386-461 | lib/virtual-fs/src/mem_fs/filesystem.rs:467-525 | lib/virtual-fs/src/mem_fs/filesystem.rs:703-753 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/virtual-net/src/client.rs:711 — lib/virtual-net/src/client.rs:711-726 | lib/virtual-net/src/client.rs:771-796 | lib/virtual-net/src/client.rs:803-827 | lib/virtual-net/src/client.rs:829-848 | lib/virtual-net/src/client.rs:854-877 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/wasix/src/net/socket.rs:613 — lib/wasix/src/net/socket.rs:613-673 | lib/wasix/src/net/socket.rs:1310-1388 | lib/wasix/src/net/socket.rs:1397-1473 | lib/wasix/src/net/socket.rs:1482-1566 | lib/wasix/src/net/socket.rs:1575-1655 — These 5 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 5 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 5 times.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×5

Duplicated block (22 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:1849 — lib/compiler-singlepass/src/machine_arm64.rs:1849-1870 | lib/compiler-singlepass/src/machine_arm64.rs:1932-1953 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2038 — lib/compiler-singlepass/src/machine_arm64.rs:2038-2059 | lib/compiler-singlepass/src/machine_riscv.rs:2416-2437 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:5620 — lib/compiler-singlepass/src/machine_x64.rs:5620-5641 | lib/compiler-singlepass/src/machine_x64.rs:5800-5821 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) lib/wasix/src/syscalls/wasi/fd_read.rs:328 — lib/wasix/src/syscalls/wasi/fd_read.rs:328-349 | lib/wasix/src/syscalls/wasi/fd_read.rs:382-403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) scripts/make-release.py:174 — scripts/make-release.py:174-195 | scripts/make-release.py:444-465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×5

Duplicated block (19 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:1292 — lib/compiler-singlepass/src/machine_x64.rs:1292-1310 | lib/compiler-singlepass/src/machine_x64.rs:1364-1382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:7387 — lib/compiler-singlepass/src/machine_x64.rs:7387-7405 | lib/compiler-singlepass/src/machine_x64.rs:7502-7520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/virtual-net/src/server.rs:1560 — lib/virtual-net/src/server.rs:1560-1578 | lib/virtual-net/src/server.rs:1622-1640 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/wasix/src/net/socket.rs:1544 — lib/wasix/src/net/socket.rs:1544-1562 | lib/wasix/src/net/socket.rs:1633-1651 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/wasix/src/syscalls/wasix/sock_send.rs:115 — lib/wasix/src/syscalls/wasix/sock_send.rs:115-133 | lib/wasix/src/syscalls/wasix/sock_send_to.rs:126-144 — before extracting anything, compare `lib/wasix/src/syscalls/wasix/sock_send.rs` and `lib/wasix/src/syscalls/wasix/sock_send_to.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×5

Duplicated block (18 lines × 2) lib/compiler-cranelift/src/func_environ.rs:2008 — lib/compiler-cranelift/src/func_environ.rs:2008-2025 | lib/compiler-cranelift/src/func_environ.rs:2033-2050 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/compiler-llvm/src/translator/code.rs:11919 — lib/compiler-llvm/src/translator/code.rs:11919-11936 | lib/compiler-llvm/src/translator/code.rs:11986-12003 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/compiler-singlepass/src/codegen.rs:1286 — lib/compiler-singlepass/src/codegen.rs:1286-1303 | lib/compiler-singlepass/src/codegen.rs:1308-1325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/compiler-singlepass/src/machine_arm64.rs:2336 — lib/compiler-singlepass/src/machine_arm64.rs:2336-2353 | lib/compiler-singlepass/src/machine_riscv.rs:2686-2703 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) lib/wasix/src/syscalls/wasi/path_open.rs:95 — lib/wasix/src/syscalls/wasi/path_open.rs:95-112 | lib/wasix/src/syscalls/wasix/path_open2.rs:98-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×5

Duplicated block (14–15 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:3732 — lib/compiler-singlepass/src/machine_x64.rs:3732-3746 | lib/compiler-singlepass/src/machine_x64.rs:3865-3879 | lib/compiler-singlepass/src/machine_x64.rs:4282-4295 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:3779 — lib/compiler-singlepass/src/machine_x64.rs:3779-3793 | lib/compiler-singlepass/src/machine_x64.rs:3912-3926 | lib/compiler-singlepass/src/machine_x64.rs:4327-4340 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:5674 — lib/compiler-singlepass/src/machine_x64.rs:5674-5688 | lib/compiler-singlepass/src/machine_x64.rs:5854-5868 | lib/compiler-singlepass/src/machine_x64.rs:6406-6419 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:5721 — lib/compiler-singlepass/src/machine_x64.rs:5721-5735 | lib/compiler-singlepass/src/machine_x64.rs:5901-5915 | lib/compiler-singlepass/src/machine_x64.rs:6451-6464 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:5768 — lib/compiler-singlepass/src/machine_x64.rs:5768-5782 | lib/compiler-singlepass/src/machine_x64.rs:5948-5962 | lib/compiler-singlepass/src/machine_x64.rs:6496-6509 — 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 (12–13 lines × 2) · ×5

Duplicated block (12–13 lines × 2) lib/c-api/src/wasm_c_api/engine/config/sys.rs:157 — lib/c-api/src/wasm_c_api/engine/config/sys.rs:157-168 | lib/c-api/src/wasm_c_api/engine/config/sys.rs:173-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:1074 — lib/compiler-singlepass/src/machine_riscv.rs:1074-1086 | lib/compiler-singlepass/src/machine_riscv.rs:1192-1203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:488 — lib/compiler-singlepass/src/machine_x64.rs:488-500 | lib/compiler-singlepass/src/machine_x64.rs:552-563 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) lib/wasix/src/syscalls/mod.rs:616 — lib/wasix/src/syscalls/mod.rs:616-627 | lib/wasix/src/syscalls/mod.rs:710-722 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) lib/wasix/src/syscalls/wasi/fd_dup.rs:26 — lib/wasix/src/syscalls/wasi/fd_dup.rs:26-37 | lib/wasix/src/syscalls/wasix/fd_dup2.rs:33-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (10 lines × 4) · ×5

Duplicated block (10 lines × 4) lib/compiler-llvm/src/translator/code.rs:4673 — lib/compiler-llvm/src/translator/code.rs:4673-4682 | lib/compiler-llvm/src/translator/code.rs:4684-4693 | lib/compiler-llvm/src/translator/code.rs:4695-4704 | lib/compiler-llvm/src/translator/code.rs:4949-4958 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) lib/compiler-llvm/src/translator/code.rs:6727 — lib/compiler-llvm/src/translator/code.rs:6727-6736 | lib/compiler-llvm/src/translator/code.rs:6750-6759 | lib/compiler-llvm/src/translator/code.rs:6897-6906 | lib/compiler-llvm/src/translator/code.rs:6920-6929 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:2656 — lib/compiler-singlepass/src/machine_arm64.rs:2656-2665 | lib/compiler-singlepass/src/machine_arm64.rs:2694-2703 | lib/compiler-singlepass/src/machine_arm64.rs:2917-2926 | lib/compiler-singlepass/src/machine_arm64.rs:4839-4848 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) lib/virtual-fs/src/mem_fs/file.rs:870 — lib/virtual-fs/src/mem_fs/file.rs:870-879 | lib/virtual-fs/src/mem_fs/file.rs:960-969 | lib/virtual-fs/src/mem_fs/file.rs:1068-1077 | lib/virtual-fs/src/mem_fs/file.rs:1150-1159 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) lib/compiler-cranelift/src/translator/code_translator.rs:3240 — lib/compiler-cranelift/src/translator/code_translator.rs:3240-3249 | lib/compiler-cranelift/src/translator/code_translator.rs:3289-3298 | lib/compiler-cranelift/src/translator/code_translator.rs:3338-3347 | lib/compiler-cranelift/src/translator/code_translator.rs:3380-3389 — 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.

D4 · Code Duplication · Duplicated block (9 lines × 4) · ×5

Duplicated block (9 lines × 4) lib/cli/src/commands/app/secrets/create.rs:59 — lib/cli/src/commands/app/secrets/create.rs:59-67 | lib/cli/src/commands/app/secrets/delete.rs:61-69 | lib/cli/src/commands/app/secrets/reveal.rs:50-58 | lib/cli/src/commands/app/secrets/update.rs:64-72 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/delete.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) lib/compiler-singlepass/src/emitter_x64.rs:2036 — lib/compiler-singlepass/src/emitter_x64.rs:2036-2044 | lib/compiler-singlepass/src/emitter_x64.rs:2066-2074 | lib/compiler-singlepass/src/emitter_x64.rs:2096-2104 | lib/compiler-singlepass/src/emitter_x64.rs:2126-2134 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) lib/compiler-singlepass/src/emitter_x64.rs:2051 — lib/compiler-singlepass/src/emitter_x64.rs:2051-2059 | lib/compiler-singlepass/src/emitter_x64.rs:2081-2089 | lib/compiler-singlepass/src/emitter_x64.rs:2111-2119 | lib/compiler-singlepass/src/emitter_x64.rs:2141-2149 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:7890 — lib/compiler-singlepass/src/machine_arm64.rs:7890-7898 | lib/compiler-singlepass/src/machine_arm64.rs:7928-7936 | lib/compiler-singlepass/src/machine_arm64.rs:8175-8183 | lib/compiler-singlepass/src/machine_arm64.rs:8213-8221 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:7909 — lib/compiler-singlepass/src/machine_arm64.rs:7909-7917 | lib/compiler-singlepass/src/machine_arm64.rs:7947-7955 | lib/compiler-singlepass/src/machine_arm64.rs:8194-8202 | lib/compiler-singlepass/src/machine_arm64.rs:8232-8240 — 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.

D4 · Code Duplication · Duplicated block (5 lines × 4) · ×5

Duplicated block (5 lines × 4) lib/api/src/backend/js/entities/function/mod.rs:194 — lib/api/src/backend/js/entities/function/mod.rs:194-198 | lib/api/src/backend/js/entities/function/mod.rs:250-254 | lib/api/src/backend/sys/entities/function/mod.rs:303-307 | lib/api/src/backend/sys/entities/function/mod.rs:357-361 — before extracting anything, compare `lib/api/src/backend/js/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 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 (5 lines × 4) lib/api/src/backend/sys/entities/memory/mod.rs:289 — lib/api/src/backend/sys/entities/memory/mod.rs:289-294 | lib/api/src/backend/sys/entities/memory/mod.rs:321-326 | lib/api/src/backend/v8/entities/memory/mod.rs:343-347 | lib/api/src/backend/v8/entities/memory/mod.rs:380-384 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) lib/api/src/entities/function/inner.rs:228 — lib/api/src/entities/function/inner.rs:228-232 | lib/api/src/entities/function/inner.rs:264-269 | lib/api/src/entities/function/inner.rs:293-297 | lib/api/src/entities/function/inner.rs:321-326 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 4) lib/compiler-cranelift/src/elf.rs:233 — lib/compiler-cranelift/src/elf.rs:233-239 | lib/compiler-singlepass/src/elf.rs:39-43 | lib/compiler/src/elf.rs:330-334 | lib/compiler/src/elf.rs:355-359 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler-singlepass/src/elf.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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 (5 lines × 4) lib/virtual-net/src/client.rs:785 — lib/virtual-net/src/client.rs:785-790 | lib/virtual-net/src/client.rs:816-821 | lib/virtual-net/src/client.rs:838-842 | lib/virtual-net/src/client.rs:866-871 — 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.

D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×4

Members sharing a duplicated core (6 members, 50+ identical tokens) lib/api/src/backend/js/entities/function/mod.rs:452 — lib/api/src/backend/js/entities/function/mod.rs:452-512 | lib/api/src/backend/js/entities/function/typed.rs:65-123 | lib/api/src/backend/sys/entities/function/mod.rs:513-589 | lib/api/src/backend/sys/entities/function/typed.rs:28-134 | lib/api/src/backend/sys/entities/function/typed.rs:172-272 | lib/api/src/backend/v8/entities/function/mod.rs:353-434 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) lib/compiler-llvm/src/translator/intrinsics.rs:1932 — lib/compiler-llvm/src/translator/intrinsics.rs:1932-2006 | lib/compiler-llvm/src/translator/intrinsics.rs:2012-2051 | lib/compiler-llvm/src/translator/intrinsics.rs:2057-2097 | lib/compiler-llvm/src/translator/intrinsics.rs:2103-2143 | lib/compiler-llvm/src/translator/intrinsics.rs:2149-2189 | lib/compiler-llvm/src/translator/intrinsics.rs:2195-2235 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) lib/virtual-fs/src/mem_fs/file.rs:389 — lib/virtual-fs/src/mem_fs/file.rs:389-443 | lib/virtual-fs/src/mem_fs/file.rs:445-490 | lib/virtual-fs/src/mem_fs/file.rs:1013-1048 | lib/virtual-fs/src/mem_fs/file.rs:1148-1215 | lib/virtual-fs/src/mem_fs/file.rs:1217-1252 | lib/virtual-fs/src/mem_fs/file.rs:1254-1289 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) lib/virtual-fs/src/mem_fs/file.rs:389 — lib/virtual-fs/src/mem_fs/file.rs:389-443 | lib/virtual-fs/src/mem_fs/file.rs:445-490 | lib/virtual-fs/src/mem_fs/file.rs:858-954 | lib/virtual-fs/src/mem_fs/file.rs:958-1011 | lib/virtual-fs/src/mem_fs/file.rs:1056-1142 | lib/virtual-fs/src/mem_fs/file.rs:1148-1215 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.

D4 · Code Duplication · Duplicated block (24 lines × 2) · ×4

Duplicated block (24 lines × 2) lib/compiler-llvm/src/translator/code.rs:2264 — lib/compiler-llvm/src/translator/code.rs:2264-2287 | lib/compiler-llvm/src/translator/code.rs:2296-2319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:231 — lib/compiler-singlepass/src/machine_x64.rs:231-254 | lib/compiler-singlepass/src/machine_x64.rs:259-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) lib/compiler/src/engine/artifact.rs:349 — lib/compiler/src/engine/artifact.rs:349-372 | lib/compiler/src/engine/artifact.rs:400-423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) lib/virtual-net/src/host.rs:347 — lib/virtual-net/src/host.rs:347-370 | lib/virtual-net/src/host.rs:813-836 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×4

Duplicated block (16–17 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1807 — lib/compiler-cranelift/src/func_environ.rs:1807-1823 | lib/compiler-cranelift/src/func_environ.rs:1887-1902 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16–17 lines × 2) lib/compiler-singlepass/src/codegen.rs:3652 — lib/compiler-singlepass/src/codegen.rs:3652-3668 | lib/compiler-singlepass/src/codegen.rs:3686-3701 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16–17 lines × 2) lib/wasix/src/net/socket.rs:1441 — lib/wasix/src/net/socket.rs:1441-1456 | lib/wasix/src/net/socket.rs:1533-1549 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16–17 lines × 2) lib/wasix/src/state/linker/mod.rs:535 — lib/wasix/src/state/linker/mod.rs:535-550 | lib/wasix/src/state/linker/mod.rs:779-795 — 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 (15–16 lines × 2) · ×4

Duplicated block (15–16 lines × 2) lib/compiler-singlepass/src/codegen.rs:5529 — lib/compiler-singlepass/src/codegen.rs:5529-5544 | lib/compiler-singlepass/src/codegen.rs:5661-5675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3674 — lib/compiler-singlepass/src/machine_x64.rs:3674-3688 | lib/compiler-singlepass/src/machine_x64.rs:4228-4243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:5616 — lib/compiler-singlepass/src/machine_x64.rs:5616-5630 | lib/compiler-singlepass/src/machine_x64.rs:6352-6367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) lib/types/src/vmoffsets.rs:297 — lib/types/src/vmoffsets.rs:297-311 | lib/types/src/vmoffsets.rs:334-349 — 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 (12 lines × 4) · ×4

Duplicated block (12 lines × 4) lib/api/src/backend/js/entities/function/mod.rs:224 — lib/api/src/backend/js/entities/function/mod.rs:224-235 | lib/api/src/backend/js/entities/function/mod.rs:281-292 | lib/api/src/backend/sys/entities/function/mod.rs:331-342 | lib/api/src/backend/sys/entities/function/mod.rs:388-399 — before extracting anything, compare `lib/api/src/backend/js/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) lib/api/src/backend/v8/entities/function/mod.rs:95 — lib/api/src/backend/v8/entities/function/mod.rs:95-106 | lib/api/src/backend/v8/entities/function/mod.rs:110-121 | lib/api/src/backend/v8/entities/function/mod.rs:170-181 | lib/api/src/backend/v8/entities/function/mod.rs:184-195 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:7228 — lib/compiler-singlepass/src/machine_arm64.rs:7228-7239 | lib/compiler-singlepass/src/machine_arm64.rs:7291-7302 | lib/compiler-singlepass/src/machine_arm64.rs:7354-7365 | lib/compiler-singlepass/src/machine_arm64.rs:7417-7428 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) lib/compiler-singlepass/src/machine_riscv.rs:485 — lib/compiler-singlepass/src/machine_riscv.rs:485-496 | lib/compiler-singlepass/src/machine_riscv.rs:507-518 | lib/compiler-singlepass/src/machine_riscv.rs:545-556 | lib/compiler-singlepass/src/machine_riscv.rs:754-765 — 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.

D4 · Code Duplication · Duplicated block (11 lines × 4) · ×4

Duplicated block (11 lines × 4) lib/compiler-llvm/src/translator/code.rs:6779 — lib/compiler-llvm/src/translator/code.rs:6779-6789 | lib/compiler-llvm/src/translator/code.rs:6841-6851 | lib/compiler-llvm/src/translator/code.rs:6949-6959 | lib/compiler-llvm/src/translator/code.rs:7012-7022 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) lib/compiler-llvm/src/translator/code.rs:8896 — lib/compiler-llvm/src/translator/code.rs:8896-8906 | lib/compiler-llvm/src/translator/code.rs:8970-8980 | lib/compiler-llvm/src/translator/code.rs:9045-9055 | lib/compiler-llvm/src/translator/code.rs:9111-9121 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) lib/compiler/src/engine/artifact.rs:639 — lib/compiler/src/engine/artifact.rs:639-649 | lib/compiler/src/engine/artifact.rs:651-661 | lib/compiler/src/engine/artifact.rs:666-676 | lib/compiler/src/engine/artifact.rs:678-688 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:7409 — lib/compiler-singlepass/src/machine_x64.rs:7409-7419 | lib/compiler-singlepass/src/machine_x64.rs:7524-7534 | lib/compiler-singlepass/src/machine_x64.rs:7811-7821 | lib/compiler-singlepass/src/machine_x64.rs:7926-7936 — 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.

D4 · Code Duplication · Duplicated block (8 lines × 6) · ×4

Duplicated block (8 lines × 6) lib/compiler-llvm/src/translator/code.rs:5251 — lib/compiler-llvm/src/translator/code.rs:5251-5258 | lib/compiler-llvm/src/translator/code.rs:5272-5279 | lib/compiler-llvm/src/translator/code.rs:5353-5360 | lib/compiler-llvm/src/translator/code.rs:5374-5381 | lib/compiler-llvm/src/translator/code.rs:5455-5462 | lib/compiler-llvm/src/translator/code.rs:5476-5483 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 6) lib/compiler-llvm/src/translator/code.rs:8898 — lib/compiler-llvm/src/translator/code.rs:8898-8905 | lib/compiler-llvm/src/translator/code.rs:8972-8979 | lib/compiler-llvm/src/translator/code.rs:9047-9054 | lib/compiler-llvm/src/translator/code.rs:9113-9120 | lib/compiler-llvm/src/translator/code.rs:9286-9293 | lib/compiler-llvm/src/translator/code.rs:9722-9729 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 6) lib/compiler-singlepass/src/machine_arm64.rs:1229 — lib/compiler-singlepass/src/machine_arm64.rs:1229-1236 | lib/compiler-singlepass/src/machine_riscv.rs:359-366 | lib/compiler-singlepass/src/machine_riscv.rs:419-426 | lib/compiler-singlepass/src/machine_riscv.rs:594-601 | lib/compiler-singlepass/src/machine_riscv.rs:633-640 | lib/compiler-singlepass/src/machine_riscv.rs:796-803 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 6) lib/compiler-singlepass/src/machine_riscv.rs:2982 — lib/compiler-singlepass/src/machine_riscv.rs:2982-2989 | lib/compiler-singlepass/src/machine_riscv.rs:3060-3067 | lib/compiler-singlepass/src/machine_riscv.rs:3090-3097 | lib/compiler-singlepass/src/machine_riscv.rs:4305-4312 | lib/compiler-singlepass/src/machine_riscv.rs:4384-4391 | lib/compiler-singlepass/src/machine_riscv.rs:4414-4421 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×4

Duplicated block (7–8 lines × 2) lib/compiler-llvm/src/translator/intrinsics.rs:1604 — lib/compiler-llvm/src/translator/intrinsics.rs:1604-1611 | lib/compiler-llvm/src/translator/intrinsics.rs:1644-1650 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 2) lib/compiler-llvm/src/translator/intrinsics.rs:1602 — lib/compiler-llvm/src/translator/intrinsics.rs:1602-1609 | lib/compiler-llvm/src/translator/intrinsics.rs:1613-1619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:1118 — lib/compiler-singlepass/src/machine_riscv.rs:1118-1124 | lib/compiler-singlepass/src/machine_riscv.rs:1234-1241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 2) lib/wasix/src/syscalls/wasix/closure_allocate.rs:13 — lib/wasix/src/syscalls/wasix/closure_allocate.rs:13-19 | lib/wasix/src/syscalls/wasix/closure_free.rs:11-18 — 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.

D5 · Coupling · Off the main sequence · ×4

Off the main sequence: wasmer-config — wasmer-config: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: wasmer-types — wasmer-types: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: virtual-mio — virtual-mio: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: wasmer-vm — wasmer-vm: 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.

D1 · Cyclomatic Complexity · wasmer_compiler_cranelift · ×3

wasmer_compiler_cranelift::translator::code_translator::translate_operator (cyclomatic 403) lib/compiler-cranelift/src/translator/code_translator.rs:157 — wasmer_compiler_cranelift::translator::code_translator::translate_operator has cyclomatic complexity 403 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
wasmer_compiler_cranelift::eh::compact_unwind_encoding_aarch64 (cyclomatic 19) lib/compiler-cranelift/src/eh.rs:419 — wasmer_compiler_cranelift::eh::compact_unwind_encoding_aarch64 has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
wasmer_compiler_cranelift::eh::build_function_lsda (cyclomatic 17) lib/compiler-cranelift/src/eh.rs:43 — wasmer_compiler_cranelift::eh::build_function_lsda has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · wasmer_vm · ×3

wasmer_vm::libcalls::eh::dwarf::eh::find_eh_action (cognitive 80) lib/vm/src/libcalls/eh/dwarf/eh.rs:72 — wasmer_vm::libcalls::eh::dwarf::eh::find_eh_action has cognitive complexity 80 (threshold 15). Drivers by points: if/else 20 (66 pts), loops 2 (7 pts), match/switch 1 (7 pts) (nesting depth added 57). 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.
wasmer_vm::trap::traphandlers::process_illegal_op (cognitive 27) lib/vm/src/trap/traphandlers.rs:185 — wasmer_vm::trap::traphandlers::process_illegal_op has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_vm::instance::initialize_tables (cognitive 16) lib/vm/src/instance/mod.rs:1592 — wasmer_vm::instance::initialize_tables has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (7 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MachineARM64 · ×3

MachineARM64::location_to_reg (cognitive 67) lib/compiler-singlepass/src/machine_arm64.rs:132 — MachineARM64::location_to_reg has cognitive complexity 67 (threshold 15). Drivers by points: if/else 30 (60 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 32). 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.
MachineARM64::move_location (cognitive 40) lib/compiler-singlepass/src/machine_arm64.rs:1835 — MachineARM64::move_location has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 9 (16 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MachineARM64::location_to_neon (cognitive 23) lib/compiler-singlepass/src/machine_arm64.rs:284 — MachineARM64::location_to_neon has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · WasiEnv · ×3

WasiEnv::process_signals_internal (cognitive 37) lib/wasix/src/state/env.rs:811 — WasiEnv::process_signals_internal has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 3 (8 pts), match/switch 1 (4 pts) (nesting depth added 24). 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.
WasiEnv::instantiate (cognitive 20) lib/wasix/src/state/env.rs:496 — WasiEnv::instantiate has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 6 (10 pts), if/else 7 (9 pts), boolean chains 1 (nesting depth added 6). 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.
WasiEnv::on_exit (cognitive 18) lib/wasix/src/state/env.rs:1304 — WasiEnv::on_exit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FileSystem · ×3

FileSystem::open (cognitive 32) lib/virtual-fs/src/mem_fs/file_opener.rs:328 — FileSystem::open has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 7, match/switch 5 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileSystem::union (cognitive 17) lib/virtual-fs/src/mem_fs/filesystem.rs:121 — FileSystem::union has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 2 (6 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FileSystem::rename (cognitive 16) lib/virtual-fs/src/mem_fs/filesystem.rs:527 — FileSystem::rename has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 6 (11 pts), if/else 3 (5 pts) (nesting depth added 7). 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 · CmdAppCreate · ×3

CmdAppCreate::run_async (cognitive 30) lib/cli/src/commands/app/create.rs:854 — CmdAppCreate::run_async has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CmdAppCreate::create_from_template (cognitive 28) lib/cli/src/commands/app/create.rs:645 — CmdAppCreate::create_from_template has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (22 pts), match/switch 2 (3 pts), boolean chains 2, 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.
CmdAppCreate::get_template_url (cognitive 20) lib/cli/src/commands/app/create.rs:521 — CmdAppCreate::get_template_url has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D23 · Boundary Type-Coupling · Cross-context type Iter (types → api) · ×3

Cross-context type Iter (types → api) lib/api/src/backend/js/entities/store/obj.rs:89 — Iter (context types) is exposed in api's public surface via StoreObjects.iter_globals — couples the contexts.
Cross-context type Iter (types → api) lib/api/src/backend/v8/entities/store/obj.rs:110 — Iter (context types) is exposed in api's public surface via StoreObjects.iter_globals — couples the contexts.
Cross-context type Iter (types → api) lib/api/src/utils/mem/access.rs:73 — Iter (context types) is exposed in api's public surface via WasmSliceAccess.iter — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type IntoIter (types → api) · ×3

Cross-context type IntoIter (types → api) lib/api/src/entities/exports.rs:268 — IntoIter (context types) is exposed in api's public surface via Exports.into_iter — couples the contexts.
Cross-context type IntoIter (types → api) lib/api/src/entities/exports.rs:277 — IntoIter (context types) is exposed in api's public surface via Exports.into_iter — couples the contexts.
Cross-context type IntoIter (types → api) lib/api/src/entities/imports.rs:191 — IntoIter (context types) is exposed in api's public surface via Imports.into_iter — couples the contexts.

D31 · IaC & Container Security · Medium IaC · ×3

REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Change-coupling hub · ×3

Change-coupling hub: proc_fork.rs → proc_exit.rs, stack_checkpoint.rs, thread_spawn.rs lib/wasix/src/syscalls/wasix/proc_fork.rs — `lib/wasix/src/syscalls/wasix/proc_fork.rs` changes together with 3 other files — `lib/wasix/src/syscalls/wasi/proc_exit.rs`, `lib/wasix/src/syscalls/wasix/stack_checkpoint.rs`, `lib/wasix/src/syscalls/wasix/thread_spawn.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: mod.rs → compile.rs, inspect.rs, validate.rs lib/cli/src/commands/run/mod.rs — `lib/cli/src/commands/run/mod.rs` changes together with 3 other files — `lib/cli/src/commands/compile.rs`, `lib/cli/src/commands/inspect.rs`, `lib/cli/src/commands/validate.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: fd_write.rs → fd_read.rs, fd_seek.rs, sock_send_file.rs lib/wasix/src/syscalls/wasi/fd_write.rs — `lib/wasix/src/syscalls/wasi/fd_write.rs` changes together with 3 other files — `lib/wasix/src/syscalls/wasi/fd_read.rs`, `lib/wasix/src/syscalls/wasi/fd_seek.rs`, `lib/wasix/src/syscalls/wasix/sock_send_file.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED
REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED
REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×3

Duplicated block (26 lines × 2) lib/api/src/backend/sys/entities/function/mod.rs:108 — lib/api/src/backend/sys/entities/function/mod.rs:108-133 | lib/api/src/backend/sys/entities/function/mod.rs:223-248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) lib/backend-api/src/query.rs:1529 — lib/backend-api/src/query.rs:1529-1554 | lib/backend-api/src/query.rs:1594-1619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) lib/types/src/module.rs:239 — lib/types/src/module.rs:239-264 | lib/types/src/module.rs:271-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (14 lines × 3) · ×3

Duplicated block (14 lines × 3) lib/compiler-cranelift/src/translator/code_translator.rs:3252 — lib/compiler-cranelift/src/translator/code_translator.rs:3252-3265 | lib/compiler-cranelift/src/translator/code_translator.rs:3305-3318 | lib/compiler-cranelift/src/translator/code_translator.rs:3391-3404 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) lib/virtual-fs/src/mem_fs/file.rs:880 — lib/virtual-fs/src/mem_fs/file.rs:880-893 | lib/virtual-fs/src/mem_fs/file.rs:895-908 | lib/virtual-fs/src/mem_fs/file.rs:910-923 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) lib/compiler-cranelift/src/translator/code_translator.rs:3235 — lib/compiler-cranelift/src/translator/code_translator.rs:3235-3248 | lib/compiler-cranelift/src/translator/code_translator.rs:3284-3297 | lib/compiler-cranelift/src/translator/code_translator.rs:3375-3388 — 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 (9–10 lines × 4) · ×3

Duplicated block (9–10 lines × 4) lib/compiler-llvm/src/translator/code.rs:6823 — lib/compiler-llvm/src/translator/code.rs:6823-6831 | lib/compiler-llvm/src/translator/code.rs:6885-6893 | lib/compiler-llvm/src/translator/code.rs:6993-7002 | lib/compiler-llvm/src/translator/code.rs:7056-7064 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 4) lib/cli/src/commands/app/deploy.rs:899 — lib/cli/src/commands/app/deploy.rs:899-909 | lib/cli/src/commands/app/deploy.rs:912-921 | lib/cli/src/commands/app/deploy.rs:923-932 | lib/cli/src/commands/app/deploy.rs:933-941 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 4) lib/compiler-llvm/src/object_file.rs:851 — lib/compiler-llvm/src/object_file.rs:851-860 | lib/compiler-llvm/src/object_file.rs:865-874 | lib/compiler-llvm/src/object_file.rs:879-888 | lib/compiler-llvm/src/object_file.rs:890-898 — 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.

D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×3

Duplicated block (9–10 lines × 2) lib/compiler-cranelift/src/compiler.rs:158 — lib/compiler-cranelift/src/compiler.rs:158-166 | lib/compiler-llvm/src/compiler.rs:269-278 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–10 lines × 2) lib/compiler-llvm/src/translator/code.rs:9673 — lib/compiler-llvm/src/translator/code.rs:9673-9681 | lib/compiler-llvm/src/translator/code.rs:9697-9706 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) lib/wasix/src/state/func_env.rs:392 — lib/wasix/src/state/func_env.rs:392-400 | lib/wasix/src/state/func_env.rs:406-415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×3

Duplicated block (8–9 lines × 2) lib/cli/src/commands/package/download.rs:82 — lib/cli/src/commands/package/download.rs:82-89 | lib/cli/src/commands/package/download.rs:103-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) lib/virtual-fs/src/overlay_fs.rs:1187 — lib/virtual-fs/src/overlay_fs.rs:1187-1195 | lib/virtual-fs/src/overlay_fs.rs:1204-1211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) lib/vm/src/instance/allocator.rs:215 — lib/vm/src/instance/allocator.rs:215-223 | lib/vm/src/instance/allocator.rs:250-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (8 lines × 4) · ×3

Duplicated block (8 lines × 4) lib/compiler-cranelift/src/func_environ.rs:2166 — lib/compiler-cranelift/src/func_environ.rs:2166-2173 | lib/compiler-cranelift/src/func_environ.rs:2194-2201 | lib/compiler-cranelift/src/func_environ.rs:2253-2265 | lib/compiler-cranelift/src/func_environ.rs:2287-2294 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) lib/compiler-llvm/src/translator/code.rs:4084 — lib/compiler-llvm/src/translator/code.rs:4084-4091 | lib/compiler-llvm/src/translator/code.rs:4100-4107 | lib/compiler-llvm/src/translator/code.rs:4144-4151 | lib/compiler-llvm/src/translator/code.rs:4156-4163 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) lib/compiler-llvm/src/translator/code.rs:6738 — lib/compiler-llvm/src/translator/code.rs:6738-6745 | lib/compiler-llvm/src/translator/code.rs:6761-6768 | lib/compiler-llvm/src/translator/code.rs:6908-6915 | lib/compiler-llvm/src/translator/code.rs:6931-6938 — 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.

D4 · Code Duplication · Duplicated block (5 lines × 6) · ×3

Duplicated block (5 lines × 6) lib/api/src/backend/js/entities/function/mod.rs:473 — lib/api/src/backend/js/entities/function/mod.rs:473-481 | lib/api/src/backend/js/entities/function/typed.rs:88-92 | lib/api/src/backend/sys/entities/function/mod.rs:551-559 | lib/api/src/backend/sys/entities/function/typed.rs:92-96 | lib/api/src/backend/sys/entities/function/typed.rs:229-234 | lib/api/src/backend/v8/entities/function/mod.rs:403-411 — before extracting anything, compare `lib/api/src/backend/js/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 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 (5 lines × 6) lib/compiler-cranelift/src/func_environ.rs:1394 — lib/compiler-cranelift/src/func_environ.rs:1394-1399 | lib/compiler-cranelift/src/func_environ.rs:1415-1419 | lib/compiler-cranelift/src/func_environ.rs:2101-2105 | lib/compiler-cranelift/src/func_environ.rs:2117-2121 | lib/compiler-cranelift/src/func_environ.rs:2229-2233 | lib/compiler-cranelift/src/func_environ.rs:2353-2357 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 6) lib/compiler/src/engine/link.rs:137 — lib/compiler/src/engine/link.rs:137-141 | lib/compiler/src/engine/link.rs:143-147 | lib/compiler/src/engine/link.rs:149-153 | lib/compiler/src/engine/link.rs:181-185 | lib/compiler/src/engine/link.rs:193-197 | lib/compiler/src/engine/link.rs:199-203 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D1 · Cyclomatic Complexity · FuncGen · ×2

FuncGen::feed_operator (cyclomatic 369) lib/compiler-singlepass/src/codegen.rs:1170 — FuncGen::feed_operator has cyclomatic complexity 369 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FuncGen::emit_call_native (cyclomatic 19) lib/compiler-singlepass/src/codegen.rs:730 — FuncGen::emit_call_native has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · RemoteNetworkingServerDriver · ×2

RemoteNetworkingServerDriver::process_socket (cyclomatic 125) lib/virtual-net/src/server.rs:860 — RemoteNetworkingServerDriver::process_socket has cyclomatic complexity 125 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RemoteNetworkingServerDriver::process_interface (cyclomatic 26) lib/virtual-net/src/server.rs:657 — RemoteNetworkingServerDriver::process_interface has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · wasmer_compiler · ×2

wasmer_compiler::engine::link::apply_relocation (cyclomatic 57) lib/compiler/src/engine/link.rs:21 — wasmer_compiler::engine::link::apply_relocation has cyclomatic complexity 57 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
wasmer_compiler::object::module::emit_compilation (cyclomatic 44) lib/compiler/src/object/module.rs:139 — wasmer_compiler::object::module::emit_compilation has cyclomatic complexity 44 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · WasiFs · ×2

WasiFs::get_inode_at_path_inner (cyclomatic 43) lib/wasix/src/fs/mod.rs:1241 — WasiFs::get_inode_at_path_inner has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WasiFs::create_preopens (cyclomatic 18) lib/wasix/src/fs/mod.rs:2387 — WasiFs::create_preopens has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: wasmer_wasix::fs::fs_error_into_wasi_err (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D1 · Cyclomatic Complexity · MachineARM64 · ×2

MachineARM64::location_to_reg (cyclomatic 32) lib/compiler-singlepass/src/machine_arm64.rs:132 — MachineARM64::location_to_reg has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MachineARM64::move_location (cyclomatic 32) lib/compiler-singlepass/src/machine_arm64.rs:1835 — MachineARM64::move_location has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · RemoteAdapterSocket · ×2

RemoteAdapterSocket::drain_reads_and_accepts (cyclomatic 26) lib/virtual-net/src/server.rs:1506 — RemoteAdapterSocket::drain_reads_and_accepts has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RemoteAdapterSocket::send (cyclomatic 16) lib/virtual-net/src/server.rs:1340 — RemoteAdapterSocket::send has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · wasmer_vm · ×2

wasmer_vm::trap::traphandlers::process_illegal_op (cyclomatic 26) lib/vm/src/trap/traphandlers.rs:185 — wasmer_vm::trap::traphandlers::process_illegal_op has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
wasmer_vm::libcalls::eh::dwarf::eh::find_eh_action (cyclomatic 22) lib/vm/src/libcalls/eh/dwarf/eh.rs:72 — wasmer_vm::libcalls::eh::dwarf::eh::find_eh_action has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · RemoteTx · ×2

RemoteTx::poll_send (cyclomatic 23) lib/virtual-net/src/rx_tx.rs:160 — RemoteTx::poll_send has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RemoteTx::send_with_driver (cyclomatic 17) lib/virtual-net/src/rx_tx.rs:327 — RemoteTx::send_with_driver has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · LLVMAbi · ×2

LLVMAbi::func_type_to_llvm (cyclomatic 19) lib/compiler-llvm/src/abi.rs:204 — LLVMAbi::func_type_to_llvm has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
LLVMAbi::rets_from_call (cyclomatic 18) lib/compiler-llvm/src/abi.rs:363 — LLVMAbi::rets_from_call has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D2 · Cognitive Complexity · FuncGen · ×2

FuncGen::feed_operator (cognitive 228) lib/compiler-singlepass/src/codegen.rs:1170 — FuncGen::feed_operator has cognitive complexity 228 (threshold 15). Drivers by points: if/else 102 (180 pts), loops 10 (25 pts), boolean chains 17, match/switch 3 (6 pts) (nesting depth added 96). 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.
FuncGen::emit_call_native (cognitive 20) lib/compiler-singlepass/src/codegen.rs:730 — FuncGen::emit_call_native has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), loops 5, match/switch 3 (5 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · RemoteNetworkingServerDriver · ×2

RemoteNetworkingServerDriver::process_socket (cognitive 93) lib/virtual-net/src/server.rs:860 — RemoteNetworkingServerDriver::process_socket has cognitive complexity 93 (threshold 15). Drivers by points: match/switch 62 (93 pts) (nesting depth added 31). 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.
RemoteNetworkingServerDriver::poll (cognitive 17) lib/virtual-net/src/server.rs:328 — RemoteNetworkingServerDriver::poll has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (7 pts), if/else 3 (6 pts), loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WasiFs · ×2

WasiFs::get_inode_at_path_inner (cognitive 83) lib/wasix/src/fs/mod.rs:1241 — WasiFs::get_inode_at_path_inner has cognitive complexity 83 (threshold 15). Drivers by points: if/else 30 (66 pts), match/switch 4 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WasiFs::create_preopens (cognitive 32) lib/wasix/src/fs/mod.rs:2387 — WasiFs::create_preopens has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RemoteAdapterSocket · ×2

RemoteAdapterSocket::drain_reads_and_accepts (cognitive 50) lib/virtual-net/src/server.rs:1506 — RemoteAdapterSocket::drain_reads_and_accepts has cognitive complexity 50 (threshold 15). Drivers by points: if/else 9 (29 pts), match/switch 6 (18 pts), loops 2 (3 pts) (nesting depth added 33). 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.
RemoteAdapterSocket::send (cognitive 41) lib/virtual-net/src/server.rs:1340 — RemoteAdapterSocket::send has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (34 pts), match/switch 3 (7 pts) (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · FuncTrampoline · ×2

FuncTrampoline::dynamic_trampoline (cognitive 33) lib/compiler-llvm/src/translator/trampoline.rs:318 — FuncTrampoline::dynamic_trampoline has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (13 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FuncTrampoline::trampoline (cognitive 17) lib/compiler-llvm/src/translator/trampoline.rs:161 — FuncTrampoline::trampoline has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InstanceGroupState · ×2

InstanceGroupState::define_common_import (cognitive 29) lib/wasix/src/state/linker/instance_group/imports.rs:396 — InstanceGroupState::define_common_import has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (26 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstanceGroupState::generate_stub_function (cognitive 22) lib/wasix/src/state/linker/instance_group/imports.rs:520 — InstanceGroupState::generate_stub_function has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), match/switch 3 (5 pts) (nesting depth added 13). 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 · RemoteTx · ×2

RemoteTx::poll_send (cognitive 26) lib/virtual-net/src/rx_tx.rs:160 — RemoteTx::poll_send has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 10 (14 pts), if/else 6 (12 pts) (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RemoteTx::send_with_driver (cognitive 22) lib/virtual-net/src/rx_tx.rs:327 — RemoteTx::send_with_driver has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 7 (10 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · LLVMAbi · ×2

LLVMAbi::rets_from_call (cognitive 23) lib/compiler-llvm/src/abi.rs:363 — LLVMAbi::rets_from_call has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 4 (6 pts), loops 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLVMAbi::func_type_to_llvm (cognitive 18) lib/compiler-llvm/src/abi.rs:204 — LLVMAbi::func_type_to_llvm has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 2 (6 pts), match/switch 4 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CmdAppSecretsCreate · ×2

CmdAppSecretsCreate::create (cognitive 18) lib/cli/src/commands/app/secrets/create.rs:145 — CmdAppSecretsCreate::create has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CmdAppSecretsCreate::filter_secrets (cognitive 16) lib/cli/src/commands/app/secrets/create.rs:90 — CmdAppSecretsCreate::filter_secrets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Wasi · ×2

Wasi::build_mapped_directories (cognitive 18) lib/cli/src/commands/run/wasi.rs:505 — Wasi::build_mapped_directories has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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.
Wasi::prepare (cognitive 16) lib/cli/src/commands/run/wasi.rs:343 — Wasi::prepare has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · wasmer_package_sdk · ×2

wasmer_package_sdk::app::deploy_remote_build::deploy_app_remote (cognitive 17) lib/package-sdk/src/app/deploy_remote_build.rs:101 — wasmer_package_sdk::app::deploy_remote_build::deploy_app_remote has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 1 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasmer_package_sdk::app::deploy::wait_app (cognitive 16) lib/package-sdk/src/app/deploy.rs:132 — wasmer_package_sdk::app::deploy::wait_app has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D23 · Boundary Type-Coupling · Cross-context type FunctionEnv (api → wasix) · ×2

Cross-context type FunctionEnv (api → wasix) lib/wasix/src/state/func_env.rs:28 — FunctionEnv (context api) is exposed in wasix's public surface via WasiFunctionEnv.env — couples the contexts.
Cross-context type FunctionEnv (api → wasix) lib/wasix/src/lib.rs:374 — FunctionEnv (context api) is exposed in wasix's public surface via wasmer_wasix$module.generate_import_object_from_env — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Table (api → wasix) · ×2

Cross-context type Table (api → wasix) lib/wasix/src/state/handles/mod.rs:119 — Table (context api) is exposed in wasix's public surface via WasiModuleInstanceHandles.new — couples the contexts.
Cross-context type Table (api → wasix) lib/wasix/src/state/linker/types.rs:39 — Table (context api) is exposed in wasix's public surface via LinkedMainModule.indirect_function_table — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ModuleHandle (api → wasix) · ×2

Cross-context type ModuleHandle (api → wasix) lib/wasix/src/state/linker/mod.rs:1202 — ModuleHandle (context api) is exposed in wasix's public surface via Linker.resolve_export — couples the contexts.
Cross-context type ModuleHandle (api → wasix) lib/wasix/src/state/linker/mod.rs:1321 — ModuleHandle (context api) is exposed in wasix's public surface via Linker.is_handle_valid — couples the contexts.

D3 · God Classes · TooManyFields · ×2

TooManyFields: Intrinsics lib/compiler-llvm/src/translator/intrinsics.rs:71 — TooManyFields — 179 stored fields beside 1 method. The bar is 30 stored fields; this is 149 over it, 5.97× 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: FuncEnvironment lib/compiler-cranelift/src/func_environ.rs:89 — TooManyFields — 38 stored fields beside 99 methods. The bar is 30 stored fields; this is 8 over it, 1.27× 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.

D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (7 members, 50+ identical tokens) lib/compiler-cranelift/src/func_environ.rs:1391 — lib/compiler-cranelift/src/func_environ.rs:1391-1403 | lib/compiler-cranelift/src/func_environ.rs:1410-1422 | lib/compiler-cranelift/src/func_environ.rs:2099-2108 | lib/compiler-cranelift/src/func_environ.rs:2115-2124 | lib/compiler-cranelift/src/func_environ.rs:2226-2236 | lib/compiler-cranelift/src/func_environ.rs:2327-2342 | lib/compiler-cranelift/src/func_environ.rs:2351-2360 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_x64.rs:4354 — lib/compiler-singlepass/src/machine_x64.rs:4354-4394 | lib/compiler-singlepass/src/machine_x64.rs:4408-4454 | lib/compiler-singlepass/src/machine_x64.rs:4468-4514 | lib/compiler-singlepass/src/machine_x64.rs:6523-6563 | lib/compiler-singlepass/src/machine_x64.rs:6577-6623 | lib/compiler-singlepass/src/machine_x64.rs:6637-6683 | lib/compiler-singlepass/src/machine_x64.rs:6697-6743 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.

D4 · Code Duplication · Duplicated block (36 lines × 2) · ×2

Duplicated block (36 lines × 2) lib/virtual-net/src/rx_tx.rs:204 — lib/virtual-net/src/rx_tx.rs:204-239 | lib/virtual-net/src/rx_tx.rs:265-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (36 lines × 2) lib/wasix/src/syscalls/wasi/path_open.rs:41 — lib/wasix/src/syscalls/wasi/path_open.rs:41-76 | lib/wasix/src/syscalls/wasix/path_open2.rs:44-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (31 lines × 2) · ×2

Duplicated block (31 lines × 2) lib/cli/src/commands/app/create.rs:406 — lib/cli/src/commands/app/create.rs:406-436 | lib/cli/src/commands/app/create.rs:488-518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) lib/compiler-llvm/src/translator/code.rs:4750 — lib/compiler-llvm/src/translator/code.rs:4750-4780 | lib/compiler-llvm/src/translator/code.rs:4869-4899 — 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 (30 lines × 2) · ×2

Duplicated block (30 lines × 2) lib/compiler-cranelift/src/trampoline/dynamic_function.rs:137 — lib/compiler-cranelift/src/trampoline/dynamic_function.rs:137-166 | lib/compiler-cranelift/src/trampoline/function_call.rs:127-156 — 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 (30 lines × 2) lib/virtual-net/src/rx_tx.rs:559 — lib/virtual-net/src/rx_tx.rs:559-588 | lib/virtual-net/src/rx_tx.rs:592-621 — 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 (25 lines × 4) · ×2

Duplicated block (25 lines × 4) lib/compiler-llvm/src/translator/code.rs:1481 — lib/compiler-llvm/src/translator/code.rs:1481-1505 | lib/compiler-llvm/src/translator/code.rs:1564-1588 | lib/compiler-llvm/src/translator/code.rs:1612-1636 | lib/compiler-llvm/src/translator/code.rs:1675-1699 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (25 lines × 4) lib/compiler-llvm/src/translator/code.rs:8859 — lib/compiler-llvm/src/translator/code.rs:8859-8883 | lib/compiler-llvm/src/translator/code.rs:8933-8957 | lib/compiler-llvm/src/translator/code.rs:9008-9032 | lib/compiler-llvm/src/translator/code.rs:9074-9098 — 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.

D4 · Code Duplication · Duplicated block (25 lines × 2) · ×2

Duplicated block (25 lines × 2) lib/compiler-llvm/src/translator/code.rs:12209 — lib/compiler-llvm/src/translator/code.rs:12209-12233 | lib/compiler-llvm/src/translator/code.rs:12247-12271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) lib/sys-utils/src/memory/fd_memory/memories.rs:115 — lib/sys-utils/src/memory/fd_memory/memories.rs:115-139 | lib/vm/src/memory.rs:110-134 — before extracting anything, compare `lib/sys-utils/src/memory/fd_memory/memories.rs` and `lib/vm/src/memory.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 156 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 (23 lines × 4) · ×2

Duplicated block (23 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:3717 — lib/compiler-singlepass/src/machine_x64.rs:3717-3739 | lib/compiler-singlepass/src/machine_x64.rs:3850-3872 | lib/compiler-singlepass/src/machine_x64.rs:5659-5681 | lib/compiler-singlepass/src/machine_x64.rs:5839-5861 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:3764 — lib/compiler-singlepass/src/machine_x64.rs:3764-3786 | lib/compiler-singlepass/src/machine_x64.rs:3897-3919 | lib/compiler-singlepass/src/machine_x64.rs:5706-5728 | lib/compiler-singlepass/src/machine_x64.rs:5886-5908 — 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.

D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×2

Duplicated block (21–23 lines × 2) lib/sys-utils/src/memory/fd_memory/memories.rs:92 — lib/sys-utils/src/memory/fd_memory/memories.rs:92-112 | lib/vm/src/memory.rs:86-108 — before extracting anything, compare `lib/sys-utils/src/memory/fd_memory/memories.rs` and `lib/vm/src/memory.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 156 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 (21–23 lines × 2) lib/wasix/src/net/socket.rs:332 — lib/wasix/src/net/socket.rs:332-352 | lib/wasix/src/net/socket.rs:373-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2

Duplicated block (23 lines × 2) lib/wasix/src/syscalls/wasix/epoll_create.rs:60 — lib/wasix/src/syscalls/wasix/epoll_create.rs:60-82 | lib/wasix/src/syscalls/wasix/sock_open.rs:103-125 — 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 (23 lines × 2) lib/wasix/src/syscalls/wasix/fd_pipe.rs:88 — lib/wasix/src/syscalls/wasix/fd_pipe.rs:88-110 | lib/wasix/src/syscalls/wasix/fd_pipe.rs:112-134 — 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 (18 lines × 4) · ×2

Duplicated block (18 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:3678 — lib/compiler-singlepass/src/machine_x64.rs:3678-3695 | lib/compiler-singlepass/src/machine_x64.rs:3811-3828 | lib/compiler-singlepass/src/machine_x64.rs:5753-5770 | lib/compiler-singlepass/src/machine_x64.rs:5933-5950 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 4) lib/virtual-net/src/client.rs:147 — lib/virtual-net/src/client.rs:147-164 | lib/virtual-net/src/client.rs:168-185 | lib/virtual-net/src/server.rs:117-134 | lib/virtual-net/src/server.rs:138-155 — before extracting anything, compare `lib/virtual-net/src/client.rs` and `lib/virtual-net/src/server.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2

Duplicated block (17–18 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:3056 — lib/compiler-singlepass/src/machine_x64.rs:3056-3072 | lib/compiler-singlepass/src/machine_x64.rs:3109-3126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–18 lines × 2) lib/virtual-fs/src/mem_fs/file.rs:1701 — lib/virtual-fs/src/mem_fs/file.rs:1701-1718 | lib/virtual-fs/src/mem_fs/file.rs:1807-1823 — 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 (17 lines × 3) · ×2

Duplicated block (17 lines × 3) lib/virtual-net/src/rx_tx.rs:185 — lib/virtual-net/src/rx_tx.rs:185-201 | lib/virtual-net/src/rx_tx.rs:246-262 | lib/virtual-net/src/rx_tx.rs:307-323 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 3) lib/virtual-net/src/rx_tx.rs:360 — lib/virtual-net/src/rx_tx.rs:360-376 | lib/virtual-net/src/rx_tx.rs:422-438 | lib/virtual-net/src/rx_tx.rs:484-500 — 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 (15 lines × 3) · ×2

Duplicated block (15 lines × 3) lib/api/src/backend/js/entities/function/mod.rs:475 — lib/api/src/backend/js/entities/function/mod.rs:475-489 | lib/api/src/backend/sys/entities/function/mod.rs:553-567 | lib/api/src/backend/v8/entities/function/mod.rs:405-419 — before extracting anything, compare `lib/api/src/backend/js/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 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 (15 lines × 3) lib/wasix/src/net/socket.rs:1459 — lib/wasix/src/net/socket.rs:1459-1473 | lib/wasix/src/net/socket.rs:1552-1566 | lib/wasix/src/net/socket.rs:1641-1655 — 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 (14–15 lines × 2) · ×2

Duplicated block (14–15 lines × 2) lib/c-api-imports/src/lib.rs:1441 — lib/c-api-imports/src/lib.rs:1441-1454 | lib/c-api-imports/src/lib.rs:1461-1475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–15 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:361 — lib/compiler-singlepass/src/machine_riscv.rs:361-374 | lib/compiler-singlepass/src/machine_riscv.rs:635-649 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2

Duplicated block (13 lines × 4) lib/api/src/backend/js/entities/memory/view.rs:255 — lib/api/src/backend/js/entities/memory/view.rs:255-267 | lib/api/src/backend/sys/entities/memory/view.rs:178-190 | lib/api/src/backend/v8/entities/memory/view.rs:173-185 | lib/api/src/entities/memory/view/inner.rs:208-220 — before extracting anything, compare `lib/api/src/backend/sys/entities/memory/view.rs` and `lib/api/src/backend/v8/entities/memory/view.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:6990 — lib/compiler-singlepass/src/machine_arm64.rs:6990-7002 | lib/compiler-singlepass/src/machine_arm64.rs:7048-7060 | lib/compiler-singlepass/src/machine_arm64.rs:7106-7118 | lib/compiler-singlepass/src/machine_arm64.rs:7164-7176 — 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.

D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×2

Duplicated block (12–13 lines × 4) lib/compiler-singlepass/src/codegen.rs:3650 — lib/compiler-singlepass/src/codegen.rs:3650-3661 | lib/compiler-singlepass/src/codegen.rs:3684-3695 | lib/compiler-singlepass/src/codegen.rs:3731-3743 | lib/compiler-singlepass/src/codegen.rs:3756-3767 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 4) lib/virtual-net/src/rx_tx.rs:117 — lib/virtual-net/src/rx_tx.rs:117-128 | lib/virtual-net/src/rx_tx.rs:138-149 | lib/virtual-net/src/rx_tx.rs:380-392 | lib/virtual-net/src/rx_tx.rs:442-454 — 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.

D4 · Code Duplication · Duplicated block (11–12 lines × 4) · ×2

Duplicated block (11–12 lines × 4) lib/compiler-llvm/src/translator/code.rs:4944 — lib/compiler-llvm/src/translator/code.rs:4944-4955 | lib/compiler-llvm/src/translator/code.rs:4960-4971 | lib/compiler-llvm/src/translator/code.rs:8726-8736 | lib/compiler-llvm/src/translator/code.rs:8750-8760 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11–12 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:147 — lib/compiler-singlepass/src/machine_arm64.rs:147-158 | lib/compiler-singlepass/src/machine_arm64.rs:167-178 | lib/compiler-singlepass/src/machine_arm64.rs:187-198 | lib/compiler-singlepass/src/machine_riscv.rs:186-196 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×2

Duplicated block (10–12 lines × 3) lib/compiler-llvm/src/translator/code.rs:2352 — lib/compiler-llvm/src/translator/code.rs:2352-2361 | lib/compiler-llvm/src/translator/code.rs:2370-2379 | lib/compiler-llvm/src/translator/code.rs:4007-4018 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10–12 lines × 3) lib/compiler-singlepass/src/codegen.rs:2814 — lib/compiler-singlepass/src/codegen.rs:2814-2823 | lib/compiler-singlepass/src/codegen.rs:2882-2893 | lib/compiler-singlepass/src/codegen.rs:5863-5874 — 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 (10–12 lines × 2) · ×2

Duplicated block (10–12 lines × 2) lib/c-api/src/wasm_c_api/wasi/mod.rs:254 — lib/c-api/src/wasm_c_api/wasi/mod.rs:254-265 | lib/c-api/src/wasm_c_api/wasi/mod.rs:281-290 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–12 lines × 2) scripts/make-release.py:398 — scripts/make-release.py:398-407 | scripts/make-release.py:467-478 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×2

Duplicated block (10–11 lines × 3) lib/cli/src/commands/app/secrets/create.rs:218 — lib/cli/src/commands/app/secrets/create.rs:218-227 | lib/cli/src/commands/app/secrets/delete.rs:140-149 | lib/cli/src/commands/app/secrets/update.rs:212-222 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/delete.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:2538 — lib/compiler-singlepass/src/machine_x64.rs:2538-2547 | lib/compiler-singlepass/src/machine_x64.rs:7392-7402 | lib/compiler-singlepass/src/machine_x64.rs:7507-7517 — 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 (9–11 lines × 2) · ×2

Duplicated block (9–11 lines × 2) lib/api/src/backend/v8/entities/function/mod.rs:263 — lib/api/src/backend/v8/entities/function/mod.rs:263-273 | lib/api/src/backend/v8/entities/tag.rs:36-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–11 lines × 2) scripts/make-release.py:246 — scripts/make-release.py:246-256 | scripts/make-release.py:294-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/make-release.py:246` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×2

Duplicated block (10–11 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:2212 — lib/compiler-singlepass/src/machine_riscv.rs:2212-2222 | lib/compiler-singlepass/src/machine_x64.rs:2248-2257 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) lib/compiler/src/engine/artifact.rs:1770 — lib/compiler/src/engine/artifact.rs:1770-1779 | lib/compiler/src/engine/artifact.rs:1818-1828 — 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 (10 lines × 13) · ×2

Duplicated block (10 lines × 13) lib/compiler-llvm/src/translator/code.rs:7487 — lib/compiler-llvm/src/translator/code.rs:7487-7496 | lib/compiler-llvm/src/translator/code.rs:7562-7571 | lib/compiler-llvm/src/translator/code.rs:7645-7655 | lib/compiler-llvm/src/translator/code.rs:7732-7742 | lib/compiler-llvm/src/translator/code.rs:7804-7814 | lib/compiler-llvm/src/translator/code.rs:7894-7904 | lib/compiler-llvm/src/translator/code.rs:7966-7976 | lib/compiler-llvm/src/translator/code.rs:8056-8066 | lib/compiler-llvm/src/translator/code.rs:8125-8135 | lib/compiler-llvm/src/translator/code.rs:8215-8225 | lib/compiler-llvm/src/translator/code.rs:8625-8634 | lib/compiler-llvm/src/translator/code.rs:8653-8662 | lib/compiler-llvm/src/translator/code.rs:10594-10603 — all 13 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 13) lib/compiler-llvm/src/translator/code.rs:7517 — lib/compiler-llvm/src/translator/code.rs:7517-7526 | lib/compiler-llvm/src/translator/code.rs:7592-7601 | lib/compiler-llvm/src/translator/code.rs:7681-7691 | lib/compiler-llvm/src/translator/code.rs:7840-7850 | lib/compiler-llvm/src/translator/code.rs:8002-8012 | lib/compiler-llvm/src/translator/code.rs:8161-8171 | lib/compiler-llvm/src/translator/code.rs:8297-8307 | lib/compiler-llvm/src/translator/code.rs:8349-8359 | lib/compiler-llvm/src/translator/code.rs:8401-8411 | lib/compiler-llvm/src/translator/code.rs:8453-8463 | lib/compiler-llvm/src/translator/code.rs:8505-8515 | lib/compiler-llvm/src/translator/code.rs:8557-8567 | lib/compiler-llvm/src/translator/code.rs:10669-10678 — all 13 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 (10 lines × 10) · ×2

Duplicated block (10 lines × 10) lib/compiler-llvm/src/translator/code.rs:6204 — lib/compiler-llvm/src/translator/code.rs:6204-6214 | lib/compiler-llvm/src/translator/code.rs:6230-6240 | lib/compiler-llvm/src/translator/code.rs:6298-6308 | lib/compiler-llvm/src/translator/code.rs:6324-6334 | lib/compiler-llvm/src/translator/code.rs:6392-6402 | lib/compiler-llvm/src/translator/code.rs:6499-6509 | lib/compiler-llvm/src/translator/code.rs:6780-6789 | lib/compiler-llvm/src/translator/code.rs:6842-6851 | lib/compiler-llvm/src/translator/code.rs:6950-6959 | lib/compiler-llvm/src/translator/code.rs:7013-7022 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 10) lib/compiler-llvm/src/translator/code.rs:7472 — lib/compiler-llvm/src/translator/code.rs:7472-7481 | lib/compiler-llvm/src/translator/code.rs:7547-7556 | lib/compiler-llvm/src/translator/code.rs:7627-7637 | lib/compiler-llvm/src/translator/code.rs:7714-7724 | lib/compiler-llvm/src/translator/code.rs:7786-7796 | lib/compiler-llvm/src/translator/code.rs:7876-7886 | lib/compiler-llvm/src/translator/code.rs:7948-7958 | lib/compiler-llvm/src/translator/code.rs:8038-8048 | lib/compiler-llvm/src/translator/code.rs:8107-8117 | lib/compiler-llvm/src/translator/code.rs:8197-8207 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×2

Duplicated block (8–10 lines × 2) lib/compiler/src/engine/tunables.rs:96 — lib/compiler/src/engine/tunables.rs:96-105 | lib/compiler/src/engine/tunables.rs:142-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 2) lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs:59 — lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs:59-66 | lib/wasix/src/syscalls/wasi/path_filestat_set_times.rs:89-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (9 lines × 7) · ×2

Duplicated block (9 lines × 7) lib/compiler-llvm/src/translator/code.rs:6209 — lib/compiler-llvm/src/translator/code.rs:6209-6217 | lib/compiler-llvm/src/translator/code.rs:6303-6311 | lib/compiler-llvm/src/translator/code.rs:6397-6405 | lib/compiler-llvm/src/translator/code.rs:6784-6792 | lib/compiler-llvm/src/translator/code.rs:6809-6817 | lib/compiler-llvm/src/translator/code.rs:6954-6962 | lib/compiler-llvm/src/translator/code.rs:6979-6987 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 7) lib/compiler-llvm/src/translator/code.rs:6235 — lib/compiler-llvm/src/translator/code.rs:6235-6243 | lib/compiler-llvm/src/translator/code.rs:6329-6337 | lib/compiler-llvm/src/translator/code.rs:6504-6512 | lib/compiler-llvm/src/translator/code.rs:6846-6854 | lib/compiler-llvm/src/translator/code.rs:6871-6879 | lib/compiler-llvm/src/translator/code.rs:7017-7025 | lib/compiler-llvm/src/translator/code.rs:7042-7050 — all 7 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 (2–8 lines × 8) · ×2

Duplicated block (2–8 lines × 8) lib/compiler-singlepass/src/machine_arm64.rs:2585 — lib/compiler-singlepass/src/machine_arm64.rs:2585-2586 | lib/compiler-singlepass/src/machine_arm64.rs:2611-2612 | lib/compiler-singlepass/src/machine_arm64.rs:2653-2654 | lib/compiler-singlepass/src/machine_arm64.rs:2691-2692 | lib/compiler-singlepass/src/machine_riscv.rs:2980-2987 | lib/compiler-singlepass/src/machine_riscv.rs:3011-3018 | lib/compiler-singlepass/src/machine_riscv.rs:3058-3065 | lib/compiler-singlepass/src/machine_riscv.rs:3088-3095 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (2–8 lines × 8) lib/compiler-singlepass/src/machine_arm64.rs:4768 — lib/compiler-singlepass/src/machine_arm64.rs:4768-4769 | lib/compiler-singlepass/src/machine_arm64.rs:4794-4795 | lib/compiler-singlepass/src/machine_arm64.rs:4836-4837 | lib/compiler-singlepass/src/machine_arm64.rs:4874-4875 | lib/compiler-singlepass/src/machine_riscv.rs:4303-4310 | lib/compiler-singlepass/src/machine_riscv.rs:4334-4341 | lib/compiler-singlepass/src/machine_riscv.rs:4382-4389 | lib/compiler-singlepass/src/machine_riscv.rs:4412-4419 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7 lines × 8) · ×2

Duplicated block (7 lines × 8) lib/compiler-singlepass/src/machine_riscv.rs:2982 — lib/compiler-singlepass/src/machine_riscv.rs:2982-2988 | lib/compiler-singlepass/src/machine_riscv.rs:3013-3019 | lib/compiler-singlepass/src/machine_riscv.rs:3060-3066 | lib/compiler-singlepass/src/machine_riscv.rs:3090-3096 | lib/compiler-singlepass/src/machine_riscv.rs:4305-4311 | lib/compiler-singlepass/src/machine_riscv.rs:4336-4342 | lib/compiler-singlepass/src/machine_riscv.rs:4384-4390 | lib/compiler-singlepass/src/machine_riscv.rs:4414-4420 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 8) lib/compiler-singlepass/src/machine_x64.rs:1145 — lib/compiler-singlepass/src/machine_x64.rs:1145-1151 | lib/compiler-singlepass/src/machine_x64.rs:1259-1265 | lib/compiler-singlepass/src/machine_x64.rs:1351-1357 | lib/compiler-singlepass/src/machine_x64.rs:1437-1443 | lib/compiler-singlepass/src/machine_x64.rs:1558-1564 | lib/compiler-singlepass/src/machine_x64.rs:1672-1678 | lib/compiler-singlepass/src/machine_x64.rs:1751-1757 | lib/compiler-singlepass/src/machine_x64.rs:1824-1830 — all 8 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 (7 lines × 5) · ×2

Duplicated block (7 lines × 5) lib/virtual-fs/src/mem_fs/filesystem.rs:200 — lib/virtual-fs/src/mem_fs/filesystem.rs:200-210 | lib/virtual-fs/src/mem_fs/filesystem.rs:262-268 | lib/virtual-fs/src/mem_fs/filesystem.rs:400-410 | lib/virtual-fs/src/mem_fs/filesystem.rs:476-486 | lib/virtual-fs/src/mem_fs/filesystem.rs:712-722 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 5) lib/virtual-net/src/client.rs:719 — lib/virtual-net/src/client.rs:719-725 | lib/virtual-net/src/client.rs:789-795 | lib/virtual-net/src/client.rs:820-826 | lib/virtual-net/src/client.rs:841-847 | lib/virtual-net/src/client.rs:870-876 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6 lines × 4) · ×2

Duplicated block (6 lines × 4) lib/compiler-llvm/src/translator/code.rs:2833 — lib/compiler-llvm/src/translator/code.rs:2833-2838 | lib/compiler-llvm/src/translator/code.rs:2844-2853 | lib/compiler-llvm/src/translator/code.rs:3004-3010 | lib/compiler-llvm/src/translator/code.rs:11706-11712 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) lib/compiler-singlepass/src/machine_arm64.rs:2655 — lib/compiler-singlepass/src/machine_arm64.rs:2655-2660 | lib/compiler-singlepass/src/machine_arm64.rs:2693-2698 | lib/compiler-singlepass/src/machine_arm64.rs:4838-4843 | lib/compiler-singlepass/src/machine_arm64.rs:4876-4881 — 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.

D4 · Code Duplication · Duplicated block (5 lines × 5) · ×2

Duplicated block (5 lines × 5) lib/compiler-cranelift/src/func_environ.rs:1394 — lib/compiler-cranelift/src/func_environ.rs:1394-1399 | lib/compiler-cranelift/src/func_environ.rs:1415-1419 | lib/compiler-cranelift/src/func_environ.rs:2101-2105 | lib/compiler-cranelift/src/func_environ.rs:2333-2338 | lib/compiler-cranelift/src/func_environ.rs:2353-2357 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 5) lib/compiler-llvm/src/translator/code.rs:2804 — lib/compiler-llvm/src/translator/code.rs:2804-2808 | lib/compiler-llvm/src/translator/code.rs:2833-2837 | lib/compiler-llvm/src/translator/code.rs:2844-2848 | lib/compiler-llvm/src/translator/code.rs:3004-3008 | lib/compiler-llvm/src/translator/code.rs:11706-11710 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (4–5 lines × 3) · ×2

Duplicated block (4–5 lines × 3) lib/virtual-fs/src/cow_file.rs:152 — lib/virtual-fs/src/cow_file.rs:152-156 | lib/virtual-fs/src/cow_file.rs:165-169 | lib/virtual-fs/src/cow_file.rs:276-279 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (4–5 lines × 3) lib/virtual-fs/src/mem_fs/mod.rs:153 — lib/virtual-fs/src/mem_fs/mod.rs:153-156 | lib/virtual-fs/src/mem_fs/mod.rs:178-182 | lib/virtual-fs/src/mem_fs/mod.rs:202-206 — 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.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

C2 · Access Controls · No authorization · ×1

No authorization lib/cli/src/commands/auth/login/mod.rs:132 — This repository serves requests — a server (.serve_connection) (lib/cli/src/commands/auth/login/mod.rs:132) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.

D1 · Cyclomatic Complexity · JournalSyscallPlayer · ×1

JournalSyscallPlayer::play_event (cyclomatic 118) lib/wasix/src/syscalls/journal/play_event.rs:7 — JournalSyscallPlayer::play_event has cyclomatic complexity 118 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · wasmer_compiler_llvm · ×1

wasmer_compiler_llvm::object_file::load_object_file (cyclomatic 93) lib/compiler-llvm/src/object_file.rs:194 — wasmer_compiler_llvm::object_file::load_object_file has cyclomatic complexity 93 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · virtual_fs · ×1

virtual_fs::overlay_fs::open_copy_on_write (cyclomatic 72) lib/virtual-fs/src/overlay_fs.rs:741 — virtual_fs::overlay_fs::open_copy_on_write has cyclomatic complexity 72 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · make-release.make_release (cyclomatic 69) · ×1

make-release.make_release (cyclomatic 69) scripts/make-release.py:78 — make-release.make_release has cyclomatic complexity 69 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · JournalEntry · ×1

JournalEntry::fmt (cyclomatic 66) lib/journal/src/concrete/printing.rs:67 — JournalEntry::fmt has cyclomatic complexity 66 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · CompactingJournalTx · ×1

CompactingJournalTx::write (cyclomatic 60) lib/journal/src/concrete/compacting.rs:528 — CompactingJournalTx::write has cyclomatic complexity 60 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CmdAppDeploy · ×1

CmdAppDeploy::run_async (cyclomatic 49) lib/cli/src/commands/app/deploy.rs:565 — CmdAppDeploy::run_async has cyclomatic complexity 49 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InodeValFilePollGuardJoin · ×1

InodeValFilePollGuardJoin::poll (cyclomatic 45) lib/wasix/src/fs/inode_guard.rs:161 — InodeValFilePollGuardJoin::poll has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CraneliftCompiler · ×1

CraneliftCompiler::compile_module_internal (cyclomatic 40) lib/compiler-cranelift/src/compiler.rs:107 — CraneliftCompiler::compile_module_internal has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · virtual_net · ×1

virtual_net::io_err_into_net_error (cyclomatic 39) lib/virtual-net/src/lib.rs:903 — virtual_net::io_err_into_net_error has cyclomatic complexity 39 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · BackendType · ×1

BackendType::get_engine (cyclomatic 32) lib/cli/src/backend.rs:594 — BackendType::get_engine has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · SinglepassCompiler · ×1

SinglepassCompiler::compile_module_internal (cyclomatic 31) lib/compiler-singlepass/src/compiler.rs:67 — SinglepassCompiler::compile_module_internal has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · RuntimeOptions · ×1

RuntimeOptions::get_sys_compiler_config (cyclomatic 30) lib/cli/src/backend.rs:438 — RuntimeOptions::get_sys_compiler_config has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · FileSystem · ×1

FileSystem::open (cyclomatic 30) lib/virtual-fs/src/mem_fs/file_opener.rs:328 — FileSystem::open has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · Tty · ×1

Tty::apply_canonical_input (cyclomatic 29) lib/wasix/src/os/tty/mod.rs:607 — Tty::apply_canonical_input has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · InputParser · ×1

InputParser::feed (cyclomatic 29) lib/wasix/src/os/tty/mod.rs:396 — InputParser::feed has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · LLVMCompiler · ×1

LLVMCompiler::compile_module (cyclomatic 28) lib/compiler-llvm/src/compiler.rs:249 — LLVMCompiler::compile_module has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · RemoteNetworkingClientDriver · ×1

RemoteNetworkingClientDriver::poll (cyclomatic 28) lib/virtual-net/src/client.rs:297 — RemoteNetworkingClientDriver::poll has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · FuncTranslator · ×1

FuncTranslator::translate_to_module (cyclomatic 26) lib/compiler-llvm/src/translator/code.rs:186 — FuncTranslator::translate_to_module has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: LLVMFunctionCodeGenerator::translate_floating_point_arithmetic_operator (cyclomatic 70) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D1 · Cyclomatic Complexity · Run · ×1

Run::execute_inner (cyclomatic 25) lib/cli/src/commands/run/mod.rs:214 — Run::execute_inner has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WasiFunctionEnv · ×1

WasiFunctionEnv::initialize_handles_and_layout (cyclomatic 25) lib/wasix/src/state/func_env.rs:161 — WasiFunctionEnv::initialize_handles_and_layout has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PackageDownload · ×1

PackageDownload::execute (cyclomatic 24) lib/cli/src/commands/package/download.rs:58 — PackageDownload::execute has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Features · ×1

Features::detect_from_wasm (cyclomatic 23) lib/types/src/features.rs:378 — Features::detect_from_wasm has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · WasiEnvBuilder · ×1

WasiEnvBuilder::build_init (cyclomatic 23) lib/wasix/src/state/builder.rs:884 — WasiEnvBuilder::build_init has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Artifact · ×1

Artifact::from_parts_with_module_file (cyclomatic 21) lib/compiler/src/engine/artifact.rs:448 — Artifact::from_parts_with_module_file has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · RemoteRx · ×1

RemoteRx::poll (cyclomatic 21) lib/virtual-net/src/rx_tx.rs:537 — RemoteRx::poll has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · CmdAppLogs · ×1

CmdAppLogs::run_async (cyclomatic 20) lib/cli/src/commands/app/logs.rs:84 — CmdAppLogs::run_async has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · FilteredJournalTx · ×1

FilteredJournalTx::write (cyclomatic 19) lib/journal/src/concrete/filter.rs:227 — FilteredJournalTx::write has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · wasmer_compiler_singlepass · ×1

wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 (cyclomatic 18) lib/compiler-singlepass/src/emitter_arm64.rs:3108 — wasmer_compiler_singlepass::emitter_arm64::gen_import_call_trampoline_arm64 has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · wasmer_package · ×1

wasmer_package::convert::webc_to_package::webc_to_package_dir (cyclomatic 18) lib/package/src/convert/webc_to_package.rs:11 — wasmer_package::convert::webc_to_package::webc_to_package_dir has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Module · ×1

Module::annotate_table_functions (cyclomatic 17) lib/api/src/backend/js/entities/module.rs:324 — Module::annotate_table_functions has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MemoryMappedBinary · ×1

MemoryMappedBinary::try_from_source (cyclomatic 17) lib/compiler/src/engine/mapped_binary.rs:275 — MemoryMappedBinary::try_from_source has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · OverlayFileSystem · ×1

OverlayFileSystem::open (cyclomatic 17) lib/virtual-fs/src/overlay_fs.rs:619 — OverlayFileSystem::open has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InodeSocketProtected · ×1

InodeSocketProtected::poll_read_ready (cyclomatic 17) lib/wasix/src/net/socket.rs:1759 — InodeSocketProtected::poll_read_ready has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: WasiSocketOption::try_from (cyclomatic 28) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D1 · Cyclomatic Complexity · InstanceGroupState · ×1

InstanceGroupState::define_common_import (cyclomatic 17) lib/wasix/src/state/linker/instance_group/imports.rs:396 — InstanceGroupState::define_common_import has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Target · ×1

Target::command (cyclomatic 16) lib/cli/src/commands/add.rs:155 — Target::command has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GetOrSet · ×1

GetOrSet::execute (cyclomatic 16) lib/cli/src/commands/config.rs:239 — GetOrSet::execute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CmdCronInvocations · ×1

CmdCronInvocations::run_async (cyclomatic 16) lib/cli/src/commands/cron.rs:161 — CmdCronInvocations::run_async has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · wasmer_cli · ×1

wasmer_cli::commands::init::construct_manifest (cyclomatic 16) lib/cli/src/commands/init.rs:362 — wasmer_cli::commands::init::construct_manifest has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CpuFeature · ×1

CpuFeature::for_host (cyclomatic 16) lib/types/src/target.rs:57 — CpuFeature::for_host has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: CpuFeature::from_str (cyclomatic 17) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D1 · Cyclomatic Complexity · OffloadedFile · ×1

OffloadedFile::write (cyclomatic 16) lib/virtual-fs/src/mem_fs/offloaded_file.rs:234 — OffloadedFile::write has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · JournalSyscallPlayer · ×1

JournalSyscallPlayer::play_event (cognitive 137) lib/wasix/src/syscalls/journal/play_event.rs:7 — JournalSyscallPlayer::play_event has cognitive complexity 137 (threshold 15). Drivers by points: if/else 93 (136 pts), match/switch 1 (nesting depth added 43). 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 · make-release.make_release (cognitive 132) · ×1

make-release.make_release (cognitive 132) scripts/make-release.py:78 — make-release.make_release has cognitive complexity 132 (threshold 15). Drivers by points: if/else 42 (75 pts), loops 29 (53 pts), boolean chains 4 (nesting depth added 57). 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 · CmdAppDeploy · ×1

CmdAppDeploy::run_async (cognitive 112) lib/cli/src/commands/app/deploy.rs:565 — CmdAppDeploy::run_async has cognitive complexity 112 (threshold 15). Drivers by points: if/else 55 (105 pts), boolean chains 6, match/switch 1 (nesting depth added 50). 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 · virtual_fs · ×1

virtual_fs::overlay_fs::open_copy_on_write (cognitive 96) lib/virtual-fs/src/overlay_fs.rs:741 — virtual_fs::overlay_fs::open_copy_on_write has cognitive complexity 96 (threshold 15). Drivers by points: match/switch 27 (47 pts), if/else 13 (45 pts), loops 2 (4 pts) (nesting depth added 54). 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 · wasmer_compiler_llvm · ×1

wasmer_compiler_llvm::object_file::load_object_file (cognitive 78) lib/compiler-llvm/src/object_file.rs:194 — wasmer_compiler_llvm::object_file::load_object_file has cognitive complexity 78 (threshold 15). Drivers by points: if/else 18 (53 pts), match/switch 6 (21 pts), loops 3 (4 pts) (nesting depth added 51). 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 · CraneliftCompiler · ×1

CraneliftCompiler::compile_module_internal (cognitive 77) lib/compiler-cranelift/src/compiler.rs:107 — CraneliftCompiler::compile_module_internal has cognitive complexity 77 (threshold 15). Drivers by points: if/else 41 (62 pts), match/switch 4 (7 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InodeValFilePollGuardJoin · ×1

InodeValFilePollGuardJoin::poll (cognitive 77) lib/wasix/src/fs/inode_guard.rs:161 — InodeValFilePollGuardJoin::poll has cognitive complexity 77 (threshold 15). Drivers by points: if/else 20 (48 pts), match/switch 11 (26 pts), boolean chains 2, loops 1 (nesting depth added 43). 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 · LLVMCompiler · ×1

LLVMCompiler::compile_module (cognitive 64) lib/compiler-llvm/src/compiler.rs:249 — LLVMCompiler::compile_module has cognitive complexity 64 (threshold 15). Drivers by points: if/else 23 (41 pts), loops 6 (18 pts), match/switch 3 (5 pts) (nesting depth added 32). 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 · RemoteNetworkingClientDriver · ×1

RemoteNetworkingClientDriver::poll (cognitive 61) lib/virtual-net/src/client.rs:297 — RemoteNetworkingClientDriver::poll has cognitive complexity 61 (threshold 15). Drivers by points: if/else 9 (38 pts), match/switch 8 (20 pts), loops 2 (3 pts) (nesting depth added 42). 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 · WasiFunctionEnv · ×1

WasiFunctionEnv::initialize_handles_and_layout (cognitive 61) lib/wasix/src/state/func_env.rs:161 — WasiFunctionEnv::initialize_handles_and_layout has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (39 pts), match/switch 6 (22 pts) (nesting depth added 37). 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 · CompactingJournalTx · ×1

CompactingJournalTx::write (cognitive 48) lib/journal/src/concrete/compacting.rs:528 — CompactingJournalTx::write has cognitive complexity 48 (threshold 15). Drivers by points: if/else 34 (46 pts), boolean chains 1, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Run · ×1

Run::execute_inner (cognitive 46) lib/cli/src/commands/run/mod.rs:214 — Run::execute_inner has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (27 pts), match/switch 6 (15 pts), boolean chains 4 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BackendType · ×1

BackendType::get_engine (cognitive 44) lib/cli/src/backend.rs:594 — BackendType::get_engine has cognitive complexity 44 (threshold 15). Drivers by points: if/else 20 (38 pts), match/switch 4 (6 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InputParser · ×1

InputParser::feed (cognitive 44) lib/wasix/src/os/tty/mod.rs:396 — InputParser::feed has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (32 pts), match/switch 2 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 28). 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 · PackageTag · ×1

PackageTag::get_version (cognitive 40) lib/cli/src/commands/package/tag.rs:387 — PackageTag::get_version has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (38 pts), match/switch 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SinglepassCompiler · ×1

SinglepassCompiler::compile_module_internal (cognitive 40) lib/compiler-singlepass/src/compiler.rs:67 — SinglepassCompiler::compile_module_internal has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 8 (14 pts), if/else 12 (13 pts), loops 6 (11 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RuntimeOptions · ×1

RuntimeOptions::get_sys_compiler_config (cognitive 39) lib/cli/src/backend.rs:438 — RuntimeOptions::get_sys_compiler_config has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (33 pts), match/switch 4 (6 pts) (nesting depth added 17). 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 · Tty · ×1

Tty::apply_canonical_input (cognitive 38) lib/wasix/src/os/tty/mod.rs:607 — Tty::apply_canonical_input has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 4 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 21). 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 · PackageDownload · ×1

PackageDownload::execute (cognitive 37) lib/cli/src/commands/package/download.rs:58 — PackageDownload::execute has cognitive complexity 37 (threshold 15). Drivers by points: if/else 24 (32 pts), match/switch 3 (5 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 · Artifact · ×1

Artifact::from_parts_with_module_file (cognitive 37) lib/compiler/src/engine/artifact.rs:448 — Artifact::from_parts_with_module_file has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (27 pts), match/switch 8 (10 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 · FsVolume · ×1

FsVolume::as_directory_tree (cognitive 37) lib/package/src/package/volume/fs.rs:304 — FsVolume::as_directory_tree has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · wasmer_package · ×1

wasmer_package::convert::webc_to_package::webc_to_package_dir (cognitive 36) lib/package/src/convert/webc_to_package.rs:11 — wasmer_package::convert::webc_to_package::webc_to_package_dir has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 5 (8 pts), match/switch 1 (2 pts) (nesting depth added 17). 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 · CmdAppLogs · ×1

CmdAppLogs::run_async (cognitive 35) lib/cli/src/commands/app/logs.rs:84 — CmdAppLogs::run_async has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 4 (7 pts), boolean chains 3, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FuncTranslator · ×1

FuncTranslator::translate_to_module (cognitive 34) lib/compiler-llvm/src/translator/code.rs:186 — FuncTranslator::translate_to_module has cognitive complexity 34 (threshold 15). Drivers by points: if/else 19 (23 pts), loops 5 (6 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · Selector · ×1

Selector::run (cognitive 33) lib/virtual-io/src/selector.rs:220 — Selector::run has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Module · ×1

Module::annotate_table_functions (cognitive 29) lib/api/src/backend/js/entities/module.rs:324 — Module::annotate_table_functions has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 4 (5 pts), match/switch 2 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WasmerCmd · ×1

WasmerCmd::run_inner (cognitive 29) lib/cli/src/commands/mod.rs:226 — WasmerCmd::run_inner has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (5 pts), boolean chains 2, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Features · ×1

Features::detect_from_wasm (cognitive 29) lib/types/src/features.rs:378 — Features::detect_from_wasm has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 3, loops 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RemoteRx · ×1

RemoteRx::poll (cognitive 29) lib/virtual-net/src/rx_tx.rs:537 — RemoteRx::poll has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 8 (25 pts), if/else 1 (3 pts), loops 1 (nesting depth added 19). 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 · OffloadedFile · ×1

OffloadedFile::write (cognitive 28) lib/virtual-fs/src/mem_fs/offloaded_file.rs:234 — OffloadedFile::write has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 3 (5 pts), match/switch 2 (4 pts), boolean chains 2 (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 · WasiEnvBuilder · ×1

WasiEnvBuilder::build_init (cognitive 28) lib/wasix/src/state/builder.rs:884 — WasiEnvBuilder::build_init has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 7 (8 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MemoryMappedBinary · ×1

MemoryMappedBinary::try_from_source (cognitive 26) lib/compiler/src/engine/mapped_binary.rs:275 — MemoryMappedBinary::try_from_source has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WasiProcessInner · ×1

WasiProcessInner::maybe_checkpoint (cognitive 26) lib/wasix/src/os/task/process.rs:226 — WasiProcessInner::maybe_checkpoint has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LocalRwLockInner · ×1

LocalRwLockInner::poll_lock (cognitive 25) lib/api/src/entities/store/local_rwlock.rs:188 — LocalRwLockInner::poll_lock has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (25 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 · Target · ×1

Target::command (cognitive 25) lib/cli/src/commands/add.rs:155 — Target::command has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TokioTaskManager · ×1

TokioTaskManager::task_wasm (cognitive 25) lib/wasix/src/runtime/task_manager/tokio.rs:141 — TokioTaskManager::task_wasm has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 6 (11 pts), loops 1 (2 pts) (nesting depth added 13). Of this number, 24 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · CmdAppSecretsImport · ×1

CmdAppSecretsImport::import (cognitive 24) lib/cli/src/commands/app/secrets/import.rs:128 — CmdAppSecretsImport::import has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TunTapSocket · ×1

TunTapSocket::create (cognitive 24) lib/cli/src/net/tun.rs:42 — TunTapSocket::create has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 6 (8 pts), loops 3 (5 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 · ReqwestHttpClient · ×1

ReqwestHttpClient::request (cognitive 24) lib/wasix/src/http/reqwest.rs:41 — ReqwestHttpClient::request has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (9 pts), loops 3 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WasiThread · ×1

WasiThread::add_snapshot (cognitive 24) lib/wasix/src/os/task/thread.rs:433 — WasiThread::add_snapshot has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CmdCronInvocations · ×1

CmdCronInvocations::run_async (cognitive 23) lib/cli/src/commands/cron.rs:161 — CmdCronInvocations::run_async has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Mmap · ×1

Mmap::accessible_reserved (cognitive 23) lib/vm/src/mmap.rs:69 — Mmap::accessible_reserved has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 2, match/switch 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MachineRiscv · ×1

MachineRiscv::location_to_reg (cognitive 22) lib/compiler-singlepass/src/machine_riscv.rs:136 — MachineRiscv::location_to_reg has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · Manifest · ×1

Manifest::validate (cognitive 22) lib/config/src/package/mod.rs:805 — Manifest::validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 2, match/switch 1 (2 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 · OverlayFileSystem · ×1

OverlayFileSystem::open (cognitive 22) lib/virtual-fs/src/overlay_fs.rs:619 — OverlayFileSystem::open has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 2 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CmdAppList · ×1

CmdAppList::run_async (cognitive 21) lib/cli/src/commands/app/list.rs:56 — CmdAppList::run_async has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GetOrSet · ×1

GetOrSet::execute (cognitive 21) lib/cli/src/commands/config.rs:239 — GetOrSet::execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 3 (5 pts), boolean chains 2 (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 · LoopbackNetworking · ×1

LoopbackNetworking::allocate_tcp_bind_addr (cognitive 21) lib/virtual-net/src/loopback.rs:82 — LoopbackNetworking::allocate_tcp_bind_addr has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, loops 1 (2 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 · FilteredJournalTx · ×1

FilteredJournalTx::write (cognitive 20) lib/journal/src/concrete/filter.rs:227 — FilteredJournalTx::write has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MachineX86_64 · ×1

MachineX86_64::gen_import_call_trampoline (cognitive 19) lib/compiler-singlepass/src/machine_x64.rs:8207 — MachineX86_64::gen_import_call_trampoline has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 2 (6 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Publisher.publish (cognitive 19) · ×1

Publisher.publish (cognitive 19) scripts/publish.py:297 — Publisher.publish has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CmdAppSecretsUpdate · ×1

CmdAppSecretsUpdate::update (cognitive 18) lib/cli/src/commands/app/secrets/update.rs:139 — CmdAppSecretsUpdate::update has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GlobalFrameInfo · ×1

GlobalFrameInfo::lookup_frame_info (cognitive 18) lib/compiler/src/engine/trap/frame_info.rs:109 — GlobalFrameInfo::lookup_frame_info has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · AsyncifyPoller · ×1

AsyncifyPoller::poll (cognitive 18) lib/wasix/src/syscalls/mod.rs:379 — AsyncifyPoller::poll has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WasmerClient · ×1

WasmerClient::run_graphql_raw (cognitive 17) lib/backend-api/src/client.rs:121 — WasmerClient::run_graphql_raw has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 4 (8 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · CmdSsh · ×1

CmdSsh::run_async (cognitive 17) lib/cli/src/commands/ssh.rs:47 — CmdSsh::run_async has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · TunTapDriver · ×1

TunTapDriver::poll (cognitive 17) lib/cli/src/net/tun.rs:302 — TunTapDriver::poll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 3 (6 pts), loops 3 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WasmSourceMap · ×1

WasmSourceMap::new (cognitive 17) lib/compiler/src/source_map.rs:35 — WasmSourceMap::new has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), match/switch 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ThreadConditions · ×1

ThreadConditions::do_wait (cognitive 17) lib/vm/src/threadconditions.rs:104 — ThreadConditions::do_wait has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · AsyncCallFuture · ×1

AsyncCallFuture::poll (cognitive 16) lib/api/src/backend/sys/async_runtime.rs:160 — AsyncCallFuture::poll has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (7 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.

D2 · Cognitive Complexity · wasmer · ×1

wasmer::backend::js::utils::shared_handle::import_shared_objects (cognitive 16) lib/api/src/backend/js/utils/shared_handle.rs:207 — wasmer::backend::js::utils::shared_handle::import_shared_objects has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Logout · ×1

Logout::run_async (cognitive 16) lib/cli/src/commands/auth/logout.rs:27 — Logout::run_async has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Indented · ×1

Indented::write_str (cognitive 16) lib/cli/src/error.rs:115 — Indented::write_str has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (3 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.

D2 · Cognitive Complexity · CmdWasmer · ×1

CmdWasmer::run (cognitive 16) lib/wasix/src/os/command/builtins/cmd_wasmer.rs:94 — CmdWasmer::run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · wasmer-perf-record.annotate_function (cognitive 16) · ×1

wasmer-perf-record.annotate_function (cognitive 16) scripts/wasmer-perf-record.py:161 — wasmer-perf-record.annotate_function has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D23 · Boundary Type-Coupling · Cross-context type Bytes (types → api) · ×1

Cross-context type Bytes (types → api) lib/api/src/utils/into_bytes.rs:7 — Bytes (context types) is exposed in api's public surface via IntoBytes.into_bytes — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type IterMut (types → api) · ×1

Cross-context type IterMut (types → api) lib/api/src/utils/mem/access.rs:78 — IterMut (context types) is exposed in api's public surface via WasmSliceAccess.iter_mut — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ExportsIterator (api → types) · ×1

Cross-context type ExportsIterator (api → types) lib/types/src/module.rs:420 — ExportsIterator (context api) is exposed in types's public surface via ModuleInfo.exports — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ImportsIterator (api → types) · ×1

Cross-context type ImportsIterator (api → types) lib/types/src/module.rs:456 — ImportsIterator (context api) is exposed in types's public surface via ModuleInfo.imports — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type AsyncFunctionEnvMut (api → wasix) · ×1

Cross-context type AsyncFunctionEnvMut (api → wasix) lib/wasix/src/syscalls/wasix/context_switch.rs:17 — AsyncFunctionEnvMut (context api) is exposed in wasix's public surface via context_switch$module.context_switch — couples the contexts.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×1

REDACTED

D35 · Change Coupling · Change coupling clique · ×1

Change coupling clique: context_create.rs, context_destroy.rs, context_switch.rs lib/wasix/src/syscalls/wasix/context_create.rs — 3 files — `lib/wasix/src/syscalls/wasix/context_create.rs`, `lib/wasix/src/syscalls/wasix/context_destroy.rs`, `lib/wasix/src/syscalls/wasix/context_switch.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Near-duplicate member family (4 members, 25 shared lines) · ×1

Near-duplicate member family (4 members, 25 shared lines) lib/compiler-llvm/src/translator/code.rs:1480 — lib/compiler-llvm/src/translator/code.rs:1480-1525 | lib/compiler-llvm/src/translator/code.rs:1563-1601 | lib/compiler-llvm/src/translator/code.rs:1611-1664 | lib/compiler-llvm/src/translator/code.rs:1674-1736 — These 4 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member family (4 members, 17 shared lines) · ×1

Near-duplicate member family (4 members, 17 shared lines) lib/api/src/backend/js/entities/function/mod.rs:191 — lib/api/src/backend/js/entities/function/mod.rs:191-235 | lib/api/src/backend/js/entities/function/mod.rs:248-292 | lib/api/src/backend/sys/entities/function/mod.rs:300-342 | lib/api/src/backend/sys/entities/function/mod.rs:355-399 — These 4 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member family (4 members, 14 shared lines) · ×1

Near-duplicate member family (4 members, 14 shared lines) lib/compiler-singlepass/src/machine_x64.rs:3019 — lib/compiler-singlepass/src/machine_x64.rs:3019-3072 | lib/compiler-singlepass/src/machine_x64.rs:3074-3126 | lib/compiler-singlepass/src/machine_x64.rs:4802-4855 | lib/compiler-singlepass/src/machine_x64.rs:4857-4909 — These 4 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member family (3 members, 28 shared lines) · ×1

Near-duplicate member family (3 members, 28 shared lines) lib/compiler-singlepass/src/machine_riscv.rs:1380 — lib/compiler-singlepass/src/machine_riscv.rs:1380-1429 | lib/compiler-singlepass/src/machine_riscv.rs:1431-1486 | lib/compiler-singlepass/src/machine_riscv.rs:1488-1557 — These 3 members are variants of one another: a block of 28 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.

D4 · Code Duplication · Near-duplicate member pair (192 shared lines) · ×1

Near-duplicate member pair (192 shared lines) lib/compiler-llvm/src/translator/code.rs:7450 — lib/compiler-llvm/src/translator/code.rs:7450-8247 | lib/compiler-llvm/src/translator/code.rs:8254-8571 — These two members are variants of one another: 192 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (74 shared lines) · ×1

Near-duplicate member pair (74 shared lines) lib/compiler-singlepass/src/machine_riscv.rs:327 — lib/compiler-singlepass/src/machine_riscv.rs:327-570 | lib/compiler-singlepass/src/machine_riscv.rs:579-775 — These two members are variants of one another: 74 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (67 shared lines) · ×1

Near-duplicate member pair (67 shared lines) lib/sys-utils/src/memory/fd_memory/memories.rs:63 — lib/sys-utils/src/memory/fd_memory/memories.rs:63-139 | lib/vm/src/memory.rs:57-134 — These two members are variants of one another: 67 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (47 shared lines) · ×1

Near-duplicate member pair (47 shared lines) lib/wasix/src/syscalls/wasix/sock_send.rs:90 — lib/wasix/src/syscalls/wasix/sock_send.rs:90-171 | lib/wasix/src/syscalls/wasix/sock_send_to.rs:88-185 — These two members are variants of one another: 47 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (44 shared lines) · ×1

Near-duplicate member pair (44 shared lines) lib/compiler-cranelift/src/func_environ.rs:1186 — lib/compiler-cranelift/src/func_environ.rs:1186-1242 | lib/compiler-cranelift/src/func_environ.rs:1254-1314 — These two members are variants of one another: 44 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (38 shared lines) · ×1

Near-duplicate member pair (38 shared lines) lib/virtual-net/src/rx_tx.rs:160 — lib/virtual-net/src/rx_tx.rs:160-325 | lib/virtual-net/src/rx_tx.rs:327-502 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (34 shared lines) · ×1

Near-duplicate member pair (34 shared lines) lib/api/src/backend/v8/entities/function/mod.rs:167 — lib/api/src/backend/v8/entities/function/mod.rs:167-231 | lib/api/src/backend/v8/entities/function/mod.rs:243-311 — These two members are variants of one another: 34 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (32 shared lines) · ×1

Near-duplicate member pair (32 shared lines) lib/wasix/src/lib.rs:407 — lib/wasix/src/lib.rs:407-458 | lib/wasix/src/lib.rs:463-515 — These two members are variants of one another: 32 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (28 shared lines) · ×1

Near-duplicate member pair (28 shared lines) lib/compiler-singlepass/src/machine_arm64.rs:2877 — lib/compiler-singlepass/src/machine_arm64.rs:2877-2956 | lib/compiler-singlepass/src/machine_arm64.rs:5060-5140 — These two members are variants of one another: 28 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (24 shared lines) · ×1

Near-duplicate member pair (24 shared lines) lib/compiler-singlepass/src/machine_x64.rs:670 — lib/compiler-singlepass/src/machine_x64.rs:670-713 | lib/compiler-singlepass/src/machine_x64.rs:816-859 — These two members are variants of one another: 24 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1

Edited copy of a member (14 corresponding lines) lib/compiler-singlepass/src/machine_arm64.rs:473 — lib/compiler-singlepass/src/machine_arm64.rs:473-486 | lib/compiler-singlepass/src/machine_riscv.rs:305-318 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Members sharing a duplicated core (49 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (49 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_arm64.rs:3426 — lib/compiler-singlepass/src/machine_arm64.rs:3426-3474 | lib/compiler-singlepass/src/machine_arm64.rs:3487-3535 | lib/compiler-singlepass/src/machine_arm64.rs:3548-3596 | lib/compiler-singlepass/src/machine_arm64.rs:3609-3657 | lib/compiler-singlepass/src/machine_arm64.rs:3670-3718 | lib/compiler-singlepass/src/machine_arm64.rs:3731-3779 | lib/compiler-singlepass/src/machine_arm64.rs:3792-3840 | lib/compiler-singlepass/src/machine_arm64.rs:3853-3901 | lib/compiler-singlepass/src/machine_arm64.rs:3914-3962 | lib/compiler-singlepass/src/machine_arm64.rs:3975-4023 | lib/compiler-singlepass/src/machine_arm64.rs:4036-4084 | lib/compiler-singlepass/src/machine_arm64.rs:4097-4145 | lib/compiler-singlepass/src/machine_arm64.rs:4158-4206 | lib/compiler-singlepass/src/machine_arm64.rs:4219-4267 | lib/compiler-singlepass/src/machine_arm64.rs:4280-4328 | lib/compiler-singlepass/src/machine_arm64.rs:4341-4386 | lib/compiler-singlepass/src/machine_arm64.rs:4399-4444 | lib/compiler-singlepass/src/machine_arm64.rs:4457-4502 | lib/compiler-singlepass/src/machine_arm64.rs:4516-4565 | lib/compiler-singlepass/src/machine_arm64.rs:4579-4628 | lib/compiler-singlepass/src/machine_arm64.rs:4642-4691 | lib/compiler-singlepass/src/machine_arm64.rs:5737-5785 | lib/compiler-singlepass/src/machine_arm64.rs:5798-5846 | lib/compiler-singlepass/src/machine_arm64.rs:5859-5907 | lib/compiler-singlepass/src/machine_arm64.rs:5920-5968 | lib/compiler-singlepass/src/machine_arm64.rs:5981-6029 | lib/compiler-singlepass/src/machine_arm64.rs:6042-6090 | lib/compiler-singlepass/src/machine_arm64.rs:6103-6151 | lib/compiler-singlepass/src/machine_arm64.rs:6164-6212 | lib/compiler-singlepass/src/machine_arm64.rs:6225-6273 | lib/compiler-singlepass/src/machine_arm64.rs:6286-6334 | lib/compiler-singlepass/src/machine_arm64.rs:6347-6395 | lib/compiler-singlepass/src/machine_arm64.rs:6408-6456 | lib/compiler-singlepass/src/machine_arm64.rs:6469-6517 | lib/compiler-singlepass/src/machine_arm64.rs:6530-6578 | lib/compiler-singlepass/src/machine_arm64.rs:6591-6639 | lib/compiler-singlepass/src/machine_arm64.rs:6652-6700 | lib/compiler-singlepass/src/machine_arm64.rs:6713-6761 | lib/compiler-singlepass/src/machine_arm64.rs:6774-6822 | lib/compiler-singlepass/src/machine_arm64.rs:6835-6883 | lib/compiler-singlepass/src/machine_arm64.rs:6896-6944 | lib/compiler-singlepass/src/machine_arm64.rs:6957-7002 | lib/compiler-singlepass/src/machine_arm64.rs:7015-7060 | lib/compiler-singlepass/src/machine_arm64.rs:7073-7118 | lib/compiler-singlepass/src/machine_arm64.rs:7131-7176 | lib/compiler-singlepass/src/machine_arm64.rs:7190-7239 | lib/compiler-singlepass/src/machine_arm64.rs:7253-7302 | lib/compiler-singlepass/src/machine_arm64.rs:7316-7365 | lib/compiler-singlepass/src/machine_arm64.rs:7379-7428 — These 49 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 49 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 49 times.

D4 · Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (16 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_x64.rs:1056 — lib/compiler-singlepass/src/machine_x64.rs:1056-1143 | lib/compiler-singlepass/src/machine_x64.rs:1144-1210 | lib/compiler-singlepass/src/machine_x64.rs:1211-1257 | lib/compiler-singlepass/src/machine_x64.rs:1258-1290 | lib/compiler-singlepass/src/machine_x64.rs:1291-1349 | lib/compiler-singlepass/src/machine_x64.rs:1350-1394 | lib/compiler-singlepass/src/machine_x64.rs:1395-1435 | lib/compiler-singlepass/src/machine_x64.rs:1436-1468 | lib/compiler-singlepass/src/machine_x64.rs:1469-1556 | lib/compiler-singlepass/src/machine_x64.rs:1557-1623 | lib/compiler-singlepass/src/machine_x64.rs:1624-1670 | lib/compiler-singlepass/src/machine_x64.rs:1671-1702 | lib/compiler-singlepass/src/machine_x64.rs:1703-1749 | lib/compiler-singlepass/src/machine_x64.rs:1750-1782 | lib/compiler-singlepass/src/machine_x64.rs:1783-1822 | lib/compiler-singlepass/src/machine_x64.rs:1823-1854 — These 16 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 16 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 16 times.

D4 · Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (13 members, 50+ identical tokens) lib/compiler-singlepass/src/machine_arm64.rs:291 — lib/compiler-singlepass/src/machine_arm64.rs:291-399 | lib/compiler-singlepass/src/machine_arm64.rs:514-546 | lib/compiler-singlepass/src/machine_arm64.rs:552-584 | lib/compiler-singlepass/src/machine_arm64.rs:590-620 | lib/compiler-singlepass/src/machine_arm64.rs:626-656 | lib/compiler-singlepass/src/machine_arm64.rs:662-692 | lib/compiler-singlepass/src/machine_arm64.rs:698-728 | lib/compiler-singlepass/src/machine_arm64.rs:734-764 | lib/compiler-singlepass/src/machine_arm64.rs:765-794 | lib/compiler-singlepass/src/machine_arm64.rs:795-824 | lib/compiler-singlepass/src/machine_arm64.rs:825-852 | lib/compiler-singlepass/src/machine_arm64.rs:853-881 | lib/compiler-singlepass/src/machine_arm64.rs:2065-2146 — These 13 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 13 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 13 times.

D4 · Code Duplication · Duplicated block (62 lines × 2) · ×1

Duplicated block (62 lines × 2) lib/wasix/src/fs/inode_guard.rs:215 — lib/wasix/src/fs/inode_guard.rs:215-276 | lib/wasix/src/fs/inode_guard.rs:314-375 — 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 (45 lines × 2) · ×1

Duplicated block (45 lines × 2) lib/wasix/src/syscalls/wasi/fd_write.rs:416 — lib/wasix/src/syscalls/wasi/fd_write.rs:416-460 | lib/wasix/src/syscalls/wasi/fd_write.rs:475-519 — 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 (44 lines × 2) · ×1

Duplicated block (44 lines × 2) lib/wasix/src/syscalls/wasix/proc_spawn2.rs:53 — lib/wasix/src/syscalls/wasix/proc_spawn2.rs:53-96 | lib/wasix/src/syscalls/wasix/proc_spawn3.rs:44-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1

Duplicated block (38 lines × 2) lib/api/src/backend/sys/entities/function/typed.rs:97 — lib/api/src/backend/sys/entities/function/typed.rs:97-134 | lib/api/src/backend/sys/entities/function/typed.rs:235-272 — 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 (34 lines × 2) · ×1

Duplicated block (34 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:382 — lib/compiler-singlepass/src/machine_riscv.rs:382-415 | lib/compiler-singlepass/src/machine_riscv.rs:657-690 — 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 (33–34 lines × 2) · ×1

Duplicated block (33–34 lines × 2) lib/compiler-singlepass/src/machine_riscv.rs:1432 — lib/compiler-singlepass/src/machine_riscv.rs:1432-1464 | lib/compiler-singlepass/src/machine_riscv.rs:1489-1522 — 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 (33 lines × 2) · ×1

Duplicated block (33 lines × 2) lib/backend-api/src/subscription.rs:26 — lib/backend-api/src/subscription.rs:26-58 | lib/backend-api/src/subscription.rs:80-112 — 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 (32 lines × 4) · ×1

Duplicated block (32 lines × 4) lib/compiler-singlepass/src/codegen.rs:2841 — lib/compiler-singlepass/src/codegen.rs:2841-2872 | lib/compiler-singlepass/src/codegen.rs:2911-2942 | lib/compiler-singlepass/src/codegen.rs:5740-5771 | lib/compiler-singlepass/src/codegen.rs:5822-5853 — 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.

D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1

Duplicated block (32 lines × 2) lib/api/src/utils/polyfill.rs:637 — lib/api/src/utils/polyfill.rs:637-668 | lib/compiler/src/translator/sections.rs:156-187 — before extracting anything, compare `lib/api/src/utils/polyfill.rs` and `lib/compiler/src/translator/sections.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 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 (28–29 lines × 2) · ×1

Duplicated block (28–29 lines × 2) lib/compiler-cranelift/src/func_environ.rs:1207 — lib/compiler-cranelift/src/func_environ.rs:1207-1234 | lib/compiler-cranelift/src/func_environ.rs:1277-1305 — 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 (17–29 lines × 2) · ×1

Duplicated block (17–29 lines × 2) lib/compiler-llvm/src/translator/intrinsics.rs:1505 — lib/compiler-llvm/src/translator/intrinsics.rs:1505-1533 | lib/compiler-llvm/src/translator/trampoline.rs:504-520 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1

Duplicated block (27–28 lines × 2) lib/api/src/backend/sys/entities/function/typed.rs:68 — lib/api/src/backend/sys/entities/function/typed.rs:68-94 | lib/api/src/backend/sys/entities/function/typed.rs:205-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1

Duplicated block (28 lines × 2) lib/wasix/src/runtime/resolver/backend_source.rs:84 — lib/wasix/src/runtime/resolver/backend_source.rs:84-111 | lib/wasix/src/runtime/resolver/backend_source.rs:146-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (26 lines × 4) · ×1

Duplicated block (26 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:6526 — lib/compiler-singlepass/src/machine_x64.rs:6526-6551 | lib/compiler-singlepass/src/machine_x64.rs:6580-6605 | lib/compiler-singlepass/src/machine_x64.rs:6640-6665 | lib/compiler-singlepass/src/machine_x64.rs:6700-6725 — 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.

D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1

Duplicated block (26 lines × 3) lib/compiler-singlepass/src/machine_x64.rs:4357 — lib/compiler-singlepass/src/machine_x64.rs:4357-4382 | lib/compiler-singlepass/src/machine_x64.rs:4411-4436 | lib/compiler-singlepass/src/machine_x64.rs:4471-4496 — 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 (24–25 lines × 3) · ×1

Duplicated block (24–25 lines × 3) lib/cli/src/commands/app/logs.rs:140 — lib/cli/src/commands/app/logs.rs:140-163 | lib/cli/src/commands/app/logs.rs:175-198 | lib/cli/src/commands/app/logs.rs:209-233 — 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 (23–25 lines × 2) · ×1

Duplicated block (23–25 lines × 2) lib/sys-utils/src/memory/fd_memory/memories.rs:250 — lib/sys-utils/src/memory/fd_memory/memories.rs:250-274 | lib/vm/src/memory.rs:305-327 — before extracting anything, compare `lib/sys-utils/src/memory/fd_memory/memories.rs` and `lib/vm/src/memory.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 156 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 (24 lines × 3) · ×1

Duplicated block (24 lines × 3) lib/cli/src/commands/app/secrets/create.rs:173 — lib/cli/src/commands/app/secrets/create.rs:173-196 | lib/cli/src/commands/app/secrets/import.rs:168-191 | lib/cli/src/commands/app/secrets/update.rs:167-190 — before extracting anything, compare `lib/cli/src/commands/app/secrets/create.rs` and `lib/cli/src/commands/app/secrets/update.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1

Duplicated block (23 lines × 3) lib/backend-api/src/query.rs:281 — lib/backend-api/src/query.rs:281-303 | lib/backend-api/src/query.rs:657-679 | lib/backend-api/src/query.rs:713-735 — 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 (12–23 lines × 2) · ×1

Duplicated block (12–23 lines × 2) lib/compiler-llvm/src/translator/intrinsics.rs:1520 — lib/compiler-llvm/src/translator/intrinsics.rs:1520-1542 | lib/compiler-llvm/src/translator/intrinsics.rs:1625-1636 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1

Duplicated block (22–23 lines × 2) lib/wasix/src/syscalls/wasix/fd_pipe.rs:101 — lib/wasix/src/syscalls/wasix/fd_pipe.rs:101-123 | lib/wasix/src/syscalls/wasix/sock_pair.rs:122-143 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (20–22 lines × 2) · ×1

Duplicated block (20–22 lines × 2) lib/compiler-cranelift/src/elf.rs:233 — lib/compiler-cranelift/src/elf.rs:233-254 | lib/compiler-singlepass/src/elf.rs:39-58 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler-singlepass/src/elf.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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–22 lines × 2) · ×1

Duplicated block (17–22 lines × 2) lib/compiler-cranelift/src/translator/code_translator.rs:396 — lib/compiler-cranelift/src/translator/code_translator.rs:396-417 | lib/compiler-cranelift/src/translator/code_translator.rs:2689-2705 — 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 (18–22 lines × 2) · ×1

Duplicated block (18–22 lines × 2) lib/wasix/src/net/socket.rs:451 — lib/wasix/src/net/socket.rs:451-472 | lib/wasix/src/net/socket.rs:485-502 — 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 (20–21 lines × 5) · ×1

Duplicated block (20–21 lines × 5) lib/compiler-llvm/src/translator/intrinsics.rs:2032 — lib/compiler-llvm/src/translator/intrinsics.rs:2032-2051 | lib/compiler-llvm/src/translator/intrinsics.rs:2078-2097 | lib/compiler-llvm/src/translator/intrinsics.rs:2123-2143 | lib/compiler-llvm/src/translator/intrinsics.rs:2170-2189 | lib/compiler-llvm/src/translator/intrinsics.rs:2215-2235 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (20 lines × 4) · ×1

Duplicated block (20 lines × 4) lib/compiler-singlepass/src/codegen.rs:2958 — lib/compiler-singlepass/src/codegen.rs:2958-2977 | lib/compiler-singlepass/src/codegen.rs:5896-5915 | lib/compiler-singlepass/src/codegen.rs:5946-5965 | lib/compiler-singlepass/src/codegen.rs:5995-6014 — 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.

D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1

Duplicated block (20 lines × 3) lib/compiler-llvm/src/translator/code.rs:4535 — lib/compiler-llvm/src/translator/code.rs:4535-4554 | lib/compiler-llvm/src/translator/code.rs:4587-4606 | lib/compiler-llvm/src/translator/code.rs:4633-4652 — 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 (17–20 lines × 2) · ×1

Duplicated block (17–20 lines × 2) lib/cli/src/commands/run/capabilities/mod.rs:44 — lib/cli/src/commands/run/capabilities/mod.rs:44-63 | lib/cli/src/commands/run/capabilities/mod.rs:68-84 — 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 (18–19 lines × 3) · ×1

Duplicated block (18–19 lines × 3) lib/api/src/backend/sys/entities/function/mod.rs:516 — lib/api/src/backend/sys/entities/function/mod.rs:516-534 | lib/api/src/backend/sys/entities/function/typed.rs:60-77 | lib/api/src/backend/sys/entities/function/typed.rs:197-214 — before extracting anything, compare `lib/api/src/backend/sys/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/typed.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1

Duplicated block (18–19 lines × 2) lib/virtual-net/src/client.rs:301 — lib/virtual-net/src/client.rs:301-318 | lib/virtual-net/src/server.rs:359-377 — before extracting anything, compare `lib/virtual-net/src/client.rs` and `lib/virtual-net/src/server.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17 lines × 8) · ×1

Duplicated block (17 lines × 8) lib/compiler-singlepass/src/machine_x64.rs:7323 — lib/compiler-singlepass/src/machine_x64.rs:7323-7339 | lib/compiler-singlepass/src/machine_x64.rs:7343-7359 | lib/compiler-singlepass/src/machine_x64.rs:7443-7459 | lib/compiler-singlepass/src/machine_x64.rs:7463-7479 | lib/compiler-singlepass/src/machine_x64.rs:7725-7741 | lib/compiler-singlepass/src/machine_x64.rs:7745-7761 | lib/compiler-singlepass/src/machine_x64.rs:7845-7861 | lib/compiler-singlepass/src/machine_x64.rs:7865-7881 — all 8 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 (17 lines × 4) · ×1

Duplicated block (17 lines × 4) lib/compiler-singlepass/src/codegen.rs:2968 — lib/compiler-singlepass/src/codegen.rs:2968-2984 | lib/compiler-singlepass/src/codegen.rs:5786-5802 | lib/compiler-singlepass/src/codegen.rs:5906-5922 | lib/compiler-singlepass/src/codegen.rs:5956-5972 — 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.

D4 · Code Duplication · Duplicated block (8–17 lines × 3) · ×1

Duplicated block (8–17 lines × 3) lib/virtual-fs/src/mem_fs/filesystem.rs:260 — lib/virtual-fs/src/mem_fs/filesystem.rs:260-267 | lib/virtual-fs/src/mem_fs/filesystem.rs:393-409 | lib/virtual-fs/src/mem_fs/filesystem.rs:706-721 — 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 (10–17 lines × 2) · ×1

Duplicated block (10–17 lines × 2) lib/wasix/src/syscalls/wasix/proc_exec4.rs:102 — lib/wasix/src/syscalls/wasix/proc_exec4.rs:102-111 | lib/wasix/src/syscalls/wasix/proc_spawn3.rs:118-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1

Duplicated block (16 lines × 3) lib/backend-api/src/query.rs:2411 — lib/backend-api/src/query.rs:2411-2426 | lib/backend-api/src/query.rs:2458-2473 | lib/backend-api/src/query.rs:2505-2520 — 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 (15–16 lines × 3) · ×1

Duplicated block (15–16 lines × 3) lib/compiler-singlepass/src/machine_riscv.rs:482 — lib/compiler-singlepass/src/machine_riscv.rs:482-497 | lib/compiler-singlepass/src/machine_riscv.rs:505-519 | lib/compiler-singlepass/src/machine_riscv.rs:543-557 — 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 (14–16 lines × 2) · ×1

Duplicated block (14–16 lines × 2) lib/compiler-llvm/src/translator/code.rs:1205 — lib/compiler-llvm/src/translator/code.rs:1205-1218 | lib/compiler-llvm/src/translator/code.rs:1264-1279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1

Duplicated block (13–16 lines × 2) lib/virtual-fs/src/mem_fs/file.rs:1732 — lib/virtual-fs/src/mem_fs/file.rs:1732-1747 | lib/virtual-fs/src/mem_fs/file.rs:1833-1845 — 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 (12–15 lines × 5) · ×1

Duplicated block (12–15 lines × 5) lib/compiler-singlepass/src/machine_x64.rs:977 — lib/compiler-singlepass/src/machine_x64.rs:977-988 | lib/compiler-singlepass/src/machine_x64.rs:7311-7325 | lib/compiler-singlepass/src/machine_x64.rs:7431-7445 | lib/compiler-singlepass/src/machine_x64.rs:7713-7727 | lib/compiler-singlepass/src/machine_x64.rs:7833-7847 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1

Duplicated block (15 lines × 4) lib/compiler-llvm/src/translator/code.rs:6800 — lib/compiler-llvm/src/translator/code.rs:6800-6814 | lib/compiler-llvm/src/translator/code.rs:6862-6876 | lib/compiler-llvm/src/translator/code.rs:6970-6984 | lib/compiler-llvm/src/translator/code.rs:7033-7047 — 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.

D4 · Code Duplication · Duplicated block (10–15 lines × 3) · ×1

Duplicated block (10–15 lines × 3) lib/virtual-fs/src/overlay_fs.rs:365 — lib/virtual-fs/src/overlay_fs.rs:365-379 | lib/virtual-fs/src/overlay_fs.rs:392-401 | lib/virtual-fs/src/overlay_fs.rs:408-417 — 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 (7–15 lines × 2) · ×1

Duplicated block (7–15 lines × 2) lib/compiler-singlepass/src/machine_x64.rs:7181 — lib/compiler-singlepass/src/machine_x64.rs:7181-7187 | lib/compiler-singlepass/src/machine_x64.rs:7200-7214 — 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 (12–14 lines × 8) · ×1

Duplicated block (12–14 lines × 8) lib/compiler-llvm/src/translator/code.rs:6201 — lib/compiler-llvm/src/translator/code.rs:6201-6214 | lib/compiler-llvm/src/translator/code.rs:6227-6240 | lib/compiler-llvm/src/translator/code.rs:6295-6308 | lib/compiler-llvm/src/translator/code.rs:6321-6334 | lib/compiler-llvm/src/translator/code.rs:6389-6402 | lib/compiler-llvm/src/translator/code.rs:6496-6509 | lib/compiler-llvm/src/translator/code.rs:6639-6650 | lib/compiler-llvm/src/translator/code.rs:6662-6673 — all 8 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 (14 lines × 5) · ×1

Duplicated block (14 lines × 5) lib/compiler-singlepass/src/codegen.rs:2967 — lib/compiler-singlepass/src/codegen.rs:2967-2980 | lib/compiler-singlepass/src/codegen.rs:5785-5798 | lib/compiler-singlepass/src/codegen.rs:5905-5918 | lib/compiler-singlepass/src/codegen.rs:5955-5968 | lib/compiler-singlepass/src/codegen.rs:6004-6017 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1

Duplicated block (14 lines × 4) lib/compiler-llvm/src/translator/code.rs:6424 — lib/compiler-llvm/src/translator/code.rs:6424-6437 | lib/compiler-llvm/src/translator/code.rs:6470-6483 | lib/compiler-llvm/src/translator/code.rs:6531-6544 | lib/compiler-llvm/src/translator/code.rs:6577-6590 — 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.

D4 · Code Duplication · Duplicated block (8–14 lines × 3) · ×1

Duplicated block (8–14 lines × 3) lib/compiler-cranelift/src/func_environ.rs:2194 — lib/compiler-cranelift/src/func_environ.rs:2194-2201 | lib/compiler-cranelift/src/func_environ.rs:2253-2266 | lib/compiler-cranelift/src/func_environ.rs:2287-2294 — 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 (13–14 lines × 3) · ×1

Duplicated block (13–14 lines × 3) lib/compiler-llvm/src/translator/code.rs:4664 — lib/compiler-llvm/src/translator/code.rs:4664-4676 | lib/compiler-llvm/src/translator/code.rs:4765-4778 | lib/compiler-llvm/src/translator/code.rs:4884-4897 — 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 (11–14 lines × 2) · ×1

Duplicated block (11–14 lines × 2) lib/api/src/backend/v8/entities/function/mod.rs:200 — lib/api/src/backend/v8/entities/function/mod.rs:200-210 | lib/api/src/backend/v8/entities/function/mod.rs:277-290 — 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 (10–14 lines × 2) · ×1

Duplicated block (10–14 lines × 2) lib/cli/src/commands/app/deploy.rs:340 — lib/cli/src/commands/app/deploy.rs:340-349 | lib/cli/src/commands/app/deploy.rs:1004-1017 — 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 (12–14 lines × 2) · ×1

Duplicated block (12–14 lines × 2) lib/compiler-cranelift/src/elf.rs:265 — lib/compiler-cranelift/src/elf.rs:265-278 | lib/compiler-singlepass/src/elf.rs:62-73 — before extracting anything, compare `lib/compiler-cranelift/src/elf.rs` and `lib/compiler-singlepass/src/elf.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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 (13–14 lines × 2) · ×1

Duplicated block (13–14 lines × 2) lib/wasix/src/syscalls/unix/mod.rs:16 — lib/wasix/src/syscalls/unix/mod.rs:16-28 | lib/wasix/src/syscalls/unix/mod.rs:40-53 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13 lines × 49) · ×1

Duplicated block (13 lines × 49) lib/compiler-singlepass/src/machine_arm64.rs:3427 — lib/compiler-singlepass/src/machine_arm64.rs:3427-3439 | lib/compiler-singlepass/src/machine_arm64.rs:3488-3500 | lib/compiler-singlepass/src/machine_arm64.rs:3549-3561 | lib/compiler-singlepass/src/machine_arm64.rs:3610-3622 | lib/compiler-singlepass/src/machine_arm64.rs:3671-3683 | lib/compiler-singlepass/src/machine_arm64.rs:3732-3744 | lib/compiler-singlepass/src/machine_arm64.rs:3793-3805 | lib/compiler-singlepass/src/machine_arm64.rs:3854-3866 | lib/compiler-singlepass/src/machine_arm64.rs:3915-3927 | lib/compiler-singlepass/src/machine_arm64.rs:3976-3988 | lib/compiler-singlepass/src/machine_arm64.rs:4037-4049 | lib/compiler-singlepass/src/machine_arm64.rs:4098-4110 | lib/compiler-singlepass/src/machine_arm64.rs:4159-4171 | lib/compiler-singlepass/src/machine_arm64.rs:4220-4232 | lib/compiler-singlepass/src/machine_arm64.rs:4281-4293 | lib/compiler-singlepass/src/machine_arm64.rs:4342-4354 | lib/compiler-singlepass/src/machine_arm64.rs:4400-4412 | lib/compiler-singlepass/src/machine_arm64.rs:4458-4470 | lib/compiler-singlepass/src/machine_arm64.rs:4517-4529 | lib/compiler-singlepass/src/machine_arm64.rs:4580-4592 | lib/compiler-singlepass/src/machine_arm64.rs:4643-4655 | lib/compiler-singlepass/src/machine_arm64.rs:5738-5750 | lib/compiler-singlepass/src/machine_arm64.rs:5799-5811 | lib/compiler-singlepass/src/machine_arm64.rs:5860-5872 | lib/compiler-singlepass/src/machine_arm64.rs:5921-5933 | lib/compiler-singlepass/src/machine_arm64.rs:5982-5994 | lib/compiler-singlepass/src/machine_arm64.rs:6043-6055 | lib/compiler-singlepass/src/machine_arm64.rs:6104-6116 | lib/compiler-singlepass/src/machine_arm64.rs:6165-6177 | lib/compiler-singlepass/src/machine_arm64.rs:6226-6238 | lib/compiler-singlepass/src/machine_arm64.rs:6287-6299 | lib/compiler-singlepass/src/machine_arm64.rs:6348-6360 | lib/compiler-singlepass/src/machine_arm64.rs:6409-6421 | lib/compiler-singlepass/src/machine_arm64.rs:6470-6482 | lib/compiler-singlepass/src/machine_arm64.rs:6531-6543 | lib/compiler-singlepass/src/machine_arm64.rs:6592-6604 | lib/compiler-singlepass/src/machine_arm64.rs:6653-6665 | lib/compiler-singlepass/src/machine_arm64.rs:6714-6726 | lib/compiler-singlepass/src/machine_arm64.rs:6775-6787 | lib/compiler-singlepass/src/machine_arm64.rs:6836-6848 | lib/compiler-singlepass/src/machine_arm64.rs:6897-6909 | lib/compiler-singlepass/src/machine_arm64.rs:6958-6970 | lib/compiler-singlepass/src/machine_arm64.rs:7016-7028 | lib/compiler-singlepass/src/machine_arm64.rs:7074-7086 | lib/compiler-singlepass/src/machine_arm64.rs:7132-7144 | lib/compiler-singlepass/src/machine_arm64.rs:7191-7203 | lib/compiler-singlepass/src/machine_arm64.rs:7254-7266 | lib/compiler-singlepass/src/machine_arm64.rs:7317-7329 | lib/compiler-singlepass/src/machine_arm64.rs:7380-7392 — all 49 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 (13 lines × 12) · ×1

Duplicated block (13 lines × 12) lib/compiler-llvm/src/translator/code.rs:6200 — lib/compiler-llvm/src/translator/code.rs:6200-6212 | lib/compiler-llvm/src/translator/code.rs:6226-6238 | lib/compiler-llvm/src/translator/code.rs:6294-6306 | lib/compiler-llvm/src/translator/code.rs:6320-6332 | lib/compiler-llvm/src/translator/code.rs:6388-6400 | lib/compiler-llvm/src/translator/code.rs:6423-6435 | lib/compiler-llvm/src/translator/code.rs:6469-6481 | lib/compiler-llvm/src/translator/code.rs:6495-6507 | lib/compiler-llvm/src/translator/code.rs:6530-6542 | lib/compiler-llvm/src/translator/code.rs:6576-6588 | lib/compiler-llvm/src/translator/code.rs:6638-6650 | lib/compiler-llvm/src/translator/code.rs:6661-6673 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (13 lines × 5) · ×1

Duplicated block (13 lines × 5) lib/backend-api/src/query.rs:281 — lib/backend-api/src/query.rs:281-293 | lib/backend-api/src/query.rs:657-669 | lib/backend-api/src/query.rs:713-725 | lib/backend-api/src/query.rs:1529-1541 | lib/backend-api/src/query.rs:1594-1606 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (4–13 lines × 3) · ×1

Duplicated block (4–13 lines × 3) lib/compiler-llvm/src/translator/code.rs:4711 — lib/compiler-llvm/src/translator/code.rs:4711-4714 | lib/compiler-llvm/src/translator/code.rs:4806-4818 | lib/compiler-llvm/src/translator/code.rs:4925-4937 — 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 (12 lines × 20) · ×1

Duplicated block (12 lines × 20) lib/compiler-singlepass/src/machine_arm64.rs:5774 — lib/compiler-singlepass/src/machine_arm64.rs:5774-5785 | lib/compiler-singlepass/src/machine_arm64.rs:5835-5846 | lib/compiler-singlepass/src/machine_arm64.rs:5896-5907 | lib/compiler-singlepass/src/machine_arm64.rs:5957-5968 | lib/compiler-singlepass/src/machine_arm64.rs:6018-6029 | lib/compiler-singlepass/src/machine_arm64.rs:6079-6090 | lib/compiler-singlepass/src/machine_arm64.rs:6140-6151 | lib/compiler-singlepass/src/machine_arm64.rs:6201-6212 | lib/compiler-singlepass/src/machine_arm64.rs:6262-6273 | lib/compiler-singlepass/src/machine_arm64.rs:6323-6334 | lib/compiler-singlepass/src/machine_arm64.rs:6384-6395 | lib/compiler-singlepass/src/machine_arm64.rs:6445-6456 | lib/compiler-singlepass/src/machine_arm64.rs:6506-6517 | lib/compiler-singlepass/src/machine_arm64.rs:6567-6578 | lib/compiler-singlepass/src/machine_arm64.rs:6628-6639 | lib/compiler-singlepass/src/machine_arm64.rs:6689-6700 | lib/compiler-singlepass/src/machine_arm64.rs:6750-6761 | lib/compiler-singlepass/src/machine_arm64.rs:6811-6822 | lib/compiler-singlepass/src/machine_arm64.rs:6872-6883 | lib/compiler-singlepass/src/machine_arm64.rs:6933-6944 — all 20 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (12 lines × 15) · ×1

Duplicated block (12 lines × 15) lib/compiler-singlepass/src/machine_arm64.rs:3463 — lib/compiler-singlepass/src/machine_arm64.rs:3463-3474 | lib/compiler-singlepass/src/machine_arm64.rs:3524-3535 | lib/compiler-singlepass/src/machine_arm64.rs:3585-3596 | lib/compiler-singlepass/src/machine_arm64.rs:3646-3657 | lib/compiler-singlepass/src/machine_arm64.rs:3707-3718 | lib/compiler-singlepass/src/machine_arm64.rs:3768-3779 | lib/compiler-singlepass/src/machine_arm64.rs:3829-3840 | lib/compiler-singlepass/src/machine_arm64.rs:3890-3901 | lib/compiler-singlepass/src/machine_arm64.rs:3951-3962 | lib/compiler-singlepass/src/machine_arm64.rs:4012-4023 | lib/compiler-singlepass/src/machine_arm64.rs:4073-4084 | lib/compiler-singlepass/src/machine_arm64.rs:4134-4145 | lib/compiler-singlepass/src/machine_arm64.rs:4195-4206 | lib/compiler-singlepass/src/machine_arm64.rs:4256-4267 | lib/compiler-singlepass/src/machine_arm64.rs:4317-4328 — all 15 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (12 lines × 8) · ×1

Duplicated block (12 lines × 8) lib/compiler-llvm/src/translator/code.rs:7084 — lib/compiler-llvm/src/translator/code.rs:7084-7095 | lib/compiler-llvm/src/translator/code.rs:7113-7124 | lib/compiler-llvm/src/translator/code.rs:7142-7153 | lib/compiler-llvm/src/translator/code.rs:7171-7182 | lib/compiler-llvm/src/translator/code.rs:7199-7210 | lib/compiler-llvm/src/translator/code.rs:7227-7238 | lib/compiler-llvm/src/translator/code.rs:7256-7267 | lib/compiler-llvm/src/translator/code.rs:7285-7296 — all 8 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 (12 lines × 7) · ×1

Duplicated block (12 lines × 7) lib/compiler-singlepass/src/machine_x64.rs:4355 — lib/compiler-singlepass/src/machine_x64.rs:4355-4366 | lib/compiler-singlepass/src/machine_x64.rs:4409-4420 | lib/compiler-singlepass/src/machine_x64.rs:4469-4480 | lib/compiler-singlepass/src/machine_x64.rs:6524-6535 | lib/compiler-singlepass/src/machine_x64.rs:6578-6589 | lib/compiler-singlepass/src/machine_x64.rs:6638-6649 | lib/compiler-singlepass/src/machine_x64.rs:6698-6709 — all 7 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 (12 lines × 6) · ×1

Duplicated block (12 lines × 6) lib/compiler-llvm/src/translator/code.rs:6156 — lib/compiler-llvm/src/translator/code.rs:6156-6167 | lib/compiler-llvm/src/translator/code.rs:6177-6188 | lib/compiler-llvm/src/translator/code.rs:6250-6261 | lib/compiler-llvm/src/translator/code.rs:6271-6282 | lib/compiler-llvm/src/translator/code.rs:6344-6355 | lib/compiler-llvm/src/translator/code.rs:6365-6376 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (11–12 lines × 6) · ×1

Duplicated block (11–12 lines × 6) lib/virtual-fs/src/mem_fs/file.rs:432 — lib/virtual-fs/src/mem_fs/file.rs:432-443 | lib/virtual-fs/src/mem_fs/file.rs:479-490 | lib/virtual-fs/src/mem_fs/file.rs:1037-1048 | lib/virtual-fs/src/mem_fs/file.rs:1201-1211 | lib/virtual-fs/src/mem_fs/file.rs:1241-1252 | lib/virtual-fs/src/mem_fs/file.rs:1278-1289 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (8–12 lines × 4) · ×1

Duplicated block (8–12 lines × 4) lib/virtual-fs/src/mem_fs/filesystem.rs:262 — lib/virtual-fs/src/mem_fs/filesystem.rs:262-269 | lib/virtual-fs/src/mem_fs/filesystem.rs:400-411 | lib/virtual-fs/src/mem_fs/filesystem.rs:476-487 | lib/virtual-fs/src/mem_fs/filesystem.rs:712-723 — 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.

D4 · Code Duplication · Duplicated block (8–12 lines × 3) · ×1

Duplicated block (8–12 lines × 3) lib/compiler-singlepass/src/machine_arm64.rs:1229 — lib/compiler-singlepass/src/machine_arm64.rs:1229-1237 | lib/compiler-singlepass/src/machine_riscv.rs:363-370 | lib/compiler-singlepass/src/machine_riscv.rs:633-644 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_riscv.rs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1

Duplicated block (11–12 lines × 2) lib/cli/src/commands/app/deploy.rs:942 — lib/cli/src/commands/app/deploy.rs:942-953 | lib/cli/src/commands/app/deploy.rs:955-965 — 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 (11 lines × 39) · ×1

Duplicated block (11 lines × 39) lib/compiler-singlepass/src/codegen.rs:3280 — lib/compiler-singlepass/src/codegen.rs:3280-3290 | lib/compiler-singlepass/src/codegen.rs:3330-3340 | lib/compiler-singlepass/src/codegen.rs:3355-3365 | lib/compiler-singlepass/src/codegen.rs:3380-3390 | lib/compiler-singlepass/src/codegen.rs:3405-3415 | lib/compiler-singlepass/src/codegen.rs:3430-3440 | lib/compiler-singlepass/src/codegen.rs:3455-3465 | lib/compiler-singlepass/src/codegen.rs:3983-3993 | lib/compiler-singlepass/src/codegen.rs:4008-4018 | lib/compiler-singlepass/src/codegen.rs:4033-4043 | lib/compiler-singlepass/src/codegen.rs:4058-4068 | lib/compiler-singlepass/src/codegen.rs:4207-4217 | lib/compiler-singlepass/src/codegen.rs:4288-4298 | lib/compiler-singlepass/src/codegen.rs:4315-4325 | lib/compiler-singlepass/src/codegen.rs:4342-4352 | lib/compiler-singlepass/src/codegen.rs:4396-4406 | lib/compiler-singlepass/src/codegen.rs:4477-4487 | lib/compiler-singlepass/src/codegen.rs:4504-4514 | lib/compiler-singlepass/src/codegen.rs:4531-4541 | lib/compiler-singlepass/src/codegen.rs:4585-4595 | lib/compiler-singlepass/src/codegen.rs:4666-4676 | lib/compiler-singlepass/src/codegen.rs:4693-4703 | lib/compiler-singlepass/src/codegen.rs:4720-4730 | lib/compiler-singlepass/src/codegen.rs:4774-4784 | lib/compiler-singlepass/src/codegen.rs:4855-4865 | lib/compiler-singlepass/src/codegen.rs:4882-4892 | lib/compiler-singlepass/src/codegen.rs:4909-4919 | lib/compiler-singlepass/src/codegen.rs:4963-4973 | lib/compiler-singlepass/src/codegen.rs:5044-5054 | lib/compiler-singlepass/src/codegen.rs:5071-5081 | lib/compiler-singlepass/src/codegen.rs:5098-5108 | lib/compiler-singlepass/src/codegen.rs:5152-5162 | lib/compiler-singlepass/src/codegen.rs:5233-5243 | lib/compiler-singlepass/src/codegen.rs:5260-5270 | lib/compiler-singlepass/src/codegen.rs:5287-5297 | lib/compiler-singlepass/src/codegen.rs:5344-5354 | lib/compiler-singlepass/src/codegen.rs:5431-5441 | lib/compiler-singlepass/src/codegen.rs:5460-5470 | lib/compiler-singlepass/src/codegen.rs:5489-5499 — all 39 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 (11 lines × 29) · ×1

Duplicated block (11 lines × 29) lib/compiler-singlepass/src/codegen.rs:3032 — lib/compiler-singlepass/src/codegen.rs:3032-3042 | lib/compiler-singlepass/src/codegen.rs:3082-3092 | lib/compiler-singlepass/src/codegen.rs:3107-3117 | lib/compiler-singlepass/src/codegen.rs:3132-3142 | lib/compiler-singlepass/src/codegen.rs:3157-3167 | lib/compiler-singlepass/src/codegen.rs:3836-3846 | lib/compiler-singlepass/src/codegen.rs:3861-3871 | lib/compiler-singlepass/src/codegen.rs:3886-3896 | lib/compiler-singlepass/src/codegen.rs:4180-4190 | lib/compiler-singlepass/src/codegen.rs:4234-4244 | lib/compiler-singlepass/src/codegen.rs:4261-4271 | lib/compiler-singlepass/src/codegen.rs:4369-4379 | lib/compiler-singlepass/src/codegen.rs:4423-4433 | lib/compiler-singlepass/src/codegen.rs:4450-4460 | lib/compiler-singlepass/src/codegen.rs:4558-4568 | lib/compiler-singlepass/src/codegen.rs:4612-4622 | lib/compiler-singlepass/src/codegen.rs:4639-4649 | lib/compiler-singlepass/src/codegen.rs:4747-4757 | lib/compiler-singlepass/src/codegen.rs:4801-4811 | lib/compiler-singlepass/src/codegen.rs:4828-4838 | lib/compiler-singlepass/src/codegen.rs:4936-4946 | lib/compiler-singlepass/src/codegen.rs:4990-5000 | lib/compiler-singlepass/src/codegen.rs:5017-5027 | lib/compiler-singlepass/src/codegen.rs:5125-5135 | lib/compiler-singlepass/src/codegen.rs:5179-5189 | lib/compiler-singlepass/src/codegen.rs:5206-5216 | lib/compiler-singlepass/src/codegen.rs:5315-5325 | lib/compiler-singlepass/src/codegen.rs:5373-5383 | lib/compiler-singlepass/src/codegen.rs:5402-5412 — all 29 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 (10–11 lines × 8) · ×1

Duplicated block (10–11 lines × 8) lib/compiler-llvm/src/translator/code.rs:4141 — lib/compiler-llvm/src/translator/code.rs:4141-4150 | lib/compiler-llvm/src/translator/code.rs:4153-4162 | lib/compiler-llvm/src/translator/code.rs:4941-4950 | lib/compiler-llvm/src/translator/code.rs:4957-4966 | lib/compiler-llvm/src/translator/code.rs:8723-8733 | lib/compiler-llvm/src/translator/code.rs:8747-8757 | lib/compiler-llvm/src/translator/code.rs:8771-8781 | lib/compiler-llvm/src/translator/code.rs:8795-8805 — all 8 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 (11 lines × 5) · ×1

Duplicated block (11 lines × 5) lib/compiler-llvm/src/translator/code.rs:8916 — lib/compiler-llvm/src/translator/code.rs:8916-8926 | lib/compiler-llvm/src/translator/code.rs:8990-9000 | lib/compiler-llvm/src/translator/code.rs:9057-9067 | lib/compiler-llvm/src/translator/code.rs:9123-9133 | lib/compiler-llvm/src/translator/code.rs:9292-9302 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7–11 lines × 4) · ×1

Duplicated block (7–11 lines × 4) lib/api/src/backend/sys/entities/function/mod.rs:549 — lib/api/src/backend/sys/entities/function/mod.rs:549-559 | lib/api/src/backend/sys/entities/function/typed.rs:90-96 | lib/api/src/backend/sys/entities/function/typed.rs:227-234 | lib/api/src/backend/v8/entities/function/mod.rs:403-411 — before extracting anything, compare `lib/api/src/backend/sys/entities/function/mod.rs` and `lib/api/src/backend/sys/entities/function/typed.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5–11 lines × 3) · ×1

Duplicated block (5–11 lines × 3) lib/compiler-llvm/src/translator/intrinsics.rs:1519 — lib/compiler-llvm/src/translator/intrinsics.rs:1519-1529 | lib/compiler-llvm/src/translator/intrinsics.rs:1816-1825 | lib/compiler-llvm/src/translator/trampoline.rs:514-518 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.

D4 · Code Duplication · Duplicated block (10 lines × 19) · ×1

Duplicated block (10 lines × 19) lib/compiler-llvm/src/translator/code.rs:7502 — lib/compiler-llvm/src/translator/code.rs:7502-7511 | lib/compiler-llvm/src/translator/code.rs:7577-7586 | lib/compiler-llvm/src/translator/code.rs:7663-7673 | lib/compiler-llvm/src/translator/code.rs:7750-7760 | lib/compiler-llvm/src/translator/code.rs:7822-7832 | lib/compiler-llvm/src/translator/code.rs:7912-7922 | lib/compiler-llvm/src/translator/code.rs:7984-7994 | lib/compiler-llvm/src/translator/code.rs:8074-8084 | lib/compiler-llvm/src/translator/code.rs:8143-8153 | lib/compiler-llvm/src/translator/code.rs:8233-8243 | lib/compiler-llvm/src/translator/code.rs:8279-8289 | lib/compiler-llvm/src/translator/code.rs:8331-8341 | lib/compiler-llvm/src/translator/code.rs:8383-8393 | lib/compiler-llvm/src/translator/code.rs:8435-8445 | lib/compiler-llvm/src/translator/code.rs:8487-8497 | lib/compiler-llvm/src/translator/code.rs:8539-8549 | lib/compiler-llvm/src/translator/code.rs:8733-8742 | lib/compiler-llvm/src/translator/code.rs:8757-8766 | lib/compiler-llvm/src/translator/code.rs:10631-10640 — all 19 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (10 lines × 14) · ×1

Duplicated block (10 lines × 14) lib/compiler-singlepass/src/codegen.rs:3182 — lib/compiler-singlepass/src/codegen.rs:3182-3191 | lib/compiler-singlepass/src/codegen.rs:3232-3241 | lib/compiler-singlepass/src/codegen.rs:3256-3265 | lib/compiler-singlepass/src/codegen.rs:3480-3490 | lib/compiler-singlepass/src/codegen.rs:3531-3540 | lib/compiler-singlepass/src/codegen.rs:3555-3564 | lib/compiler-singlepass/src/codegen.rs:3579-3588 | lib/compiler-singlepass/src/codegen.rs:3911-3920 | lib/compiler-singlepass/src/codegen.rs:3935-3944 | lib/compiler-singlepass/src/codegen.rs:3959-3968 | lib/compiler-singlepass/src/codegen.rs:4083-4092 | lib/compiler-singlepass/src/codegen.rs:4107-4116 | lib/compiler-singlepass/src/codegen.rs:4131-4140 | lib/compiler-singlepass/src/codegen.rs:4155-4164 — all 14 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 (10 lines × 11) · ×1

Duplicated block (10 lines × 11) lib/compiler-llvm/src/translator/code.rs:4191 — lib/compiler-llvm/src/translator/code.rs:4191-4200 | lib/compiler-llvm/src/translator/code.rs:4209-4218 | lib/compiler-llvm/src/translator/code.rs:4227-4236 | lib/compiler-llvm/src/translator/code.rs:4245-4254 | lib/compiler-llvm/src/translator/code.rs:4315-4324 | lib/compiler-llvm/src/translator/code.rs:4333-4342 | lib/compiler-llvm/src/translator/code.rs:4351-4360 | lib/compiler-llvm/src/translator/code.rs:4369-4378 | lib/compiler-llvm/src/translator/code.rs:4428-4437 | lib/compiler-llvm/src/translator/code.rs:5119-5128 | lib/compiler-llvm/src/translator/code.rs:10483-10492 — all 11 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 (10 lines × 9) · ×1

Duplicated block (10 lines × 9) lib/compiler-llvm/src/translator/code.rs:4678 — lib/compiler-llvm/src/translator/code.rs:4678-4687 | lib/compiler-llvm/src/translator/code.rs:4689-4698 | lib/compiler-llvm/src/translator/code.rs:4700-4709 | lib/compiler-llvm/src/translator/code.rs:4780-4789 | lib/compiler-llvm/src/translator/code.rs:4791-4801 | lib/compiler-llvm/src/translator/code.rs:4803-4812 | lib/compiler-llvm/src/translator/code.rs:4899-4908 | lib/compiler-llvm/src/translator/code.rs:4910-4920 | lib/compiler-llvm/src/translator/code.rs:4922-4931 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1

Duplicated block (10 lines × 6) lib/compiler-llvm/src/translator/code.rs:8915 — lib/compiler-llvm/src/translator/code.rs:8915-8924 | lib/compiler-llvm/src/translator/code.rs:8989-8998 | lib/compiler-llvm/src/translator/code.rs:9056-9065 | lib/compiler-llvm/src/translator/code.rs:9122-9131 | lib/compiler-llvm/src/translator/code.rs:9291-9300 | lib/compiler-llvm/src/translator/code.rs:9727-9736 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×1

Duplicated block (9–10 lines × 5) lib/compiler-singlepass/src/codegen.rs:2830 — lib/compiler-singlepass/src/codegen.rs:2830-2838 | lib/compiler-singlepass/src/codegen.rs:2900-2908 | lib/compiler-singlepass/src/codegen.rs:5728-5737 | lib/compiler-singlepass/src/codegen.rs:5774-5782 | lib/compiler-singlepass/src/codegen.rs:5811-5819 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1

Duplicated block (9–10 lines × 3) lib/virtual-net/src/rx_tx.rs:171 — lib/virtual-net/src/rx_tx.rs:171-179 | lib/virtual-net/src/rx_tx.rs:209-218 | lib/virtual-net/src/rx_tx.rs:270-279 — 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 (7–10 lines × 2) · ×1

Duplicated block (7–10 lines × 2) lib/compiler-cranelift/src/func_environ.rs:2214 — lib/compiler-cranelift/src/func_environ.rs:2214-2220 | lib/compiler-cranelift/src/func_environ.rs:2308-2317 — 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–9 lines × 15) · ×1

Duplicated block (7–9 lines × 15) lib/compiler-llvm/src/translator/code.rs:7458 — lib/compiler-llvm/src/translator/code.rs:7458-7466 | lib/compiler-llvm/src/translator/code.rs:7533-7541 | lib/compiler-llvm/src/translator/code.rs:7610-7619 | lib/compiler-llvm/src/translator/code.rs:7699-7705 | lib/compiler-llvm/src/translator/code.rs:7769-7778 | lib/compiler-llvm/src/translator/code.rs:7859-7868 | lib/compiler-llvm/src/translator/code.rs:7931-7940 | lib/compiler-llvm/src/translator/code.rs:8021-8030 | lib/compiler-llvm/src/translator/code.rs:8180-8189 | lib/compiler-llvm/src/translator/code.rs:8262-8271 | lib/compiler-llvm/src/translator/code.rs:8314-8323 | lib/compiler-llvm/src/translator/code.rs:8366-8375 | lib/compiler-llvm/src/translator/code.rs:8418-8427 | lib/compiler-llvm/src/translator/code.rs:8470-8479 | lib/compiler-llvm/src/translator/code.rs:8522-8531 — all 15 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (9 lines × 10) · ×1

Duplicated block (9 lines × 10) lib/compiler-llvm/src/translator/code.rs:4082 — lib/compiler-llvm/src/translator/code.rs:4082-4090 | lib/compiler-llvm/src/translator/code.rs:4098-4106 | lib/compiler-llvm/src/translator/code.rs:8616-8624 | lib/compiler-llvm/src/translator/code.rs:8644-8652 | lib/compiler-llvm/src/translator/code.rs:8672-8680 | lib/compiler-llvm/src/translator/code.rs:8700-8708 | lib/compiler-llvm/src/translator/code.rs:8912-8920 | lib/compiler-llvm/src/translator/code.rs:8986-8994 | lib/compiler-llvm/src/translator/code.rs:9053-9061 | lib/compiler-llvm/src/translator/code.rs:9119-9127 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1

Duplicated block (9 lines × 8) lib/compiler-singlepass/src/machine_x64.rs:1155 — lib/compiler-singlepass/src/machine_x64.rs:1155-1163 | lib/compiler-singlepass/src/machine_x64.rs:1269-1277 | lib/compiler-singlepass/src/machine_x64.rs:1361-1369 | lib/compiler-singlepass/src/machine_x64.rs:1447-1455 | lib/compiler-singlepass/src/machine_x64.rs:1568-1576 | lib/compiler-singlepass/src/machine_x64.rs:1682-1690 | lib/compiler-singlepass/src/machine_x64.rs:1761-1769 | lib/compiler-singlepass/src/machine_x64.rs:1834-1842 — all 8 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 (9 lines × 6) · ×1

Duplicated block (9 lines × 6) lib/virtual-net/src/rx_tx.rs:117 — lib/virtual-net/src/rx_tx.rs:117-125 | lib/virtual-net/src/rx_tx.rs:138-146 | lib/virtual-net/src/rx_tx.rs:226-234 | lib/virtual-net/src/rx_tx.rs:287-295 | lib/virtual-net/src/rx_tx.rs:381-389 | lib/virtual-net/src/rx_tx.rs:443-451 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1

Duplicated block (8–9 lines × 5) lib/compiler-llvm/src/translator/code.rs:4073 — lib/compiler-llvm/src/translator/code.rs:4073-4081 | lib/compiler-llvm/src/translator/code.rs:8608-8615 | lib/compiler-llvm/src/translator/code.rs:8636-8643 | lib/compiler-llvm/src/translator/code.rs:8664-8671 | lib/compiler-llvm/src/translator/code.rs:8692-8699 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7–9 lines × 4) · ×1

Duplicated block (7–9 lines × 4) lib/compiler-llvm/src/translator/code.rs:4534 — lib/compiler-llvm/src/translator/code.rs:4534-4540 | lib/compiler-llvm/src/translator/code.rs:4586-4592 | lib/compiler-llvm/src/translator/code.rs:4632-4638 | lib/compiler-llvm/src/translator/code.rs:8839-8847 — 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.

D4 · Code Duplication · Duplicated block (6–9 lines × 2) · ×1

Duplicated block (6–9 lines × 2) lib/compiler-llvm/src/translator/code.rs:2418 — lib/compiler-llvm/src/translator/code.rs:2418-2426 | lib/compiler-llvm/src/translator/code.rs:3553-3558 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (8 lines × 16) · ×1

Duplicated block (8 lines × 16) lib/compiler-llvm/src/translator/code.rs:5788 — lib/compiler-llvm/src/translator/code.rs:5788-5795 | lib/compiler-llvm/src/translator/code.rs:5803-5810 | lib/compiler-llvm/src/translator/code.rs:5818-5825 | lib/compiler-llvm/src/translator/code.rs:5833-5840 | lib/compiler-llvm/src/translator/code.rs:5848-5855 | lib/compiler-llvm/src/translator/code.rs:5863-5870 | lib/compiler-llvm/src/translator/code.rs:5878-5885 | lib/compiler-llvm/src/translator/code.rs:5893-5900 | lib/compiler-llvm/src/translator/code.rs:5908-5915 | lib/compiler-llvm/src/translator/code.rs:5923-5930 | lib/compiler-llvm/src/translator/code.rs:5938-5945 | lib/compiler-llvm/src/translator/code.rs:5953-5960 | lib/compiler-llvm/src/translator/code.rs:6826-6833 | lib/compiler-llvm/src/translator/code.rs:6888-6895 | lib/compiler-llvm/src/translator/code.rs:6996-7004 | lib/compiler-llvm/src/translator/code.rs:7059-7066 — all 16 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (8 lines × 14) · ×1

Duplicated block (8 lines × 14) lib/compiler-llvm/src/translator/code.rs:4076 — lib/compiler-llvm/src/translator/code.rs:4076-4083 | lib/compiler-llvm/src/translator/code.rs:4092-4099 | lib/compiler-llvm/src/translator/code.rs:4140-4147 | lib/compiler-llvm/src/translator/code.rs:4152-4159 | lib/compiler-llvm/src/translator/code.rs:4940-4947 | lib/compiler-llvm/src/translator/code.rs:4956-4963 | lib/compiler-llvm/src/translator/code.rs:8610-8617 | lib/compiler-llvm/src/translator/code.rs:8638-8645 | lib/compiler-llvm/src/translator/code.rs:8666-8673 | lib/compiler-llvm/src/translator/code.rs:8694-8701 | lib/compiler-llvm/src/translator/code.rs:8722-8729 | lib/compiler-llvm/src/translator/code.rs:8746-8753 | lib/compiler-llvm/src/translator/code.rs:8770-8777 | lib/compiler-llvm/src/translator/code.rs:8794-8801 — all 14 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 × 8) · ×1

Duplicated block (8 lines × 8) lib/compiler-llvm/src/translator/code.rs:4943 — lib/compiler-llvm/src/translator/code.rs:4943-4950 | lib/compiler-llvm/src/translator/code.rs:4959-4966 | lib/compiler-llvm/src/translator/code.rs:8725-8734 | lib/compiler-llvm/src/translator/code.rs:8749-8758 | lib/compiler-llvm/src/translator/code.rs:8773-8782 | lib/compiler-llvm/src/translator/code.rs:8797-8806 | lib/compiler-llvm/src/translator/code.rs:9289-9298 | lib/compiler-llvm/src/translator/code.rs:9725-9734 — all 8 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 (7–8 lines × 8) · ×1

Duplicated block (7–8 lines × 8) lib/compiler-llvm/src/translator/code.rs:8879 — lib/compiler-llvm/src/translator/code.rs:8879-8885 | lib/compiler-llvm/src/translator/code.rs:8887-8894 | lib/compiler-llvm/src/translator/code.rs:8953-8959 | lib/compiler-llvm/src/translator/code.rs:8961-8968 | lib/compiler-llvm/src/translator/code.rs:9028-9034 | lib/compiler-llvm/src/translator/code.rs:9036-9043 | lib/compiler-llvm/src/translator/code.rs:9094-9100 | lib/compiler-llvm/src/translator/code.rs:9102-9109 — all 8 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 × 7) · ×1

Duplicated block (8 lines × 7) lib/compiler-singlepass/src/codegen.rs:2831 — lib/compiler-singlepass/src/codegen.rs:2831-2838 | lib/compiler-singlepass/src/codegen.rs:2901-2908 | lib/compiler-singlepass/src/codegen.rs:5561-5568 | lib/compiler-singlepass/src/codegen.rs:5686-5693 | lib/compiler-singlepass/src/codegen.rs:5730-5737 | lib/compiler-singlepass/src/codegen.rs:5775-5782 | lib/compiler-singlepass/src/codegen.rs:5812-5819 — all 7 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 (7 lines × 17) · ×1

Duplicated block (7 lines × 17) lib/compiler-llvm/src/translator/code.rs:5153 — lib/compiler-llvm/src/translator/code.rs:5153-5159 | lib/compiler-llvm/src/translator/code.rs:5788-5795 | lib/compiler-llvm/src/translator/code.rs:5803-5810 | lib/compiler-llvm/src/translator/code.rs:5818-5825 | lib/compiler-llvm/src/translator/code.rs:5833-5840 | lib/compiler-llvm/src/translator/code.rs:5848-5855 | lib/compiler-llvm/src/translator/code.rs:5863-5870 | lib/compiler-llvm/src/translator/code.rs:5878-5885 | lib/compiler-llvm/src/translator/code.rs:5893-5900 | lib/compiler-llvm/src/translator/code.rs:5908-5915 | lib/compiler-llvm/src/translator/code.rs:5923-5930 | lib/compiler-llvm/src/translator/code.rs:5938-5945 | lib/compiler-llvm/src/translator/code.rs:5953-5960 | lib/compiler-llvm/src/translator/code.rs:6826-6833 | lib/compiler-llvm/src/translator/code.rs:6888-6895 | lib/compiler-llvm/src/translator/code.rs:6996-7004 | lib/compiler-llvm/src/translator/code.rs:7059-7066 — all 17 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6–7 lines × 12) · ×1

Duplicated block (6–7 lines × 12) lib/compiler-singlepass/src/machine_x64.rs:1471 — lib/compiler-singlepass/src/machine_x64.rs:1471-1477 | lib/compiler-singlepass/src/machine_x64.rs:1560-1565 | lib/compiler-singlepass/src/machine_x64.rs:1572-1578 | lib/compiler-singlepass/src/machine_x64.rs:1626-1632 | lib/compiler-singlepass/src/machine_x64.rs:1674-1679 | lib/compiler-singlepass/src/machine_x64.rs:1686-1692 | lib/compiler-singlepass/src/machine_x64.rs:1705-1711 | lib/compiler-singlepass/src/machine_x64.rs:1753-1758 | lib/compiler-singlepass/src/machine_x64.rs:1765-1771 | lib/compiler-singlepass/src/machine_x64.rs:1785-1790 | lib/compiler-singlepass/src/machine_x64.rs:1826-1831 | lib/compiler-singlepass/src/machine_x64.rs:1838-1843 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7 lines × 10) · ×1

Duplicated block (7 lines × 10) lib/compiler-llvm/src/translator/code.rs:4079 — lib/compiler-llvm/src/translator/code.rs:4079-4085 | lib/compiler-llvm/src/translator/code.rs:4095-4101 | lib/compiler-llvm/src/translator/code.rs:8613-8619 | lib/compiler-llvm/src/translator/code.rs:8641-8647 | lib/compiler-llvm/src/translator/code.rs:8669-8675 | lib/compiler-llvm/src/translator/code.rs:8697-8703 | lib/compiler-llvm/src/translator/code.rs:8901-8907 | lib/compiler-llvm/src/translator/code.rs:8975-8981 | lib/compiler-llvm/src/translator/code.rs:9050-9056 | lib/compiler-llvm/src/translator/code.rs:9116-9122 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6–7 lines × 10) · ×1

Duplicated block (6–7 lines × 10) lib/compiler-singlepass/src/machine_x64.rs:1058 — lib/compiler-singlepass/src/machine_x64.rs:1058-1064 | lib/compiler-singlepass/src/machine_x64.rs:1147-1152 | lib/compiler-singlepass/src/machine_x64.rs:1159-1165 | lib/compiler-singlepass/src/machine_x64.rs:1213-1219 | lib/compiler-singlepass/src/machine_x64.rs:1261-1266 | lib/compiler-singlepass/src/machine_x64.rs:1273-1279 | lib/compiler-singlepass/src/machine_x64.rs:1353-1358 | lib/compiler-singlepass/src/machine_x64.rs:1397-1403 | lib/compiler-singlepass/src/machine_x64.rs:1439-1444 | lib/compiler-singlepass/src/machine_x64.rs:1451-1457 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7 lines × 7) · ×1

Duplicated block (7 lines × 7) lib/compiler-singlepass/src/machine_riscv.rs:1383 — lib/compiler-singlepass/src/machine_riscv.rs:1383-1389 | lib/compiler-singlepass/src/machine_riscv.rs:1435-1441 | lib/compiler-singlepass/src/machine_riscv.rs:1492-1498 | lib/compiler-singlepass/src/machine_x64.rs:7315-7321 | lib/compiler-singlepass/src/machine_x64.rs:7435-7441 | lib/compiler-singlepass/src/machine_x64.rs:7717-7723 | lib/compiler-singlepass/src/machine_x64.rs:7837-7843 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7 lines × 6) · ×1

Duplicated block (7 lines × 6) lib/compiler-llvm/src/translator/code.rs:5293 — lib/compiler-llvm/src/translator/code.rs:5293-5299 | lib/compiler-llvm/src/translator/code.rs:5311-5317 | lib/compiler-llvm/src/translator/code.rs:5395-5401 | lib/compiler-llvm/src/translator/code.rs:5413-5419 | lib/compiler-llvm/src/translator/code.rs:5497-5503 | lib/compiler-llvm/src/translator/code.rs:5515-5521 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6–7 lines × 6) · ×1

Duplicated block (6–7 lines × 6) lib/compiler-llvm/src/translator/intrinsics.rs:1952 — lib/compiler-llvm/src/translator/intrinsics.rs:1952-1958 | lib/compiler-llvm/src/translator/intrinsics.rs:2036-2041 | lib/compiler-llvm/src/translator/intrinsics.rs:2082-2087 | lib/compiler-llvm/src/translator/intrinsics.rs:2127-2132 | lib/compiler-llvm/src/translator/intrinsics.rs:2174-2179 | lib/compiler-llvm/src/translator/intrinsics.rs:2219-2224 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6–7 lines × 3) · ×1

Duplicated block (6–7 lines × 3) lib/virtual-net/src/rx_tx.rs:342 — lib/virtual-net/src/rx_tx.rs:342-347 | lib/virtual-net/src/rx_tx.rs:394-400 | lib/virtual-net/src/rx_tx.rs:456-462 — 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 (6 lines × 22) · ×1

Duplicated block (6 lines × 22) lib/compiler-singlepass/src/machine_x64.rs:1057 — lib/compiler-singlepass/src/machine_x64.rs:1057-1062 | lib/compiler-singlepass/src/machine_x64.rs:1146-1151 | lib/compiler-singlepass/src/machine_x64.rs:1158-1163 | lib/compiler-singlepass/src/machine_x64.rs:1212-1217 | lib/compiler-singlepass/src/machine_x64.rs:1260-1265 | lib/compiler-singlepass/src/machine_x64.rs:1272-1277 | lib/compiler-singlepass/src/machine_x64.rs:1352-1357 | lib/compiler-singlepass/src/machine_x64.rs:1396-1401 | lib/compiler-singlepass/src/machine_x64.rs:1438-1443 | lib/compiler-singlepass/src/machine_x64.rs:1450-1455 | lib/compiler-singlepass/src/machine_x64.rs:1470-1475 | lib/compiler-singlepass/src/machine_x64.rs:1559-1564 | lib/compiler-singlepass/src/machine_x64.rs:1571-1576 | lib/compiler-singlepass/src/machine_x64.rs:1625-1630 | lib/compiler-singlepass/src/machine_x64.rs:1673-1678 | lib/compiler-singlepass/src/machine_x64.rs:1685-1690 | lib/compiler-singlepass/src/machine_x64.rs:1704-1709 | lib/compiler-singlepass/src/machine_x64.rs:1752-1757 | lib/compiler-singlepass/src/machine_x64.rs:1764-1769 | lib/compiler-singlepass/src/machine_x64.rs:1784-1789 | lib/compiler-singlepass/src/machine_x64.rs:1825-1830 | lib/compiler-singlepass/src/machine_x64.rs:1837-1842 — all 22 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 (6 lines × 14) · ×1

Duplicated block (6 lines × 14) lib/compiler-singlepass/src/machine_arm64.rs:381 — lib/compiler-singlepass/src/machine_arm64.rs:381-386 | lib/compiler-singlepass/src/machine_arm64.rs:523-528 | lib/compiler-singlepass/src/machine_arm64.rs:561-566 | lib/compiler-singlepass/src/machine_arm64.rs:597-602 | lib/compiler-singlepass/src/machine_arm64.rs:633-638 | lib/compiler-singlepass/src/machine_arm64.rs:669-674 | lib/compiler-singlepass/src/machine_arm64.rs:705-710 | lib/compiler-singlepass/src/machine_arm64.rs:741-746 | lib/compiler-singlepass/src/machine_arm64.rs:774-779 | lib/compiler-singlepass/src/machine_arm64.rs:804-809 | lib/compiler-singlepass/src/machine_arm64.rs:832-837 | lib/compiler-singlepass/src/machine_arm64.rs:861-866 | lib/compiler-singlepass/src/machine_arm64.rs:2092-2098 | lib/compiler-singlepass/src/machine_arm64.rs:2116-2122 — all 14 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 (5–6 lines × 8) · ×1

Duplicated block (5–6 lines × 8) lib/compiler-llvm/src/translator/code.rs:9912 — lib/compiler-llvm/src/translator/code.rs:9912-9916 | lib/compiler-llvm/src/translator/code.rs:9926-9930 | lib/compiler-llvm/src/translator/code.rs:9940-9944 | lib/compiler-llvm/src/translator/code.rs:9954-9958 | lib/compiler-llvm/src/translator/code.rs:10366-10370 | lib/compiler-llvm/src/translator/code.rs:10379-10383 | lib/compiler-llvm/src/translator/code.rs:10393-10398 | lib/compiler-llvm/src/translator/code.rs:10408-10413 — all 8 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 (6 lines × 7) · ×1

Duplicated block (6 lines × 7) lib/compiler-singlepass/src/machine_riscv.rs:1384 — lib/compiler-singlepass/src/machine_riscv.rs:1384-1389 | lib/compiler-singlepass/src/machine_riscv.rs:1436-1441 | lib/compiler-singlepass/src/machine_riscv.rs:1493-1498 | lib/compiler-singlepass/src/machine_riscv.rs:6059-6064 | lib/compiler-singlepass/src/machine_riscv.rs:6295-6300 | lib/compiler-singlepass/src/machine_x64.rs:185-190 | lib/compiler-singlepass/src/machine_x64.rs:7173-7178 — before extracting anything, compare `lib/compiler-singlepass/src/machine_riscv.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1

Duplicated block (6 lines × 6) lib/compiler-singlepass/src/machine_x64.rs:973 — lib/compiler-singlepass/src/machine_x64.rs:973-978 | lib/compiler-singlepass/src/machine_x64.rs:2509-2514 | lib/compiler-singlepass/src/machine_x64.rs:7310-7315 | lib/compiler-singlepass/src/machine_x64.rs:7430-7435 | lib/compiler-singlepass/src/machine_x64.rs:7712-7717 | lib/compiler-singlepass/src/machine_x64.rs:7832-7837 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (3–6 lines × 4) · ×1

Duplicated block (3–6 lines × 4) lib/compiler-singlepass/src/machine_x64.rs:686 — lib/compiler-singlepass/src/machine_x64.rs:686-688 | lib/compiler-singlepass/src/machine_x64.rs:697-702 | lib/compiler-singlepass/src/machine_x64.rs:832-834 | lib/compiler-singlepass/src/machine_x64.rs:843-848 — 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.

D4 · Code Duplication · Duplicated block (1–6 lines × 3) · ×1

Duplicated block (1–6 lines × 3) lib/wasix/src/net/mod.rs:154 — lib/wasix/src/net/mod.rs:154-158 | lib/wasix/src/net/mod.rs:221-221 | lib/wasix/src/net/mod.rs:317-322 — 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 (5 lines × 10) · ×1

Duplicated block (5 lines × 10) lib/compiler-llvm/src/translator/code.rs:9912 — lib/compiler-llvm/src/translator/code.rs:9912-9916 | lib/compiler-llvm/src/translator/code.rs:9926-9930 | lib/compiler-llvm/src/translator/code.rs:9940-9944 | lib/compiler-llvm/src/translator/code.rs:9954-9958 | lib/compiler-llvm/src/translator/code.rs:10366-10370 | lib/compiler-llvm/src/translator/code.rs:10379-10383 | lib/compiler-llvm/src/translator/code.rs:10393-10397 | lib/compiler-llvm/src/translator/code.rs:10408-10412 | lib/compiler-llvm/src/translator/code.rs:10432-10436 | lib/compiler-llvm/src/translator/code.rs:10460-10464 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (3–5 lines × 31) · ×1

Duplicated block (3–5 lines × 31) lib/compiler-llvm/src/translator/code.rs:4034 — lib/compiler-llvm/src/translator/code.rs:4034-4036 | lib/compiler-llvm/src/translator/code.rs:4256-4258 | lib/compiler-llvm/src/translator/code.rs:4380-4382 | lib/compiler-llvm/src/translator/code.rs:4981-4983 | lib/compiler-llvm/src/translator/code.rs:4993-4997 | lib/compiler-llvm/src/translator/code.rs:5003-5005 | lib/compiler-llvm/src/translator/code.rs:5059-5063 | lib/compiler-llvm/src/translator/code.rs:5069-5071 | lib/compiler-llvm/src/translator/code.rs:5077-5079 | lib/compiler-llvm/src/translator/code.rs:5085-5087 | lib/compiler-llvm/src/translator/code.rs:5093-5095 | lib/compiler-llvm/src/translator/code.rs:5229-5231 | lib/compiler-llvm/src/translator/code.rs:5239-5241 | lib/compiler-llvm/src/translator/code.rs:5331-5333 | lib/compiler-llvm/src/translator/code.rs:5341-5343 | lib/compiler-llvm/src/translator/code.rs:5433-5435 | lib/compiler-llvm/src/translator/code.rs:5443-5445 | lib/compiler-llvm/src/translator/code.rs:5535-5537 | lib/compiler-llvm/src/translator/code.rs:5551-5553 | lib/compiler-llvm/src/translator/code.rs:5567-5569 | lib/compiler-llvm/src/translator/code.rs:5583-5585 | lib/compiler-llvm/src/translator/code.rs:7453-7455 | lib/compiler-llvm/src/translator/code.rs:7528-7530 | lib/compiler-llvm/src/translator/code.rs:7603-7605 | lib/compiler-llvm/src/translator/code.rs:7693-7695 | lib/compiler-llvm/src/translator/code.rs:7762-7764 | lib/compiler-llvm/src/translator/code.rs:7852-7854 | lib/compiler-llvm/src/translator/code.rs:7924-7926 | lib/compiler-llvm/src/translator/code.rs:8014-8016 | lib/compiler-llvm/src/translator/code.rs:8086-8088 | lib/compiler-llvm/src/translator/code.rs:8173-8175 — all 31 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 (69 lines × 2) · ×1

Duplicated block (69 lines × 2) lib/virtual-fs/src/null_file.rs:16 — lib/virtual-fs/src/null_file.rs:16-84 | lib/virtual-fs/src/special_file.rs:25-107 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (14 lines × 11) · ×1

Duplicated block (14 lines × 11) lib/compiler-singlepass/src/machine_arm64.rs:3197 — lib/compiler-singlepass/src/machine_arm64.rs:3197-3210 | lib/compiler-singlepass/src/machine_arm64.rs:3222-3235 | lib/compiler-singlepass/src/machine_arm64.rs:3247-3260 | lib/compiler-singlepass/src/machine_arm64.rs:5432-5445 | lib/compiler-singlepass/src/machine_arm64.rs:5457-5470 | lib/compiler-singlepass/src/machine_arm64.rs:5482-5495 | lib/compiler-singlepass/src/machine_arm64.rs:5507-5520 | lib/compiler-singlepass/src/machine_x64.rs:5514-5527 | lib/compiler-singlepass/src/machine_x64.rs:5539-5552 | lib/compiler-singlepass/src/machine_x64.rs:5564-5577 | lib/compiler-singlepass/src/machine_x64.rs:5589-5602 — before extracting anything, compare `lib/compiler-singlepass/src/machine_arm64.rs` and `lib/compiler-singlepass/src/machine_x64.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14 lines × 7) · ×1

Duplicated block (14 lines × 7) lib/compiler-singlepass/src/machine_arm64.rs:533 — lib/compiler-singlepass/src/machine_arm64.rs:533-546 | lib/compiler-singlepass/src/machine_arm64.rs:571-584 | lib/compiler-singlepass/src/machine_arm64.rs:607-620 | lib/compiler-singlepass/src/machine_arm64.rs:643-656 | lib/compiler-singlepass/src/machine_arm64.rs:679-692 | lib/compiler-singlepass/src/machine_arm64.rs:715-728 | lib/compiler-singlepass/src/machine_arm64.rs:751-764 — all 7 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.

D44 · Platform End-of-Life · End-of-life runtime · ×1

End-of-life runtime: Rust 1.96 rust-toolchain.toml:1 — rust-toolchain.toml declares Rust 1.96 as this project's toolchain file, and Rust 1.96, superseded by 1.97 on 2026-07-09 (the Rust project patches only the current stable). An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-07-09 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.

D5 · Coupling · Unstable project wasmer-journal · ×1

Unstable project wasmer-journal — wasmer-journal has instability 0.83 with 1 dependents.

X1 · Async correctness · Blocking `thread · ×1

Blocking `thread::sleep` inside an `async` body lib/backend-api/src/query.rs:2356 — This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`.

Minor — 202 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×132

Orphaned file lib/journal/src/concrete/log_file.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/api/src/entities/function/mod.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/wasix/src/os/posix_err.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/journal/src/concrete/printing.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/journal/src/concrete/filter.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/wasix/src/syscalls/wasix/closure_prepare.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/api/src/entities/imports.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/types/src/entity/primary_map.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/virtual-net/src/meta.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/cli/src/config/mod.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/vm/src/probestack/compiler_builtins.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/cli/src/commands/package/push.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/wasix/src/journal/effector/memory_and_snapshot.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/c-api/src/wasm_c_api/unstable/middlewares/metering.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/cli/src/commands/config.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/types/src/entity/secondary_map.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/c-api/src/wasm_c_api/instance.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/virtual-fs/src/ops.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/cli/src/commands/run/capabilities/net.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/api/src/entities/function/host/imp.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/virtual-fs/src/mem_fs/stdio.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/c-api/src/wasm_c_api/types/extern_.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/api/src/backend/v8/entities/store/obj.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/api/src/utils/mem/ptr.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/wasix/src/runtime/module_cache/fallback.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 107 more in this group — see findings.md.

X4 · Structured logging · Interpolated log message defeats structured logging · ×40

Interpolated log message defeats structured logging lib/wasix/src/utils/mod.rs:44 — `warn!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:391 — `debug!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:469 — `trace!` at line 469 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:778 — `warn!` at line 778 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:811 — `warn!` at line 811 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:824 — `warn!` at line 824 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:1109 — `trace!` at line 1109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:1198 — `warn!` at line 1198 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:1243 — `trace!` at line 1243 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:1268 — `trace!` at line 1268 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:1374 — `warn!` at line 1374 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/mod.rs:1541 — `trace!` at line 1541 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/windows.rs:41 — `debug!` at line 41 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/callback_signal.rs:21 — `warn!` at line 21 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/chdir.rs:25 — `error!` at line 25 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/closure_allocate.rs:25 — `error!` at line 25 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_create.rs:22 — `trace!` at line 22 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_create.rs:36 — `trace!` at line 36 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_destroy.rs:40 — `trace!` at line 40 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_destroy.rs:48 — `trace!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_destroy.rs:62 — `trace!` at line 62 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_switch.rs:49 — `trace!` at line 49 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_switch.rs:59 — `trace!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_switch.rs:68 — `trace!` at line 68 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging lib/wasix/src/syscalls/wasix/context_switch.rs:72 — `trace!` at line 72 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
+ 15 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×9

Duplicated predicate lib/cli/src/commands/app/secrets/create.rs:172 — `!self.non_interactive && self.from_file.is_some()` appears character-identically in 2 files — lib/cli/src/commands/app/secrets/create.rs, lib/cli/src/commands/app/secrets/update.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 lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs:62 — `(fst_flags.contains(Fstflags::SET_ATIM) && fst_flags.contains(Fstflags::SET_ATIM_NOW)) || (fst_flags.contains(Fstflags::SET_MTIM) && fst_fla…` appears character-identically in 2 files — lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs, lib/wasix/src/syscalls/wasi/path_filestat_set_times.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 lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs:73 — `fst_flags.contains(Fstflags::SET_ATIM) || fst_flags.contains(Fstflags::SET_ATIM_NOW)` appears character-identically in 2 files — lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs, lib/wasix/src/syscalls/wasi/path_filestat_set_times.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 lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs:83 — `fst_flags.contains(Fstflags::SET_MTIM) || fst_flags.contains(Fstflags::SET_MTIM_NOW)` appears character-identically in 2 files — lib/wasix/src/syscalls/wasi/fd_filestat_set_times.rs, lib/wasix/src/syscalls/wasi/path_filestat_set_times.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 lib/wasix/src/syscalls/wasix/sock_recv.rs:137 — `nonblocking_flag || fd.inner.flags.contains(Fdflags::NONBLOCK)` appears character-identically in 4 files — lib/wasix/src/syscalls/wasix/sock_recv.rs, lib/wasix/src/syscalls/wasix/sock_recv_from.rs, lib/wasix/src/syscalls/wasix/sock_send.rs, lib/wasix/src/syscalls/wasix/sock_send_to.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 lib/wasix/src/syscalls/wasix/proc_exec4.rs:110 — `search_path == Bool::False && !name.starts_with('/')` appears character-identically in 2 files — lib/wasix/src/syscalls/wasix/proc_exec4.rs, lib/wasix/src/syscalls/wasix/proc_spawn3.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 lib/wasix/src/syscalls/wasix/proc_exec4.rs:89 — `search_path == Bool::True && !name.contains('/')` appears character-identically in 2 files — lib/wasix/src/syscalls/wasix/proc_exec4.rs, lib/wasix/src/syscalls/wasix/proc_spawn3.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 lib/cli/src/commands/package/common/wait.rs:23 — `self.container || self.native_executables || self.bindings` appears character-identically in 2 files — lib/cli/src/commands/package/common/wait.rs, lib/package-sdk/src/package/publish.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 lib/api/src/backend/sys/entities/memory/view.rs:214 — `source_end > self.buffer.len || target_end > new_memory.buffer.len` appears character-identically in 2 files — lib/api/src/backend/sys/entities/memory/view.rs, lib/api/src/backend/v8/entities/memory/view.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.

D16 · Bus Factor · Off-boarding risk · ×3

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 32 significant file(s) lose their only recent owner: lib/compiler-singlepass/src/machine_x64.rs, lib/compiler-singlepass/src/codegen.rs, lib/compiler-singlepass/src/machine_riscv.rs, lib/compiler-singlepass/src/machine.rs, lib/compiler-cranelift/src/func_environ.rs, lib/compiler-singlepass/src/emitter_riscv.rs, lib/compiler-llvm/src/abi.rs, lib/types/src/types.rs (+24 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 11 significant file(s) lose their only recent owner: lib/c-api-imports/src/lib.rs, lib/wasix/src/state/linker/mod.rs, lib/api/src/backend/js/entities/module.rs, lib/wasix/src/state/linker/instance_group.rs, lib/wasix/src/http/web_http_client.rs, lib/api/src/backend/js/entities/function/typed.rs, lib/api/src/backend/sys/entities/memory/view.rs, lib/api/src/entities/memory/view/mod.rs (+3 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 7 significant file(s) lose their only recent owner: lib/wasix/src/state/context_switching.rs, lib/wasix/src/utils/thread_local_executor.rs, lib/wasix/src/syscalls/wasix/context_switch.rs, lib/wasix/src/syscalls/wasix/context_create.rs, lib/wasix/src/syscalls/wasix/proc_fork_env.rs, lib/wasix/src/syscalls/wasix/proc_exit2.rs, lib/wasix/src/syscalls/wasix/context_destroy.rs. Pair on, review, or document these before any departure.

M4 · Documentation accuracy · README/code drift · ×3

README/code drift lib/c-api/README.md:202 — lib/c-api/README.md links to `./wasmer.hh`, but `lib/c-api/wasmer.hh` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift lib/config/README.md:17 — lib/config/README.md links to `.github/workflows/release-please.yml`, but `lib/config/.github/workflows/release-please.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift lib/wasix/tests/wasm_tests/README.md:31 — lib/wasix/tests/wasm_tests/README.md links to `../wasm_tests.rs`, but `lib/wasix/tests/wasm_tests.rs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

X7 · Silent fallback defaults · Silent fallback default on Err · ×2

Silent fallback default on Err lib/api/src/backend/js/vm/memory.rs:36 — `get_runtime_size` turns every `Err` into `0` — 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 lib/cli/src/config/mod.rs:224 — `from_file` turns every `Err` into `Ok(Self::default())` — 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.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (53 single-owned of 567 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 567 of the 977 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: lib/wasix/src/syscalls/wasix/proc_exec4.rs, lib/cli/src/commands/cron.rs, lib/cli/src/commands/namespace/create.rs.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — 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/`.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 6 of 27 project(s) overshoot their size bounds, lowering Project Cohesion to 5.7/10. The most over is `lib/wasix` (57458 LoC, 411 module-visible types across 29 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 132 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: lib/api/src/entities/function/mod.rs, lib/journal/src/concrete/log_file.rs, lib/api/src/entities/imports.rs, lib/wasix/src/os/posix_err.rs, lib/journal/src/concrete/printing.rs, lib/api/src/entities/function/host/imp.rs, lib/journal/src/concrete/filter.rs, lib/wasix/src/syscalls/wasix/closure_prepare.rs (and 124 more) (139 orphaned of 567 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 567 of the 977 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

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.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 16/18 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `lib/config`.

S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1

No app-layer HTTPS enforcement detected — This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `.serve_connection(` (lib/cli/src/commands/auth/login/mod.rs:132).

S1 · Web-Security Posture · No security response headers detected · ×1

No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (lib/cli/src/commands/auth/login/mod.rs:132).

Minor — 5 finding(s)

D12 · Dependency Hygiene · Outdated · ×5

Outdated: cc — `cc` is locked at 1.9.0 but 1.10.0 is the current stable release on crates.io, and it already satisfies the `"1.2.47"` requirement declared in lib/compiler/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cc` and commit the updated REDACTED.
Outdated: enumset — `enumset` is locked at 1.1.14 but 1.1.15 is the current stable release on crates.io, and it already satisfies the `"1.1.0"` requirement declared in lib/c-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p enumset` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.16.3 but 1.16.4 is the current stable release on crates.io, and it already satisfies the `"1.6"` requirement declared in lib/compiler-cranelift/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.28.0 but 1.29.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in lib/cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
Outdated: zip — `zip` is locked at 9.0.5 but 9.1.1 is the current stable release on crates.io, and it already satisfies the `"9.0.4"` requirement declared in lib/api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zip` 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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1ddadbc5793741aca4903c6cee61234d/history.json --exit-code 0 --source .	9	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1ddadbc5793741aca4903c6cee61234d/tree.json --exit-code 0 --source .	1	artifacts/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/watchdog-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 .	149	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .	8	artifacts/raw/osv-scanner.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	9	artifacts/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	—
D40 · Network Egress Confinement	runtime-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 Confinement	runtime-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 Enforcement	runtime-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 Dependencies	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .	0	artifacts/raw/osv-scanner.json

Run 01a17689-b662-7c50-89b9-d011ab7611a4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 68% · Adequate · gated by X4 ·

At a glance — Architecture · 86% · Strong ·

At a glance — Maturity · 62% · Adequate ·

At a glance — Readiness · 78% · Strong ·

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

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Accessibility · 36% · Weak · gated by AC1, AC3 ·

At a glance — Performance · 94% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts