Public report — opendal, published 30 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.18 (frozen) · verify this surveyFiledcd_e207a68c015849de9834cf4651ac375d
Filed 30 September 2026, 02:50 UTC
Public
Large · 202,987 LoC · 130 projects · rebuild ~1.5 person-years · weakest lens: Readiness (56%)
Findings by grade
372 critical908 serious287 minor4 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
30 September 2026, 02:31 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
1531findings with an exact file:lineof 1567 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
90/144dimensions across the health lenses202987 LoC · 130 projects — wide & deep
Preview (pre-1.0). This repo hasn't declared a stable release, so it's judged against a relaxed, pre-production bar.
The system holds an adequate standing with a health score of 62%, reflecting a large, complex asset that is fundamentally sound in design but carries significant operational risk. With nearly 203,000 lines of production code and a rebuild cost of approximately €210,000, this is a substantial business investment. The architecture is robust, and the code is clean, yet the low readiness score indicates that the system is not yet safe to operate at scale without intervention.
The primary risk lies in operational resilience. While the code structure is mature and well-modeled, the system lacks proven disaster recovery capabilities. A backup configuration is not a recovery plan; without documented recovery time objectives and tested restore procedures, a failure could lead to prolonged outages and data loss. This gap exposes the business to unacceptable downtime costs, making it the most critical area for immediate attention. The low readiness score suggests that while the code works, the processes to keep it running reliably are underdeveloped.
Conversely, the system’s strengths are notable. The architecture is nearly perfect, meaning changes are unlikely to cause unintended side effects. The code is highly maintainable, with minimal boilerplate and clear logic, which reduces long-term maintenance costs. The domain modeling is strong, ensuring that the software accurately reflects business rules. These factors mean that once operational risks are mitigated, the team can deliver new features quickly and safely.
The highest-leverage action is to document recovery objectives and test restore procedures. This step provides the most protection for the business with relatively low effort compared to refactoring code. Other improvements, such as adding tests for unreached modules and tightening access controls, are important but secondary. Until recovery is proven, the system remains fragile despite its technical quality. The assessment is based on measured data, though some areas like event-driven patterns were not evaluated. Focus first on resilience to secure the asset’s value.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
D20 · No consequences/trade-offs section (e.g. API surface growth, cost of the new AccessorCapability enum) core/core/src/docs/rfcs/0409_accessor_capabilities.md
D20 · No consequences/trade-offs section; the body is a boilerplate guide-level explanation and reference-level API signature with no discussion of cost or trade-offs core/core/src/docs/rfcs/0429_init_from_iter.md
D20 · No consequences/trade-offs section; the body is a guide-level install list with no discussion of how oay behaves when opendal changes or what happens if oay outdates opendal core/core/src/docs/rfcs/0443_gateway.md
D22 · Redundant naming convention. The `Operator` type exposes both `copier` and `copier_options`. While this follows the existing pattern of `read`/`read_options` and `writer`/`writer_options`, the suffix `_options` is verbose and inconsistent with common Rust idioms where builder patterns or distinct method names (like `copier_with`) are preferred. More critically, it duplicates the intent of configuring the copy operation, just like `copy` vs `copy_options`.
D22 · Inconsistent deletion API surface. `Operator` provides simple `delete` and `delete_options` methods, but also exposes `delete_iter` and `delete_try_iter` for batch operations. Meanwhile, `Deleter` (a separate type) also has `delete`, `delete_iter`, and `delete_try_iter`. This creates confusion: should the user call `op.delete()` for single items and `op.deleter().delete_iter()` for batches, or is there a direct batch method on `Operator`? The existence of `delete_iter` on both `Operator` and `Deleter` suggests overlapping functionality.
D22 · Inconsistent naming with `copy`. `Operator` has `copy` and `copy_options`, but also `copier` and `copier_options`. For rename, it only has `rename` and `rename_options`. This inconsistency in method naming (`_options` vs `_options` vs implicit builder) makes the API harder to memorize. Specifically, `copier` returns a `Copier` type, while `rename` is a direct call. This asymmetry between copy (streaming/batch capable via Copier) and rename (direct) is a design inconsistency.
AXR1 · WCAG 2.4.2 reproducibly failed in a rendered surface
AXR1 · WCAG 3.1.1 reproducibly failed in a rendered surface
AXH1 · Runtime security header not set: content-security-policy
AXH1 · Runtime security header not set: strict-transport-security
AXH1 · Runtime security header not set: x-content-type-options
AXH1 · Runtime security header not set: x-frame-options
AXH1 · Runtime security header not set: referrer-policy
AXH1 · Runtime security header not set: permissions-policy
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.9× (at 62% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified for 197,550 line(s) outside the .NET model (the tier breakdown is a C#-only syntax walk)
Effort basis
The rebuild estimate prices 200,776 code lines. Comment-only lines count toward the 202,987-line size but are not build effort.
This codebase represents roughly ~1.5 person-years of build effort (about ~€210,000 to rebuild). Its weakest lens is Readiness at 56% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Low (×0.9) — library/CLI × a 0.9× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Value concentrated against a weak lens · Medium · Value at risk
This is a Large asset (~1.5 person-years to rebuild), and its weakest lens is Readiness at 56%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
861 modules, 2914 dependencies. 5 dependency cycles across 37 modules, marked above the diagonal.
Showing the 40 most-connected modules; 821 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
opendal_core.raw.oio.list.page_list uses opendal_core.raw.oio.list.api. Changing opendal_core.raw.oio.list.api can break opendal_core.raw.oio.list.page_list, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
13→3 opendal_core.raw.oio.read.api depends on opendal_core.types.bytes_range✕
Type pairs
2 distinct (type in opendal_core.raw.oio.read.api → type in opendal_core.types.bytes_range) references.
opendal_core.raw.oio.read.api uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_core.raw.oio.read.api, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
14→7 opendal_core.raw.ops depends on opendal_cpp.ffi✕
Type pairs
5 distinct (type in opendal_core.raw.ops → type in opendal_cpp.ffi) references.
opendal_core.types.builder uses opendal_core.types.operator.uri. Changing opendal_core.types.operator.uri can break opendal_core.types.builder, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
16→5 opendal_core.types.operator.registry depends on opendal_core.types.operator.uri✕
Type pairs
1 distinct (type in opendal_core.types.operator.registry → type in opendal_core.types.operator.uri) reference.
opendal_core.types.operator.registry uses opendal_core.types.operator.uri. Changing opendal_core.types.operator.uri can break opendal_core.types.operator.registry, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
17→6 opendal_nodejs.layer depends on opendal_cpp.async✕
Type pairs
7 distinct (type in opendal_nodejs.layer → type in opendal_cpp.async) references.
opendal_core.raw.accessor uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_core.raw.accessor, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
19→7 opendal_core.raw.accessor depends on opendal_cpp.ffi✕
Type pairs
2 distinct (type in opendal_core.raw.accessor → type in opendal_cpp.ffi) references.
opendal_core.raw.oio.read.stream_read uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_core.raw.oio.read.stream_read, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→13 opendal_core.raw.oio.read.stream_read depends on opendal_core.raw.oio.read.api✕
Type pairs
1 distinct (type in opendal_core.raw.oio.read.stream_read → type in opendal_core.raw.oio.read.api) reference.
opendal_core.raw.oio.read.stream_read uses opendal_core.raw.oio.read.api. Changing opendal_core.raw.oio.read.api can break opendal_core.raw.oio.read.stream_read, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→7 opendal_core.types.buffer depends on opendal_cpp.ffi✕
Type pairs
2 distinct (type in opendal_core.types.buffer → type in opendal_cpp.ffi) references.
opendal_core.types.buffer uses opendal_core.raw.oio.read.api. Changing opendal_core.raw.oio.read.api can break opendal_core.types.buffer, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→4 opendal_service_azdls.lister depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_azdls.lister → type in opendal_core.types.context.operation) reference.
opendal_service_azdls.lister uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_azdls.lister, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→12 opendal_service_azdls.lister depends on opendal_core.raw.oio.list.page_list✕
Type pairs
2 distinct (type in opendal_service_azdls.lister → type in opendal_core.raw.oio.list.page_list) references.
opendal_service_azdls.lister uses opendal_core.raw.oio.list.page_list. Changing opendal_core.raw.oio.list.page_list can break opendal_service_azdls.lister, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→22 opendal_core.raw.oio.buf.queue_buf depends on opendal_core.types.buffer✕
Type pairs
1 distinct (type in opendal_core.raw.oio.buf.queue_buf → type in opendal_core.types.buffer) reference.
opendal_core.raw.oio.buf.queue_buf uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_core.raw.oio.buf.queue_buf, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
25→14 opendal_core.raw.oio.delete.one_shot_delete depends on opendal_core.raw.ops✕
Type pairs
2 distinct (type in opendal_core.raw.oio.delete.one_shot_delete → type in opendal_core.raw.ops) references.
opendal_core.raw.oio.delete.one_shot_delete uses opendal_core.raw.ops. Changing opendal_core.raw.ops can break opendal_core.raw.oio.delete.one_shot_delete, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
25→20 opendal_core.raw.oio.delete.one_shot_delete depends on opendal_core.raw.oio.delete.api✕
Type pairs
1 distinct (type in opendal_core.raw.oio.delete.one_shot_delete → type in opendal_core.raw.oio.delete.api) reference.
opendal_core.raw.oio.delete.one_shot_delete uses opendal_core.raw.oio.delete.api. Changing opendal_core.raw.oio.delete.api can break opendal_core.raw.oio.delete.one_shot_delete, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
26→3 opendal_core.raw.oio.write.api depends on opendal_core.types.bytes_range✕
Type pairs
2 distinct (type in opendal_core.raw.oio.write.api → type in opendal_core.types.bytes_range) references.
opendal_core.raw.oio.write.api uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_core.raw.oio.write.api, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
26→14 opendal_core.raw.oio.write.api depends on opendal_core.raw.ops✕
Type pairs
2 distinct (type in opendal_core.raw.oio.write.api → type in opendal_core.raw.ops) references.
opendal_core.raw.oio.write.api uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_core.raw.oio.write.api, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→2 opendal_service_aliyun_drive.core depends on opendal_core.raw.operation✕
Type pairs
1 distinct (type in opendal_service_aliyun_drive.core → type in opendal_core.raw.operation) reference.
opendal_service_aliyun_drive.core uses opendal_core.raw.operation. Changing opendal_core.raw.operation can break opendal_service_aliyun_drive.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→3 opendal_service_aliyun_drive.core depends on opendal_core.types.bytes_range✕
Type pairs
1 distinct (type in opendal_service_aliyun_drive.core → type in opendal_core.types.bytes_range) reference.
opendal_service_aliyun_drive.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_aliyun_drive.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→4 opendal_service_aliyun_drive.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_aliyun_drive.core → type in opendal_core.types.context.operation) reference.
opendal_service_aliyun_drive.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_aliyun_drive.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→7 opendal_service_aliyun_drive.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_aliyun_drive.core → type in opendal_cpp.ffi) reference.
opendal_service_aliyun_drive.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_aliyun_drive.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→19 opendal_service_aliyun_drive.core depends on opendal_core.raw.accessor✕
Type pairs
1 distinct (type in opendal_service_aliyun_drive.core → type in opendal_core.raw.accessor) reference.
opendal_service_aliyun_drive.core uses opendal_core.raw.accessor. Changing opendal_core.raw.accessor can break opendal_service_aliyun_drive.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→22 opendal_service_aliyun_drive.core depends on opendal_core.types.buffer✕
Type pairs
1 distinct (type in opendal_service_aliyun_drive.core → type in opendal_core.types.buffer) reference.
opendal_service_aliyun_drive.core uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_service_aliyun_drive.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→3 opendal_core.raw.oio.write.multipart_write depends on opendal_core.types.bytes_range✕
Type pairs
2 distinct (type in opendal_core.raw.oio.write.multipart_write → type in opendal_core.types.bytes_range) references.
opendal_core.raw.oio.write.multipart_write uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_core.raw.oio.write.multipart_write, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→14 opendal_core.raw.oio.write.multipart_write depends on opendal_core.raw.ops✕
Type pairs
2 distinct (type in opendal_core.raw.oio.write.multipart_write → type in opendal_core.raw.ops) references.
opendal_core.raw.oio.write.multipart_write uses opendal_core.raw.ops. Changing opendal_core.raw.ops can break opendal_core.raw.oio.write.multipart_write, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→22 opendal_core.raw.oio.write.multipart_write depends on opendal_core.types.buffer✕
Type pairs
2 distinct (type in opendal_core.raw.oio.write.multipart_write → type in opendal_core.types.buffer) references.
opendal_core.raw.oio.write.multipart_write uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_core.raw.oio.write.multipart_write, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→26 opendal_core.raw.oio.write.multipart_write depends on opendal_core.raw.oio.write.api✕
Type pairs
1 distinct (type in opendal_core.raw.oio.write.multipart_write → type in opendal_core.raw.oio.write.api) reference.
opendal_core.raw.oio.write.multipart_write uses opendal_core.raw.oio.write.api. Changing opendal_core.raw.oio.write.api can break opendal_core.raw.oio.write.multipart_write, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
29→22 opendal_core.raw.oio.write.one_shot_write depends on opendal_core.types.buffer✕
Type pairs
2 distinct (type in opendal_core.raw.oio.write.one_shot_write → type in opendal_core.types.buffer) references.
opendal_core.raw.oio.write.one_shot_write uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_core.raw.oio.write.one_shot_write, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
29→26 opendal_core.raw.oio.write.one_shot_write depends on opendal_core.raw.oio.write.api✕
Type pairs
1 distinct (type in opendal_core.raw.oio.write.one_shot_write → type in opendal_core.raw.oio.write.api) reference.
opendal_core.raw.oio.write.one_shot_write uses opendal_core.raw.oio.write.api. Changing opendal_core.raw.oio.write.api can break opendal_core.raw.oio.write.one_shot_write, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→1 opendal_layer_observe_metrics_common depends on opendal_core.raw.oio.list.api✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.oio.list.api) reference.
opendal_layer_observe_metrics_common uses opendal_core.raw.oio.list.api. Changing opendal_core.raw.oio.list.api can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→3 opendal_layer_observe_metrics_common depends on opendal_core.types.bytes_range✕
Type pairs
2 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.types.bytes_range) references.
opendal_layer_observe_metrics_common uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→4 opendal_layer_observe_metrics_common depends on opendal_core.types.context.operation✕
Type pairs
2 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.types.context.operation) references.
opendal_layer_observe_metrics_common uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→7 opendal_layer_observe_metrics_common depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_cpp.ffi) reference.
opendal_layer_observe_metrics_common uses opendal_java.error. Changing opendal_java.error can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→11 opendal_layer_observe_metrics_common depends on opendal_core.raw.oio.copy.api✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.oio.copy.api) reference.
opendal_layer_observe_metrics_common uses opendal_core.raw.oio.copy.api. Changing opendal_core.raw.oio.copy.api can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→13 opendal_layer_observe_metrics_common depends on opendal_core.raw.oio.read.api✕
Type pairs
2 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.oio.read.api) references.
opendal_layer_observe_metrics_common uses opendal_core.raw.oio.read.api. Changing opendal_core.raw.oio.read.api can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→14 opendal_layer_observe_metrics_common depends on opendal_core.raw.ops✕
Type pairs
12 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.ops) references.
opendal_layer_observe_metrics_common uses opendal_core.raw.ops. Changing opendal_core.raw.ops can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→17 opendal_layer_observe_metrics_common depends on opendal_nodejs.layer✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_nodejs.layer) reference.
opendal_layer_observe_metrics_common uses opendal_nodejs.layer. Changing opendal_nodejs.layer can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→19 opendal_layer_observe_metrics_common depends on opendal_core.raw.accessor✕
Type pairs
4 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.accessor) references.
opendal_layer_observe_metrics_common uses opendal_core.raw.accessor. Changing opendal_core.raw.accessor can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→20 opendal_layer_observe_metrics_common depends on opendal_core.raw.oio.delete.api✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.oio.delete.api) reference.
opendal_layer_observe_metrics_common uses opendal_core.raw.oio.delete.api. Changing opendal_core.raw.oio.delete.api can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→22 opendal_layer_observe_metrics_common depends on opendal_core.types.buffer✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.types.buffer) reference.
opendal_layer_observe_metrics_common uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→26 opendal_layer_observe_metrics_common depends on opendal_core.raw.oio.write.api✕
Type pairs
1 distinct (type in opendal_layer_observe_metrics_common → type in opendal_core.raw.oio.write.api) reference.
opendal_layer_observe_metrics_common uses opendal_core.raw.oio.write.api. Changing opendal_core.raw.oio.write.api can break opendal_layer_observe_metrics_common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→1 opendal_layer_timeout depends on opendal_core.raw.oio.list.api✕
Type pairs
1 distinct (type in opendal_layer_timeout → type in opendal_core.raw.oio.list.api) reference.
opendal_layer_timeout uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_layer_timeout, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→7 opendal_layer_timeout depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_layer_timeout → type in opendal_cpp.ffi) reference.
opendal_service_azblob.core uses opendal_core.raw.operation. Changing opendal_core.raw.operation can break opendal_service_azblob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→3 opendal_service_azblob.core depends on opendal_core.types.bytes_range✕
Type pairs
1 distinct (type in opendal_service_azblob.core → type in opendal_core.types.bytes_range) reference.
opendal_service_azblob.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_azblob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→4 opendal_service_azblob.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_azblob.core → type in opendal_core.types.context.operation) reference.
opendal_service_azblob.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_azblob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→7 opendal_service_azblob.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_azblob.core → type in opendal_cpp.ffi) reference.
opendal_service_azblob.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_azblob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→14 opendal_service_azblob.core depends on opendal_core.raw.ops✕
Type pairs
5 distinct (type in opendal_service_azblob.core → type in opendal_core.raw.ops) references.
opendal_service_azblob.core uses opendal_core.types.builder. Changing opendal_core.types.builder can break opendal_service_azblob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→19 opendal_service_azblob.core depends on opendal_core.raw.accessor✕
Type pairs
1 distinct (type in opendal_service_azblob.core → type in opendal_core.raw.accessor) reference.
opendal_service_azblob.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_azblob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
33→2 opendal_service_b2.core depends on opendal_core.raw.operation✕
Type pairs
2 distinct (type in opendal_service_b2.core → type in opendal_core.raw.operation) references.
opendal_service_b2.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_b2.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
33→4 opendal_service_b2.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_b2.core → type in opendal_core.types.context.operation) reference.
opendal_service_b2.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_b2.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
33→7 opendal_service_b2.core depends on opendal_cpp.ffi✕
Type pairs
2 distinct (type in opendal_service_b2.core → type in opendal_cpp.ffi) references.
opendal_service_b2.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_b2.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
33→14 opendal_service_b2.core depends on opendal_core.raw.ops✕
Type pairs
2 distinct (type in opendal_service_b2.core → type in opendal_core.raw.ops) references.
opendal_service_b2.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_b2.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→2 opendal_service_cos.core depends on opendal_core.raw.operation✕
Type pairs
1 distinct (type in opendal_service_cos.core → type in opendal_core.raw.operation) reference.
opendal_service_cos.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_cos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→4 opendal_service_cos.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_cos.core → type in opendal_core.types.context.operation) reference.
opendal_service_cos.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_cos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→7 opendal_service_cos.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_cos.core → type in opendal_cpp.ffi) reference.
opendal_service_cos.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_cos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→14 opendal_service_cos.core depends on opendal_core.raw.ops✕
Type pairs
5 distinct (type in opendal_service_cos.core → type in opendal_core.raw.ops) references.
opendal_service_cos.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_cos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→2 opendal_service_hf.core depends on opendal_core.raw.operation✕
Type pairs
3 distinct (type in opendal_service_hf.core → type in opendal_core.raw.operation) references.
opendal_service_hf.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_hf.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→4 opendal_service_hf.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_hf.core → type in opendal_core.types.context.operation) reference.
opendal_service_hf.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_hf.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→7 opendal_service_hf.core depends on opendal_cpp.ffi✕
Type pairs
2 distinct (type in opendal_service_hf.core → type in opendal_cpp.ffi) references.
opendal_service_hf.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_hf.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→19 opendal_service_hf.core depends on opendal_core.raw.accessor✕
Type pairs
1 distinct (type in opendal_service_hf.core → type in opendal_core.raw.accessor) reference.
opendal_service_hf.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_hf.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→2 opendal_service_gcs.core depends on opendal_core.raw.operation✕
Type pairs
1 distinct (type in opendal_service_gcs.core → type in opendal_core.raw.operation) reference.
opendal_service_gcs.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_gcs.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→4 opendal_service_gcs.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_gcs.core → type in opendal_core.types.context.operation) reference.
opendal_service_gcs.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_gcs.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→7 opendal_service_gcs.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_gcs.core → type in opendal_cpp.ffi) reference.
opendal_service_gcs.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_gcs.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→14 opendal_service_gcs.core depends on opendal_core.raw.ops✕
Type pairs
6 distinct (type in opendal_service_gcs.core → type in opendal_core.raw.ops) references.
opendal_service_gcs.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_gcs.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→34 opendal_service_gcs.core depends on opendal_service_cos.core✕
Type pairs
2 distinct (type in opendal_service_gcs.core → type in opendal_service_cos.core) references.
opendal_service_oss.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_oss.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→4 opendal_service_oss.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_oss.core → type in opendal_core.types.context.operation) reference.
opendal_service_oss.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_oss.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→7 opendal_service_oss.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_oss.core → type in opendal_cpp.ffi) reference.
opendal_service_oss.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_oss.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→14 opendal_service_oss.core depends on opendal_core.raw.ops✕
Type pairs
4 distinct (type in opendal_service_oss.core → type in opendal_core.raw.ops) references.
opendal_service_oss.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_oss.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→34 opendal_service_oss.core depends on opendal_service_cos.core✕
Type pairs
5 distinct (type in opendal_service_oss.core → type in opendal_service_cos.core) references.
opendal_service_vercel_blob.core uses opendal_core.raw.operation. Changing opendal_core.raw.operation can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→3 opendal_service_vercel_blob.core depends on opendal_core.types.bytes_range✕
Type pairs
1 distinct (type in opendal_service_vercel_blob.core → type in opendal_core.types.bytes_range) reference.
opendal_service_vercel_blob.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→4 opendal_service_vercel_blob.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_vercel_blob.core → type in opendal_core.types.context.operation) reference.
opendal_service_vercel_blob.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→7 opendal_service_vercel_blob.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_vercel_blob.core → type in opendal_cpp.ffi) reference.
opendal_service_vercel_blob.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→14 opendal_service_vercel_blob.core depends on opendal_core.raw.ops✕
Type pairs
2 distinct (type in opendal_service_vercel_blob.core → type in opendal_core.raw.ops) references.
opendal_service_vercel_blob.core uses opendal_core.types.builder. Changing opendal_core.types.builder can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→19 opendal_service_vercel_blob.core depends on opendal_core.raw.accessor✕
Type pairs
1 distinct (type in opendal_service_vercel_blob.core → type in opendal_core.raw.accessor) reference.
opendal_service_vercel_blob.core uses opendal_core.raw.accessor. Changing opendal_core.raw.accessor can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→22 opendal_service_vercel_blob.core depends on opendal_core.types.buffer✕
Type pairs
1 distinct (type in opendal_service_vercel_blob.core → type in opendal_core.types.buffer) reference.
opendal_service_vercel_blob.core uses opendal_core.types.buffer. Changing opendal_core.types.buffer can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→27 opendal_service_vercel_blob.core depends on opendal_service_aliyun_drive.core✕
Type pairs
1 distinct (type in opendal_service_vercel_blob.core → type in opendal_service_aliyun_drive.core) reference.
opendal_service_vercel_blob.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→32 opendal_service_vercel_blob.core depends on opendal_service_azblob.core✕
Type pairs
2 distinct (type in opendal_service_vercel_blob.core → type in opendal_service_azblob.core) references.
opendal_service_vercel_blob.core uses opendal_service_azblob.core. Changing opendal_service_azblob.core can break opendal_service_vercel_blob.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→2 opendal_service_s3.core depends on opendal_core.raw.operation✕
Type pairs
2 distinct (type in opendal_service_s3.core → type in opendal_core.raw.operation) references.
opendal_service_s3.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_s3.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→4 opendal_service_s3.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_s3.core → type in opendal_core.types.context.operation) reference.
opendal_service_s3.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_s3.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→7 opendal_service_s3.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_s3.core → type in opendal_cpp.ffi) reference.
opendal_service_s3.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_s3.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→14 opendal_service_s3.core depends on opendal_core.raw.ops✕
Type pairs
5 distinct (type in opendal_service_s3.core → type in opendal_core.raw.ops) references.
opendal_service_s3.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_s3.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→34 opendal_service_s3.core depends on opendal_service_cos.core✕
Type pairs
9 distinct (type in opendal_service_s3.core → type in opendal_service_cos.core) references.
opendal_service_tos.core uses opendal_core.types.bytes_range. Changing opendal_core.types.bytes_range can break opendal_service_tos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→4 opendal_service_tos.core depends on opendal_core.types.context.operation✕
Type pairs
1 distinct (type in opendal_service_tos.core → type in opendal_core.types.context.operation) reference.
opendal_service_tos.core uses opendal_core.types.context.operation. Changing opendal_core.types.context.operation can break opendal_service_tos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→7 opendal_service_tos.core depends on opendal_cpp.ffi✕
Type pairs
1 distinct (type in opendal_service_tos.core → type in opendal_cpp.ffi) reference.
opendal_service_tos.core uses opendal_service_memcached.binary. Changing opendal_service_memcached.binary can break opendal_service_tos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→14 opendal_service_tos.core depends on opendal_core.raw.ops✕
Type pairs
5 distinct (type in opendal_service_tos.core → type in opendal_core.raw.ops) references.
opendal_service_tos.core uses opendal_service_aliyun_drive.core. Changing opendal_service_aliyun_drive.core can break opendal_service_tos.core, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→34 opendal_service_tos.core depends on opendal_service_cos.core✕
Type pairs
7 distinct (type in opendal_service_tos.core → type in opendal_service_cos.core) references.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
629
High / Critical
A06:2021 — Vulnerable & Outdated Components
54
High / Critical
A02:2021 — Cryptographic Failures
3
High / Critical
Roadmap
First, establish a tested disaster recovery plan by documenting RTO/RPO and restore procedures, as backups alone are insufficient. Second, improve test coverage by adding tests for unreached production modules and ensure library stability by making types internal by default to protect the public API. Third, clean up dependencies by removing unused packages and explicitly declaring imports, while immediately resolving the leaked secret found in the configuration files.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download it.
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
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 — 372
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 — 908
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 — 287
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 4
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. 83 of 90 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 7 documentation/naming judgement(s) are LLM-assisted and labelled advisory. 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 — 90 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1531 of 1567 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
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.
D10 Test 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. The 111 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 159 test source file(s) (.rs, .go, .java, .py, .mjs, .js) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — 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 reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — unit: measured (0 flaky); JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in bindings/nodejs/): not included — the dependency install for bindings/nodejs/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
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 reliability for the vitest suite in bindings/nodejs/ was NOT MEASURED: the dependency install for bindings/nodejs/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D12 Dependency Hygiene — 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 repository has NuGet-managed production source (.cs), whose `<PackageReference>` dependencies are exactly what this dimension assesses — but `dotnet list package` returned no packages, so there was nothing to assess. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED. This is a gap in the analysis run (restore or project-load failed), not a verdict about this repository. Dependencies declared for the other ecosystems present here (.c, .cpp, .dart, .go, .hs, .java, .lua, .ml, .php, .py, .rb, .rs, .swift, .tsx, .zig) are not read yet either.
D14 License Compliance — 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. This repository declares a Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .rs (173,405 lines, 87% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 35 task marker(s) (TODO/FIXME/HACK/XXX) across 30 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D23 Boundary Type-Coupling — 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. At 190720 LoC spread over 6 projects this is a large multi-module system that clearly needs explicit bounded contexts. Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D32 Data Compliance (PII/GDPR) — 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. `bindings/nodejs/generated.d.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
Repo exclusion declarations: 16 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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
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.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (7): D19, D20, D21, D22, D24, D25, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was S3Builder::build at 32. A further 10 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 FastmetricsInterceptor::observe at 18 — they are counted neither in the figure above nor in this dimension's score. 8 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: core/layers/fastmetrics/src/lib.rs (FastmetricsInterceptor::observe at 18), core/layers/metrics/src/lib.rs (MetricsInterceptor::observe at 18), core/layers/otelmetrics/src/lib.rs (OtelMetricsInterceptor::observe at 18), core/layers/prometheus-client/src/lib.rs (PrometheusClientInterceptor::observe at 18), core/layers/prometheus/src/lib.rs (PrometheusInterceptor::observe at 18), and 3 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.
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 S3Builder finding(s) in Cyclomatic Complexity — start with backend.rs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Storage.init (cyclomatic 32) finding(s) in Cyclomatic Complexity — start with opendal.dart. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 local-images.localImages (cyclomatic 31) finding(s) in Cyclomatic Complexity — start with local-images.js. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 59 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 odev finding(s) in Cognitive Complexity — start with metadata.rs (2), docs.rs (2), python.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 2 opendal_service_webdav finding(s) in Cognitive Complexity — start with core.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 GdriveFlatLister finding(s) in Cognitive Complexity — start with lister.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 30 FileTooLong finding(s) in God Classes — start with core.rs (13), lib.rs (6), operator.rs (4). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 11 ClassTooLong finding(s) in God Classes — start with core.rs (7), operator.rs (2), backend.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 9 TooManyMethods finding(s) in God Classes — start with operator.rs (2), Operator.cs, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
540 duplicated block group(s) detected. A further 54 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 169 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 33 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with core.rs (15), backend.rs (6), lib.rs (3). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 29 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with core.rs (13), backend.rs (7), deleter.rs (2). — One of this dimension's main actionable groups (29 warning-level).
Resolve the 27 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with core.rs (9), backend.rs (5), operator.rs (3). — One of this dimension's main actionable groups (27 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 10Stronggated by 4 serious findings✓ 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.
130 production modules (Maven+Cargo+npm+Go+SwiftPM+RubyGems), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 115 of the 130 (the rest declare no modelled class or interface, export only macros, or have no source directory of their own).
Off the main sequence: opendal · ×4
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).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with store.rs. — One of this dimension's main actionable groups (1 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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 86 mechanizable ADR(s) are enforced: 84 by analyzers, 2 by tests. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.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.
1617 test methods: 1603 unit, 14 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 116 `it`/`test` case(s) across 17 test file(s) declaring at least one beside 222 .NET test method(s); its tier split is read from package names and paths only. The Rust suite contributes 881 `#[test]` function(s) across 210 file(s) declaring at least one; its unit/integration split is Cargo's own — 3 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. The Python suite contributes 201 test function(s) across 36 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 43 test case(s) across 3 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 1 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one. The java, swift suite(s) contribute 154 test method(s), read from the language model's own test census — every XCTest `test…` method on an XCTestCase, every swift-testing `@Test` and every JUnit/TestNG `@Test`-annotated method, which is those frameworks' own discovery rule. Their tier split is INFERRED from the test target's name and path only, not declared.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Stronggated by 4 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 111 tests. Measured on the C# suite only — at least 159 test source file(s) (.rs, .go, .java, .py, .mjs, .js) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: DeleteBehavior_DeletingMissingPath_IsAllowed · ×4bindings/dotnet/OpenDAL.Tests/Behavior/DeleteBehaviorTest.cs:68
What to do
Resolve the 4 No assertions finding(s) in Test Quality — start with DeleteBehaviorTest.cs (2), ListBehaviorTest.cs (2). — One of this dimension's main actionable groups (4 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 118 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 114 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Cargo manifest and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: core/services/s3/src/backend.rs (15×32=480); core/services/hf/src/core.rs (14×18=252); core/services/gcs/src/core.rs (12×17=204) Repeated repair below the complexity floor: core/services/hf/src/reader.rs (6 of 8 changes were fixes); scripts/release_lifecycle.py (6 of 6 changes were fixes); core/services/gcs/src/writer.rs (5 of 8 changes were fixes)
Resolve the 14 Repeated repair finding(s) in Churn × Complexity Hotspots — start with config.rs (3), backend.rs (2), core.rs (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 12 Hotspot finding(s) in Churn × Complexity Hotspots — start with lister.rs (6), backend.rs (3), core.rs (3). — One of this dimension's main actionable groups (12 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.
51 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is bindings/dotnet/OpenDAL/Operator.cs. Counted over 596 of the 951 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted debt markers + 0 dead symbols across 11276 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .rs (87% of production source) was not read, and carries at least 35 uncounted task marker(s) in 30 file(s).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is a clear one-line overview of Apache OpenDAL (the 'One Layer, All Storage' data-access layer) with links to the vision, architecture, and branding pages. It documents each directory as its own README: the bindings/README.md explains what it contains without referencing the root repo; core/README.md gives an in-depth Rust core description including a build section, quickstart, useful links, and license info; website/README.md is a separate site README covering installation, local dev, build, LLM docs, and image-resolver rules; and each bindings subdir's README documents its own directory. The architecture/design docs are not shown in the summary but the outline lists them as present, so they are assumed present rather than missing. A comprehensive set of READMEs for each binding (Go, Haskell, Java, Lua, MoonBit, Node.js, OCaml, PHP, Python, Ruby) that document their respective directories rather than the repository root. Each directory's README is clear and complete: it names itself, states what it provides, gives installation commands, a quickstart example, links to the user guide, API docs, upgrade guides, and contributes sections for contributors and licensing. The architecture/Docs markdown files (162) provide design documentation that the READMEs do not cover; these are separate from the per-directory READMEs and should be judged against them. The OpenDAL Swift and Zig bindings are documented with focused READMEs for their respective directories (each ~300 words), covering installation, build commands, a quickstart example, and contributing guidance. The root repository has no overview, install/usage/contribution sections; the two directory READMEs alone cover the project's scope and usage. Architecture/design docs are present but not shown in this summary.
Documentation: no contributor guidancebindings/go/README.md
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityStrong◐ Sampled · advisory
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.
Evaluated 89 ADR(s) individually; mean quality 8.5/10 (consistently complete and clear). 6 flagged with a specific gap.
No consequences/trade-offs section; the decision is stated but no negative impact or alternative trade-off is noted · ×2core/core/src/docs/rfcs/2774_lister_api.md
No consequences/trade-offs section (e.g. API surface growth, cost of the new AccessorCapability enum)core/core/src/docs/rfcs/0409_accessor_capabilities.md
No consequences/trade-offs section; the body is a boilerplate guide-level explanation and reference-level API signature with no discussion of cost or trade-offscore/core/src/docs/rfcs/0429_init_from_iter.md
No consequences/trade-offs section; the body is a guide-level install list with no discussion of how oay behaves when opendal changes or what happens if oay outdates opendalcore/core/src/docs/rfcs/0443_gateway.md
Rationale and alternatives are both empty; the decision is stated but no trade-offs or future work discussedcore/core/src/docs/rfcs/3232_align_list_api.md
What to do
Resolve the 2 No consequences/trade-offs section; the decision is stated but no… finding(s) in ADR Quality — start with 2774_lister_api.md, 3356_lazy_reader.md. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 No consequences/trade-offs section (e.g. API surface growth, cost of the… finding(s) in ADR Quality — start with 0409_accessor_capabilities.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No consequences/trade-offs section; the body is a boilerplate… finding(s) in ADR Quality — start with 0429_init_from_iter.md. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStrong◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
3 API inconsistencies across a 400-member sample of 385 exposed types.
Redundant naming convention. The `Operator` type exposes both `copier` and `copier_options`. While this follows the existing pattern of `read`/`read_options` and `writer`/`writer_options`, the suffix `_options` is verbose and inconsistent with common Rust idioms where builder patterns or distinct method names (like `copier_with`) are preferred. More critically, it duplicates the intent of configuring the copy operation, just like `copy` vs `copy_options`.
Inconsistent deletion API surface. `Operator` provides simple `delete` and `delete_options` methods, but also exposes `delete_iter` and `delete_try_iter` for batch operations. Meanwhile, `Deleter` (a separate type) also has `delete`, `delete_iter`, and `delete_try_iter`. This creates confusion: should the user call `op.delete()` for single items and `op.deleter().delete_iter()` for batches, or is there a direct batch method on `Operator`? The existence of `delete_iter` on both `Operator` and `Deleter` suggests overlapping functionality.
Inconsistent naming with `copy`. `Operator` has `copy` and `copy_options`, but also `copier` and `copier_options`. For rename, it only has `rename` and `rename_options`. This inconsistency in method naming (`_options` vs `_options` vs implicit builder) makes the API harder to memorize. Specifically, `copier` returns a `Copier` type, while `rename` is a direct call. This asymmetry between copy (streaming/batch capable via Copier) and rename (direct) is a design inconsistency.
What to do
Resolve the 1 Redundant naming convention. The `Operator` type exposes both `copier`… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent deletion API surface. `Operator` provides simple `delete`… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent naming with `copy`. `Operator` has `copy` and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
663 finding(s): 0 critical, 348 high, 10 medium, 305 low. 267 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 5 file(s) — `bindings/java/mvnw` (lines 204–205, line 257), `bindings/nodejs/generated.d.ts` (line 25), `core/services/gdrive/src/path_index.rs` (line 290), `core/services/hf/src/reader.rs` (line 152), `core/services/seafile/src/core.rs` (line 78) — 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 40 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) charged to Static Analysis (SAST) — the other 267 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (279 issue-level, 12 of them charged here).
Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
19 of 596 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/edge/opfs_wasm32/src/lib.rs. Counted over 596 of the 951 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned files with no living knowledge
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 26 Change coupling finding(s) in Change Coupling — start with backend.rs (11), lib.rs (4), lister.rs (3). — One of this dimension's main actionable groups (26 warning-level).
Resolve the 7 Change-coupling hub finding(s) in Change Coupling — start with backend.rs (3), lib.rs (2), lister.rs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 15 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.
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.
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.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ 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.
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?
DM4 · Rich vs anemic domain model8.0 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`Capability` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside. — bindings/python/src/capability.rs:29
What to do
Move the domain logic onto the entity (invariant-enforcing `&mut self` commands) instead of a foreign service.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
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
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — 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 3 of 3 project(s) that lack one — worth up to 2 pts.
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.
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 & versioning6.0 / 10Adequate✓ Tool-verified
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.
182/246 types (74%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
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
Dependabot is configured but does not watch `nuget`, `pip`, `maven` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download it.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
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.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 23 use(s) across 11,368 production line(s) (~2.0/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
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) or inside a Java method returning a Reactor Mono/Flux — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`run` holds an async function that calls statSync, readSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bindings/nodejs/tests/suites/sync.suite.mjs:25
`servicesDocsPlugin` holds an async function that calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — website/plugins/services-docs-plugin.js:38
`includeSpecifications` is async and calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — website/plugins/specifications-docs-plugin.js:69
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety0.4 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
1 typed · 22 plain JS — the untyped files are bindings/nodejs/index.cjs, bindings/nodejs/index.mjs, bindings/nodejs/scripts/header.mjs, bindings/nodejs/tests/service.test.mjs, bindings/nodejs/tests/suites/async.suite.mjs, bindings/nodejs/tests/suites/asyncDeleteOptions.suite.mjs (+16 more).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
bindings/nodejs/index.cjs:24 · bindings/nodejs/index.mjs:24 — these 2 files are line-for-line copies of one another — 68 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — bindings/nodejs/index.cjs:24
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage2.5 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — bindings/nodejs/index.cjs, bindings/nodejs/scripts/header.mjs, bindings/nodejs/theme/index.tsx
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
24 file(s) (~3375 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: bindings/nodejs/index.d.ts imports './generated', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — bindings/nodejs
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — bindings/nodejs/theme/index.tsx:20
Declared in bindings/nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · 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.
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. Deterministic, provable per finding. Advisory.
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.
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. 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. Deterministic, provable per finding. Advisory.
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. Deterministic, provable per finding. Advisory.
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. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
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.
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.
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. 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. Deterministic, provable per finding. Advisory.
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. 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. Deterministic, provable per finding. Advisory.
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. 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 `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` 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. Deterministic, provable per finding. Advisory.
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?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
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. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.2 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 29313 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
AXH1 Runtime security headers — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXI1 Runtime container hardening — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test reliability not measured — polyglot suite, one half not re-run
D12 Dependency Hygiene — Dependency hygiene not measured — no packages were read
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .c, .cpp, .dart, .go, .hs, .java, .lua, .ml, .php, .py, .rb, .rs, .swift, .tsx, .zig, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — bindings/nodejs/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
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
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D30 · Dependency Vulnerabilities· High vulnerability · ×1
REDACTED
DM4 · Rich vs anemic domain model· Anemic domain model · ×1
Anemic domain model: Capability bindings/python/src/capability.rs:29— `Capability` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside.
Unlisted import 'react' bindings/nodejs/theme/index.tsx:20— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Duplicated block (8 lines × 2) bindings/dotnet/src/operator.rs:829— bindings/dotnet/src/operator.rs:829-836 | bindings/dotnet/src/operator.rs:2290-2297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/layers/dtrace/src/lib.rs:342— core/layers/dtrace/src/lib.rs:342-349 | core/layers/dtrace/src/lib.rs:381-388 — both copies are in the same file, so extract the block into 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) core/layers/fastmetrics/src/lib.rs:173— core/layers/fastmetrics/src/lib.rs:173-180 | core/layers/prometheus-client/src/lib.rs:117-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/services/azblob/src/backend.rs:305— core/services/azblob/src/backend.rs:305-312 | core/services/azdls/src/backend.rs:250-257 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/azdls/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 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) core/services/azblob/src/core.rs:668— core/services/azblob/src/core.rs:668-675 | core/services/s3/src/core.rs:799-807 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/services/azblob/src/core.rs:803— core/services/azblob/src/core.rs:803-810 | core/services/gcs/src/core.rs:547-554 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 83 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) core/services/cos/src/core.rs:530— core/services/cos/src/core.rs:530-540 | core/services/s3/src/core.rs:1289-1296 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 91 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) core/services/dropbox/src/core.rs:184— core/services/dropbox/src/core.rs:184-191 | core/services/dropbox/src/core.rs:208-215 — both copies are in the same file, so extract the block into 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) core/services/dropbox/src/core.rs:251— core/services/dropbox/src/core.rs:251-258 | core/services/dropbox/src/core.rs:276-283 — both copies are in the same file, so extract the block into 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) core/services/gcs/src/core.rs:404— core/services/gcs/src/core.rs:404-411 | core/services/gcs/src/core.rs:837-844 — both copies are in the same file, so extract the block into 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) core/services/http/src/core.rs:171— core/services/http/src/core.rs:171-178 | core/services/obs/src/core.rs:708-715 — before extracting anything, compare `core/services/http/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 5 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 (8 lines × 2) core/services/ipfs/src/core.rs:60— core/services/ipfs/src/core.rs:60-67 | core/services/webdav/src/core.rs:214-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/services/onedrive/src/core.rs:194— core/services/onedrive/src/core.rs:194-201 | core/services/onedrive/src/core.rs:251-258 — both copies are in the same file, so extract the block into 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) core/services/pcloud/src/backend.rs:359— core/services/pcloud/src/backend.rs:359-366 | core/services/pcloud/src/core.rs:145-152 — 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) core/services/pcloud/src/core.rs:145— core/services/pcloud/src/core.rs:145-152 | core/services/pcloud/src/writer.rs:49-56 — 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) core/services/pcloud/src/deleter.rs:48— core/services/pcloud/src/deleter.rs:48-55 | core/services/pcloud/src/writer.rs:49-56 — 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) core/services/redis/src/reader.rs:39— core/services/redis/src/reader.rs:39-46 | core/services/sqlite/src/reader.rs:40-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/services/webdav/src/core.rs:341— core/services/webdav/src/core.rs:341-348 | core/services/webdav/src/core.rs:376-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) dev/src/release/package.rs:325— dev/src/release/package.rs:325-332 | dev/src/release/package.rs:459-469 — both copies are in the same file, so extract the block into 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) bindings/nodejs/src/lib.rs:966— bindings/nodejs/src/lib.rs:966-973 | bindings/python/src/metadata.rs:157-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/services/hdfs/src/backend.rs:99— core/services/hdfs/src/backend.rs:99-106 | core/services/webhdfs/src/backend.rs:125-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/services/rocksdb/src/lister.rs:32— core/services/rocksdb/src/lister.rs:32-39 | core/services/sled/src/lister.rs:32-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) bindings/c/src/entry.rs:92— bindings/c/src/entry.rs:92-99 | bindings/c/src/metadata.rs:106-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) bindings/c/src/lister.rs:86— bindings/c/src/lister.rs:86-93 | bindings/c/src/writer.rs:135-142 — 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) core/services/dashmap/src/backend.rs:172— core/services/dashmap/src/backend.rs:172-179 | core/services/moka/src/backend.rs:302-309 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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.
FileTooLong: src/operator.rs bindings/dotnet/src/operator.rs— FileTooLong — 1447 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 106 free functions. The bar is 500 significant lines; this is 947 over it, 2.89× 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/core.rs core/services/s3/src/core.rs— FileTooLong — 1119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: S3Core (4 blocks, 95-1470). The bar is 500 significant lines; this is 619 over it, 2.24× 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/core.rs core/services/gcs/src/core.rs— FileTooLong — 1014 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: GcsCore (4 blocks, 67-1089). The bar is 500 significant lines; this is 514 over it, 2.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/operator.rs bindings/python/src/operator.rs— FileTooLong — 1013 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 513 over it, 2.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/core.rs core/services/hf/src/core.rs— FileTooLong — 876 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 376 over it, 1.75× 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/types.rs bindings/c/src/types.rs— FileTooLong — 841 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 341 over it, 1.68× 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: operator/operator.rs core/core/src/types/operator/operator.rs— FileTooLong — 841 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: Operator (5 blocks, 196-2828). The bar is 500 significant lines; this is 341 over it, 1.68× 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 core/layers/observe-metrics-common/src/lib.rs— FileTooLong — 835 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 335 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: raw/ops.rs core/core/src/raw/ops.rs— FileTooLong — 834 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 334 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/core.rs core/services/tos/src/core.rs— FileTooLong — 833 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: TosCore (3 blocks, 61-917). The bar is 500 significant lines; this is 333 over it, 1.67× 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/core.rs core/services/azblob/src/core.rs— FileTooLong — 774 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 69% of them inside a single declaration: AzblobCore (4 blocks, 75-884). The bar is 500 significant lines; this is 274 over it, 1.55× 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/backend.rs core/services/s3/src/backend.rs— FileTooLong — 774 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: S3Builder (4 blocks, 82-1166). The bar is 500 significant lines; this is 274 over it, 1.55× 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/core.rs core/services/oss/src/core.rs— FileTooLong — 668 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 168 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs core/layers/retry/src/lib.rs— FileTooLong — 658 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 158 over it, 1.32× 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/core.rs core/services/gdrive/src/core.rs— FileTooLong — 654 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 154 over it, 1.31× 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/core.rs core/services/aliyun-drive/src/core.rs— FileTooLong — 625 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: AliyunDriveCore (3 blocks, 61-615). The bar is 500 significant lines; this is 125 over it, 1.25× 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: OpenDAL/Operator.cs bindings/dotnet/OpenDAL/Operator.cs— FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 122 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs core/layers/logging/src/lib.rs— FileTooLong — 603 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 103 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/core.rs core/services/b2/src/core.rs— FileTooLong — 574 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: B2Core (4 blocks, 46-654). The bar is 500 significant lines; this is 74 over it, 1.15× 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/core.rs core/services/webdav/src/core.rs— FileTooLong — 571 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 71 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/operator.rs bindings/c/src/operator.rs— FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 31 free functions. The bar is 500 significant lines; this is 67 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/core.rs core/services/azdls/src/core.rs— FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: AzdlsCore (4 blocks, 51-621). The bar is 500 significant lines; this is 56 over it, 1.11× 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/store.rs integrations/object_store/src/store.rs— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: OpendalStore (6 blocks, 182-755). The bar is 500 significant lines; this is 53 over it, 1.11× 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: REDACTED REDACTED— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 51 over it, 1.10× 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/lib.rs core/layers/tail-cut/src/lib.rs— FileTooLong — 547 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 47 over it, 1.09× 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.
Duplicated block (9 lines × 2) bindings/dotnet/src/operator.rs:919— bindings/dotnet/src/operator.rs:919-927 | bindings/dotnet/src/operator.rs:1006-1014 — both copies are in the same file, so extract the block into 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) bindings/python/src/options.rs:178— bindings/python/src/options.rs:178-186 | bindings/python/src/options.rs:198-206 — both copies are in the same file, so extract the block into 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) core/core/src/raw/http_util/multipart.rs:225— core/core/src/raw/http_util/multipart.rs:225-233 | core/core/src/raw/http_util/multipart.rs:391-401 — both copies are in the same file, so extract the block into 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) core/core/src/types/delete/futures_delete_sink.rs:98— core/core/src/types/delete/futures_delete_sink.rs:98-106 | core/core/src/types/delete/futures_delete_sink.rs:131-139 — both copies are in the same file, so extract the block into 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) core/services/azblob/src/core.rs:670— core/services/azblob/src/core.rs:670-678 | core/services/azblob/src/core.rs:800-808 — both copies are in the same file, so extract the block into 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) core/services/azfile/src/backend.rs:167— core/services/azfile/src/backend.rs:167-175 | core/services/dbfs/src/backend.rs:85-93 — 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) core/services/b2/src/backend.rs:114— core/services/b2/src/backend.rs:114-122 | core/services/upyun/src/backend.rs:106-114 — before extracting anything, compare `core/services/b2/src/backend.rs` and `core/services/upyun/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) core/services/cos/src/backend.rs:170— core/services/cos/src/backend.rs:170-178 | core/services/obs/src/backend.rs:138-146 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/obs/src/backend.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 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) core/services/dropbox/src/core.rs:301— core/services/dropbox/src/core.rs:301-309 | core/services/dropbox/src/core.rs:328-336 — both copies are in the same file, so extract the block into 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) core/services/onedrive/src/writer.rs:82— core/services/onedrive/src/writer.rs:82-90 | core/services/onedrive/src/writer.rs:141-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 (9 lines × 2) core/services/oss/src/core.rs:321— core/services/oss/src/core.rs:321-329 | core/services/oss/src/core.rs:415-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 (9 lines × 2) core/services/s3/src/backend.rs:1428— core/services/s3/src/backend.rs:1428-1438 | core/services/tos/src/backend.rs:443-451 — before extracting anything, compare `core/services/s3/src/backend.rs` and `core/services/tos/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) core/services/tos/src/core.rs:694— core/services/tos/src/core.rs:694-702 | core/services/tos/src/core.rs:740-748 — both copies are in the same file, so extract the block into 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) core/services/webhdfs/src/core.rs:183— core/services/webhdfs/src/core.rs:183-191 | core/services/webhdfs/src/core.rs:342-350 — both copies are in the same file, so extract the block into 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) core/core/src/raw/std_io_util.rs:57— core/core/src/raw/std_io_util.rs:57-65 | core/core/src/types/error.rs:519-527 — 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) core/services/rocksdb/src/backend.rs:175— core/services/rocksdb/src/backend.rs:175-183 | core/services/sled/src/backend.rs:199-207 — before extracting anything, compare `core/services/rocksdb/src/backend.rs` and `core/services/sled/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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) core/core/src/layers/simulate.rs:506— core/core/src/layers/simulate.rs:506-514 | core/core/src/raw/oio/list/flat_list.rs:98-109 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) core/services/cloudflare-kv/src/deleter.rs:83— core/services/cloudflare-kv/src/deleter.rs:83-92 | core/services/s3/src/deleter.rs:71-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.
Duplicated block (9 lines × 2) core/services/mongodb/src/backend.rs:119— core/services/mongodb/src/backend.rs:119-127 | core/services/mongodb/src/backend.rs:135-143 — both copies are in the same file, so extract the block into 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) core/services/b2/src/core.rs:596— core/services/b2/src/core.rs:596-604 | core/services/b2/src/core.rs:627-635 — both copies are in the same file, so extract the block into 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) core/services/gdrive/src/deleter.rs:69— core/services/gdrive/src/deleter.rs:69-77 | core/services/gdrive/src/deleter.rs:101-109 — both copies are in the same file, so extract the block into 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) core/services/b2/src/core.rs:440— core/services/b2/src/core.rs:440-448 | core/services/b2/src/core.rs:472-480 — both copies are in the same file, so extract the block into 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) core/services/upyun/src/core.rs:363— core/services/upyun/src/core.rs:363-371 | core/services/upyun/src/core.rs:432-440 — both copies are in the same file, so extract the block into 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) core/services/b2/src/core.rs:180— core/services/b2/src/core.rs:180-188 | core/services/b2/src/core.rs:374-382 — both copies are in the same file, so extract the block into 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) core/services/azdls/src/core.rs:474— core/services/azdls/src/core.rs:474-482 | core/services/azdls/src/core.rs:520-528 — both copies are in the same file, so extract the block into 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) bindings/c/src/operator.rs:995— bindings/c/src/operator.rs:995-1004 | bindings/c/src/operator.rs:1044-1053 — both copies are in the same file, so extract the block into 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) bindings/c/src/operator.rs:1113— bindings/c/src/operator.rs:1113-1122 | bindings/c/src/operator.rs:1179-1188 — both copies are in the same file, so extract the block into 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) bindings/c/src/operator.rs:1490— bindings/c/src/operator.rs:1490-1499 | bindings/c/src/operator.rs:1534-1543 — both copies are in the same file, so extract the block into 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) bindings/java/src/async_operator.rs:504— bindings/java/src/async_operator.rs:504-513 | bindings/java/src/operator.rs:335-344 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) bindings/python/src/file.rs:496— bindings/python/src/file.rs:496-505 | bindings/python/src/file.rs:642-651 — both copies are in the same file, so extract the block into 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) core/core/src/raw/oio/copy/block_copy.rs:128— core/core/src/raw/oio/copy/block_copy.rs:128-137 | core/core/src/raw/oio/copy/multipart_copy.rs:154-166 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. 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) core/core/src/types/write/buffer_sink.rs:91— core/core/src/types/write/buffer_sink.rs:91-100 | core/core/src/types/write/buffer_sink.rs:138-147 — both copies are in the same file, so extract the block into 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) core/services/cos/src/deleter.rs:43— core/services/cos/src/deleter.rs:43-52 | core/services/obs/src/deleter.rs:42-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) core/services/d1/src/core.rs:151— core/services/d1/src/core.rs:151-160 | core/services/d1/src/core.rs:170-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 (10 lines × 2) core/services/gcs/src/core.rs:629— core/services/gcs/src/core.rs:629-638 | core/services/oss/src/core.rs:425-434 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) core/services/lakefs/src/core.rs:64— core/services/lakefs/src/core.rs:64-73 | core/services/lakefs/src/core.rs:96-105 — both copies are in the same file, so extract the block into 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) core/services/lakefs/src/core.rs:176— core/services/lakefs/src/core.rs:176-185 | core/services/lakefs/src/core.rs:241-250 — both copies are in the same file, so extract the block into 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) core/services/mysql/src/backend.rs:131— core/services/mysql/src/backend.rs:131-140 | core/services/postgresql/src/backend.rs:125-134 — before extracting anything, compare `core/services/mysql/src/backend.rs` and `core/services/postgresql/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) core/services/oss/src/core.rs:338— core/services/oss/src/core.rs:338-348 | core/services/s3/src/core.rs:575-584 — before extracting anything, compare `core/services/oss/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) core/services/pcloud/src/backend.rs:357— core/services/pcloud/src/backend.rs:357-366 | core/services/pcloud/src/deleter.rs:46-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 (10 lines × 2) core/services/redis/src/reader.rs:60— core/services/redis/src/reader.rs:60-69 | core/services/sqlite/src/reader.rs:58-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) core/core/src/raw/oio/copy/block_copy.rs:172— core/core/src/raw/oio/copy/block_copy.rs:172-181 | core/core/src/raw/oio/copy/multipart_copy.rs:197-206 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. 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) core/services/cos/src/lister.rs:49— core/services/cos/src/lister.rs:49-58 | core/services/obs/src/lister.rs:45-55 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) core/services/s3/src/core.rs:893— core/services/s3/src/core.rs:893-902 | core/services/s3/src/core.rs:942-954 — both copies are in the same file, so extract the block into 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) core/services/alluxio/src/core.rs:60— core/services/alluxio/src/core.rs:60-70 | core/services/alluxio/src/core.rs:98-107 — both copies are in the same file, so extract the block into 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) core/services/upyun/src/core.rs:193— core/services/upyun/src/core.rs:193-202 | core/services/upyun/src/core.rs:355-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 (10 lines × 2) core/services/dbfs/src/backend.rs:165— core/services/dbfs/src/backend.rs:165-174 | core/services/ipmfs/src/backend.rs:187-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) core/services/swift/src/core.rs:272— core/services/swift/src/core.rs:272-281 | core/services/swift/src/core.rs:453-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.
Duplicated block (10 lines × 2) core/services/gdrive/src/backend.rs:290— core/services/gdrive/src/backend.rs:290-299 | core/services/gdrive/src/backend.rs:567-576 — both copies are in the same file, so extract the block into 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) core/services/koofr/src/backend.rs:377— core/services/koofr/src/backend.rs:377-386 | core/services/upyun/src/backend.rs:326-335 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/upyun/src/backend.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 68 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.
Change coupling: operator_info.rs ↔ REDACTED bindings/c/src/operator_info.rs— `bindings/c/src/operator_info.rs` and `REDACTED` 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `62d8866f` feat(REDACTED): add copy options (#7707); `6d0e75db` feat(REDACTED): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/azdls/src/backend.rs— `core/services/azdls/src/backend.rs` and `core/services/azfile/src/backend.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d5dd6dfa` fix: repair azfile, b2, and conditional read behavior (#8175); `15fd535c` test: Add suffix read behavior tests (#7739); `0f45d6af` refactor(core): route reqsign send via accessor http client (#7234) — run `git show` on any of them.
Change coupling: lib.rs ↔ lib.rs core/layers/await-tree/src/lib.rs— `core/layers/await-tree/src/lib.rs` and `core/layers/fastrace/src/lib.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4196c1fe` fix(layers): wrap copier with all layers (#7596); `ebcdfb4c` refactor!: Refactor oio::Delete to make it's API simple (#6823) (at that commit the files were still `core/src/layers/await_tree.rs` and `core/src/layers/fastrace.rs`); `13c3214d` refactor(core)!: Merge operations to build more clean metrics (#5892) (at that commit the files were still `core/src/layers/await_tree.rs` and `core/src/layers/fastrace.rs`) — run `git show` on any of them.
Change coupling: operator_info.rs ↔ types.rs bindings/c/src/operator_info.rs— `bindings/c/src/operator_info.rs` and `bindings/c/src/types.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `62d8866f` feat(REDACTED): add copy options (#7707); `6d0e75db` feat(REDACTED): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/mysql/src/backend.rs— `core/services/mysql/src/backend.rs` and `core/services/postgresql/src/backend.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `311f324c` fix(services): improve stat implementation (#7857); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/postgresql/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/postgresql/backend.rs`) — run `git show` on any of them.
Change coupling: types.rs ↔ REDACTED bindings/c/src/types.rs— `bindings/c/src/types.rs` and `REDACTED` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `62d8866f` feat(REDACTED): add copy options (#7707); `6d0e75db` feat(REDACTED): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
Change coupling: lister.rs ↔ lister.rs core/services/gcs/src/lister.rs— `core/services/gcs/src/lister.rs` and `core/services/obs/src/lister.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 — 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 `09b0672f` fix(core): List root should not return itself (#3824) (at that commit the files were still `core/src/services/gcs/lister.rs` and `core/src/services/obs/lister.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/gcs/dir_stream.rs` and `src/services/obs/dir_stream.rs`); `c2147124` feat: Implement object page stream for services like s3 (#787) (at that commit the files were still `src/services/gcs/dir_stream.rs` and `src/services/obs/dir_stream.rs`) — run `git show` on any of them.
Change coupling: lib.rs ↔ lib.rs core/layers/concurrent-limit/src/lib.rs— `core/layers/concurrent-limit/src/lib.rs` and `core/layers/retry/src/lib.rs` change together 62% of the time (18 of the 29 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 18 shared commits counted here, the most recent 3 are `ebcdfb4c` refactor!: Refactor oio::Delete to make it's API simple (#6823) (at that commit the files were still `core/src/layers/concurrent_limit.rs` and `core/src/layers/retry.rs`); `0805ddd1` chore(layers): check the examples when running tests (#5104) (at that commit the files were still `core/src/layers/concurrent_limit.rs` and `core/src/layers/retry.rs`); `1ec735ec` feat: add Writer::abort method (#1937) (at that commit the files were still `core/src/layers/concurrent_limit.rs` and `core/src/layers/retry.rs`) — run `git show` on any of them.
Change coupling: backend.rs ↔ lister.rs core/services/fs/src/backend.rs— `core/services/fs/src/backend.rs` and `core/services/fs/src/lister.rs` change together 61% of the time (11 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `cd2fc9ff` refactor: Remove metakey concept (#5319) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/fs/lister.rs`); `87e98ef7` feat(fs): expose the metadata for fs services (#5005) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/fs/lister.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/fs/backend.rs` and `src/services/fs/dir_stream.rs`) — run `git show` on any of them.
Change coupling: lister.rs ↔ lister.rs core/services/azblob/src/lister.rs— `core/services/azblob/src/lister.rs` and `core/services/gcs/src/lister.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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `09b0672f` fix(core): List root should not return itself (#3824) (at that commit the files were still `core/src/services/azblob/lister.rs` and `core/src/services/gcs/lister.rs`); `42ad2dd7` refactor: Use chrono instead of time to work well with ecosystem (#1912) (at that commit the files were still `core/src/services/azblob/pager.rs` and `core/src/services/gcs/pager.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/azblob/dir_stream.rs` and `src/services/gcs/dir_stream.rs`) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/fs/src/backend.rs— `core/services/fs/src/backend.rs` and `core/services/hdfs/src/backend.rs` change together 60% of the time (43 of the 72 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 43 shared commits counted here, the most recent 3 are `b94d02e0` refactor(core): lazy open positioned read handles (#7796); `577912df` refactor: remove uuid dependency when creating a temp path (#6324) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/hdfs/backend.rs`); `c00f0fdd` refactor(raw/oio): Reorganize to allow adding more features (#2698) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/hdfs/backend.rs`) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/rocksdb/src/backend.rs— `core/services/rocksdb/src/backend.rs` and `core/services/sled/src/backend.rs` change together 59% of the time (10 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `15d6d484` Set shared capability of Mini Moka and OPFS (#7856); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/rocksdb/backend.rs` and `core/src/services/sled/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/rocksdb/backend.rs` and `core/src/services/sled/backend.rs`) — run `git show` on any of them.
Change coupling: lib.rs ↔ lib.rs core/layers/concurrent-limit/src/lib.rs— `core/layers/concurrent-limit/src/lib.rs` and `core/layers/metrics/src/lib.rs` change together 59% of the time (17 of the 29 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `0805ddd1` chore(layers): check the examples when running tests (#5104) (at that commit the files were still `core/src/layers/concurrent_limit.rs` and `core/src/layers/metrics.rs`); `1ec735ec` feat: add Writer::abort method (#1937) (at that commit the files were still `core/src/layers/concurrent_limit.rs` and `core/src/layers/metrics.rs`); `f2f013e0` refactor: Polish the implement details for Writer (#1445) (at that commit the files were still `src/layers/concurrent_limit.rs` and `src/layers/metrics.rs`) — run `git show` on any of them.
Change coupling: async_operator.rs ↔ operator.rs bindings/java/src/async_operator.rs— `bindings/java/src/async_operator.rs` and `bindings/java/src/operator.rs` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 `06235da7` refactor: Deprecate remove_all API in favor of RFC-3911: Deleter API …; `a612f32a` feat(bindings/java): Add StatOptions support for new options API (#6255); `7c6e970f` feat(bindings/java): Add ListOptions support for new options API (#6246) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/gcs/src/backend.rs— `core/services/gcs/src/backend.rs` and `core/services/obs/src/backend.rs` change together 57% of the time (46 of the 81 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 46 shared commits counted here, the most recent 3 are `0f45d6af` refactor(core): route reqsign send via accessor http client (#7234); `bb145e66` feat: Add from_uri support for more object storage services (#6665) (at that commit the files were still `core/src/services/gcs/backend.rs` and `core/src/services/obs/backend.rs`); `83c9f916` refactor(core): Migrate MultipartWrite Executor to context based (#5835) (at that commit the files were still `core/src/services/gcs/backend.rs` and `core/src/services/obs/backend.rs`) — run `git show` on any of them.
Change coupling: lister.rs ↔ lister.rs core/services/azblob/src/lister.rs— `core/services/azblob/src/lister.rs` and `core/services/obs/src/lister.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 — 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 `09b0672f` fix(core): List root should not return itself (#3824) (at that commit the files were still `core/src/services/azblob/lister.rs` and `core/src/services/obs/lister.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/azblob/dir_stream.rs` and `src/services/obs/dir_stream.rs`); `9fdd2d6e` feat: Implement cached metadata for ObjectEntry (#761) (at that commit the files were still `src/services/azblob/dir_stream.rs` and `src/services/obs/dir_stream.rs`) — run `git show` on any of them.
Change coupling: operator.rs ↔ REDACTED bindings/c/src/operator.rs— `bindings/c/src/operator.rs` and `REDACTED` change together 55% of the time (11 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `2f395484` feat(binding/go): Add Copier (#7732); `dc006976` feat(binding/go): add write with metadata (#7827); `57307918` feat(binding/go): add reader with options (#7817) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/mysql/src/backend.rs— `core/services/mysql/src/backend.rs` and `core/services/sqlite/src/backend.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 — 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 `311f324c` fix(services): improve stat implementation (#7857); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/sqlite/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/sqlite/backend.rs`) — run `git show` on any of them.
Change coupling: operator.rs ↔ REDACTED bindings/c/src/operator.rs— `bindings/c/src/operator.rs` and `REDACTED` 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `62d8866f` feat(REDACTED): add copy options (#7707); `6d0e75db` feat(REDACTED): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/cloudflare-kv/src/backend.rs— `core/services/cloudflare-kv/src/backend.rs` and `core/services/redis/src/backend.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 — 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 `dcbf53ea` Reapply "fix(core): deserialize duration config values from strings" …; `399cfbf3` Revert "fix(core): deserialize duration config values from strings" (…; `188f0c07` fix(core): deserialize duration config values from strings (#7983) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/cloudflare-kv/src/backend.rs— `core/services/cloudflare-kv/src/backend.rs` and `core/services/memcached/src/backend.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 — 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 `dcbf53ea` Reapply "fix(core): deserialize duration config values from strings" …; `399cfbf3` Revert "fix(core): deserialize duration config values from strings" (…; `188f0c07` fix(core): deserialize duration config values from strings (#7983) — run `git show` on any of them.
Change coupling: lib.rs ↔ Operator.java bindings/java/src/lib.rs— `bindings/java/src/lib.rs` and `bindings/java/src/main/java/org/apache/opendal/Operator.java` change together 53% of the time (16 of the 30 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `a76040c6` feat: Binding Java's createInputStream and createOutputStream to supp…; `a612f32a` feat(bindings/java): Add StatOptions support for new options API (#6255); `0c44e07c` feat(java): add WriteOptions for write methods (#5664) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/redis/src/backend.rs— `core/services/redis/src/backend.rs` and `core/services/sled/src/backend.rs` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/redis/backend.rs` and `core/src/services/sled/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/redis/backend.rs` and `core/src/services/sled/backend.rs`); `52998792` refactor: kv::adapter should use Buffer (write part) (#4496) (at that commit the files were still `core/src/services/redis/backend.rs` and `core/src/services/sled/backend.rs`) — run `git show` on any of them.
Change coupling: config.rs ↔ core.rs core/services/s3/src/config.rs— `core/services/s3/src/config.rs` and `core/services/s3/src/core.rs` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `b25d98f3` feat(services/s3): Rename allow_anonymous to skip_signature (#7544); `77e74d05` feat(services/s3): Add a way to specify a default object ACL (#7186); `7f7583d8` refactor!: Migrate service s3 to reqsign-core 2.0 (#6656) (at that commit the files were still `core/src/services/s3/config.rs` and `core/src/services/s3/core.rs`) — run `git show` on any of them.
Change coupling: backend.rs ↔ backend.rs core/services/postgresql/src/backend.rs— `core/services/postgresql/src/backend.rs` and `core/services/sqlite/src/backend.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 — 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 `311f324c` fix(services): improve stat implementation (#7857); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/postgresql/backend.rs` and `core/src/services/sqlite/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/postgresql/backend.rs` and `core/src/services/sqlite/backend.rs`) — run `git show` on any of them.
Duplicated block (7 lines × 2) bindings/c/src/operator.rs:539— bindings/c/src/operator.rs:539-545 | bindings/c/src/operator.rs:668-674 — both copies are in the same file, so extract the block into 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) bindings/java/src/async_operator.rs:373— bindings/java/src/async_operator.rs:373-379 | bindings/java/src/async_operator.rs:413-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 (7 lines × 2) bindings/python/src/options.rs:106— bindings/python/src/options.rs:106-112 | bindings/python/src/options.rs:308-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) core/core/src/raw/ops.rs:534— core/core/src/raw/ops.rs:534-540 | core/core/src/raw/ops.rs:748-754 — both copies are in the same file, so extract the block into 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) core/layers/foyer/src/lib.rs:137— core/layers/foyer/src/lib.rs:137-143 | core/services/foyer/src/lib.rs:104-110 — 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) core/services/cos/src/backend.rs:180— core/services/cos/src/backend.rs:180-186 | core/services/obs/src/backend.rs:148-154 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/obs/src/backend.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 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) core/services/d1/src/core.rs:97— core/services/d1/src/core.rs:97-103 | core/services/d1/src/core.rs:121-127 — both copies are in the same file, so extract the block into 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) core/services/fs/src/backend.rs:85— core/services/fs/src/backend.rs:85-91 | core/services/monoiofs/src/backend.rs:65-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) core/services/gcs/src/reader.rs:55— core/services/gcs/src/reader.rs:55-61 | core/services/s3/src/reader.rs:52-58 — 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) core/services/gdrive/src/core.rs:274— core/services/gdrive/src/core.rs:274-280 | core/services/gdrive/src/core.rs:542-548 — both copies are in the same file, so extract the block into 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) core/services/tos/src/copier.rs:228— core/services/tos/src/copier.rs:228-234 | core/services/tos/src/writer.rs:179-185 — before extracting anything, compare `core/services/tos/src/copier.rs` and `core/services/tos/src/writer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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) core/services/upyun/src/backend.rs:252— core/services/upyun/src/backend.rs:252-258 | core/services/vercel-blob/src/backend.rs:202-208 — before extracting anything, compare `core/services/upyun/src/backend.rs` and `core/services/vercel-blob/src/backend.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 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) core/services/aliyun-drive/src/core.rs:324— core/services/aliyun-drive/src/core.rs:324-334 | core/services/aliyun-drive/src/core.rs:460-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) core/services/b2/src/core.rs:217— core/services/b2/src/core.rs:217-226 | core/services/b2/src/core.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 (7 lines × 2) core/services/azblob/src/backend.rs:347— core/services/azblob/src/backend.rs:347-354 | core/services/azblob/src/backend.rs:355-361 — both copies are in the same file, so extract the block into 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) core/services/b2/src/core.rs:162— core/services/b2/src/core.rs:162-169 | core/services/lakefs/src/core.rs:111-117 — 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) core/services/gdrive/src/core.rs:741— core/services/gdrive/src/core.rs:741-747 | core/services/onedrive/src/core.rs:785-791 — 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) core/services/seafile/src/backend.rs:138— core/services/seafile/src/backend.rs:138-144 | core/services/seafile/src/backend.rs:145-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) core/services/surrealdb/src/backend.rs:147— core/services/surrealdb/src/backend.rs:147-153 | core/services/surrealdb/src/backend.rs:154-160 — both copies are in the same file, so extract the block into 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) core/services/lakefs/src/core.rs:75— core/services/lakefs/src/core.rs:75-81 | core/services/lakefs/src/core.rs:155-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) core/services/azdls/src/config.rs:106— core/services/azdls/src/config.rs:106-112 | core/services/azfile/src/config.rs:81-87 — 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) core/core/src/raw/http_util/bytes_content_range.rs:168— core/core/src/raw/http_util/bytes_content_range.rs:168-174 | core/core/src/types/bytes_range.rs:345-351 — 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) core/services/s3/src/core.rs:887— core/services/s3/src/core.rs:887-893 | core/services/swift/src/core.rs:214-220 — 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) core/services/ghac/src/config.rs:69— core/services/ghac/src/config.rs:69-75 | core/services/swift/src/config.rs:85-91 — 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) core/services/hf/src/backend.rs:261— core/services/hf/src/backend.rs:261-267 | core/services/lakefs/src/backend.rs:132-138 — 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 (12 lines × 2) bindings/c/src/operator.rs:1422— bindings/c/src/operator.rs:1422-1433 | bindings/c/src/operator.rs:1521-1532 — both copies are in the same file, so extract the block into 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) bindings/nodejs/src/options.rs:218— bindings/nodejs/src/options.rs:218-229 | bindings/nodejs/src/options.rs:334-345 — both copies are in the same file, so extract the block into 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) bindings/python/src/operator.rs:346— bindings/python/src/operator.rs:346-357 | bindings/python/src/operator.rs:1109-1120 — both copies are in the same file, so extract the block into 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) core/core/src/raw/futures_util.rs:265— core/core/src/raw/futures_util.rs:265-276 | core/core/src/raw/futures_util.rs:308-319 — both copies are in the same file, so extract the block into 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) core/layers/tail-cut/src/lib.rs:327— core/layers/tail-cut/src/lib.rs:327-338 | core/layers/tail-cut/src/lib.rs:511-522 — both copies are in the same file, so extract the block into 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) core/services/b2/src/writer.rs:134— core/services/b2/src/writer.rs:134-145 | core/services/vercel-blob/src/writer.rs:110-121 — 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 (12 lines × 2) core/services/cos/src/core.rs:169— core/services/cos/src/core.rs:169-180 | core/services/oss/src/core.rs:366-377 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) core/services/cos/src/core.rs:189— core/services/cos/src/core.rs:189-200 | core/services/obs/src/core.rs:173-184 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) core/services/cos/src/core.rs:271— core/services/cos/src/core.rs:271-282 | core/services/oss/src/core.rs:437-448 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) core/services/etcd/src/reader.rs:48— core/services/etcd/src/reader.rs:48-59 | core/services/mini_moka/src/reader.rs:50-61 — 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 (12 lines × 2) core/services/gcs/src/core.rs:196— core/services/gcs/src/core.rs:196-207 | core/services/gcs/src/core.rs:265-276 — both copies are in the same file, so extract the block into 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) core/services/github/src/core.rs:287— core/services/github/src/core.rs:287-298 | core/services/github/src/core.rs:326-337 — both copies are in the same file, so extract the block into 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) core/services/http/src/backend.rs:117— core/services/http/src/backend.rs:117-128 | core/services/webdav/src/backend.rs:192-203 — before extracting anything, compare `core/services/http/src/backend.rs` and `core/services/webdav/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) core/services/koofr/src/core.rs:523— core/services/koofr/src/core.rs:523-534 | core/services/upyun/src/core.rs:619-630 — 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 (12 lines × 2) core/services/persy/src/core.rs:79— core/services/persy/src/core.rs:79-90 | core/services/persy/src/core.rs:115-126 — both copies are in the same file, so extract the block into 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) core/services/swift/src/writer.rs:46— core/services/swift/src/writer.rs:46-57 | core/services/webdav/src/writer.rs:46-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) core/services/upyun/src/core.rs:240— core/services/upyun/src/core.rs:240-251 | core/services/upyun/src/core.rs:275-286 — both copies are in the same file, so extract the block into 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) core/services/s3/src/backend.rs:865— core/services/s3/src/backend.rs:865-877 | core/services/s3/src/backend.rs:882-893 — both copies are in the same file, so extract the block into 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) core/services/azfile/src/core.rs:226— core/services/azfile/src/core.rs:226-237 | core/services/azfile/src/core.rs:250-262 — both copies are in the same file, so extract the block into 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) core/core/src/raw/oio/copy/block_copy.rs:294— core/core/src/raw/oio/copy/block_copy.rs:294-305 | core/core/src/raw/oio/copy/multipart_copy.rs:367-378 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. 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) core/services/koofr/src/deleter.rs:42— core/services/koofr/src/deleter.rs:42-53 | core/services/upyun/src/deleter.rs:42-53 — 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 (12 lines × 2) core/services/seafile/src/core.rs:422— core/services/seafile/src/core.rs:422-433 | core/services/vercel-blob/src/core.rs:306-317 — 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 (12 lines × 2) REDACTED:351— REDACTED:351-362 | REDACTED:366-377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:351` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:44— bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:44-55 | bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:85-96 — both copies are in the same file, so extract the 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (11 lines × 2) core/services/azblob/src/core.rs:156— core/services/azblob/src/core.rs:156-166 | core/services/oss/src/core.rs:105-115 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/services/cos/src/core.rs:145— core/services/cos/src/core.rs:145-155 | core/services/gcs/src/core.rs:240-250 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/services/cos/src/core.rs:927— core/services/cos/src/core.rs:927-937 | core/services/obs/src/core.rs:714-724 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/services/dbfs/src/core.rs:56— core/services/dbfs/src/core.rs:56-66 | core/services/dbfs/src/core.rs:85-95 — both copies are in the same file, so extract the block into 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) core/services/fs/src/writer.rs:118— core/services/fs/src/writer.rs:118-128 | core/services/fs/src/writer.rs:192-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 (11 lines × 2) core/services/gcs/src/core.rs:180— core/services/gcs/src/core.rs:180-190 | core/services/gcs/src/core.rs:574-584 — both copies are in the same file, so extract the block into 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) core/services/gdrive/src/lister.rs:171— core/services/gdrive/src/lister.rs:171-181 | core/services/gdrive/src/lister.rs:530-540 — both copies are in the same file, so extract the block into 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) core/services/github/src/lister.rs:65— core/services/github/src/lister.rs:65-75 | core/services/github/src/lister.rs:105-115 — both copies are in the same file, so extract the block into 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) core/services/mini_moka/src/backend.rs:99— core/services/mini_moka/src/backend.rs:99-109 | core/services/moka/src/backend.rs:161-171 — before extracting anything, compare `core/services/mini_moka/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/services/obs/src/backend.rs:423— core/services/obs/src/backend.rs:423-433 | core/services/oss/src/backend.rs:799-809 — before extracting anything, compare `core/services/obs/src/backend.rs` and `core/services/oss/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/services/s3/src/core.rs:578— core/services/s3/src/core.rs:578-588 | core/services/tos/src/core.rs:273-283 — 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) core/services/s3/src/writer.rs:83— core/services/s3/src/writer.rs:83-93 | core/services/s3/src/writer.rs:372-382 — both copies are in the same file, so extract the block into 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) core/services/webhdfs/src/core.rs:66— core/services/webhdfs/src/core.rs:66-76 | core/services/webhdfs/src/core.rs:100-110 — both copies are in the same file, so extract the block into 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) core/services/webhdfs/src/core.rs:297— core/services/webhdfs/src/core.rs:297-307 | core/services/webhdfs/src/core.rs:326-336 — both copies are in the same file, so extract the block into 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) dev/src/generate/options.rs:169— dev/src/generate/options.rs:169-179 | dev/src/generate/parser.rs:358-368 — 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) core/services/gcs/src/lister.rs:51— core/services/gcs/src/lister.rs:51-62 | core/services/oss/src/lister.rs:51-61 — 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) core/services/oss/src/deleter.rs:66— core/services/oss/src/deleter.rs:66-77 | core/services/s3/src/deleter.rs:71-81 — 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) core/services/dbfs/src/core.rs:144— core/services/dbfs/src/core.rs:144-154 | core/services/dbfs/src/core.rs:195-206 — both copies are in the same file, so extract the block into 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) core/services/swift/src/backend.rs:131— core/services/swift/src/backend.rs:131-141 | core/services/webhdfs/src/backend.rs:148-159 — before extracting anything, compare `core/services/swift/src/backend.rs` and `core/services/webhdfs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/core/src/types/operator/operator.rs:1488— core/core/src/types/operator/operator.rs:1488-1498 | core/core/src/types/operator/operator.rs:1534-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 (11 lines × 2) core/services/yandex-disk/src/core.rs:232— core/services/yandex-disk/src/core.rs:232-242 | core/services/yandex-disk/src/core.rs:261-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/services/swift/src/writer.rs:69— core/services/swift/src/writer.rs:69-79 | core/services/swift/src/writer.rs:152-162 — both copies are in the same file, so extract the block into 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) core/services/tos/src/core.rs:713— core/services/tos/src/core.rs:713-723 | core/services/tos/src/core.rs:756-766 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) REDACTED:286— REDACTED:286-296 | REDACTED:435-445 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:286` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:434` calls `Pointer` and `REDACTED:285` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) bindings/nodejs/src/lib.rs:335— bindings/nodejs/src/lib.rs:335-340 | bindings/nodejs/src/lib.rs:402-407 — both copies are in the same file, so extract the block into 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) core/layers/prometheus-client/src/lib.rs:220— core/layers/prometheus-client/src/lib.rs:220-225 | core/layers/prometheus-client/src/lib.rs:252-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 (6 lines × 2) core/services/aliyun-drive/src/backend.rs:339— core/services/aliyun-drive/src/backend.rs:339-344 | core/services/aliyun-drive/src/lister.rs:145-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) core/services/b2/src/core.rs:882— core/services/b2/src/core.rs:882-887 | core/services/s3/src/core.rs:2180-2185 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/compfs/src/backend.rs:64— core/services/compfs/src/backend.rs:64-69 | core/services/fs/src/backend.rs:82-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/cos/src/core.rs:923— core/services/cos/src/core.rs:923-928 | core/services/oss/src/core.rs:1234-1239 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) core/services/dashmap/src/writer.rs:53— core/services/dashmap/src/writer.rs:53-58 | core/services/mini_moka/src/writer.rs:52-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/dropbox/src/core.rs:552— core/services/dropbox/src/core.rs:552-557 | core/services/gdrive/src/core.rs:1120-1125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/foyer/src/backend.rs:271— core/services/foyer/src/backend.rs:271-276 | core/services/moka/src/backend.rs:252-258 — before extracting anything, compare `core/services/foyer/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) core/services/gcs/src/core.rs:638— core/services/gcs/src/core.rs:638-644 | core/services/s3/src/core.rs:510-515 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) core/services/github/src/core.rs:425— core/services/github/src/core.rs:425-430 | core/services/yandex-disk/src/core.rs:422-427 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/vercel-blob/src/writer.rs:151— core/services/vercel-blob/src/writer.rs:151-157 | core/services/webhdfs/src/writer.rs:221-226 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/webdav/src/core.rs:331— core/services/webdav/src/core.rs:331-336 | core/services/webdav/src/core.rs:366-371 — both copies are in the same file, so extract the block into 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) dev/src/release/package.rs:347— dev/src/release/package.rs:347-352 | dev/src/release/package.rs:490-495 — both copies are in the same file, so extract the block into 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) core/layers/foyer/src/lib.rs:126— core/layers/foyer/src/lib.rs:126-131 | core/services/foyer/src/lib.rs:93-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/aliyun-drive/src/writer.rs:104— core/services/aliyun-drive/src/writer.rs:104-109 | core/services/ftp/src/reader.rs:164-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/aliyun-drive/src/writer.rs:111— core/services/aliyun-drive/src/writer.rs:111-116 | core/services/hf/src/writer.rs:76-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/mini_moka/src/backend.rs:58— core/services/mini_moka/src/backend.rs:58-63 | core/services/moka/src/backend.rs:114-119 — before extracting anything, compare `core/services/mini_moka/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) core/services/mini_moka/src/backend.rs:68— core/services/mini_moka/src/backend.rs:68-73 | core/services/moka/src/backend.rs:124-129 — before extracting anything, compare `core/services/mini_moka/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) core/services/gcs/src/core.rs:402— core/services/gcs/src/core.rs:402-407 | core/services/gcs/src/core.rs:757-762 — both copies are in the same file, so extract the block into 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) core/services/lakefs/src/backend.rs:124— core/services/lakefs/src/backend.rs:124-129 | core/services/lakefs/src/backend.rs:141-146 — both copies are in the same file, so extract the block into 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) core/services/koofr/src/config.rs:71— core/services/koofr/src/config.rs:71-76 | core/services/lakefs/src/config.rs:95-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) core/services/upyun/src/backend.rs:120— core/services/upyun/src/backend.rs:120-125 | core/services/upyun/src/backend.rs:127-132 — both copies are in the same file, so extract the block into 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) core/services/azfile/src/core.rs:238— core/services/azfile/src/core.rs:238-243 | core/services/azfile/src/core.rs:263-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) bindings/c/src/operator.rs:673— bindings/c/src/operator.rs:673-686 | bindings/c/src/operator.rs:705-718 — both copies are in the same file, so extract the block into 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) bindings/c/src/types.rs:1064— bindings/c/src/types.rs:1064-1077 | bindings/c/src/types.rs:1290-1303 — both copies are in the same file, so extract the block into 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) bindings/haskell/src/lib.rs:516— bindings/haskell/src/lib.rs:516-529 | bindings/haskell/src/lib.rs:748-761 — both copies are in the same file, so extract the block into 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) bindings/python/src/file.rs:99— bindings/python/src/file.rs:99-112 | bindings/python/src/file.rs:147-160 — both copies are in the same file, so extract the block into 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) core/services/azdls/src/core.rs:844— core/services/azdls/src/core.rs:844-857 | core/services/oss/src/core.rs:1235-1248 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 87 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) core/services/cloudflare-kv/src/core.rs:235— core/services/cloudflare-kv/src/core.rs:235-248 | core/services/d1/src/core.rs:237-250 — before extracting anything, compare `core/services/cloudflare-kv/src/core.rs` and `core/services/d1/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) core/services/cos/src/core.rs:955— core/services/cos/src/core.rs:955-968 | core/services/oss/src/core.rs:1257-1270 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 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) core/services/foyer/src/config.rs:65— core/services/foyer/src/config.rs:65-78 | core/services/moka/src/config.rs:52-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) core/services/gcs/src/writer.rs:314— core/services/gcs/src/writer.rs:314-327 | core/services/gcs/src/writer.rs:411-424 — both copies are in the same file, so extract the block into 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) core/services/ghac/src/reader.rs:52— core/services/ghac/src/reader.rs:52-65 | core/services/yandex-disk/src/reader.rs:57-70 — before extracting anything, compare `core/services/ghac/src/reader.rs` and `core/services/yandex-disk/src/reader.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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) core/services/http/src/reader.rs:61— core/services/http/src/reader.rs:61-74 | core/services/ipfs/src/reader.rs:53-66 — before extracting anything, compare `core/services/http/src/reader.rs` and `core/services/ipfs/src/reader.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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) core/services/mini_moka/src/writer.rs:60— core/services/mini_moka/src/writer.rs:60-73 | core/services/moka/src/writer.rs:60-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) core/services/obs/src/core.rs:472— core/services/obs/src/core.rs:472-485 | core/services/oss/src/core.rs:791-804 — before extracting anything, compare `core/services/obs/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 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) core/services/s3/src/copier.rs:256— core/services/s3/src/copier.rs:256-269 | core/services/s3/src/writer.rs:117-130 — 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) core/services/surrealdb/src/core.rs:96— core/services/surrealdb/src/core.rs:96-109 | core/services/surrealdb/src/core.rs:125-138 — both copies are in the same file, so extract the block into 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) core/services/postgresql/src/core.rs:111— core/services/postgresql/src/core.rs:111-124 | core/services/sqlite/src/core.rs:185-198 — before extracting anything, compare `core/services/postgresql/src/core.rs` and `core/services/sqlite/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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) core/services/azfile/src/core.rs:364— core/services/azfile/src/core.rs:364-377 | core/services/azfile/src/core.rs:391-404 — both copies are in the same file, so extract the block into 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) core/services/pcloud/src/core.rs:264— core/services/pcloud/src/core.rs:264-277 | core/services/pcloud/src/core.rs:291-304 — both copies are in the same file, so extract the 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×15
Members sharing a duplicated core (4 members, 50+ identical tokens) bindings/c/src/presign.rs:146— bindings/c/src/presign.rs:146-159 | bindings/c/src/presign.rs:184-197 | bindings/c/src/presign.rs:221-250 | bindings/c/src/presign.rs:275-288 — 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) core/layers/retry/src/lib.rs:764— core/layers/retry/src/lib.rs:764-793 | core/layers/retry/src/lib.rs:795-825 | core/layers/retry/src/lib.rs:827-856 | core/layers/retry/src/lib.rs:858-887 — 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) core/services/aliyun-drive/src/config.rs:76— core/services/aliyun-drive/src/config.rs:76-92 | core/services/foyer/src/config.rs:64-78 | core/services/goosefs/src/config.rs:110-122 | core/services/moka/src/config.rs:51-65 — 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) core/services/alluxio/src/config.rs:54— core/services/alluxio/src/config.rs:54-67 | core/services/ipfs/src/config.rs:37-50 | core/services/ipmfs/src/config.rs:37-50 | core/services/webhdfs/src/config.rs:59-72 — 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) core/services/alluxio/src/core.rs:51— core/services/alluxio/src/core.rs:51-88 | core/services/alluxio/src/core.rs:164-192 | core/services/alluxio/src/core.rs:194-222 | core/services/alluxio/src/core.rs:357-380 — 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) core/services/cos/src/core.rs:518— core/services/cos/src/core.rs:518-555 | core/services/gcs/src/core.rs:1026-1056 | core/services/oss/src/core.rs:618-650 | core/services/oss/src/core.rs:744-781 — 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) core/services/cos/src/lister.rs:142— core/services/cos/src/lister.rs:142-156 | core/services/oss/src/lister.rs:145-159 | core/services/s3/src/lister.rs:298-312 | core/services/tos/src/lister.rs:139-153 — 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) core/services/dbfs/src/core.rs:267— core/services/dbfs/src/core.rs:267-297 | core/services/lakefs/src/core.rs:358-388 | core/services/swift/src/core.rs:901-932 | core/services/webhdfs/src/core.rs:468-499 — 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) core/services/dropbox/src/core.rs:181— core/services/dropbox/src/core.rs:181-199 | core/services/dropbox/src/core.rs:205-234 | core/services/dropbox/src/core.rs:242-265 | core/services/dropbox/src/core.rs:271-290 — 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) core/services/foyer/src/reader.rs:38— core/services/foyer/src/reader.rs:38-59 | core/services/memcached/src/reader.rs:38-55 | core/services/mysql/src/reader.rs:39-56 | core/services/tikv/src/reader.rs:39-56 — 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) core/services/hf/src/core.rs:556— core/services/hf/src/core.rs:556-597 | core/services/hf/src/core.rs:743-772 | core/services/hf/src/core.rs:949-980 | core/services/hf/src/core.rs:989-1022 — 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) core/services/koofr/src/core.rs:521— core/services/koofr/src/core.rs:521-548 | core/services/seafile/src/core.rs:560-581 | core/services/upyun/src/core.rs:617-646 | core/services/vercel-blob/src/core.rs:515-540 — 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) core/services/obs/src/backend.rs:404— core/services/obs/src/backend.rs:404-433 | core/services/oss/src/backend.rs:770-809 | core/services/upyun/src/backend.rs:286-315 | core/services/vercel-blob/src/backend.rs:216-245 — 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) core/services/persy/src/backend.rs:179— core/services/persy/src/backend.rs:179-194 | core/services/redb/src/backend.rs:197-212 | core/services/rocksdb/src/backend.rs:147-162 | core/services/sled/src/backend.rs:171-186 — 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) core/services/persy/src/writer.rs:46— core/services/persy/src/writer.rs:46-57 | core/services/redb/src/writer.rs:46-57 | core/services/rocksdb/src/writer.rs:47-58 | core/services/sled/src/writer.rs:46-57 — 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.
Repeated repair: core/services/hf/src/reader.rs core/services/hf/src/reader.rs:145— core/services/hf/src/reader.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 6 (its worst body is HfReader::open at line 145), 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(services/hf): restore reader-local XET resolution reuse (#8285)”; “fix(services/hf): make resolve cache opt-in (#8282)”; “fix(services/hf): pin the xet probe range and drop dead http-mode classification (#8263)”; “fix(services/hf): follow case redirects instead of resolving the canonical repo id (#8225)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/hf/src/reader.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: scripts/release_lifecycle.py scripts/release_lifecycle.py:560— scripts/release_lifecycle.py changed 6 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 release_lifecycle.nexus_release at line 560), 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(release): validate declarations and published state correctly (#8322)”; “fix(ci): publish dotnet packages only from final release tags (#8311)”; “fix(release): include unlabeled PRs and preserve version titles (#8308)”; “fix(release): publish approved source before optional distributions (#8304)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- scripts/release_lifecycle.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.
Repeated repair: core/services/gcs/src/writer.rs core/services/gcs/src/writer.rs:376— core/services/gcs/src/writer.rs changed 8 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 11 (its worst body is GcsConditionalWriter::close at line 376), 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: preserve conditional error semantics (#8204)”; “fix(services/gcs): make conditional uploads retry-safe (#8199)”; “fix(services/gcs): encode object paths exactly once (#7947)”; “Revert "fix(services/gcs): stop double-encoding object paths in writer (#7943)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/gcs/src/writer.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: core/services/memcached/src/backend.rs core/services/memcached/src/backend.rs:100— core/services/memcached/src/backend.rs changed 7 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 9 (its worst body is MemcachedBuilder::build at line 100), 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(services/memcached): reject a TTL over 30 days (#8150)”; “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/memcached/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.
Repeated repair: core/services/redis/src/backend.rs core/services/redis/src/backend.rs:147— core/services/redis/src/backend.rs changed 7 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 6 (its worst body is RedisBuilder::build at line 147), 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: “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”; “fix(services): improve stat implementation (#7857)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/redis/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.
Repeated repair: core/services/hf/src/lister.rs core/services/hf/src/lister.rs:121— core/services/hf/src/lister.rs changed 6 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 9 (its worst body is HfLister::next_page at line 121), 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(services/hf): drop the trailing slash from the root tree URL (#8243)”; “fix(services/hf): follow case redirects instead of resolving the canonical repo id (#8225)”; “fix: Canonicalize HuggingFace IDs to avoid inconsistent API (#8108)”; “fix: CI prints clippy version and clippy fix (#7895)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/hf/src/lister.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: core/services/cos/src/core.rs core/services/cos/src/core.rs:917— core/services/cos/src/core.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 13 (its worst body is opendal_service_cos::core::parse_error at line 917), 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: preserve conditional error semantics (#8204)”; “fix(services): percent-encode the pagination marker in list queries (#8073)”; “fix(services/cos): honor if_not_exists on multipart uploads (#8043)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/cos/src/core.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: core/services/cloudflare-kv/src/config.rs core/services/cloudflare-kv/src/config.rs:57— core/services/cloudflare-kv/src/config.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 3 (its worst body is CloudflareKvConfig::from_uri at line 57), 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: “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/cloudflare-kv/src/config.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: core/services/memcached/src/config.rs core/services/memcached/src/config.rs:68— core/services/memcached/src/config.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 4 (its worst body is MemcachedConfig::from_uri at line 68), 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: “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/memcached/src/config.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: core/services/redis/src/config.rs core/services/redis/src/config.rs:81— core/services/redis/src/config.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 RedisConfig::from_uri at line 81), 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: “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/redis/src/config.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: dev/src/generate/parser.rs dev/src/generate/parser.rs:112— dev/src/generate/parser.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 ConfigType::from_str at line 112), 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: “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- dev/src/generate/parser.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: core/services/sqlite/src/core.rs core/services/sqlite/src/core.rs:107— core/services/sqlite/src/core.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 4 (its worst body is SqliteCore::get_range at line 107), 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(services/sqlite): match the directory prefix exactly instead of with LIKE (#8085)”; “fix(services): improve stat implementation (#7857)”; “fix(services/sqlite): stat getting the entire object (#7853)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/sqlite/src/core.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: bindings/java/src/executor.rs bindings/java/src/executor.rs:217— bindings/java/src/executor.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 3 (its worst body is opendal_java::executor::executor_or_default at line 217), 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(bindings/java): use defining class loader on executor threads (#8293)”; “fix(bindings/java): release default executor after its last owner (#8289)”; “fix(bindings/java): install default HTTP transport on load (#8288)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- bindings/java/src/executor.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: core/core/src/raw/time.rs core/core/src/raw/time.rs:50— core/core/src/raw/time.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 2 (its worst body is Timestamp::from_str at line 50), 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: “Reapply "fix(core): deserialize duration config values from strings" (#8123)”; “Revert "fix(core): deserialize duration config values from strings" (#8034)”; “fix(core): deserialize duration config values from strings (#7983)”. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/core/src/raw/time.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.
Duplicated block (5 lines × 2) core/core/src/raw/ops.rs:558— core/core/src/raw/ops.rs:558-562 | core/core/src/raw/ops.rs:794-798 — both copies are in the same file, so extract the block into 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) core/services/aliyun-drive/src/backend.rs:228— core/services/aliyun-drive/src/backend.rs:228-232 | core/services/aliyun-drive/src/writer.rs:74-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 (5 lines × 2) core/services/azdls/src/backend.rs:286— core/services/azdls/src/backend.rs:286-290 | core/services/azfile/src/backend.rs:204-208 — before extracting anything, compare `core/services/azdls/src/backend.rs` and `core/services/azfile/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 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) core/services/pcloud/src/core.rs:137— core/services/pcloud/src/core.rs:137-141 | core/services/yandex-disk/src/core.rs:182-186 — 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) core/services/azblob/src/core.rs:518— core/services/azblob/src/core.rs:518-522 | core/services/oss/src/core.rs:557-561 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 78 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) core/services/cloudflare-kv/src/config.rs:81— core/services/cloudflare-kv/src/config.rs:81-85 | core/services/d1/src/config.rs:86-90 — 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) core/services/redis/src/config.rs:82— core/services/redis/src/config.rs:82-86 | core/services/swift/src/config.rs:67-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) core/core/src/types/operator/operator.rs:2709— core/core/src/types/operator/operator.rs:2709-2713 | core/core/src/types/operator/operator.rs:2823-2827 — both copies are in the same file, so extract the block into 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) core/services/cos/src/core.rs:365— core/services/cos/src/core.rs:365-369 | core/services/obs/src/core.rs:315-319 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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) core/services/persy/src/core.rs:55— core/services/persy/src/core.rs:55-59 | core/services/persy/src/core.rs:96-100 — both copies are in the same file, so extract the block into 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) REDACTED:762— REDACTED:762-766 | REDACTED:772-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:762` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) REDACTED:912— REDACTED:912-916 | REDACTED:922-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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:912` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) REDACTED:371— REDACTED:371-375 | REDACTED:381-385 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:371` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Hotspot: core/services/s3/src/backend.rs core/services/s3/src/backend.rs:826— core/services/s3/src/backend.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in S3Builder::build at line 826. 4 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/s3/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: core/services/hf/src/core.rs core/services/hf/src/core.rs:774— core/services/hf/src/core.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in HfCore::read at line 774. 9 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/hf/src/core.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: core/services/gcs/src/core.rs core/services/gcs/src/core.rs:2014— core/services/gcs/src/core.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in opendal_service_gcs::core::parse_error at line 2014. 6 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/gcs/src/core.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: core/services/cloudflare-kv/src/backend.rs core/services/cloudflare-kv/src/backend.rs:257— core/services/cloudflare-kv/src/backend.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CloudflareKvBackend::stat at line 257. 3 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/cloudflare-kv/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: core/services/oss/src/backend.rs core/services/oss/src/backend.rs:412— core/services/oss/src/backend.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in OssBuilder::build at line 412. 3 of those changes were fix/bug commits, 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/oss/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: core/services/azdls/src/core.rs core/services/azdls/src/core.rs:826— core/services/azdls/src/core.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in opendal_service_azdls::core::parse_error at line 826. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/azdls/src/core.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: core/services/gdrive/src/lister.rs core/services/gdrive/src/lister.rs:400— core/services/gdrive/src/lister.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in GdriveFlatLister::initialize at line 400. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/gdrive/src/lister.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: core/services/onedrive/src/lister.rs core/services/onedrive/src/lister.rs:63— core/services/onedrive/src/lister.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in OneDriveLister::next_page at line 63. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/onedrive/src/lister.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: core/services/cos/src/lister.rs core/services/cos/src/lister.rs:160— core/services/cos/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CosObjectVersionsLister::next_page at line 160. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/cos/src/lister.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: core/services/oss/src/lister.rs core/services/oss/src/lister.rs:163— core/services/oss/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in OssObjectVersionsLister::next_page at line 163. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/oss/src/lister.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: core/services/s3/src/lister.rs core/services/s3/src/lister.rs:316— core/services/s3/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in S3ObjectVersionsLister::next_page at line 316. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/s3/src/lister.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: core/services/tos/src/lister.rs core/services/tos/src/lister.rs:157— core/services/tos/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in TosObjectVersionsLister::next_page at line 157. 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-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 14:19:53 +08:00' --until='2026-09-24 14:19:53 +08:00' --full-history --no-merges -- core/services/tos/src/lister.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.
Duplicated block (9 lines × 3) bindings/c/src/operator.rs:296— bindings/c/src/operator.rs:296-304 | bindings/c/src/operator.rs:352-360 | bindings/c/src/operator.rs:695-703 — 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) bindings/python/src/file.rs:498— bindings/python/src/file.rs:498-506 | bindings/python/src/file.rs:609-617 | bindings/python/src/file.rs:644-652 — 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) core/services/azblob/src/reader.rs:68— core/services/azblob/src/reader.rs:68-76 | core/services/gcs/src/reader.rs:75-83 | core/services/s3/src/reader.rs:68-76 — 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) core/services/azdls/src/core.rs:849— core/services/azdls/src/core.rs:849-857 | core/services/azfile/src/core.rs:568-576 | core/services/oss/src/core.rs:1240-1248 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 98 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) core/services/b2/src/core.rs:101— core/services/b2/src/core.rs:101-110 | core/services/gdrive/src/core.rs:757-765 | core/services/webhdfs/src/core.rs:196-205 — 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) core/services/cos/src/core.rs:95— core/services/cos/src/core.rs:95-103 | core/services/obs/src/core.rs:90-98 | core/services/oss/src/core.rs:128-136 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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) core/services/cos/src/core.rs:259— core/services/cos/src/core.rs:259-267 | core/services/gcs/src/core.rs:630-638 | core/services/oss/src/core.rs:426-434 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 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) core/services/cos/src/lister.rs:255— core/services/cos/src/lister.rs:255-263 | core/services/oss/src/lister.rs:258-266 | core/services/tos/src/lister.rs:245-253 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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) core/services/gridfs/src/config.rs:69— core/services/gridfs/src/config.rs:69-77 | core/services/mongodb/src/config.rs:71-79 | core/services/surrealdb/src/config.rs:85-93 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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) core/services/dbfs/src/writer.rs:59— core/services/dbfs/src/writer.rs:59-67 | core/services/ipmfs/src/writer.rs:43-52 | core/services/webhdfs/src/writer.rs:58-68 — 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) core/services/s3/src/core.rs:898— core/services/s3/src/core.rs:898-906 | core/services/s3/src/core.rs:950-958 | core/services/s3/src/core.rs:1461-1469 — 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) REDACTED:228— REDACTED:228-236 | REDACTED:542-550 | REDACTED:588-596 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:228` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
ClassTooLong: Operator core/core/src/types/operator/operator.rs:196— ClassTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 92 methods, 5 blocks, lines 196-2828. The bar is 400 significant lines; this is 431 over it, 2.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: S3Core core/services/s3/src/core.rs:95— ClassTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 31 methods, 4 blocks, lines 95-1470. The bar is 400 significant lines; this is 418 over it, 2.05× 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: GcsCore core/services/gcs/src/core.rs:67— 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), 30 methods, 4 blocks, lines 67-1089. 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: TosCore core/services/tos/src/core.rs:61— ClassTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 3 blocks, lines 61-917. The bar is 400 significant lines; this is 189 over it, 1.47× 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: AsyncOperator bindings/python/src/operator.rs:936— ClassTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 2 blocks, lines 936-2042. The bar is 400 significant lines; this is 142 over it, 1.36× 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: AzblobCore core/services/azblob/src/core.rs:75— ClassTooLong — 532 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, 4 blocks, lines 75-884. The bar is 400 significant lines; this is 132 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: S3Builder core/services/s3/src/backend.rs:82— ClassTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 4 blocks, lines 82-1166. The bar is 400 significant lines; this is 130 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AliyunDriveCore core/services/aliyun-drive/src/core.rs:61— ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 3 blocks, lines 61-615. The bar is 400 significant lines; this is 41 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: OneDriveCore core/services/onedrive/src/core.rs:35— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 4 blocks, lines 35-713. The bar is 400 significant lines; this is 20 over it, 1.05× 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: OpendalStore integrations/object_store/src/store.rs:182— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 6 blocks, lines 182-755. The bar is 400 significant lines; this is 10 over it, 1.03× 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: HfCore core/services/hf/src/core.rs:421— ClassTooLong — 403 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 3 blocks, lines 421-1023. The bar is 400 significant lines; this is 3 over it, 1.01× 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 (5 members, 50+ identical tokens) · ×11
Members sharing a duplicated core (5 members, 50+ identical tokens) bindings/c/src/operator.rs:1285— bindings/c/src/operator.rs:1285-1299 | bindings/c/src/operator.rs:1347-1361 | bindings/c/src/operator.rs:1420-1439 | bindings/c/src/operator.rs:1480-1499 | bindings/c/src/operator.rs:1519-1543 — 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) bindings/python/src/file.rs:97— bindings/python/src/file.rs:97-120 | bindings/python/src/file.rs:145-172 | bindings/python/src/file.rs:186-225 | bindings/python/src/file.rs:286-315 | bindings/python/src/file.rs:323-340 — 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) core/core/src/services/memory/backend.rs:217— core/core/src/services/memory/backend.rs:217-242 | core/services/persy/src/reader.rs:38-57 | core/services/redb/src/reader.rs:38-57 | core/services/rocksdb/src/reader.rs:38-57 | core/services/sled/src/reader.rs:38-57 — 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) core/services/azfile/src/core.rs:136— core/services/azfile/src/core.rs:136-180 | core/services/cos/src/core.rs:325-356 | core/services/obs/src/core.rs:275-307 | core/services/oss/src/core.rs:177-224 | core/services/oss/src/core.rs:666-699 — 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) core/services/cloudflare-kv/src/core.rs:197— core/services/cloudflare-kv/src/core.rs:197-232 | core/services/d1/src/core.rs:199-234 | core/services/dropbox/src/core.rs:551-585 | core/services/gdrive/src/core.rs:1119-1154 | core/services/tos/src/core.rs:1111-1146 — 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) core/services/cos/src/core.rs:94— core/services/cos/src/core.rs:94-103 | core/services/gcs/src/core.rs:130-151 | core/services/obs/src/core.rs:89-98 | core/services/oss/src/core.rs:123-136 | core/services/tos/src/core.rs:108-122 — 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) core/services/cos/src/writer.rs:75— core/services/cos/src/writer.rs:75-96 | core/services/cos/src/writer.rs:245-265 | core/services/obs/src/writer.rs:67-87 | core/services/oss/src/writer.rs:66-85 | core/services/oss/src/writer.rs:238-256 — 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) core/services/etcd/src/core.rs:94— core/services/etcd/src/core.rs:94-106 | core/services/ftp/src/core.rs:59-71 | core/services/memcached/src/core.rs:191-203 | core/services/redis/src/core.rs:158-170 | core/services/sftp/src/core.rs:78-90 — 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) core/services/fs/src/core.rs:107— core/services/fs/src/core.rs:107-136 | core/services/fs/src/writer.rs:180-221 | core/services/hdfs/src/core.rs:64-83 | core/services/monoiofs/src/backend.rs:110-133 | core/services/monoiofs/src/writer.rs:147-172 — 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) core/services/ghac/src/core.rs:560— core/services/ghac/src/core.rs:560-588 | core/services/http/src/core.rs:169-199 | core/services/ipfs/src/core.rs:273-301 | core/services/onedrive/src/core.rs:1021-1068 | core/services/vercel-artifacts/src/core.rs:148-174 — 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) core/services/github/src/core.rs:424— core/services/github/src/core.rs:424-458 | core/services/seafile/src/core.rs:560-581 | core/services/upyun/src/core.rs:617-646 | core/services/vercel-blob/src/core.rs:515-540 | core/services/yandex-disk/src/core.rs:421-449 — 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.
Duplicated block (7 lines × 3) bindings/java/src/async_operator.rs:541— bindings/java/src/async_operator.rs:541-547 | bindings/java/src/async_operator.rs:577-583 | bindings/java/src/async_operator.rs:614-620 — 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) core/layers/fastmetrics/src/lib.rs:171— core/layers/fastmetrics/src/lib.rs:171-177 | core/layers/prometheus-client/src/lib.rs:115-121 | core/layers/prometheus/src/lib.rs:203-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) core/services/alluxio/src/core.rs:76— core/services/alluxio/src/core.rs:76-83 | core/services/alluxio/src/core.rs:211-217 | core/services/alluxio/src/core.rs:369-375 — 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) core/services/alluxio/src/core.rs:177— core/services/alluxio/src/core.rs:177-183 | core/services/alluxio/src/core.rs:209-216 | core/services/alluxio/src/core.rs:367-374 — 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) core/services/cos/src/writer.rs:57— core/services/cos/src/writer.rs:57-63 | core/services/obs/src/writer.rs:51-57 | core/services/oss/src/writer.rs:50-56 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. 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) core/services/gcs/src/core.rs:180— core/services/gcs/src/core.rs:180-186 | core/services/gcs/src/core.rs:574-580 | core/services/gcs/src/core.rs:701-707 — 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) core/services/gcs/src/core.rs:258— core/services/gcs/src/core.rs:258-264 | core/services/http/src/core.rs:75-81 | core/services/http/src/core.rs:124-130 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/http/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) core/services/ghac/src/core.rs:150— core/services/ghac/src/core.rs:150-157 | core/services/ghac/src/core.rs:286-293 | core/services/ghac/src/core.rs:395-401 — 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) core/services/gridfs/src/config.rs:65— core/services/gridfs/src/config.rs:65-71 | core/services/mongodb/src/config.rs:67-73 | core/services/surrealdb/src/config.rs:75-81 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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) core/services/gdrive/src/backend.rs:306— core/services/gdrive/src/backend.rs:306-312 | core/services/gdrive/src/backend.rs:523-529 | core/services/gdrive/src/backend.rs:591-597 — 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) core/services/azblob/src/reader.rs:52— core/services/azblob/src/reader.rs:52-58 | core/services/gcs/src/reader.rs:55-61 | core/services/s3/src/reader.rs:52-58 — 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×10
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×10
Duplicated block (15 lines × 2) bindings/dotnet/OpenDAL/Operator.cs:1309— bindings/dotnet/OpenDAL/Operator.cs:1309-1323 | bindings/dotnet/OpenDAL/Operator.cs:1342-1356 — both copies are in the same file, so extract the 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 `bindings/dotnet/OpenDAL/Operator.cs:1309` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) bindings/c/src/operator_info.rs:312— bindings/c/src/operator_info.rs:312-326 | bindings/python/src/capability.rs:182-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) bindings/dotnet/src/operator.rs:1595— bindings/dotnet/src/operator.rs:1595-1609 | bindings/dotnet/src/operator.rs:1703-1717 — both copies are in the same file, so extract the block into 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) core/core/src/raw/oio/copy/block_copy.rs:279— core/core/src/raw/oio/copy/block_copy.rs:279-293 | core/core/src/raw/oio/copy/multipart_copy.rs:352-366 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. 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) core/services/b2/src/backend.rs:374— core/services/b2/src/backend.rs:374-388 | core/services/b2/src/backend.rs:404-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/services/cloudflare-kv/src/core.rs:198— core/services/cloudflare-kv/src/core.rs:198-212 | core/services/d1/src/core.rs:200-214 — before extracting anything, compare `core/services/cloudflare-kv/src/core.rs` and `core/services/d1/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 × 2) core/services/cos/src/reader.rs:64— core/services/cos/src/reader.rs:64-78 | core/services/oss/src/reader.rs:64-78 — before extracting anything, compare `core/services/cos/src/reader.rs` and `core/services/oss/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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 × 2) core/services/s3/src/core.rs:1322— core/services/s3/src/core.rs:1322-1336 | core/services/s3/src/core.rs:1353-1367 — both copies are in the same file, so extract the block into 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) core/services/tos/src/core.rs:189— core/services/tos/src/core.rs:189-203 | core/services/tos/src/core.rs:785-799 — both copies are in the same file, so extract the block into 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) REDACTED:141— REDACTED:141-155 | REDACTED:451-465 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TooManyMethods: Operator core/core/src/types/operator/operator.rs:196— TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.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: Operator bindings/dotnet/OpenDAL/Operator.cs— TooManyMethods — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Capability REDACTED:89— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: Operator core/core/src/blocking/operator.rs:127— TooManyMethods — 47 methods, declared across 2 files: blocking/operator.rs (43), operator/builder.rs (4). The bar is 30 methods; this is 17 over it, 1.57× 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: AsyncOperator bindings/java/src/main/java/org/apache/opendal/AsyncOperator.java:43— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: S3Builder core/services/s3/src/backend.rs:82— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Operator bindings/nodejs/src/lib.rs:40— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Operator bindings/java/src/main/java/org/apache/opendal/Operator.java:31— 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: S3Core core/services/s3/src/core.rs:95— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
MethodTooLong: S3Builder.build core/services/s3/src/backend.rs:826— MethodTooLong — build runs 235 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 135 over it, 2.35× 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: PrometheusLayerBuilder.register core/layers/prometheus/src/lib.rs:286— MethodTooLong — register runs 174 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 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: OssBuilder.build core/services/oss/src/backend.rs:412— MethodTooLong — build 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.
MethodTooLong: OtelMetricsLayerBuilder.register core/layers/otelmetrics/src/lib.rs:169— MethodTooLong — register runs 134 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 34 over it, 1.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: GcsBuilder.build core/services/gcs/src/backend.rs:246— MethodTooLong — build runs 131 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 31 over it, 1.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: PrometheusClientLayerBuilder.register core/layers/prometheus-client/src/lib.rs:204— MethodTooLong — register runs 130 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 30 over it, 1.30× 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: GdriveFlatLister.initialize core/services/gdrive/src/lister.rs:400— MethodTooLong — initialize 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.
MethodTooLong: AzblobBuilder.build core/services/azblob/src/backend.rs:304— MethodTooLong — build runs 121 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 21 over it, 1.21× 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: GdriveBackend.rename core/services/gdrive/src/backend.rs:482— MethodTooLong — rename runs 113 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 13 over it, 1.13× 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.
Duplicated block (13 lines × 2) bindings/c/src/layer.rs:48— bindings/c/src/layer.rs:48-60 | bindings/cpp/src/layer.rs:47-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) core/services/dbfs/src/config.rs:49— core/services/dbfs/src/config.rs:49-61 | core/services/pcloud/src/config.rs:57-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) core/services/hdfs-native/src/config.rs:64— core/services/hdfs-native/src/config.rs:64-76 | core/services/hdfs/src/config.rs:69-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) core/services/memcached/src/binary.rs:165— core/services/memcached/src/binary.rs:165-177 | core/services/memcached/src/binary.rs:231-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/services/oss/src/core.rs:382— core/services/oss/src/core.rs:382-394 | core/services/oss/src/core.rs:417-429 — both copies are in the same file, so extract the block into 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) core/services/tos/src/copier.rs:148— core/services/tos/src/copier.rs:148-160 | core/services/tos/src/writer.rs:101-113 — before extracting anything, compare `core/services/tos/src/copier.rs` and `core/services/tos/src/writer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 (13 lines × 2) core/services/pcloud/src/core.rs:466— core/services/pcloud/src/core.rs:466-478 | core/services/pcloud/src/core.rs:483-495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) REDACTED:511— REDACTED:511-523 | REDACTED:529-541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:511` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) core/layers/prometheus-client/src/lib.rs:205— core/layers/prometheus-client/src/lib.rs:205-214 | core/layers/prometheus-client/src/lib.rs:233-242 | core/layers/prometheus-client/src/lib.rs:245-254 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) core/services/azblob/src/core.rs:155— core/services/azblob/src/core.rs:155-164 | core/services/gcs/src/core.rs:103-112 | core/services/oss/src/core.rs:104-113 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) core/services/b2/src/backend.rs:392— core/services/b2/src/backend.rs:392-402 | core/services/b2/src/backend.rs:425-435 | core/services/b2/src/backend.rs:449-458 — 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) core/services/b2/src/core.rs:353— core/services/b2/src/core.rs:353-362 | core/services/b2/src/core.rs:613-622 | core/services/b2/src/core.rs:644-653 — 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) core/services/cos/src/core.rs:416— core/services/cos/src/core.rs:416-425 | core/services/gcs/src/core.rs:917-926 | core/services/obs/src/core.rs:357-366 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) core/services/ghac/src/backend.rs:188— core/services/ghac/src/backend.rs:188-197 | core/services/upyun/src/core.rs:566-575 | dev/src/release/mod.rs:275-284 — 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) core/services/seafile/src/core.rs:267— core/services/seafile/src/core.rs:267-276 | core/services/seafile/src/core.rs:325-334 | core/services/seafile/src/core.rs:361-370 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) REDACTED:288— REDACTED:288-298 | REDACTED:387-396 | REDACTED:398-407 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:288` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) core/services/azfile/src/core.rs:567— core/services/azfile/src/core.rs:567-574 | core/services/dropbox/src/core.rs:557-564 | core/services/ghac/src/core.rs:566-573 — 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) core/services/pcloud/src/backend.rs:211— core/services/pcloud/src/backend.rs:211-218 | core/services/pcloud/src/core.rs:93-100 | core/services/pcloud/src/core.rs:151-158 — 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 (8 lines × 3) core/services/webhdfs/src/core.rs:296— core/services/webhdfs/src/core.rs:296-303 | core/services/webhdfs/src/core.rs:325-332 | core/services/webhdfs/src/core.rs:389-396 — 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) core/services/azblob/src/core.rs:99— core/services/azblob/src/core.rs:99-106 | core/services/cos/src/core.rs:69-76 | core/services/obs/src/core.rs:64-71 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 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 × 3) core/services/dbfs/src/backend.rs:62— core/services/dbfs/src/backend.rs:62-69 | core/services/swift/src/backend.rs:55-62 | core/services/swift/src/backend.rs:67-74 — 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 (8 lines × 3) core/services/azblob/src/backend.rs:605— core/services/azblob/src/backend.rs:605-612 | core/services/s3/src/backend.rs:1297-1304 | core/services/tos/src/backend.rs:401-408 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/s3/src/backend.rs` as WHOLE FILES: this scan already matched 4 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 (8 lines × 3) core/services/cloudflare-kv/src/config.rs:72— core/services/cloudflare-kv/src/config.rs:72-79 | core/services/d1/src/config.rs:77-84 | core/services/koofr/src/config.rs:62-69 — 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) core/services/cloudflare-kv/src/config.rs:87— core/services/cloudflare-kv/src/config.rs:87-94 | core/services/d1/src/config.rs:92-99 | core/services/koofr/src/config.rs:79-86 — 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.
Change-coupling hub: lib.rs → error_context.rs, lib.rs, lib.rs, lib.rs, lib.rs, lib.rs, lib.rs core/layers/logging/src/lib.rs— `core/layers/logging/src/lib.rs` changes together with 7 other files — `core/core/src/layers/error_context.rs`, `core/layers/await-tree/src/lib.rs`, `core/layers/concurrent-limit/src/lib.rs`, `core/layers/fastrace/src/lib.rs`, `core/layers/metrics/src/lib.rs`, `core/layers/oteltrace/src/lib.rs`, `core/layers/tracing/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 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 7.
Change-coupling hub: lister.rs → lister.rs, lister.rs, lister.rs, lister.rs core/services/s3/src/lister.rs— `core/services/s3/src/lister.rs` changes together with 4 other files — `core/services/azblob/src/lister.rs`, `core/services/gcs/src/lister.rs`, `core/services/obs/src/lister.rs`, `core/services/oss/src/lister.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 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 4.
Change-coupling hub: lib.rs → lib.rs, lib.rs, lib.rs, lib.rs core/layers/tracing/src/lib.rs— `core/layers/tracing/src/lib.rs` changes together with 4 other files — `core/layers/concurrent-limit/src/lib.rs`, `core/layers/metrics/src/lib.rs`, `core/layers/oteltrace/src/lib.rs`, `core/layers/retry/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 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 4.
Change-coupling hub: error_context.rs → lib.rs, lib.rs, lib.rs, lib.rs, lib.rs core/core/src/layers/error_context.rs— `core/core/src/layers/error_context.rs` changes together with 5 other files — `core/layers/await-tree/src/lib.rs`, `core/layers/concurrent-limit/src/lib.rs`, `core/layers/metrics/src/lib.rs`, `core/layers/retry/src/lib.rs`, `core/layers/tracing/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 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 5.
Change-coupling hub: backend.rs → uri.rs, backend.rs, backend.rs, backend.rs, backend.rs core/services/s3/src/backend.rs— `core/services/s3/src/backend.rs` changes together with 5 other files — `core/core/src/raw/http_util/uri.rs`, `core/services/azblob/src/backend.rs`, `core/services/http/src/backend.rs`, `core/services/obs/src/backend.rs`, `core/services/oss/src/backend.rs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 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 5.
Change-coupling hub: backend.rs → backend.rs, backend.rs, backend.rs core/services/azblob/src/backend.rs— `core/services/azblob/src/backend.rs` changes together with 3 other files — `core/services/azdls/src/backend.rs`, `core/services/azfile/src/backend.rs`, `core/services/http/src/backend.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: backend.rs → backend.rs, backend.rs, backend.rs, backend.rs core/services/gridfs/src/backend.rs— `core/services/gridfs/src/backend.rs` changes together with 4 other files — `core/services/mysql/src/backend.rs`, `core/services/postgresql/src/backend.rs`, `core/services/redis/src/backend.rs`, `core/services/sqlite/src/backend.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 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 4.
Duplicated block (16 lines × 2) bindings/dotnet/src/operator.rs:1869— bindings/dotnet/src/operator.rs:1869-1884 | bindings/dotnet/src/operator.rs:2008-2023 — both copies are in the same file, so extract the block into 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) core/core/src/raw/http_util/multipart.rs:422— core/core/src/raw/http_util/multipart.rs:422-437 | core/core/src/raw/http_util/multipart.rs:606-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.
Duplicated block (16 lines × 2) core/services/azblob/src/writer.rs:55— core/services/azblob/src/writer.rs:55-70 | core/services/azdls/src/writer.rs:98-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) core/services/b2/src/writer.rs:75— core/services/b2/src/writer.rs:75-90 | core/services/b2/src/writer.rs:179-194 — both copies are in the same file, so extract the block into 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) core/services/oss/src/lister.rs:74— core/services/oss/src/lister.rs:74-89 | core/services/tos/src/lister.rs:70-85 — before extracting anything, compare `core/services/oss/src/lister.rs` and `core/services/tos/src/lister.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 135 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) core/services/persy/src/backend.rs:133— core/services/persy/src/backend.rs:133-148 | core/services/redb/src/backend.rs:145-160 — before extracting anything, compare `core/services/persy/src/backend.rs` and `core/services/redb/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) core/services/tos/src/core.rs:624— core/services/tos/src/core.rs:624-639 | core/services/tos/src/core.rs:860-875 — both copies are in the same file, so extract the block into 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 × 3) core/services/compfs/src/core.rs:72— core/services/compfs/src/core.rs:72-84 | core/services/fs/src/core.rs:49-61 | core/services/monoiofs/src/core.rs:99-111 — 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 (13 lines × 3) core/services/cos/src/core.rs:137— core/services/cos/src/core.rs:137-149 | core/services/cos/src/core.rs:251-263 | core/services/cos/src/core.rs:292-304 — 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) core/services/oss/src/lister.rs:76— core/services/oss/src/lister.rs:76-89 | core/services/s3/src/lister.rs:212-224 | core/services/tos/src/lister.rs:72-85 — before extracting anything, compare `core/services/oss/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 174 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 × 3) core/services/azblob/src/lister.rs:65— core/services/azblob/src/lister.rs:65-77 | core/services/cos/src/lister.rs:67-79 | core/services/obs/src/lister.rs:64-76 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 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 × 3) REDACTED:226— REDACTED:226-238 | REDACTED:203-215 | REDACTED:232-244 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:226` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) REDACTED:254— REDACTED:254-266 | REDACTED:270-282 | REDACTED:302-314 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:254` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) REDACTED:375— REDACTED:375-387 | REDACTED:393-405 | REDACTED:411-423 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:375` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
AXH1 · Runtime security headers· Runtime security header not set · ×6
Runtime security header not set: content-security-policy — The live app's responses did not include content-security-policy (restricts the sources a page may load — mitigates XSS/injection). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: strict-transport-security — The live app's responses did not include strict-transport-security (forces HTTPS on subsequent requests — mitigates downgrade/MITM). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-content-type-options — The live app's responses did not include x-content-type-options (stops MIME-sniffing (expects 'nosniff')). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-frame-options — The live app's responses did not include x-frame-options (blocks clickjacking via framing (or use CSP frame-ancestors)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: referrer-policy — The live app's responses did not include referrer-policy (limits referrer leakage to third parties). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: permissions-policy — The live app's responses did not include permissions-policy (restricts powerful browser features (camera, geolocation, …)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
odev::generate::python::format_text (cognitive 28) dev/src/generate/python.rs:115— odev::generate::python::format_text has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 5 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
odev::generate::metadata::parse (cognitive 22) dev/src/generate/metadata.rs:75— odev::generate::metadata::parse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
odev::generate::docs::generate (cognitive 18) dev/src/generate/docs.rs:160— odev::generate::docs::generate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (5 pts), match/switch 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
odev::release::package::sync_workspace_internal_dependency_versions_in_dependencies (cognitive 16) dev/src/release/package.rs:481— odev::release::package::sync_workspace_internal_dependency_versions_in_dependencies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (5 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.
odev::generate::docs::build (cognitive 16) dev/src/generate/docs.rs:393— odev::generate::docs::build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (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.
odev::generate::metadata::classify (cognitive 16) dev/src/generate/metadata.rs:135— odev::generate::metadata::classify has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 2 (3 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TooManyFields: Capability core/core/src/types/capability.rs:65— TooManyFields — 90 stored fields. The bar is 30 stored fields; this is 60 over it, 3.00× 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: opendalCapability REDACTED:240— TooManyFields — 57 stored fields. The bar is 30 stored fields; this is 27 over it, 1.90× 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: opendal_capability bindings/c/src/operator_info.rs:45— TooManyFields — 57 stored fields. The bar is 30 stored fields; this is 27 over it, 1.90× 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: Capability bindings/python/src/capability.rs:29— TooManyFields — 48 stored fields beside 1 method. The bar is 30 stored fields; this is 18 over it, 1.60× 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: S3Config core/services/s3/src/config.rs:34— TooManyFields — 34 stored fields. The bar is 30 stored fields; this is 4 over it, 1.13× 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: Capability bindings/cpp/src/lib.rs:186— TooManyFields — 32 stored fields. The bar is 30 stored fields; this is 2 over it, 1.07× 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×6
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×6
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/aliyun-drive/src/backend.rs:258— core/services/aliyun-drive/src/backend.rs:258-316 | core/services/koofr/src/backend.rs:303-349 | core/services/lakefs/src/backend.rs:304-333 | core/services/obs/src/backend.rs:404-433 | core/services/onedrive/src/backend.rs:305-327 | core/services/pcloud/src/backend.rs:284-342 | core/services/upyun/src/backend.rs:286-315 | core/services/vercel-blob/src/backend.rs:216-245 | core/services/webdav/src/backend.rs:345-384 | core/services/yandex-disk/src/backend.rs:189-223 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/aliyun-drive/src/core.rs:208— core/services/aliyun-drive/src/core.rs:208-233 | core/services/aliyun-drive/src/core.rs:271-309 | core/services/aliyun-drive/src/core.rs:323-353 | core/services/aliyun-drive/src/core.rs:376-398 | core/services/aliyun-drive/src/core.rs:405-427 | core/services/aliyun-drive/src/core.rs:435-457 | core/services/aliyun-drive/src/core.rs:459-479 | core/services/aliyun-drive/src/core.rs:487-509 | core/services/aliyun-drive/src/core.rs:516-537 | core/services/aliyun-drive/src/core.rs:545-589 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/b2/src/config.rs:68— core/services/b2/src/config.rs:68-80 | core/services/cos/src/config.rs:84-96 | core/services/gcs-grpc/src/config.rs:80-89 | core/services/gcs/src/config.rs:127-139 | core/services/obs/src/config.rs:61-73 | core/services/oss/src/config.rs:136-148 | core/services/s3/src/config.rs:343-355 | core/services/sftp/src/config.rs:60-71 | core/services/tos/src/config.rs:105-117 | core/services/upyun/src/config.rs:56-68 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/b2/src/core.rs:174— core/services/b2/src/core.rs:174-207 | core/services/b2/src/core.rs:214-255 | core/services/b2/src/core.rs:368-402 | core/services/pcloud/src/core.rs:66-115 | core/services/seafile/src/core.rs:158-188 | core/services/seafile/src/core.rs:265-299 | core/services/seafile/src/core.rs:323-356 | core/services/seafile/src/core.rs:359-392 | core/services/yandex-disk/src/core.rs:70-107 | core/services/yandex-disk/src/core.rs:125-162 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/cos/src/lister.rs:62— core/services/cos/src/lister.rs:62-126 | core/services/cos/src/lister.rs:160-271 | core/services/obs/src/lister.rs:59-122 | core/services/oss/src/lister.rs:65-129 | core/services/oss/src/lister.rs:163-274 | core/services/s3/src/lister.rs:74-165 | core/services/s3/src/lister.rs:200-282 | core/services/s3/src/lister.rs:316-427 | core/services/tos/src/lister.rs:61-124 | core/services/tos/src/lister.rs:157-261 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/foundationdb/src/writer.rs:46— core/services/foundationdb/src/writer.rs:46-57 | core/services/gridfs/src/writer.rs:47-58 | core/services/memcached/src/writer.rs:47-58 | core/services/mongodb/src/writer.rs:46-57 | core/services/mysql/src/writer.rs:46-57 | core/services/postgresql/src/writer.rs:46-57 | core/services/redis/src/writer.rs:47-58 | core/services/sqlite/src/writer.rs:45-56 | core/services/surrealdb/src/writer.rs:46-57 | core/services/tikv/src/writer.rs:46-57 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Duplicated block (18 lines × 2) core/core/src/types/copy.rs:140— core/core/src/types/copy.rs:140-157 | core/core/src/types/list.rs:68-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 2) core/services/gridfs/src/config.rs:58— core/services/gridfs/src/config.rs:58-75 | core/services/mongodb/src/config.rs:60-77 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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 (18 lines × 2) core/services/hf/src/core.rs:1898— core/services/hf/src/core.rs:1898-1915 | core/services/webdav/src/core.rs:1713-1730 — 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 (18 lines × 2) core/services/koofr/src/core.rs:378— core/services/koofr/src/core.rs:378-395 | core/services/koofr/src/core.rs:417-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 (18 lines × 2) core/services/rocksdb/src/backend.rs:93— core/services/rocksdb/src/backend.rs:93-110 | core/services/sled/src/backend.rs:117-134 — before extracting anything, compare `core/services/rocksdb/src/backend.rs` and `core/services/sled/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 (18 lines × 2) core/services/s3/src/core.rs:252— core/services/s3/src/core.rs:252-269 | core/services/s3/src/core.rs:289-306 — both copies are in the same file, so extract the block into 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–12 lines × 2) bindings/haskell/src/types.rs:91— bindings/haskell/src/types.rs:91-101 | bindings/haskell/src/types.rs:105-116 — both copies are in the same file, so extract the block into 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–12 lines × 2) bindings/python/src/operator.rs:193— bindings/python/src/operator.rs:193-203 | bindings/python/src/operator.rs:959-970 — both copies are in the same file, so extract the block into 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–12 lines × 2) core/core/src/layers/simulate.rs:516— core/core/src/layers/simulate.rs:516-526 | core/core/src/raw/oio/list/flat_list.rs:111-122 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 2) core/services/cos/src/core.rs:936— core/services/cos/src/core.rs:936-947 | core/services/oss/src/core.rs:1245-1255 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 2) core/services/gdrive/src/backend.rs:147— core/services/gdrive/src/backend.rs:147-158 | core/services/onedrive/src/backend.rs:168-178 — before extracting anything, compare `core/services/gdrive/src/backend.rs` and `core/services/onedrive/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 2) core/services/pcloud/src/core.rs:123— core/services/pcloud/src/core.rs:123-134 | core/services/seafile/src/core.rs:310-320 — before extracting anything, compare `core/services/pcloud/src/core.rs` and `core/services/seafile/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) core/services/cos/src/lister.rs:161— core/services/cos/src/lister.rs:161-171 | core/services/oss/src/lister.rs:164-174 | core/services/s3/src/lister.rs:317-327 | core/services/tos/src/lister.rs:158-168 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) core/services/github/src/core.rs:448— core/services/github/src/core.rs:448-458 | core/services/upyun/src/core.rs:636-646 | core/services/vercel-blob/src/core.rs:530-540 | core/services/yandex-disk/src/core.rs:439-449 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (11 lines × 4) core/services/persy/src/backend.rs:180— core/services/persy/src/backend.rs:180-190 | core/services/redb/src/backend.rs:198-208 | core/services/rocksdb/src/backend.rs:148-158 | core/services/sled/src/backend.rs:172-182 — before extracting anything, compare `core/services/persy/src/backend.rs` and `core/services/redb/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) core/services/persy/src/writer.rs:47— core/services/persy/src/writer.rs:47-57 | core/services/redb/src/writer.rs:47-57 | core/services/rocksdb/src/writer.rs:48-58 | core/services/sled/src/writer.rs:47-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (11 lines × 4) core/services/github/src/backend.rs:240— core/services/github/src/backend.rs:240-250 | core/services/koofr/src/backend.rs:265-275 | core/services/pcloud/src/backend.rs:246-256 | core/services/yandex-disk/src/backend.rs:258-268 — before extracting anything, compare `core/services/github/src/backend.rs` and `core/services/koofr/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) core/services/obs/src/backend.rs:423— core/services/obs/src/backend.rs:423-433 | core/services/oss/src/backend.rs:799-809 | core/services/upyun/src/backend.rs:305-315 | core/services/vercel-blob/src/backend.rs:235-245 — before extracting anything, compare `core/services/obs/src/backend.rs` and `core/services/oss/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 × 4) bindings/dotnet/src/operator.rs:1060— bindings/dotnet/src/operator.rs:1060-1068 | bindings/dotnet/src/operator.rs:1115-1123 | bindings/dotnet/src/operator.rs:1170-1178 | bindings/dotnet/src/operator.rs:1225-1233 — 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) core/services/azblob/src/core.rs:159— core/services/azblob/src/core.rs:159-167 | core/services/cos/src/core.rs:79-87 | core/services/obs/src/core.rs:74-82 | core/services/oss/src/core.rs:108-116 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 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 × 4) core/services/cos/src/core.rs:403— core/services/cos/src/core.rs:403-411 | core/services/obs/src/core.rs:344-352 | core/services/s3/src/core.rs:880-888 | core/services/s3/src/core.rs:922-930 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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 × 4) core/services/etcd/src/core.rs:98— core/services/etcd/src/core.rs:98-106 | core/services/memcached/src/core.rs:195-203 | core/services/redis/src/core.rs:162-170 | core/services/sftp/src/core.rs:82-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (9 lines × 4) core/services/fs/src/core.rs:116— core/services/fs/src/core.rs:116-124 | core/services/fs/src/writer.rs:211-219 | core/services/monoiofs/src/backend.rs:123-131 | core/services/monoiofs/src/writer.rs:162-170 — before extracting anything, compare `core/services/fs/src/core.rs` and `core/services/monoiofs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) core/services/azdls/src/reader.rs:69— core/services/azdls/src/reader.rs:69-77 | core/services/cos/src/reader.rs:70-78 | core/services/onedrive/src/reader.rs:78-86 | core/services/oss/src/reader.rs:70-78 — before extracting anything, compare `core/services/cos/src/reader.rs` and `core/services/oss/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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 × 4) core/services/dropbox/src/core.rs:185— core/services/dropbox/src/core.rs:185-191 | core/services/dropbox/src/core.rs:209-215 | core/services/dropbox/src/core.rs:251-257 | core/services/dropbox/src/core.rs:276-282 — 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) core/services/azdls/src/core.rs:75— core/services/azdls/src/core.rs:75-81 | core/services/azfile/src/core.rs:65-71 | core/services/gcs/src/core.rs:94-100 | core/services/oss/src/core.rs:95-101 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 98 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 × 4) bindings/java/src/operator.rs:169— bindings/java/src/operator.rs:169-175 | bindings/java/src/operator.rs:195-201 | bindings/java/src/operator.rs:282-288 | bindings/java/src/operator_output_stream.rs:94-100 — 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 (7 lines × 4) core/services/cos/src/core.rs:546— core/services/cos/src/core.rs:546-554 | core/services/gcs/src/core.rs:1048-1055 | core/services/oss/src/core.rs:643-649 | core/services/oss/src/core.rs:774-780 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 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 × 4) core/services/azfile/src/core.rs:213— core/services/azfile/src/core.rs:213-219 | core/services/cos/src/core.rs:501-509 | core/services/gcs/src/core.rs:1011-1018 | core/services/oss/src/core.rs:728-734 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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 × 4) core/services/aliyun-drive/src/config.rs:85— core/services/aliyun-drive/src/config.rs:85-92 | core/services/foyer/src/config.rs:71-78 | core/services/goosefs/src/config.rs:116-122 | core/services/moka/src/config.rs:58-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (6 lines × 3) core/services/azblob/src/backend.rs:307— core/services/azblob/src/backend.rs:307-312 | core/services/azdls/src/backend.rs:252-257 | core/services/gcs/src/backend.rs:252-258 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/azdls/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) core/services/azblob/src/core.rs:1325— core/services/azblob/src/core.rs:1325-1330 | core/services/azdls/src/core.rs:831-836 | core/services/azfile/src/core.rs:556-561 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) core/core/src/raw/oio/write/block_write.rs:163— core/core/src/raw/oio/write/block_write.rs:163-168 | core/core/src/raw/oio/write/multipart_write.rs:246-251 | core/core/src/raw/oio/write/position_write.rs:119-124 — 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) core/services/azfile/src/core.rs:378— core/services/azfile/src/core.rs:378-383 | core/services/azfile/src/core.rs:405-410 | core/services/cos/src/core.rs:310-316 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) core/services/azfile/src/core.rs:175— core/services/azfile/src/core.rs:175-180 | core/services/cos/src/core.rs:470-476 | core/services/oss/src/core.rs:694-699 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) core/services/gridfs/src/config.rs:58— core/services/gridfs/src/config.rs:58-63 | core/services/mongodb/src/config.rs:60-65 | core/services/surrealdb/src/config.rs:68-73 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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 (20 lines × 2) bindings/c/src/operator.rs:544— bindings/c/src/operator.rs:544-563 | bindings/c/src/operator.rs:606-625 — both copies are in the same file, so extract the block into 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) core/core/src/raw/http_util/multipart.rs:449— core/core/src/raw/http_util/multipart.rs:449-468 | core/core/src/raw/http_util/multipart.rs:485-504 — both copies are in the same file, so extract the block into 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) core/core/src/raw/ops.rs:444— core/core/src/raw/ops.rs:444-463 | core/core/src/raw/ops.rs:1117-1136 — both copies are in the same file, so extract the block into 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) core/services/rocksdb/src/lister.rs:44— core/services/rocksdb/src/lister.rs:44-63 | core/services/sled/src/lister.rs:44-63 — 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) core/services/s3/src/core.rs:1223— core/services/s3/src/core.rs:1223-1242 | core/services/s3/src/core.rs:1275-1294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 4) core/layers/retry/src/lib.rs:780— core/layers/retry/src/lib.rs:780-793 | core/layers/retry/src/lib.rs:812-825 | core/layers/retry/src/lib.rs:843-856 | core/layers/retry/src/lib.rs:874-887 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 4) core/services/cos/src/lister.rs:99— core/services/cos/src/lister.rs:99-112 | core/services/s3/src/lister.rs:136-149 | core/services/s3/src/lister.rs:253-266 | core/services/tos/src/lister.rs:96-109 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 192 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 × 4) core/services/cos/src/lister.rs:143— core/services/cos/src/lister.rs:143-156 | core/services/oss/src/lister.rs:146-159 | core/services/s3/src/lister.rs:299-312 | core/services/tos/src/lister.rs:140-153 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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 × 4) core/services/lakefs/src/reader.rs:64— core/services/lakefs/src/reader.rs:64-77 | core/services/obs/src/reader.rs:64-77 | core/services/swift/src/reader.rs:64-77 | core/services/tos/src/reader.rs:65-78 — before extracting anything, compare `core/services/lakefs/src/reader.rs` and `core/services/obs/src/reader.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 × 4) core/services/pcloud/src/core.rs:207— core/services/pcloud/src/core.rs:207-221 | core/services/pcloud/src/core.rs:237-250 | core/services/pcloud/src/core.rs:320-334 | core/services/pcloud/src/core.rs:350-364 — 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 × 3) bindings/c/src/types.rs:765— bindings/c/src/types.rs:765-775 | bindings/c/src/types.rs:1061-1071 | bindings/c/src/types.rs:1287-1297 — 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) core/services/gridfs/src/config.rs:79— core/services/gridfs/src/config.rs:79-89 | core/services/mongodb/src/config.rs:81-91 | core/services/surrealdb/src/config.rs:95-105 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) core/services/oss/src/core.rs:334— core/services/oss/src/core.rs:334-344 | core/services/oss/src/core.rs:386-396 | core/services/oss/src/core.rs:421-431 — 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) core/services/redb/src/config.rs:40— core/services/redb/src/config.rs:40-50 | core/services/rocksdb/src/config.rs:41-51 | core/services/sled/src/config.rs:51-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (11 lines × 3) core/services/azfile/src/core.rs:137— core/services/azfile/src/core.rs:137-147 | core/services/azfile/src/core.rs:190-201 | core/services/azfile/src/core.rs:334-345 — 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 × 5) core/layers/observe-metrics-common/src/lib.rs:759— core/layers/observe-metrics-common/src/lib.rs:759-767 | core/layers/observe-metrics-common/src/lib.rs:890-898 | core/layers/observe-metrics-common/src/lib.rs:925-933 | core/layers/observe-metrics-common/src/lib.rs:956-964 | core/layers/observe-metrics-common/src/lib.rs:1054-1062 — 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 (9 lines × 5) core/services/cacache/src/reader.rs:47— core/services/cacache/src/reader.rs:47-55 | core/services/dashmap/src/reader.rs:49-57 | core/services/etcd/src/reader.rs:47-56 | core/services/mini_moka/src/reader.rs:49-58 | core/services/moka/src/reader.rs:49-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (9 lines × 5) core/services/pcloud/src/core.rs:83— core/services/pcloud/src/core.rs:83-91 | core/services/seafile/src/core.rs:170-178 | core/services/seafile/src/core.rs:280-288 | core/services/seafile/src/core.rs:338-346 | core/services/seafile/src/core.rs:374-382 — before extracting anything, compare `core/services/pcloud/src/core.rs` and `core/services/seafile/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) core/services/webhdfs/src/core.rs:64— core/services/webhdfs/src/core.rs:64-72 | core/services/webhdfs/src/core.rs:98-106 | core/services/webhdfs/src/core.rs:293-301 | core/services/webhdfs/src/core.rs:386-394 | core/services/webhdfs/src/core.rs:413-421 — 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 (9 lines × 5) core/services/foundationdb/src/config.rs:41— core/services/foundationdb/src/config.rs:41-49 | core/services/persy/src/config.rs:42-50 | core/services/redb/src/config.rs:42-50 | core/services/rocksdb/src/config.rs:43-51 | core/services/sled/src/config.rs:53-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (6 lines × 4) bindings/c/src/presign.rs:147— bindings/c/src/presign.rs:147-152 | bindings/c/src/presign.rs:185-190 | bindings/c/src/presign.rs:222-227 | bindings/c/src/presign.rs:276-281 — 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) core/services/cos/src/core.rs:261— core/services/cos/src/core.rs:261-267 | core/services/gcs/src/core.rs:632-638 | core/services/oss/src/core.rs:429-434 | core/services/tos/src/core.rs:393-399 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) core/services/http/src/core.rs:170— core/services/http/src/core.rs:170-175 | core/services/ipfs/src/core.rs:274-279 | core/services/obs/src/core.rs:707-712 | core/services/vercel-artifacts/src/core.rs:149-154 — before extracting anything, compare `core/services/http/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 5 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 (6 lines × 4) core/services/koofr/src/core.rs:522— core/services/koofr/src/core.rs:522-527 | core/services/seafile/src/core.rs:561-566 | core/services/upyun/src/core.rs:618-623 | core/services/vercel-blob/src/core.rs:516-521 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (6 lines × 4) core/services/azblob/src/core.rs:275— core/services/azblob/src/core.rs:275-280 | core/services/cos/src/core.rs:122-127 | core/services/gcs/src/core.rs:284-289 | core/services/obs/src/core.rs:117-123 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 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.
No assertions: DeleteBehavior_DeletingMissingPath_IsAllowed bindings/dotnet/OpenDAL.Tests/Behavior/DeleteBehaviorTest.cs:68— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: DeleteBehavior_DeletingMissingPath_IsAllowedAsync bindings/dotnet/OpenDAL.Tests/Behavior/DeleteBehaviorTest.cs:79— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ListBehavior_Check_Succeeds bindings/dotnet/OpenDAL.Tests/Behavior/ListBehaviorTest.cs:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ListBehavior_Check_SucceedsAsync bindings/dotnet/OpenDAL.Tests/Behavior/ListBehaviorTest.cs:45— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/alluxio/src/core.rs:90— core/services/alluxio/src/core.rs:90-130 | core/services/alluxio/src/core.rs:132-162 | core/services/alluxio/src/core.rs:224-255 | core/services/alluxio/src/core.rs:261-292 | core/services/b2/src/core.rs:80-131 | core/services/gdrive/src/core.rs:739-786 | core/services/webhdfs/src/core.rs:179-216 — 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) core/services/cacache/src/reader.rs:38— core/services/cacache/src/reader.rs:38-58 | core/services/cloudflare-kv/src/reader.rs:51-146 | core/services/dashmap/src/reader.rs:38-60 | core/services/etcd/src/reader.rs:38-59 | core/services/foyer/src/reader.rs:38-59 | core/services/mini_moka/src/reader.rs:38-61 | core/services/moka/src/reader.rs:38-60 — 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) core/services/cos/src/core.rs:917— core/services/cos/src/core.rs:917-982 | core/services/dbfs/src/core.rs:267-297 | core/services/ipmfs/src/core.rs:210-248 | core/services/lakefs/src/core.rs:358-388 | core/services/obs/src/core.rs:706-741 | core/services/oss/src/core.rs:1228-1285 | core/services/webhdfs/src/core.rs:468-499 — 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) core/services/foundationdb/src/backend.rs:96— core/services/foundationdb/src/backend.rs:96-114 | core/services/gridfs/src/backend.rs:165-187 | core/services/memcached/src/backend.rs:212-230 | core/services/mongodb/src/backend.rs:180-202 | core/services/postgresql/src/backend.rs:157-175 | core/services/surrealdb/src/backend.rs:211-229 | core/services/tikv/src/backend.rs:125-143 — 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.
Duplicated block (19 lines × 2) core/services/azdls/src/config.rs:82— core/services/azdls/src/config.rs:82-100 | core/services/azfile/src/config.rs:57-75 — 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 (19 lines × 2) core/services/s3/src/lister.rs:147— core/services/s3/src/lister.rs:147-165 | core/services/s3/src/lister.rs:264-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 (19 lines × 2) core/services/yandex-disk/src/core.rs:84— core/services/yandex-disk/src/core.rs:84-102 | core/services/yandex-disk/src/core.rs:139-157 — both copies are in the same file, so extract the block into 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) integrations/object_store/src/service/core.rs:33— integrations/object_store/src/service/core.rs:33-51 | integrations/object_store/src/service/core.rs:60-78 — both copies are in the same file, so extract the block into 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 × 4) core/core/src/raw/ops.rs:115— core/core/src/raw/ops.rs:115-126 | core/core/src/raw/ops.rs:862-873 | core/core/src/raw/ops.rs:1110-1121 | core/core/src/raw/ops.rs:1296-1307 — 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) core/services/azdls/src/core.rs:885— core/services/azdls/src/core.rs:885-896 | core/services/azfile/src/core.rs:621-632 | core/services/cos/src/core.rs:955-966 | core/services/oss/src/core.rs:1257-1268 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 98 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) core/services/fs/src/core.rs:110— core/services/fs/src/core.rs:110-121 | core/services/hdfs/src/core.rs:68-79 | core/services/monoiofs/src/backend.rs:117-128 | core/services/monoiofs/src/writer.rs:156-167 — before extracting anything, compare `core/services/fs/src/core.rs` and `core/services/monoiofs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) core/services/dbfs/src/backend.rs:218— core/services/dbfs/src/backend.rs:218-229 | core/services/onedrive/src/backend.rs:275-286 | core/services/vercel-artifacts/src/backend.rs:206-217 | core/services/webdav/src/backend.rs:302-313 — before extracting anything, compare `core/services/dbfs/src/backend.rs` and `core/services/onedrive/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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–10 lines × 2) core/services/azblob/src/core.rs:725— core/services/azblob/src/core.rs:725-734 | core/services/gcs/src/core.rs:584-592 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 83 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–10 lines × 2) core/services/cos/src/lister.rs:115— core/services/cos/src/lister.rs:115-123 | core/services/tos/src/lister.rs:227-236 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/tos/src/lister.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 147 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–10 lines × 2) core/services/ghac/src/core.rs:285— core/services/ghac/src/core.rs:285-294 | core/services/ghac/src/core.rs:394-402 — both copies are in the same file, so extract the block into 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) bindings/dart/lib/opendal.dart:45— bindings/dart/lib/opendal.dart:45-54 | bindings/dart/lib/opendal.dart:70-78 — both copies are in the same file, so extract the block into 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) core/services/cos/src/core.rs:468— core/services/cos/src/core.rs:468-476 | core/services/oss/src/core.rs:692-699 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 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–9 lines × 2) core/services/ipfs/src/core.rs:275— core/services/ipfs/src/core.rs:275-283 | core/services/vercel-artifacts/src/core.rs:150-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8–9 lines × 2) core/services/ipmfs/src/reader.rs:48— core/services/ipmfs/src/reader.rs:48-55 | core/services/webhdfs/src/reader.rs:55-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8–9 lines × 2) core/services/koofr/src/backend.rs:114— core/services/koofr/src/backend.rs:114-121 | core/services/pcloud/src/backend.rs:110-118 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/pcloud/src/backend.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 72 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 × 5) bindings/c/src/operator.rs:1286— bindings/c/src/operator.rs:1286-1293 | bindings/c/src/operator.rs:1348-1355 | bindings/c/src/operator.rs:1421-1428 | bindings/c/src/operator.rs:1481-1488 | bindings/c/src/operator.rs:1520-1527 — 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 (8 lines × 5) core/services/cos/src/lister.rs:105— core/services/cos/src/lister.rs:105-112 | core/services/s3/src/lister.rs:142-149 | core/services/s3/src/lister.rs:259-266 | core/services/tos/src/lister.rs:102-109 | core/services/tos/src/lister.rs:240-247 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 192 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 × 5) core/services/fs/src/core.rs:114— core/services/fs/src/core.rs:114-122 | core/services/fs/src/writer.rs:209-217 | core/services/hdfs/src/core.rs:72-79 | core/services/monoiofs/src/backend.rs:121-129 | core/services/monoiofs/src/writer.rs:160-168 — before extracting anything, compare `core/services/fs/src/core.rs` and `core/services/monoiofs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 5) core/services/gridfs/src/backend.rs:231— core/services/gridfs/src/backend.rs:231-238 | core/services/mongodb/src/backend.rs:246-253 | core/services/mysql/src/backend.rs:227-234 | core/services/redis/src/backend.rs:354-361 | core/services/surrealdb/src/backend.rs:273-280 — before extracting anything, compare `core/services/gridfs/src/backend.rs` and `core/services/mongodb/src/backend.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) core/services/azdls/src/core.rs:361— core/services/azdls/src/core.rs:361-366 | core/services/gcs/src/core.rs:248-253 | core/services/http/src/core.rs:67-73 | core/services/http/src/core.rs:116-122 | core/services/swift/src/core.rs:396-401 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) core/services/azfile/src/core.rs:158— core/services/azfile/src/core.rs:158-164 | core/services/cos/src/core.rs:338-344 | core/services/obs/src/core.rs:288-294 | core/services/oss/src/core.rs:180-186 | core/services/oss/src/core.rs:671-676 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 5) core/services/etcd/src/core.rs:97— core/services/etcd/src/core.rs:97-102 | core/services/ftp/src/core.rs:62-67 | core/services/memcached/src/core.rs:194-199 | core/services/redis/src/core.rs:161-166 | core/services/sftp/src/core.rs:81-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (6 lines × 5) core/services/github/src/core.rs:446— core/services/github/src/core.rs:446-451 | core/services/seafile/src/core.rs:573-578 | core/services/upyun/src/core.rs:634-639 | core/services/vercel-blob/src/core.rs:528-533 | core/services/yandex-disk/src/core.rs:437-442 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Off the main sequence: opendal — opendal: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: opendal-core — opendal-core: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 94 project(s), so it's rigid to change.
Off the main sequence: opendal-service-azure-common — opendal-service-azure-common: abstractness 0.00, instability 0.25, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: opendal-layer-observe-metrics-common — opendal-layer-observe-metrics-common: abstractness 0.11, instability 0.17, distance 0.72 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) core/services/gridfs/src/backend.rs:224— core/services/gridfs/src/backend.rs:224-238 | core/services/mongodb/src/backend.rs:239-253 | core/services/mysql/src/backend.rs:220-234 | core/services/postgresql/src/backend.rs:212-229 | core/services/redis/src/backend.rs:347-361 | core/services/surrealdb/src/backend.rs:266-280 — 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) core/services/webhdfs/src/core.rs:59— core/services/webhdfs/src/core.rs:59-83 | core/services/webhdfs/src/core.rs:93-148 | core/services/webhdfs/src/core.rs:289-307 | core/services/webhdfs/src/core.rs:314-336 | core/services/webhdfs/src/core.rs:382-403 | core/services/webhdfs/src/core.rs:409-430 — 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) REDACTED:242— REDACTED:242-252 | REDACTED:258-268 | REDACTED:733-749 | REDACTED:886-902 | REDACTED:342-358 | REDACTED:559-575 — 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.
Duplicated block (21 lines × 4) core/services/cos/src/backend.rs:506— core/services/cos/src/backend.rs:506-526 | core/services/gcs/src/backend.rs:612-632 | core/services/obs/src/backend.rs:461-481 | core/services/oss/src/backend.rs:840-860 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/gcs/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 4) core/services/cos/src/writer.rs:144— core/services/cos/src/writer.rs:144-164 | core/services/obs/src/writer.rs:141-161 | core/services/oss/src/writer.rs:141-161 | core/services/tos/src/writer.rs:134-154 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. 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 × 4) core/services/gcs/src/core.rs:221— core/services/gcs/src/core.rs:221-241 | core/services/gcs/src/core.rs:611-631 | core/services/s3/src/core.rs:474-494 | core/services/s3/src/core.rs:550-570 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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) bindings/haskell/src/lib.rs:332— bindings/haskell/src/lib.rs:332-352 | bindings/haskell/src/lib.rs:383-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 (21 lines × 2) core/services/cos/src/lister.rs:251— core/services/cos/src/lister.rs:251-271 | core/services/oss/src/lister.rs:254-274 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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) core/services/s3/src/core.rs:648— core/services/s3/src/core.rs:648-668 | core/services/s3/src/core.rs:693-713 — both copies are in the same file, so extract the block into 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–19 lines × 2) core/core/src/layers/simulate.rs:564— core/core/src/layers/simulate.rs:564-581 | core/core/src/raw/oio/list/flat_list.rs:161-179 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (18–19 lines × 2) core/services/azblob/src/backend.rs:379— core/services/azblob/src/backend.rs:379-397 | core/services/azdls/src/backend.rs:312-329 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/azdls/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 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 (18–19 lines × 2) core/services/s3/src/copier.rs:204— core/services/s3/src/copier.rs:204-222 | core/services/s3/src/copier.rs:371-388 — both copies are in the same file, so extract the block into 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) core/services/cos/src/core.rs:151— core/services/cos/src/core.rs:151-167 | core/services/obs/src/core.rs:135-151 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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 (17 lines × 2) core/services/cos/src/core.rs:433— core/services/cos/src/core.rs:433-449 | core/services/s3/src/core.rs:966-982 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 91 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 (17 lines × 2) core/services/postgresql/src/core.rs:46— core/services/postgresql/src/core.rs:46-62 | core/services/sqlite/src/core.rs:49-66 — before extracting anything, compare `core/services/postgresql/src/core.rs` and `core/services/sqlite/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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–16 lines × 2) core/layers/foyer/src/lib.rs:283— core/layers/foyer/src/lib.rs:283-297 | core/layers/route/src/lib.rs:206-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15–16 lines × 2) core/services/gcs-grpc/src/writer.rs:148— core/services/gcs-grpc/src/writer.rs:148-162 | core/services/gcs-grpc/src/writer.rs:258-273 — both copies are in the same file, so extract the block into 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) core/services/s3/src/core.rs:434— core/services/s3/src/core.rs:434-449 | core/services/s3/src/core.rs:989-1003 — both copies are in the same file, so extract the block into 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–13 lines × 3) core/services/azblob/src/core.rs:244— core/services/azblob/src/core.rs:244-256 | core/services/s3/src/core.rs:510-520 | core/services/s3/src/core.rs:588-600 — 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 (11–13 lines × 3) core/services/cloudflare-kv/src/reader.rs:136— core/services/cloudflare-kv/src/reader.rs:136-146 | core/services/etcd/src/reader.rs:45-56 | core/services/foyer/src/reader.rs:47-59 — 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 (11–13 lines × 3) core/services/foundationdb/src/backend.rs:152— core/services/foundationdb/src/backend.rs:152-164 | core/services/memcached/src/backend.rs:268-278 | core/services/tikv/src/backend.rs:175-185 — before extracting anything, compare `core/services/foundationdb/src/backend.rs` and `core/services/memcached/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 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–13 lines × 2) core/services/alluxio/src/core.rs:113— core/services/alluxio/src/core.rs:113-125 | core/services/alluxio/src/core.rs:146-157 — both copies are in the same file, so extract the block into 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) core/services/cos/src/core.rs:487— core/services/cos/src/core.rs:487-498 | core/services/s3/src/core.rs:1179-1191 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 91 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–13 lines × 2) core/services/cos/src/writer.rs:84— core/services/cos/src/writer.rs:84-96 | core/services/oss/src/writer.rs:74-85 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/oss/src/writer.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) core/services/cloudflare-kv/src/core.rs:222— core/services/cloudflare-kv/src/core.rs:222-232 | core/services/d1/src/core.rs:224-234 | core/services/dropbox/src/core.rs:575-585 | core/services/gdrive/src/core.rs:1144-1154 | core/services/tos/src/core.rs:1136-1146 — before extracting anything, compare `core/services/cloudflare-kv/src/core.rs` and `core/services/d1/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) core/services/gcs/src/core.rs:220— core/services/gcs/src/core.rs:220-230 | core/services/gcs/src/core.rs:610-620 | core/services/oss/src/core.rs:326-336 | core/services/s3/src/core.rs:473-483 | core/services/s3/src/core.rs:549-559 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) core/core/src/services/memory/deleter.rs:31— core/core/src/services/memory/deleter.rs:31-41 | core/services/persy/src/deleter.rs:31-41 | core/services/redb/src/deleter.rs:31-41 | core/services/rocksdb/src/deleter.rs:31-41 | core/services/sled/src/deleter.rs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (8–10 lines × 2) bindings/dotnet/src/operator.rs:1527— bindings/dotnet/src/operator.rs:1527-1536 | bindings/dotnet/src/operator.rs:1582-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 (8–10 lines × 2) core/core/src/raw/oio/write/block_write.rs:201— core/core/src/raw/oio/write/block_write.rs:201-208 | core/core/src/raw/oio/write/multipart_write.rs:329-338 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–10 lines × 2) core/services/webhdfs/src/core.rs:184— core/services/webhdfs/src/core.rs:184-193 | core/services/webhdfs/src/core.rs:265-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.
Duplicated block (8–9 lines × 3) core/services/alluxio/src/core.rs:145— core/services/alluxio/src/core.rs:145-152 | core/services/alluxio/src/core.rs:237-245 | core/services/alluxio/src/core.rs:274-282 — 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–9 lines × 3) core/services/cos/src/backend.rs:438— core/services/cos/src/backend.rs:438-445 | core/services/oss/src/backend.rs:771-778 | core/services/swift/src/backend.rs:381-389 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/oss/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 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–9 lines × 3) core/services/gcs/src/core.rs:188— core/services/gcs/src/core.rs:188-195 | core/services/gcs/src/core.rs:246-253 | core/services/http/src/core.rs:65-73 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/http/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 9) core/services/aliyun-drive/src/backend.rs:259— core/services/aliyun-drive/src/backend.rs:259-265 | core/services/koofr/src/backend.rs:305-311 | core/services/lakefs/src/backend.rs:306-312 | core/services/obs/src/backend.rs:406-411 | core/services/onedrive/src/backend.rs:307-313 | core/services/pcloud/src/backend.rs:286-292 | core/services/upyun/src/backend.rs:288-294 | core/services/vercel-blob/src/backend.rs:218-224 | core/services/yandex-disk/src/backend.rs:191-197 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/koofr/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 9) core/services/koofr/src/backend.rs:304— core/services/koofr/src/backend.rs:304-309 | core/services/lakefs/src/backend.rs:305-310 | core/services/obs/src/backend.rs:405-410 | core/services/onedrive/src/backend.rs:306-311 | core/services/pcloud/src/backend.rs:285-290 | core/services/upyun/src/backend.rs:287-292 | core/services/vercel-blob/src/backend.rs:217-222 | core/services/webdav/src/backend.rs:346-351 | core/services/yandex-disk/src/backend.rs:190-195 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/lakefs/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 9) core/services/azblob/src/backend.rs:116— core/services/azblob/src/backend.rs:116-123 | core/services/azdls/src/backend.rs:112-119 | core/services/azfile/src/backend.rs:93-100 | core/services/cos/src/backend.rs:82-88 | core/services/ipfs/src/backend.rs:78-85 | core/services/obs/src/backend.rs:84-90 | core/services/tos/src/backend.rs:85-90 | core/services/vercel-artifacts/src/backend.rs:62-67 | core/services/webhdfs/src/backend.rs:79-85 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/azdls/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 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) core/services/foyer/src/reader.rs:39— core/services/foyer/src/reader.rs:39-44 | core/services/memcached/src/reader.rs:39-43 | core/services/mysql/src/reader.rs:40-44 | core/services/tikv/src/reader.rs:40-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5 lines × 4) core/services/hf/src/core.rs:577— core/services/hf/src/core.rs:577-581 | core/services/hf/src/core.rs:752-756 | core/services/hf/src/core.rs:967-972 | core/services/hf/src/core.rs:1011-1016 — 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) core/core/src/blocking/read/buffer_iterator.rs:61— core/core/src/blocking/read/buffer_iterator.rs:61-65 | core/core/src/blocking/read/reader.rs:117-121 | core/core/src/blocking/read/std_bytes_iterator.rs:65-69 | core/core/src/blocking/write/writer.rs:104-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (8 lines × 4) core/services/alluxio/src/backend.rs:66— core/services/alluxio/src/backend.rs:66-73 | core/services/hdfs-native/src/backend.rs:64-71 | core/services/oss/src/backend.rs:91-98 | core/services/s3/src/backend.rs:128-135 — before extracting anything, compare `core/services/oss/src/backend.rs` and `core/services/s3/src/backend.rs` as WHOLE FILES: this scan already matched 4 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 (8 lines × 4) core/services/dashmap/src/backend.rs:42— core/services/dashmap/src/backend.rs:42-50 | core/services/foyer/src/backend.rs:109-116 | core/services/mini_moka/src/backend.rs:76-84 | core/services/moka/src/backend.rs:132-139 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/foyer/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) core/services/alluxio/src/backend.rs:200— core/services/alluxio/src/backend.rs:200-207 | core/services/koofr/src/backend.rs:288-295 | core/services/pcloud/src/backend.rs:269-276 | core/services/seafile/src/backend.rs:269-276 — before extracting anything, compare `core/services/alluxio/src/backend.rs` and `core/services/koofr/src/backend.rs` as WHOLE FILES: this scan already matched 4 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.
Sync-over-async blocking bindings/nodejs/tests/suites/sync.suite.mjs:25— `run` holds an async function that calls statSync, readSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking website/plugins/services-docs-plugin.js:38— `servicesDocsPlugin` holds an async function that calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking website/plugins/specifications-docs-plugin.js:69— `includeSpecifications` is async and calls readFileSync — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
R4 · Test Coverage· No test reaches this file · ×3
No test reaches this file bindings/nodejs/index.cjs— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file bindings/nodejs/scripts/header.mjs— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file bindings/nodejs/theme/index.tsx— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
opendal_service_webdav::core::parse_user_metadata_from_xml (cognitive 54) core/services/webdav/src/core.rs:609— opendal_service_webdav::core::parse_user_metadata_from_xml has cognitive complexity 54 (threshold 15). Drivers by points: if/else 10 (39 pts), loops 3 (7 pts), match/switch 2 (5 pts), boolean chains 3 (nesting depth added 36). 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.
opendal_service_webdav::core::check_proppatch_response (cognitive 16) core/services/webdav/src/core.rs:726— opendal_service_webdav::core::check_proppatch_response has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GdriveFlatLister::initialize (cognitive 47) core/services/gdrive/src/lister.rs:400— GdriveFlatLister::initialize has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (26 pts), match/switch 9 (19 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GdriveFlatLister::process_batch (cognitive 18) core/services/gdrive/src/lister.rs:613— GdriveFlatLister::process_batch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts), 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.
S3Builder::build (cognitive 40) core/services/s3/src/backend.rs:826— S3Builder::build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 28 (31 pts), match/switch 8, 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.
S3Builder::resolve_s3_express_config (cognitive 16) core/services/s3/src/backend.rs:578— S3Builder::resolve_s3_express_config has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, 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.
GdriveBackend::rename (cognitive 33) core/services/gdrive/src/backend.rs:482— GdriveBackend::rename has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (32 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
GdriveBackend::copy (cognitive 17) core/services/gdrive/src/backend.rs:382— GdriveBackend::copy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (3 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
OssBuilder::build (cognitive 28) core/services/oss/src/backend.rs:412— OssBuilder::build has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20 (23 pts), match/switch 3, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
OssBuilder::parse_endpoint (cognitive 21) core/services/oss/src/backend.rs:191— OssBuilder::parse_endpoint has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 5 (10 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
S3Copier::copy_once (cognitive 19) core/services/s3/src/copier.rs:174— S3Copier::copy_once has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, match/switch 1 (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.
S3Copier::complete_copy (cognitive 17) core/services/s3/src/copier.rs:337— S3Copier::complete_copy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 6). 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.
D20 · ADR Quality· No consequences/trade-offs section; the decision is stated but no negative impact or alternative trade-off is noted · ×2
No consequences/trade-offs section; the decision is stated but no negative impact or alternative trade-off is noted core/core/src/docs/rfcs/2774_lister_api.md— Add a Consequences section covering trade-offs such as increased boilerplate for callers needing to call lister.on_demand() separately from list(), and whether the scan/merge into list_with change has been reviewed
No consequences/trade-offs section; the decision is stated but no negative impact or alternative trade-off is noted core/core/src/docs/rfcs/3356_lazy_reader.md— Add a Consequences section covering the cost of deferring IO requests until the first read call (e.g. increased latency for readers invoked before any seek) and note how it balances against the benchmark results
FunctionTooLong: opendal::init_default_registry_inner core/src/lib.rs:69— FunctionTooLong — opendal::init_default_registry_inner runs 132 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 32 over it, 1.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.
FunctionTooLong: index.SearchBar website/src/theme/SearchBar/index.jsx:65— FunctionTooLong — SearchBar runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.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.
D4 · Code Duplication· Members sharing a duplicated core (13 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (13 members, 50+ identical tokens) bindings/haskell/src/lib.rs:153— bindings/haskell/src/lib.rs:153-177 | bindings/haskell/src/lib.rs:199-228 | bindings/haskell/src/lib.rs:245-269 | bindings/haskell/src/lib.rs:286-310 | bindings/haskell/src/lib.rs:329-361 | bindings/haskell/src/lib.rs:380-412 | bindings/haskell/src/lib.rs:429-453 | bindings/haskell/src/lib.rs:470-494 | bindings/haskell/src/lib.rs:511-535 | bindings/haskell/src/lib.rs:552-582 | bindings/haskell/src/lib.rs:691-724 | bindings/haskell/src/lib.rs:743-767 | bindings/haskell/src/lib.rs:786-816 — 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.
Members sharing a duplicated core (13 members, 50+ identical tokens) core/services/d1/src/reader.rs:40— core/services/d1/src/reader.rs:40-59 | core/services/foundationdb/src/reader.rs:38-60 | core/services/gridfs/src/reader.rs:38-57 | core/services/memcached/src/reader.rs:38-55 | core/services/mongodb/src/reader.rs:38-57 | core/services/mysql/src/reader.rs:39-56 | core/services/persy/src/reader.rs:38-57 | core/services/postgresql/src/reader.rs:38-60 | core/services/redb/src/reader.rs:38-57 | core/services/rocksdb/src/reader.rs:38-57 | core/services/sled/src/reader.rs:38-57 | core/services/surrealdb/src/reader.rs:38-57 | core/services/tikv/src/reader.rs:39-56 — 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.
Duplicated block (28 lines × 2) core/services/azdls/src/core.rs:885— core/services/azdls/src/core.rs:885-912 | core/services/azfile/src/core.rs:621-648 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 98 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 (28 lines × 2) core/services/cos/src/lister.rs:66— core/services/cos/src/lister.rs:66-93 | core/services/obs/src/lister.rs:63-90 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 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–22 lines × 2) core/services/gdrive/src/core.rs:308— core/services/gdrive/src/core.rs:308-328 | core/services/gdrive/src/core.rs:355-376 — both copies are in the same file, so extract the block into 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–22 lines × 2) REDACTED:148— REDACTED:148-168 | REDACTED:176-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:148` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–19 lines × 4) core/services/cos/src/lister.rs:198— core/services/cos/src/lister.rs:198-215 | core/services/oss/src/lister.rs:201-218 | core/services/s3/src/lister.rs:354-371 | core/services/tos/src/lister.rs:190-208 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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 (18–19 lines × 4) core/services/cos/src/writer.rs:137— core/services/cos/src/writer.rs:137-154 | core/services/obs/src/writer.rs:133-151 | core/services/oss/src/writer.rs:133-151 | core/services/s3/src/writer.rs:156-173 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–18 lines × 2) core/services/dashmap/src/backend.rs:88— core/services/dashmap/src/backend.rs:88-105 | core/services/moka/src/backend.rs:194-209 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–18 lines × 2) dev/src/generate/dotnet.rs:153— dev/src/generate/dotnet.rs:153-168 | dev/src/generate/dotnet.rs:186-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–17 lines × 2) bindings/dotnet/src/operator.rs:1776— bindings/dotnet/src/operator.rs:1776-1792 | bindings/dotnet/src/operator.rs:1853-1867 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–17 lines × 2) core/services/tos/src/copier.rs:241— core/services/tos/src/copier.rs:241-255 | core/services/tos/src/writer.rs:186-202 — before extracting anything, compare `core/services/tos/src/copier.rs` and `core/services/tos/src/writer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 3) core/layers/retry/src/lib.rs:1007— core/layers/retry/src/lib.rs:1007-1022 | core/layers/retry/src/lib.rs:1038-1053 | core/layers/retry/src/lib.rs:1069-1084 — 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 (16 lines × 3) core/services/azblob/src/core.rs:1261— core/services/azblob/src/core.rs:1261-1276 | core/services/azdls/src/core.rs:767-782 | core/services/azfile/src/core.rs:520-535 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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–16 lines × 3) core/services/cos/src/core.rs:399— core/services/cos/src/core.rs:399-414 | core/services/obs/src/core.rs:341-355 | core/services/s3/src/core.rs:876-891 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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–16 lines × 3) core/services/cos/src/writer.rs:102— core/services/cos/src/writer.rs:102-117 | core/services/obs/src/writer.rs:93-107 | core/services/oss/src/writer.rs:91-106 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. 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–14 lines × 2) core/services/cos/src/core.rs:300— core/services/cos/src/core.rs:300-312 | core/services/oss/src/core.rs:391-404 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 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–14 lines × 2) core/services/cos/src/writer.rs:252— core/services/cos/src/writer.rs:252-265 | core/services/oss/src/writer.rs:244-256 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/oss/src/writer.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 129 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 × 5) bindings/python/src/file.rs:98— bindings/python/src/file.rs:98-110 | bindings/python/src/file.rs:146-158 | bindings/python/src/file.rs:187-199 | bindings/python/src/file.rs:292-304 | bindings/python/src/file.rs:324-336 — 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 (13 lines × 5) core/services/ghac/src/core.rs:576— core/services/ghac/src/core.rs:576-588 | core/services/http/src/core.rs:187-199 | core/services/ipfs/src/core.rs:289-301 | core/services/onedrive/src/core.rs:1056-1068 | core/services/vercel-artifacts/src/core.rs:162-174 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (13 lines × 4) core/services/alluxio/src/config.rs:55— core/services/alluxio/src/config.rs:55-67 | core/services/ipfs/src/config.rs:38-50 | core/services/ipmfs/src/config.rs:38-50 | core/services/webhdfs/src/config.rs:60-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (13 lines × 4) REDACTED:192— REDACTED:192-204 | REDACTED:343-355 | REDACTED:394-406 | REDACTED:412-424 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:192` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 13) bindings/haskell/src/lib.rs:154— bindings/haskell/src/lib.rs:154-164 | bindings/haskell/src/lib.rs:200-210 | bindings/haskell/src/lib.rs:246-256 | bindings/haskell/src/lib.rs:287-297 | bindings/haskell/src/lib.rs:330-340 | bindings/haskell/src/lib.rs:381-391 | bindings/haskell/src/lib.rs:430-440 | bindings/haskell/src/lib.rs:471-481 | bindings/haskell/src/lib.rs:512-522 | bindings/haskell/src/lib.rs:553-563 | bindings/haskell/src/lib.rs:692-702 | bindings/haskell/src/lib.rs:744-754 | bindings/haskell/src/lib.rs:787-797 — 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 (11 lines × 13) core/services/d1/src/reader.rs:49— core/services/d1/src/reader.rs:49-59 | core/services/foundationdb/src/reader.rs:50-60 | core/services/gridfs/src/reader.rs:47-57 | core/services/memcached/src/reader.rs:45-55 | core/services/mongodb/src/reader.rs:47-57 | core/services/mysql/src/reader.rs:46-56 | core/services/persy/src/reader.rs:47-57 | core/services/postgresql/src/reader.rs:50-60 | core/services/redb/src/reader.rs:47-57 | core/services/rocksdb/src/reader.rs:47-57 | core/services/sled/src/reader.rs:47-57 | core/services/surrealdb/src/reader.rs:47-57 | core/services/tikv/src/reader.rs:46-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 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 13 times.
Duplicated block (10–11 lines × 3) core/services/gcs/src/core.rs:1072— core/services/gcs/src/core.rs:1072-1081 | core/services/obs/src/core.rs:479-489 | core/services/oss/src/core.rs:798-807 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 3) core/services/s3/src/core.rs:495— core/services/s3/src/core.rs:495-504 | core/services/s3/src/core.rs:571-580 | core/services/s3/src/core.rs:732-742 — 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–11 lines × 2) core/services/azblob/src/core.rs:306— core/services/azblob/src/core.rs:306-315 | core/services/azblob/src/core.rs:614-624 — both copies are in the same file, so extract the block into 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–11 lines × 2) core/services/cos/src/core.rs:267— core/services/cos/src/core.rs:267-276 | core/services/obs/src/core.rs:229-239 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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–10 lines × 3) core/services/cos/src/writer.rs:82— core/services/cos/src/writer.rs:82-91 | core/services/obs/src/writer.rs:74-82 | core/services/oss/src/writer.rs:72-80 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. 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–10 lines × 3) core/services/gcs/src/core.rs:131— core/services/gcs/src/core.rs:131-140 | core/services/oss/src/core.rs:124-133 | core/services/tos/src/core.rs:109-117 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 154 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 × 5) core/services/cos/src/core.rs:406— core/services/cos/src/core.rs:406-412 | core/services/cos/src/core.rs:598-605 | core/services/obs/src/core.rs:347-353 | core/services/oss/src/core.rs:580-587 | core/services/s3/src/core.rs:883-889 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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 × 5) core/services/pcloud/src/core.rs:83— core/services/pcloud/src/core.rs:83-91 | core/services/seafile/src/core.rs:338-346 | core/services/seafile/src/core.rs:374-382 | core/services/yandex-disk/src/core.rs:89-95 | core/services/yandex-disk/src/core.rs:144-150 — before extracting anything, compare `core/services/pcloud/src/core.rs` and `core/services/seafile/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 7) bindings/java/src/operator.rs:73— bindings/java/src/operator.rs:73-79 | bindings/java/src/operator.rs:140-146 | bindings/java/src/operator.rs:222-228 | bindings/java/src/operator.rs:253-259 | bindings/java/src/operator.rs:317-323 | bindings/java/src/operator_input_stream.rs:43-49 | bindings/java/src/operator_output_stream.rs:42-48 — there are 7 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 7) core/services/azblob/src/core.rs:847— core/services/azblob/src/core.rs:847-854 | core/services/azdls/src/core.rs:585-592 | core/services/cos/src/core.rs:417-425 | core/services/cos/src/core.rs:613-621 | core/services/gcs/src/core.rs:918-926 | core/services/obs/src/core.rs:358-366 | core/services/oss/src/core.rs:595-601 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) core/services/azblob/src/backend.rs:572— core/services/azblob/src/backend.rs:572-581 | core/services/cloudflare-kv/src/backend.rs:406-415 | core/services/gcs/src/backend.rs:527-536 | core/services/oss/src/backend.rs:727-736 | core/services/s3/src/backend.rs:1249-1258 | core/services/swift/src/backend.rs:314-323 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/cloudflare-kv/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) REDACTED:185— REDACTED:185-194 | REDACTED:188-197 | REDACTED:237-246 | REDACTED:286-295 | REDACTED:335-344 | REDACTED:433-442 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:431` calls `toOpendalBytes` and `REDACTED:183` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) core/services/azblob/src/core.rs:654— core/services/azblob/src/core.rs:654-658 | core/services/azblob/src/core.rs:706-710 | core/services/gcs/src/core.rs:806-810 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 83 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 × 3) core/services/cacache/src/backend.rs:140— core/services/cacache/src/backend.rs:140-145 | core/services/opfs/src/backend.rs:120-124 | core/services/opfs/src/backend.rs:139-143 — 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 (10 lines × 4) core/services/azblob/src/backend.rs:640— core/services/azblob/src/backend.rs:640-650 | core/services/cos/src/backend.rs:506-515 | core/services/gcs/src/backend.rs:612-621 | core/services/obs/src/backend.rs:461-470 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/cos/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) REDACTED:740— REDACTED:740-749 | REDACTED:893-902 | REDACTED:349-358 | REDACTED:566-575 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:740` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
AXR1 · Runtime accessibility (rendered)· WCAG 2.4.2 reproducibly failed in a rendered surface · ×1
WCAG 2.4.2 reproducibly failed in a rendered surface — axe-core rule(s) document-title failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
AXR1 · Runtime accessibility (rendered)· WCAG 3.1.1 reproducibly failed in a rendered surface · ×1
WCAG 3.1.1 reproducibly failed in a rendered surface — axe-core rule(s) html-has-lang failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
S3Builder::build (cyclomatic 32) core/services/s3/src/backend.rs:826— S3Builder::build has cyclomatic complexity 32 (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.
Storage.init (cyclomatic 32) bindings/dart/lib/opendal.dart:32— Storage.init 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.
local-images.localImages (cyclomatic 31) website/plugins/local-images.js:26— local-images.localImages has cyclomatic complexity 31 (threshold 15). Of this number, 16 points are the body's own statements and 15 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
opendal_service_webdav::core::parse_user_metadata_from_xml (cyclomatic 29) core/services/webdav/src/core.rs:609— opendal_service_webdav::core::parse_user_metadata_from_xml 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.
GdriveFlatLister::initialize (cyclomatic 24) core/services/gdrive/src/lister.rs:400— GdriveFlatLister::initialize 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.
CorrectnessService::compose (cyclomatic 22) core/core/src/layers/correctness_check.rs:339— CorrectnessService::compose has cyclomatic complexity 22 (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.
OssBuilder::build (cyclomatic 21) core/services/oss/src/backend.rs:412— OssBuilder::build has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ServicerFlatLister::next (cyclomatic 20) core/core/src/layers/simulate.rs:501— ServicerFlatLister::next 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.
FlatLister::next (cyclomatic 20) core/core/src/raw/oio/list/flat_list.rs:89— FlatLister::next 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.
CloudflareKvBackend::stat (cyclomatic 20) core/services/cloudflare-kv/src/backend.rs:257— CloudflareKvBackend::stat 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.
GdriveLister::next_page (cyclomatic 20) core/services/gdrive/src/lister.rs:123— GdriveLister::next_page 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.
OneDriveLister::next_page (cyclomatic 19) core/services/onedrive/src/lister.rs:63— OneDriveLister::next_page 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.
label.selected_labels (cyclomatic 19) scripts/label.py:240— label.selected_labels 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.
HfCore::read (cyclomatic 18) core/services/hf/src/core.rs:774— HfCore::read 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.
sign_source_release.validate (cyclomatic 18) scripts/sign_source_release.py:58— sign_source_release.validate 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.
verify_source_reproducibility.main (cyclomatic 18) scripts/verify_source_reproducibility.py:35— verify_source_reproducibility.main 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.
index.SearchBar (cyclomatic 18) website/src/theme/SearchBar/index.jsx:65— index.SearchBar has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 99, 130, 82, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
opendal_service_gcs::core::parse_error (cyclomatic 17) core/services/gcs/src/core.rs:2014— opendal_service_gcs::core::parse_error 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.
odev::generate::python::format_text (cyclomatic 17) dev/src/generate/python.rs:115— odev::generate::python::format_text 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.
opendal.newOpendalReadOptions (cyclomatic 17) REDACTED:239— opendal.newOpendalReadOptions has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
CosObjectVersionsLister::next_page (cyclomatic 16) core/services/cos/src/lister.rs:160— CosObjectVersionsLister::next_page 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.
FsLister::next (cyclomatic 16) core/services/fs/src/lister.rs:50— FsLister::next 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.
OssObjectVersionsLister::next_page (cyclomatic 16) core/services/oss/src/lister.rs:163— OssObjectVersionsLister::next_page 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.
S3ObjectVersionsLister::next_page (cyclomatic 16) core/services/s3/src/lister.rs:316— S3ObjectVersionsLister::next_page 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.
TosObjectVersionsLister::next_page (cyclomatic 16) core/services/tos/src/lister.rs:157— TosObjectVersionsLister::next_page 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.
local-images.localImages (cognitive 62) website/plugins/local-images.js:26— local-images.localImages has cognitive complexity 62 (threshold 15). Drivers by points: if/else 20 (44 pts), error handling 3 (10 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 32). Of this number, 26 points are the body's own statements and 36 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Storage.init (cognitive 45) bindings/dart/lib/opendal.dart:32— Storage.init has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (33 pts), boolean chains 8, ternaries 2 (4 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.
ServicerFlatLister::next (cognitive 38) core/core/src/layers/simulate.rs:501— ServicerFlatLister::next has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 5 (14 pts), loops 2 (4 pts) (nesting depth added 24). 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.
FlatLister::next (cognitive 38) core/core/src/raw/oio/list/flat_list.rs:89— FlatLister::next has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 5 (14 pts), loops 2 (4 pts) (nesting depth added 24). 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.
OneDriveLister::next_page (cognitive 38) core/services/onedrive/src/lister.rs:63— OneDriveLister::next_page has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (30 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verify_source_reproducibility.main (cognitive 33) scripts/verify_source_reproducibility.py:35— verify_source_reproducibility.main has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 3 (7 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HfCore::read (cognitive 31) core/services/hf/src/core.rs:774— HfCore::read has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 3 (8 pts), boolean chains 2, loops 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.
CloudflareKvBackend::stat (cognitive 28) core/services/cloudflare-kv/src/backend.rs:257— CloudflareKvBackend::stat has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 7, 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.
CosObjectVersionsLister::next_page (cognitive 28) core/services/cos/src/lister.rs:160— CosObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (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.
OssObjectVersionsLister::next_page (cognitive 28) core/services/oss/src/lister.rs:163— OssObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (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.
S3ObjectVersionsLister::next_page (cognitive 28) core/services/s3/src/lister.rs:316— S3ObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (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.
TosObjectVersionsLister::next_page (cognitive 28) core/services/tos/src/lister.rs:157— TosObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (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.
GcsGrpcWriter::drive_pending (cognitive 27) core/services/gcs-grpc/src/writer.rs:201— GcsGrpcWriter::drive_pending has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (20 pts), match/switch 2 (5 pts), boolean chains 1, loops 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.
GdriveLister::next_page (cognitive 27) core/services/gdrive/src/lister.rs:123— GdriveLister::next_page has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 5 (7 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.
YandexDiskLister::next_page (cognitive 27) core/services/yandex-disk/src/lister.rs:56— YandexDiskLister::next_page has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 1 (3 pts), match/switch 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.
CratesIoClient._request (cognitive 27) .github/scripts/release_rust/bootstrap.py:110— CratesIoClient._request has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (8 pts), boolean chains 4, error handling 2 (4 pts), loops 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.
SwiftLister::next_page (cognitive 26) core/services/swift/src/lister.rs:62— SwiftLister::next_page has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 2 (4 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.
CloudflareKvLister::next_page (cognitive 25) core/services/cloudflare-kv/src/lister.rs:125— CloudflareKvLister::next_page has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). 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.
GithubLister::next_page (cognitive 25) core/services/github/src/lister.rs:46— GithubLister::next_page has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.fetch_issues (cognitive 24) .github/scripts/weekly_update/main.py:81— main.fetch_issues has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 2, loops 1 (nesting depth added 13). 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.
label.selected_labels (cognitive 23) scripts/label.py:240— label.selected_labels has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 5 (6 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
opendal_dotnet::presign::presigned_request_free (cognitive 22) bindings/dotnet/src/presign.rs:85— opendal_dotnet::presign::presigned_request_free has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (6 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.
GdriveDeleter::delete_once (cognitive 22) core/services/gdrive/src/deleter.rs:39— GdriveDeleter::delete_once has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 4 (6 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.
ServiceParser::parse_field (cognitive 22) dev/src/generate/parser.rs:287— ServiceParser::parse_field has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CorrectnessService::compose (cognitive 21) core/core/src/layers/correctness_check.rs:339— CorrectnessService::compose has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 10. 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.
LakefsConfig::from_uri (cognitive 21) core/services/lakefs/src/config.rs:73— LakefsConfig::from_uri has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 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.
RedisConfig::from_uri (cognitive 21) core/services/redis/src/config.rs:81— RedisConfig::from_uri has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sign_source_release.validate (cognitive 21) scripts/sign_source_release.py:58— sign_source_release.validate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 8, 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.
DropboxLister::next_page (cognitive 20) core/services/dropbox/src/lister.rs:54— DropboxLister::next_page has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 3 (6 pts), boolean chains 1, 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.
GdrivePathIndex::ensure_dir (cognitive 20) core/services/gdrive/src/path_index.rs:256— GdrivePathIndex::ensure_dir has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (6 pts), loops 3 (4 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.
PcloudLister::next_page (cognitive 20) core/services/pcloud/src/lister.rs:46— PcloudLister::next_page has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WebhdfsLister::next_page (cognitive 20) core/services/webhdfs/src/lister.rs:47— WebhdfsLister::next_page has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (6 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.
bootstrap.preflight_authenticated (cognitive 20) .github/scripts/release_rust/bootstrap.py:330— bootstrap.preflight_authenticated has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CloudflareKvReader::open (cognitive 19) core/services/cloudflare-kv/src/reader.rs:51— CloudflareKvReader::open has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5 (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.
S3ListerV1::next_page (cognitive 19) core/services/s3/src/lister.rs:74— S3ListerV1::next_page has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 2, 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.
merge_local_staging.copy_and_append_index (cognitive 19) scripts/merge_local_staging.py:26— merge_local_staging.copy_and_append_index has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (4 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.
opendal.newOpendalWriteOptions (cognitive 19) REDACTED:193— opendal.newOpendalWriteOptions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 1 (2 pts) (nesting depth added 5). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
GcsLister::next_page (cognitive 18) core/services/gcs/src/lister.rs:66— GcsLister::next_page has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 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.
MokaBackend::stat (cognitive 18) core/services/moka/src/backend.rs:251— MokaBackend::stat has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TosDeleter::delete_batch (cognitive 18) core/services/tos/src/deleter.rs:60— TosDeleter::delete_batch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 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.
opendal.newOpendalReadOptions (cognitive 18) REDACTED:239— opendal.newOpendalReadOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17 (18 pts) (nesting depth added 1). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
FsLister::next (cognitive 17) core/services/fs/src/lister.rs:50— FsLister::next has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (6 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.
plan.plan (cognitive 17) .github/scripts/release_rust/plan.py:97— plan.plan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (6 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.
publish.publish_package (cognitive 17) .github/scripts/release_rust/publish.py:207— publish.publish_package has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
release_impact.breaking_declaration (cognitive 17) scripts/release_impact.py:36— release_impact.breaking_declaration has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
release_impact.render_plan (cognitive 17) scripts/release_impact.py:210— release_impact.render_plan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
release_lifecycle.publish (cognitive 17) scripts/release_lifecycle.py:777— release_lifecycle.publish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts), 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.
OpWrite::from_options (cognitive 16) core/core/src/raw/ops.rs:856— OpWrite::from_options has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpCompose::from_options (cognitive 16) core/core/src/raw/ops.rs:1104— OpCompose::from_options has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BufferSink::poll_close (cognitive 16) core/core/src/types/write/buffer_sink.rs:111— BufferSink::poll_close has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 3 (7 pts), loops 1 (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.
S3ListerV2::next_page (cognitive 16) core/services/s3/src/lister.rs:200— S3ListerV2::next_page has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2, 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.
SqliteBackend::stat (cognitive 16) core/services/sqlite/src/backend.rs:225— SqliteBackend::stat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 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.
TikvConfig::from_uri (cognitive 16) core/services/tikv/src/config.rs:57— TikvConfig::from_uri has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (5 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.
WebdavLister::next_page (cognitive 16) core/services/webdav/src/lister.rs:47— WebdavLister::next_page has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperatorInputStream.read (cognitive 16) bindings/java/src/main/java/org/apache/opendal/OperatorInputStream.java:62— OperatorInputStream.read has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (6 pts), boolean chains 3, loops 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.
label.label_event (cognitive 16) scripts/label.py:279— label.label_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.SearchBar (cognitive 16) website/src/theme/SearchBar/index.jsx:65— index.SearchBar has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 7. Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 99, 130, 82, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D20 · ADR Quality· No consequences/trade-offs section (e.g. API surface growth, cost of the new AccessorCapability enum) · ×1
No consequences/trade-offs section (e.g. API surface growth, cost of the new AccessorCapability enum) core/core/src/docs/rfcs/0409_accessor_capabilities.md— Add a Consequences section noting that the private AccessorCapability enum is not part of the public API and users must still check via unimplemented() for missing capabilities
D20 · ADR Quality· No consequences/trade-offs section; the body is a boilerplate guide-level explanation and reference-level API signature with no discussion of cost or trade-offs · ×1
No consequences/trade-offs section; the body is a boilerplate guide-level explanation and reference-level API signature with no discussion of cost or trade-offs core/core/src/docs/rfcs/0429_init_from_iter.md— Add a Consequences section covering any real-world costs (e.g. breaking existing callers who use `from_env` directly) that would result from exposing this new iterator-based init path
D20 · ADR Quality· No consequences/trade-offs section; the body is a guide-level install list with no discussion of how oay behaves when opendal changes or what happens if oay outdates opendal · ×1
No consequences/trade-offs section; the body is a guide-level install list with no discussion of how oay behaves when opendal changes or what happens if oay outdates opendal core/core/src/docs/rfcs/0443_gateway.md— Add a Consequences section covering trade-offs such as oay's versioning lock to opendal, whether it replaces existing gateways, and the cost of keeping new features in sync with opendal
D20 · ADR Quality· Rationale and alternatives are both empty; the decision is stated but no trade-offs or future work discussed · ×1
Rationale and alternatives are both empty; the decision is stated but no trade-offs or future work discussed core/core/src/docs/rfcs/3232_align_list_api.md— Add a Consequences section covering breaking changes for existing callers of `Page` (e.g. fs/hdfs clients) and note any migration path options
D22 · Internal API Consistency· Redundant naming convention. The `Operator` type exposes both `copier` and `copier_options`. While this follows the existing pattern of `read`/`read_options` and `writer`/`writer_options`, the suffix `_options` is verbose and inconsistent with common Rust idioms where builder patterns or distinct method names (like `copier_with`) are preferred. More critically, it duplicates the intent of configuring the copy operation, just like `copy` vs `copy_options`. · ×1
Redundant naming convention. The `Operator` type exposes both `copier` and `copier_options`. While this follows the existing pattern of `read`/`read_options` and `writer`/`writer_options`, the suffix `_options` is verbose and inconsistent with common Rust idioms where builder patterns or distinct method names (like `copier_with`) are preferred. More critically, it duplicates the intent of configuring the copy operation, just like `copy` vs `copy_options`. — Adopt a consistent builder pattern or suffix convention across all operations. For example, use `copier` for the default and `copier_with_opts` for the configured version, or rely on a builder struct `CopierBuilder` returned by `copier()` that allows chaining options, removing the need for separate `_options` methods entirely. (signatures: Operator.copier(from: str, to: str): Result | Operator.copier_options(from: str, to: str, opts: CopyOptions): Result)
D22 · Internal API Consistency· Inconsistent deletion API surface. `Operator` provides simple `delete` and `delete_options` methods, but also exposes `delete_iter` and `delete_try_iter` for batch operations. Meanwhile, `Deleter` (a separate type) also has `delete`, `delete_iter`, and `delete_try_iter`. This creates confusion · ×1
Inconsistent deletion API surface. `Operator` provides simple `delete` and `delete_options` methods, but also exposes `delete_iter` and `delete_try_iter` for batch operations. Meanwhile, `Deleter` (a separate type) also has `delete`, `delete_iter`, and `delete_try_iter`. This creates confusion: should the user call `op.delete()` for single items and `op.deleter().delete_iter()` for batches, or is there a direct batch method on `Operator`? The existence of `delete_iter` on both `Operator` and `Deleter` suggests overlapping functionality. — Clarify the boundary between `Operator` and `Deleter`. If `Deleter` is intended for batch operations, `Operator` should not expose `delete_iter`/`delete_try_iter` directly, or these should be deprecated in favor of `op.deleter().delete_iter()`. Alternatively, unify the API by having `Operator` handle all deletion via a builder or distinct method names (e.g., `delete_single` vs `delete_batch`). (signatures: Operator.delete(path: str): Result | Operator.delete_options(path: str, opts: DeleteOptions): Result | Deleter.delete(input: impl IntoDeleteInput): Result | Deleter.delete_iter(iter: I): Result | Deleter.delete_try_iter(try_iter: I): Result)
D22 · Internal API Consistency· Inconsistent naming with `copy`. `Operator` has `copy` and `copy_options`, but also `copier` and `copier_options`. For rename, it only has `rename` and `rename_options`. This inconsistency in method naming (`_options` vs `_options` vs implicit builder) makes the API harder to memorize. Specifically, `copier` returns a `Copier` type, while `rename` is a direct call. This asymmetry between copy (streaming/batch capable via Copier) and rename (direct) is a design inconsistency. · ×1
Inconsistent naming with `copy`. `Operator` has `copy` and `copy_options`, but also `copier` and `copier_options`. For rename, it only has `rename` and `rename_options`. This inconsistency in method naming (`_options` vs `_options` vs implicit builder) makes the API harder to memorize. Specifically, `copier` returns a `Copier` type, while `rename` is a direct call. This asymmetry between copy (streaming/batch capable via Copier) and rename (direct) is a design inconsistency. — Standardize the method naming. If `copier` is a distinct type for streaming, consider if `renamer` should also exist for consistency, or if `copy` should be the simple method and `copier` the advanced one. Currently, `copy` is simple, `copier` is advanced. `rename` is simple, `rename_options` is advanced. This is inconsistent: `copy` vs `copier` vs `rename`. (signatures: Operator.rename(from: str, to: str): Result | Operator.rename_options(from: str, to: str, opts: RenameOptions): Result)
TooManyFunctions: opendal_java::async_operator bindings/java/src/async_operator.rs:50— TooManyFunctions — 36 free functions. The bar is 30 free functions; 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.
D4 · Code Duplication· Near-duplicate member family (4 members, 24 shared lines) · ×1
Near-duplicate member family (4 members, 24 shared lines) bindings/dotnet/src/operator.rs:1059— bindings/dotnet/src/operator.rs:1059-1084 | bindings/dotnet/src/operator.rs:1114-1139 | bindings/dotnet/src/operator.rs:1169-1194 | bindings/dotnet/src/operator.rs:1224-1249 — These 4 members are variants of one another: a block of 24 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) core/services/gcs/src/core.rs:215— core/services/gcs/src/core.rs:215-276 | core/services/oss/src/core.rs:320-377 | core/services/s3/src/core.rs:467-535 | core/services/s3/src/core.rs:542-619 — 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, 16 shared lines) · ×1
Near-duplicate member family (4 members, 16 shared lines) core/core/src/raw/ops.rs:112— core/core/src/raw/ops.rs:112-158 | core/core/src/raw/ops.rs:859-931 | core/core/src/raw/ops.rs:1107-1172 | core/core/src/raw/ops.rs:1293-1342 — These 4 members are variants of one another: a block of 16 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, 15 shared lines) · ×1
Near-duplicate member family (4 members, 15 shared lines) core/services/cos/src/core.rs:398— core/services/cos/src/core.rs:398-425 | core/services/cos/src/core.rs:590-621 | core/services/obs/src/core.rs:340-366 | core/services/oss/src/core.rs:571-601 — These 4 members are variants of one another: a block of 15 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, 30 shared lines) · ×1
Near-duplicate member family (3 members, 30 shared lines) core/services/gridfs/src/config.rs:57— core/services/gridfs/src/config.rs:57-89 | core/services/mongodb/src/config.rs:59-91 | core/services/surrealdb/src/config.rs:67-105 — These 3 members are variants of one another: a block of 30 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.
Near-duplicate member pair (71 shared lines) core/core/src/layers/simulate.rs:501— core/core/src/layers/simulate.rs:501-590 | core/core/src/raw/oio/list/flat_list.rs:89-190 — These two members are variants of one another: 71 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.
Near-duplicate member pair (43 shared lines) core/services/azdls/src/core.rs:826— core/services/azdls/src/core.rs:826-912 | core/services/azfile/src/core.rs:551-648 — These two members are variants of one another: 43 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.
Near-duplicate member pair (21 shared lines) core/services/cloudflare-kv/src/config.rs:57— core/services/cloudflare-kv/src/config.rs:57-94 | core/services/d1/src/config.rs:62-99 — These two members are variants of one another: 21 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 (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) core/services/azdls/src/core.rs:347— core/services/azdls/src/core.rs:347-382 | core/services/http/src/core.rs:109-141 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) integrations/object_store/src/service/core.rs:27— integrations/object_store/src/service/core.rs:27-54 | integrations/object_store/src/service/core.rs:57-104 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) REDACTED:146— REDACTED:146-168 | REDACTED:174-197 | REDACTED:157-175 | REDACTED:181-200 | REDACTED:206-224 | REDACTED:230-249 | REDACTED:255-273 | REDACTED:279-298 | REDACTED:304-322 | REDACTED:328-347 | REDACTED:278-296 | REDACTED:425-445 — These 12 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 12 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 12 times.
D4 · Code Duplication· Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (11 members, 50+ identical tokens) core/layers/observe-metrics-common/src/lib.rs:756— core/layers/observe-metrics-common/src/lib.rs:756-785 | core/layers/observe-metrics-common/src/lib.rs:787-811 | core/layers/observe-metrics-common/src/lib.rs:813-842 | core/layers/observe-metrics-common/src/lib.rs:850-879 | core/layers/observe-metrics-common/src/lib.rs:887-916 | core/layers/observe-metrics-common/src/lib.rs:923-951 | core/layers/observe-metrics-common/src/lib.rs:953-982 | core/layers/observe-metrics-common/src/lib.rs:984-1013 | core/layers/observe-metrics-common/src/lib.rs:1015-1044 | core/layers/observe-metrics-common/src/lib.rs:1051-1080 | core/layers/observe-metrics-common/src/lib.rs:1101-1136 — These 11 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 11 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 11 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) core/services/compfs/src/config.rs:35— core/services/compfs/src/config.rs:35-45 | core/services/dashmap/src/config.rs:37-47 | core/services/dropbox/src/config.rs:53-63 | core/services/gdrive/src/config.rs:53-63 | core/services/mini_moka/src/config.rs:51-61 | core/services/monoiofs/src/config.rs:40-50 | core/services/vercel-blob/src/config.rs:49-59 | core/services/yandex-disk/src/config.rs:49-59 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Duplicated block (59–60 lines × 3) core/services/cos/src/lister.rs:177— core/services/cos/src/lister.rs:177-235 | core/services/oss/src/lister.rs:180-238 | core/services/s3/src/lister.rs:333-392 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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 (52 lines × 2) core/services/gdrive/src/backend.rs:504— core/services/gdrive/src/backend.rs:504-555 | core/services/gdrive/src/backend.rs:572-623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (42–46 lines × 2) core/services/s3/src/core.rs:813— core/services/s3/src/core.rs:813-854 | core/services/s3/src/core.rs:1114-1159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (41 lines × 2) core/services/cloudflare-kv/src/backend.rs:328— core/services/cloudflare-kv/src/backend.rs:328-368 | core/services/cloudflare-kv/src/reader.rs:93-133 — 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 (39 lines × 2) core/services/tos/src/core.rs:237— core/services/tos/src/core.rs:237-275 | core/services/tos/src/core.rs:357-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.
Duplicated block (31–38 lines × 2) core/services/gcs-grpc/src/backend.rs:188— core/services/gcs-grpc/src/backend.rs:188-218 | core/services/gcs/src/backend.rs:297-334 — 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 (33–34 lines × 2) core/core/src/layers/simulate.rs:530— core/core/src/layers/simulate.rs:530-562 | core/core/src/raw/oio/list/flat_list.rs:126-159 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (30–31 lines × 2) core/services/cos/src/core.rs:591— core/services/cos/src/core.rs:591-621 | core/services/oss/src/core.rs:572-601 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 287 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 (29 lines × 2) core/services/s3/src/copier.rs:43— core/services/s3/src/copier.rs:43-71 | core/services/tos/src/copier.rs:38-66 — 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 (28 lines × 3) core/services/gdrive/src/lister.rs:437— core/services/gdrive/src/lister.rs:437-464 | core/services/gdrive/src/lister.rs:493-520 | core/services/gdrive/src/lister.rs:564-591 — 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 (26–27 lines × 2) core/services/cos/src/core.rs:326— core/services/cos/src/core.rs:326-351 | core/services/obs/src/core.rs:276-302 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22–26 lines × 2) core/services/monoiofs/src/reader.rs:61— core/services/monoiofs/src/reader.rs:61-82 | core/services/monoiofs/src/writer.rs:73-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.
Duplicated block (21–23 lines × 2) core/services/tos/src/core.rs:283— core/services/tos/src/core.rs:283-305 | core/services/tos/src/core.rs:399-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 (22 lines × 3) core/services/mysql/src/config.rs:75— core/services/mysql/src/config.rs:75-96 | core/services/postgresql/src/config.rs:75-96 | core/services/sqlite/src/config.rs:81-102 — 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 (20 lines × 3) core/services/cos/src/writer.rs:224— core/services/cos/src/writer.rs:224-243 | core/services/obs/src/writer.rs:221-240 | core/services/oss/src/writer.rs:217-236 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–20 lines × 2) core/services/azdls/src/core.rs:84— core/services/azdls/src/core.rs:84-103 | core/services/azfile/src/core.rs:74-89 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 98 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–20 lines × 2) core/services/gcs/src/core.rs:132— core/services/gcs/src/core.rs:132-151 | core/services/tos/src/core.rs:110-122 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/tos/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 (19 lines × 4) core/layers/observe-metrics-common/src/lib.rs:824— core/layers/observe-metrics-common/src/lib.rs:824-842 | core/layers/observe-metrics-common/src/lib.rs:861-879 | core/layers/observe-metrics-common/src/lib.rs:995-1013 | core/layers/observe-metrics-common/src/lib.rs:1026-1044 — 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 (17–18 lines × 7) core/services/foundationdb/src/backend.rs:98— core/services/foundationdb/src/backend.rs:98-114 | core/services/gridfs/src/backend.rs:170-187 | core/services/memcached/src/backend.rs:214-230 | core/services/mongodb/src/backend.rs:185-202 | core/services/postgresql/src/backend.rs:159-175 | core/services/surrealdb/src/backend.rs:213-229 | core/services/tikv/src/backend.rs:127-143 — before extracting anything, compare `core/services/foundationdb/src/backend.rs` and `core/services/gridfs/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–18 lines × 4) core/services/cos/src/lister.rs:173— core/services/cos/src/lister.rs:173-188 | core/services/oss/src/lister.rs:176-191 | core/services/s3/src/lister.rs:329-344 | core/services/tos/src/lister.rs:170-187 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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 (17–18 lines × 2) core/services/gcs-grpc/src/backend.rs:171— core/services/gcs-grpc/src/backend.rs:171-187 | core/services/gcs/src/backend.rs:274-291 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16–17 lines × 3) core/services/cos/src/lister.rs:244— core/services/cos/src/lister.rs:244-259 | core/services/oss/src/lister.rs:247-262 | core/services/s3/src/lister.rs:400-416 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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–17 lines × 2) bindings/dotnet/src/operator.rs:1924— bindings/dotnet/src/operator.rs:1924-1940 | bindings/dotnet/src/operator.rs:1994-2006 — both copies are in the same file, so extract the block into 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) core/services/s3/src/copier.rs:295— core/services/s3/src/copier.rs:295-311 | core/services/s3/src/writer.rs:213-228 — 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–16 lines × 2) core/services/onedrive/src/core.rs:554— core/services/onedrive/src/core.rs:554-569 | core/services/onedrive/src/core.rs:674-686 — both copies are in the same file, so extract the block into 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 × 4) bindings/dotnet/src/operator.rs:1070— bindings/dotnet/src/operator.rs:1070-1084 | bindings/dotnet/src/operator.rs:1125-1139 | bindings/dotnet/src/operator.rs:1180-1194 | bindings/dotnet/src/operator.rs:1235-1249 — 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 (15 lines × 3) bindings/dotnet/src/operator.rs:929— bindings/dotnet/src/operator.rs:929-943 | bindings/dotnet/src/operator.rs:1873-1887 | bindings/dotnet/src/operator.rs:2012-2026 — 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–15 lines × 3) core/services/cos/src/core.rs:495— core/services/cos/src/core.rs:495-509 | core/services/gcs/src/core.rs:1004-1018 | core/services/oss/src/core.rs:722-734 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 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–15 lines × 3) core/services/dashmap/src/reader.rs:44— core/services/dashmap/src/reader.rs:44-57 | core/services/mini_moka/src/reader.rs:44-58 | core/services/moka/src/reader.rs:44-57 — 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 (13–15 lines × 2) core/services/s3/src/lister.rs:212— core/services/s3/src/lister.rs:212-224 | core/services/tos/src/lister.rs:72-86 — before extracting anything, compare `core/services/s3/src/lister.rs` and `core/services/tos/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 144 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–14 lines × 7) core/services/koofr/src/backend.rs:306— core/services/koofr/src/backend.rs:306-319 | core/services/lakefs/src/backend.rs:307-320 | core/services/obs/src/backend.rs:407-419 | core/services/onedrive/src/backend.rs:308-321 | core/services/upyun/src/backend.rs:289-302 | core/services/vercel-blob/src/backend.rs:219-232 | core/services/yandex-disk/src/backend.rs:192-205 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/lakefs/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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 × 5) core/layers/observe-metrics-common/src/lib.rs:772— core/layers/observe-metrics-common/src/lib.rs:772-785 | core/layers/observe-metrics-common/src/lib.rs:903-916 | core/layers/observe-metrics-common/src/lib.rs:938-951 | core/layers/observe-metrics-common/src/lib.rs:969-982 | core/layers/observe-metrics-common/src/lib.rs:1067-1080 — 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 (10–14 lines × 5) core/services/b2/src/core.rs:193— core/services/b2/src/core.rs:193-202 | core/services/b2/src/core.rs:238-250 | core/services/b2/src/core.rs:387-397 | core/services/seafile/src/core.rs:171-183 | core/services/seafile/src/core.rs:281-294 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13–14 lines × 3) core/services/tos/src/core.rs:235— core/services/tos/src/core.rs:235-247 | core/services/tos/src/core.rs:355-367 | core/services/tos/src/core.rs:443-456 — 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–14 lines × 2) core/services/http/src/core.rs:83— core/services/http/src/core.rs:83-92 | core/services/webdav/src/core.rs:203-216 — 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 (12–14 lines × 2) core/services/tos/src/core.rs:213— core/services/tos/src/core.rs:213-226 | core/services/tos/src/core.rs:801-812 — both copies are in the same file, so extract the block into 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 × 11) bindings/haskell/src/lib.rs:156— bindings/haskell/src/lib.rs:156-168 | bindings/haskell/src/lib.rs:202-214 | bindings/haskell/src/lib.rs:248-260 | bindings/haskell/src/lib.rs:289-301 | bindings/haskell/src/lib.rs:432-444 | bindings/haskell/src/lib.rs:473-485 | bindings/haskell/src/lib.rs:514-526 | bindings/haskell/src/lib.rs:555-567 | bindings/haskell/src/lib.rs:694-706 | bindings/haskell/src/lib.rs:746-758 | bindings/haskell/src/lib.rs:789-801 — 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.
Duplicated block (12–13 lines × 6) core/services/cos/src/lister.rs:96— core/services/cos/src/lister.rs:96-108 | core/services/obs/src/lister.rs:95-107 | core/services/oss/src/lister.rs:98-109 | core/services/s3/src/lister.rs:133-145 | core/services/s3/src/lister.rs:250-262 | core/services/tos/src/lister.rs:93-105 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 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–13 lines × 3) core/services/cos/src/lister.rs:231— core/services/cos/src/lister.rs:231-242 | core/services/oss/src/lister.rs:234-245 | core/services/tos/src/lister.rs:220-232 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11–13 lines × 2) bindings/c/src/types.rs:199— bindings/c/src/types.rs:199-211 | bindings/c/src/types.rs:304-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–13 lines × 2) core/services/s3/src/deleter.rs:84— core/services/s3/src/deleter.rs:84-96 | core/services/tos/src/deleter.rs:77-85 — 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–12 lines × 9) core/services/b2/src/config.rs:69— core/services/b2/src/config.rs:69-80 | core/services/cos/src/config.rs:85-96 | core/services/gcs-grpc/src/config.rs:81-89 | core/services/gcs/src/config.rs:128-139 | core/services/obs/src/config.rs:62-73 | core/services/oss/src/config.rs:137-148 | core/services/s3/src/config.rs:344-355 | core/services/tos/src/config.rs:106-117 | core/services/upyun/src/config.rs:57-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times.
Duplicated block (12 lines × 7) core/services/cos/src/core.rs:971— core/services/cos/src/core.rs:971-982 | core/services/dbfs/src/core.rs:285-297 | core/services/ipmfs/src/core.rs:236-248 | core/services/lakefs/src/core.rs:376-388 | core/services/obs/src/core.rs:729-741 | core/services/oss/src/core.rs:1273-1285 | core/services/webhdfs/src/core.rs:487-499 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 239 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 × 6) core/services/aliyun-drive/src/reader.rs:67— core/services/aliyun-drive/src/reader.rs:67-78 | core/services/dropbox/src/reader.rs:65-76 | core/services/gdrive/src/reader.rs:86-97 | core/services/pcloud/src/reader.rs:62-73 | core/services/seafile/src/reader.rs:60-71 | core/services/upyun/src/reader.rs:55-66 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–12 lines × 5) core/services/gridfs/src/backend.rs:225— core/services/gridfs/src/backend.rs:225-234 | core/services/mongodb/src/backend.rs:240-249 | core/services/mysql/src/backend.rs:221-230 | core/services/postgresql/src/backend.rs:213-224 | core/services/surrealdb/src/backend.rs:267-276 — before extracting anything, compare `core/services/gridfs/src/backend.rs` and `core/services/mongodb/src/backend.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–12 lines × 3) core/services/cos/src/core.rs:544— core/services/cos/src/core.rs:544-555 | core/services/gcs/src/core.rs:1046-1056 | core/services/oss/src/core.rs:772-781 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 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 (4–12 lines × 4) core/services/dbfs/src/core.rs:269— core/services/dbfs/src/core.rs:269-280 | core/services/lakefs/src/core.rs:360-371 | core/services/swift/src/core.rs:902-906 | core/services/webhdfs/src/core.rs:469-472 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (4–12 lines × 3) core/services/webdav/src/core.rs:633— core/services/webdav/src/core.rs:633-644 | core/services/webdav/src/core.rs:658-669 | core/services/webdav/src/core.rs:695-698 — 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–11 lines × 24) core/services/aliyun-drive/src/reader.rs:59— core/services/aliyun-drive/src/reader.rs:59-68 | core/services/azblob/src/reader.rs:60-69 | core/services/azdls/src/reader.rs:57-66 | core/services/azfile/src/reader.rs:53-60 | core/services/b2/src/reader.rs:52-61 | core/services/cos/src/reader.rs:57-67 | core/services/dropbox/src/reader.rs:57-66 | core/services/ghac/src/reader.rs:48-55 | core/services/github/src/reader.rs:53-61 | core/services/http/src/reader.rs:56-64 | core/services/ipfs/src/reader.rs:48-56 | core/services/koofr/src/reader.rs:48-55 | core/services/lakefs/src/reader.rs:57-67 | core/services/obs/src/reader.rs:57-67 | core/services/oss/src/reader.rs:57-67 | core/services/pcloud/src/reader.rs:55-63 | core/services/seafile/src/reader.rs:53-61 | core/services/swift/src/reader.rs:57-67 | core/services/tos/src/reader.rs:59-68 | core/services/upyun/src/reader.rs:48-56 | core/services/vercel-artifacts/src/reader.rs:57-67 | core/services/vercel-blob/src/reader.rs:56-64 | core/services/webdav/src/reader.rs:58-68 | core/services/yandex-disk/src/reader.rs:53-60 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 10) core/services/foundationdb/src/writer.rs:47— core/services/foundationdb/src/writer.rs:47-57 | core/services/gridfs/src/writer.rs:48-58 | core/services/memcached/src/writer.rs:48-58 | core/services/mongodb/src/writer.rs:47-57 | core/services/mysql/src/writer.rs:47-57 | core/services/postgresql/src/writer.rs:47-57 | core/services/redis/src/writer.rs:48-58 | core/services/sqlite/src/writer.rs:46-56 | core/services/surrealdb/src/writer.rs:47-57 | core/services/tikv/src/writer.rs:47-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 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 10 times.
Duplicated block (10–11 lines × 6) core/services/aliyun-drive/src/reader.rs:65— core/services/aliyun-drive/src/reader.rs:65-74 | core/services/dropbox/src/reader.rs:63-72 | core/services/gdrive/src/reader.rs:74-84 | core/services/pcloud/src/reader.rs:60-69 | core/services/seafile/src/reader.rs:58-67 | core/services/upyun/src/reader.rs:53-62 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 4 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–11 lines × 6) core/services/azdls/src/core.rs:138— core/services/azdls/src/core.rs:138-146 | core/services/azdls/src/core.rs:361-369 | core/services/http/src/core.rs:67-77 | core/services/http/src/core.rs:116-126 | core/services/swift/src/core.rs:309-317 | core/services/swift/src/core.rs:396-404 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/http/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 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–11 lines × 4) core/services/azblob/src/core.rs:1338— core/services/azblob/src/core.rs:1338-1348 | core/services/azdls/src/core.rs:847-855 | core/services/gcs/src/core.rs:2030-2038 | core/services/oss/src/core.rs:1238-1246 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 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–11 lines × 3) core/services/vercel-blob/src/core.rs:96— core/services/vercel-blob/src/core.rs:96-106 | core/services/vercel-blob/src/core.rs:162-170 | core/services/vercel-blob/src/core.rs:195-203 — 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–11 lines × 2) core/services/redb/src/core.rs:60— core/services/redb/src/core.rs:60-70 | core/services/redb/src/core.rs:80-88 — both copies are in the same file, so extract the block into 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 × 8) core/services/compfs/src/config.rs:36— core/services/compfs/src/config.rs:36-45 | core/services/dashmap/src/config.rs:38-47 | core/services/dropbox/src/config.rs:54-63 | core/services/gdrive/src/config.rs:54-63 | core/services/mini_moka/src/config.rs:52-61 | core/services/monoiofs/src/config.rs:41-50 | core/services/vercel-blob/src/config.rs:50-59 | core/services/yandex-disk/src/config.rs:50-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times.
Duplicated block (8–10 lines × 6) core/services/cos/src/core.rs:135— core/services/cos/src/core.rs:135-142 | core/services/cos/src/core.rs:249-256 | core/services/cos/src/core.rs:290-297 | core/services/s3/src/core.rs:468-476 | core/services/s3/src/core.rs:543-552 | core/services/s3/src/core.rs:726-734 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 91 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) core/services/cos/src/lister.rs:105— core/services/cos/src/lister.rs:105-114 | core/services/s3/src/lister.rs:142-151 | core/services/s3/src/lister.rs:259-268 | core/services/tos/src/lister.rs:102-111 | core/services/tos/src/lister.rs:215-224 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 192 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–10 lines × 4) core/services/azfile/src/core.rs:158— core/services/azfile/src/core.rs:158-167 | core/services/cos/src/core.rs:338-346 | core/services/obs/src/core.rs:288-296 | core/services/oss/src/core.rs:671-677 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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–9 lines × 9) core/services/azdls/src/core.rs:141— core/services/azdls/src/core.rs:141-147 | core/services/azdls/src/core.rs:364-370 | core/services/cos/src/core.rs:161-169 | core/services/http/src/core.rs:71-79 | core/services/http/src/core.rs:120-128 | core/services/obs/src/core.rs:145-153 | core/services/oss/src/core.rs:358-366 | core/services/swift/src/core.rs:312-318 | core/services/swift/src/core.rs:399-405 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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–9 lines × 8) core/services/azblob/src/core.rs:252— core/services/azblob/src/core.rs:252-260 | core/services/azdls/src/core.rs:144-151 | core/services/azdls/src/core.rs:367-374 | core/services/cos/src/core.rs:165-173 | core/services/obs/src/core.rs:149-157 | core/services/oss/src/core.rs:362-370 | core/services/swift/src/core.rs:315-322 | core/services/swift/src/core.rs:402-409 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6–9 lines × 5) core/core/src/services/memory/backend.rs:218— core/core/src/services/memory/backend.rs:218-226 | core/services/persy/src/reader.rs:39-44 | core/services/redb/src/reader.rs:39-44 | core/services/rocksdb/src/reader.rs:39-44 | core/services/sled/src/reader.rs:39-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (8–9 lines × 5) core/services/cos/src/writer.rs:80— core/services/cos/src/writer.rs:80-88 | core/services/cos/src/writer.rs:250-258 | core/services/obs/src/writer.rs:72-80 | core/services/oss/src/writer.rs:70-77 | core/services/oss/src/writer.rs:242-249 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 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. 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–9 lines × 4) core/services/azdls/src/core.rs:359— core/services/azdls/src/core.rs:359-366 | core/services/cos/src/core.rs:265-273 | core/services/http/src/core.rs:114-122 | core/services/obs/src/core.rs:227-235 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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–9 lines × 4) core/services/b2/src/core.rs:191— core/services/b2/src/core.rs:191-197 | core/services/b2/src/core.rs:385-392 | core/services/yandex-disk/src/core.rs:87-95 | core/services/yandex-disk/src/core.rs:142-150 — 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 (7–9 lines × 2) core/services/azblob/src/core.rs:478— core/services/azblob/src/core.rs:478-484 | core/services/azblob/src/core.rs:531-539 — both copies are in the same file, so extract the block into 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 × 26) core/services/aliyun-drive/src/reader.rs:63— core/services/aliyun-drive/src/reader.rs:63-70 | core/services/azblob/src/reader.rs:64-70 | core/services/azdls/src/reader.rs:61-68 | core/services/azfile/src/reader.rs:55-62 | core/services/b2/src/reader.rs:56-63 | core/services/cos/src/reader.rs:62-69 | core/services/dropbox/src/reader.rs:61-68 | core/services/gdrive/src/reader.rs:72-79 | core/services/ghac/src/reader.rs:50-57 | core/services/github/src/reader.rs:56-63 | core/services/http/src/reader.rs:59-66 | core/services/ipfs/src/reader.rs:51-58 | core/services/koofr/src/reader.rs:50-57 | core/services/lakefs/src/reader.rs:62-69 | core/services/obs/src/reader.rs:62-69 | core/services/onedrive/src/reader.rs:70-77 | core/services/oss/src/reader.rs:62-69 | core/services/pcloud/src/reader.rs:58-65 | core/services/seafile/src/reader.rs:56-63 | core/services/swift/src/reader.rs:62-69 | core/services/tos/src/reader.rs:63-70 | core/services/upyun/src/reader.rs:51-58 | core/services/vercel-artifacts/src/reader.rs:62-69 | core/services/vercel-blob/src/reader.rs:59-66 | core/services/webdav/src/reader.rs:63-70 | core/services/yandex-disk/src/reader.rs:55-62 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 4 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 × 9) core/services/cos/src/lister.rs:95— core/services/cos/src/lister.rs:95-102 | core/services/cos/src/lister.rs:209-215 | core/services/oss/src/lister.rs:97-103 | core/services/oss/src/lister.rs:212-218 | core/services/s3/src/lister.rs:132-139 | core/services/s3/src/lister.rs:249-256 | core/services/s3/src/lister.rs:365-371 | core/services/tos/src/lister.rs:92-99 | core/services/tos/src/lister.rs:201-208 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 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 × 6) core/services/alluxio/src/core.rs:146— core/services/alluxio/src/core.rs:146-152 | core/services/alluxio/src/core.rs:239-245 | core/services/alluxio/src/core.rs:276-282 | core/services/b2/src/core.rs:103-110 | core/services/gdrive/src/core.rs:758-765 | core/services/webhdfs/src/core.rs:197-205 — there are 6 copies across 4 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 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6–7 lines × 5) core/services/foundationdb/src/reader.rs:39— core/services/foundationdb/src/reader.rs:39-45 | core/services/gridfs/src/reader.rs:39-44 | core/services/mongodb/src/reader.rs:39-44 | core/services/postgresql/src/reader.rs:39-45 | core/services/surrealdb/src/reader.rs:39-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (6 lines × 13) core/services/azblob/src/core.rs:252— core/services/azblob/src/core.rs:252-258 | core/services/azdls/src/core.rs:144-149 | core/services/azdls/src/core.rs:367-372 | core/services/cos/src/core.rs:165-171 | core/services/gcs/src/core.rs:258-264 | core/services/http/src/core.rs:75-81 | core/services/http/src/core.rs:124-130 | core/services/obs/src/core.rs:149-155 | core/services/oss/src/core.rs:362-368 | core/services/s3/src/core.rs:517-522 | core/services/s3/src/core.rs:596-602 | core/services/swift/src/core.rs:315-320 | core/services/swift/src/core.rs:402-407 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 10) core/layers/observe-metrics-common/src/lib.rs:759— core/layers/observe-metrics-common/src/lib.rs:759-764 | core/layers/observe-metrics-common/src/lib.rs:790-795 | core/layers/observe-metrics-common/src/lib.rs:816-821 | core/layers/observe-metrics-common/src/lib.rs:853-858 | core/layers/observe-metrics-common/src/lib.rs:890-895 | core/layers/observe-metrics-common/src/lib.rs:925-930 | core/layers/observe-metrics-common/src/lib.rs:956-961 | core/layers/observe-metrics-common/src/lib.rs:987-992 | core/layers/observe-metrics-common/src/lib.rs:1018-1023 | core/layers/observe-metrics-common/src/lib.rs:1054-1059 — 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 (6 lines × 6) core/layers/observe-metrics-common/src/lib.rs:790— core/layers/observe-metrics-common/src/lib.rs:790-795 | core/layers/observe-metrics-common/src/lib.rs:816-821 | core/layers/observe-metrics-common/src/lib.rs:853-858 | core/layers/observe-metrics-common/src/lib.rs:987-992 | core/layers/observe-metrics-common/src/lib.rs:1018-1023 | core/layers/observe-metrics-common/src/lib.rs:1103-1108 — 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 (4–6 lines × 4) core/core/src/raw/ops.rs:145— core/core/src/raw/ops.rs:145-148 | core/core/src/raw/ops.rs:907-912 | core/core/src/raw/ops.rs:1145-1150 | core/core/src/raw/ops.rs:1325-1328 — 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 × 10) core/services/aliyun-drive/src/core.rs:223— core/services/aliyun-drive/src/core.rs:223-227 | core/services/aliyun-drive/src/core.rs:299-303 | core/services/aliyun-drive/src/core.rs:337-342 | core/services/aliyun-drive/src/core.rs:388-392 | core/services/aliyun-drive/src/core.rs:417-421 | core/services/aliyun-drive/src/core.rs:447-451 | core/services/aliyun-drive/src/core.rs:469-473 | core/services/aliyun-drive/src/core.rs:499-503 | core/services/aliyun-drive/src/core.rs:527-531 | core/services/aliyun-drive/src/core.rs:564-569 — 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 (11 lines × 11) core/services/foundationdb/src/deleter.rs:31— core/services/foundationdb/src/deleter.rs:31-41 | core/services/gridfs/src/deleter.rs:31-41 | core/services/memcached/src/deleter.rs:31-41 | core/services/moka/src/deleter.rs:31-41 | core/services/mongodb/src/deleter.rs:31-41 | core/services/mysql/src/deleter.rs:31-41 | core/services/postgresql/src/deleter.rs:31-41 | core/services/redis/src/deleter.rs:31-41 | core/services/sqlite/src/deleter.rs:28-38 | core/services/surrealdb/src/deleter.rs:31-41 | core/services/tikv/src/deleter.rs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times.
Duplicated block (8 lines × 72) core/services/aliyun-drive/src/backend.rs:53— core/services/aliyun-drive/src/backend.rs:53-61 | core/services/alluxio/src/backend.rs:53-61 | core/services/azblob/src/backend.rs:93-101 | core/services/azdls/src/backend.rs:89-97 | core/services/azfile/src/backend.rs:82-90 | core/services/b2/src/backend.rs:60-68 | core/services/b2/src/backend.rs:71-79 | core/services/b2/src/backend.rs:82-90 | core/services/cloudflare-kv/src/backend.rs:85-93 | core/services/compfs/src/backend.rs:40-48 | core/services/cos/src/backend.rs:65-73 | core/services/d1/src/backend.rs:80-88 | core/services/dbfs/src/backend.rs:46-54 | core/services/dropbox/src/backend.rs:59-67 | core/services/etcd/src/backend.rs:77-85 | core/services/fs/src/backend.rs:41-49 | core/services/ftp/src/backend.rs:48-56 | core/services/ftp/src/backend.rs:59-67 | core/services/ftp/src/backend.rs:70-78 | core/services/ftp/src/backend.rs:81-89 | core/services/gcs/src/backend.rs:76-84 | core/services/gdrive/src/backend.rs:63-71 | core/services/ghac/src/backend.rs:70-78 | core/services/github/src/backend.rs:57-65 | core/services/goosefs/src/backend.rs:53-60 | core/services/gridfs/src/backend.rs:68-76 | core/services/hdfs-native/src/backend.rs:47-55 | core/services/hdfs/src/backend.rs:42-50 | core/services/hf/src/backend.rs:95-103 | core/services/http/src/backend.rs:50-58 | core/services/http/src/backend.rs:91-99 | core/services/ipfs/src/backend.rs:57-65 | core/services/ipmfs/src/backend.rs:94-102 | core/services/ipmfs/src/backend.rs:107-114 | core/services/koofr/src/backend.rs:60-68 | core/services/koofr/src/backend.rs:98-106 | core/services/memcached/src/backend.rs:54-62 | core/services/mongodb/src/backend.rs:67-75 | core/services/monoiofs/src/backend.rs:44-51 | core/services/mysql/src/backend.rs:66-74 | core/services/obs/src/backend.rs:66-74 | core/services/onedrive/src/backend.rs:58-66 | core/services/opfs/src/backend.rs:44-51 | core/services/oss/src/backend.rs:73-81 | core/services/pcloud/src/backend.rs:57-65 | core/services/pcloud/src/backend.rs:81-89 | core/services/pcloud/src/backend.rs:94-102 | core/services/postgresql/src/backend.rs:60-68 | core/services/redis/src/backend.rs:119-127 | core/services/rocksdb/src/backend.rs:49-57 | core/services/s3/src/backend.rs:99-107 | core/services/seafile/src/backend.rs:56-64 | core/services/seafile/src/backend.rs:69-77 | core/services/seafile/src/backend.rs:82-90 | core/services/seafile/src/backend.rs:95-103 | core/services/sftp/src/backend.rs:54-62 | core/services/sftp/src/backend.rs:66-74 | core/services/sftp/src/backend.rs:77-85 | core/services/sftp/src/backend.rs:88-96 | core/services/sled/src/backend.rs:54-62 | core/services/sqlite/src/backend.rs:64-72 | core/services/surrealdb/src/backend.rs:59-67 | core/services/swift/src/backend.rs:79-87 | core/services/tos/src/backend.rs:62-69 | core/services/upyun/src/backend.rs:55-63 | core/services/upyun/src/backend.rs:77-85 | core/services/upyun/src/backend.rs:90-98 | core/services/vercel-blob/src/backend.rs:58-66 | core/services/webdav/src/backend.rs:56-64 | core/services/webdav/src/backend.rs:97-105 | core/services/webhdfs/src/backend.rs:59-67 | core/services/yandex-disk/src/backend.rs:56-64 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/alluxio/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 × 34) core/services/aliyun-drive/src/backend.rs:348— core/services/aliyun-drive/src/backend.rs:348-359 | core/services/alluxio/src/backend.rs:161-172 | core/services/azblob/src/backend.rs:535-546 | core/services/azdls/src/backend.rs:438-449 | core/services/azfile/src/backend.rs:355-366 | core/services/b2/src/backend.rs:263-274 | core/services/cloudflare-kv/src/backend.rs:380-391 | core/services/cos/src/backend.rs:362-373 | core/services/d1/src/backend.rs:262-273 | core/services/dropbox/src/backend.rs:282-293 | core/services/gcs/src/backend.rs:491-502 | core/services/gdrive/src/backend.rs:325-336 | core/services/ghac/src/backend.rs:253-264 | core/services/github/src/backend.rs:227-238 | core/services/hf/src/backend.rs:346-357 | core/services/http/src/backend.rs:226-237 | core/services/ipfs/src/backend.rs:178-189 | core/services/ipmfs/src/backend.rs:235-246 | core/services/koofr/src/backend.rs:252-263 | core/services/lakefs/src/backend.rs:244-255 | core/services/obs/src/backend.rs:339-350 | core/services/onedrive/src/backend.rs:262-273 | core/services/oss/src/backend.rs:694-705 | core/services/pcloud/src/backend.rs:233-244 | core/services/s3/src/backend.rs:1214-1225 | core/services/seafile/src/backend.rs:234-245 | core/services/swift/src/backend.rs:284-295 | core/services/tos/src/backend.rs:335-346 | core/services/upyun/src/backend.rs:234-245 | core/services/vercel-artifacts/src/backend.rs:193-204 | core/services/vercel-blob/src/backend.rs:183-194 | core/services/webdav/src/backend.rs:289-300 | core/services/webhdfs/src/backend.rs:333-344 | core/services/yandex-disk/src/backend.rs:224-235 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/alluxio/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 22) core/services/aliyun-drive/src/backend.rs:361— core/services/aliyun-drive/src/backend.rs:361-370 | core/services/alluxio/src/backend.rs:189-198 | core/services/azdls/src/backend.rs:480-489 | core/services/azfile/src/backend.rs:387-396 | core/services/b2/src/backend.rs:289-298 | core/services/cos/src/backend.rs:395-404 | core/services/dbfs/src/backend.rs:231-240 | core/services/dropbox/src/backend.rs:308-317 | core/services/gdrive/src/backend.rs:353-362 | core/services/github/src/backend.rs:252-261 | core/services/ipmfs/src/backend.rs:260-269 | core/services/koofr/src/backend.rs:277-286 | core/services/lakefs/src/backend.rs:287-296 | core/services/obs/src/backend.rs:372-381 | core/services/onedrive/src/backend.rs:288-297 | core/services/pcloud/src/backend.rs:258-267 | core/services/seafile/src/backend.rs:258-267 | core/services/upyun/src/backend.rs:260-269 | core/services/vercel-blob/src/backend.rs:256-265 | core/services/webdav/src/backend.rs:315-324 | core/services/webhdfs/src/backend.rs:371-380 | core/services/yandex-disk/src/backend.rs:270-279 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/alluxio/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 × 9) core/services/azblob/src/core.rs:413— core/services/azblob/src/core.rs:413-417 | core/services/azblob/src/core.rs:747-751 | core/services/azblob/src/core.rs:774-778 | core/services/cos/src/core.rs:241-246 | core/services/gcs/src/core.rs:440-444 | core/services/gcs/src/core.rs:663-669 | core/services/gcs/src/core.rs:676-681 | core/services/obs/src/core.rs:211-217 | core/services/oss/src/core.rs:608-612 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 24) core/services/cacache/src/backend.rs:128— core/services/cacache/src/backend.rs:128-138 | core/services/dashmap/src/backend.rs:160-170 | core/services/etcd/src/backend.rs:277-287 | core/services/foundationdb/src/backend.rs:170-180 | core/services/foyer/src/backend.rs:285-295 | core/services/ftp/src/backend.rs:254-264 | core/services/goosefs/src/backend.rs:450-460 | core/services/gridfs/src/backend.rs:239-249 | core/services/memcached/src/backend.rs:283-293 | core/services/mini_moka/src/backend.rs:211-221 | core/services/moka/src/backend.rs:290-300 | core/services/mongodb/src/backend.rs:254-264 | core/services/mysql/src/backend.rs:235-245 | core/services/opfs/src/backend.rs:108-118 | core/services/persy/src/backend.rs:195-205 | core/services/postgresql/src/backend.rs:230-240 | core/services/redb/src/backend.rs:213-223 | core/services/redis/src/backend.rs:363-373 | core/services/rocksdb/src/backend.rs:163-173 | core/services/sftp/src/backend.rs:258-268 | core/services/sled/src/backend.rs:187-197 | core/services/sqlite/src/backend.rs:260-270 | core/services/surrealdb/src/backend.rs:281-291 | core/services/tikv/src/backend.rs:190-200 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/foyer/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 6) core/services/cacache/src/backend.rs:147— core/services/cacache/src/backend.rs:147-155 | core/services/compfs/src/backend.rs:173-181 | core/services/goosefs/src/backend.rs:471-479 | core/services/monoiofs/src/backend.rs:146-154 | core/services/opfs/src/backend.rs:145-153 | core/services/sftp/src/backend.rs:274-282 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
Duplicated block (10 lines × 15) core/services/dashmap/src/backend.rs:181— core/services/dashmap/src/backend.rs:181-190 | core/services/foundationdb/src/backend.rs:191-200 | core/services/foyer/src/backend.rs:306-315 | core/services/gridfs/src/backend.rs:260-269 | core/services/memcached/src/backend.rs:304-313 | core/services/moka/src/backend.rs:311-320 | core/services/mongodb/src/backend.rs:275-284 | core/services/mysql/src/backend.rs:256-265 | core/services/persy/src/backend.rs:216-225 | core/services/postgresql/src/backend.rs:251-260 | core/services/redb/src/backend.rs:234-243 | core/services/redis/src/backend.rs:384-393 | core/services/sqlite/src/backend.rs:281-290 | core/services/surrealdb/src/backend.rs:302-311 | core/services/tikv/src/backend.rs:211-220 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/foyer/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 12) core/services/foundationdb/src/backend.rs:182— core/services/foundationdb/src/backend.rs:182-189 | core/services/foyer/src/backend.rs:297-304 | core/services/gridfs/src/backend.rs:251-258 | core/services/memcached/src/backend.rs:295-302 | core/services/mongodb/src/backend.rs:266-273 | core/services/mysql/src/backend.rs:247-254 | core/services/persy/src/backend.rs:207-214 | core/services/postgresql/src/backend.rs:242-249 | core/services/redb/src/backend.rs:225-232 | core/services/redis/src/backend.rs:375-382 | core/services/surrealdb/src/backend.rs:293-300 | core/services/tikv/src/backend.rs:202-209 — before extracting anything, compare `core/services/foundationdb/src/backend.rs` and `core/services/gridfs/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 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 (17 lines × 3) core/services/mysql/src/core.rs:46— core/services/mysql/src/core.rs:46-64 | core/services/postgresql/src/core.rs:46-62 | core/services/sqlite/src/core.rs:49-66 — before extracting anything, compare `core/services/postgresql/src/core.rs` and `core/services/sqlite/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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 × 10) core/services/b2/src/config.rs:72— core/services/b2/src/config.rs:72-80 | core/services/cos/src/config.rs:88-96 | core/services/gcs-grpc/src/config.rs:83-89 | core/services/gcs/src/config.rs:131-139 | core/services/obs/src/config.rs:65-73 | core/services/oss/src/config.rs:140-148 | core/services/s3/src/config.rs:347-355 | core/services/sftp/src/config.rs:63-71 | core/services/tos/src/config.rs:109-117 | core/services/upyun/src/config.rs:60-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 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 10 times.
Duplicated block (24 lines × 2) REDACTED:192— REDACTED:192-215 | REDACTED:221-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:192` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 8) REDACTED:159— REDACTED:159-175 | REDACTED:183-200 | REDACTED:208-224 | REDACTED:232-249 | REDACTED:257-273 | REDACTED:281-298 | REDACTED:306-322 | REDACTED:330-347 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 6) REDACTED:244— REDACTED:244-252 | REDACTED:260-268 | REDACTED:740-747 | REDACTED:893-900 | REDACTED:349-356 | REDACTED:566-573 — there are 6 copies across 4 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:244` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. 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.
Low cohesion: OpendalStore (LCOM4 4) integrations/object_store/src/store.rs:182— OpendalStore'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.
Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — bindings/nodejs/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
Wholesale file copy (68 identical lines × 2 files) bindings/nodejs/index.cjs:24— bindings/nodejs/index.cjs:24 · bindings/nodejs/index.mjs:24 — these 2 files are line-for-line copies of one another — 68 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Unused dependency '@swc-node/register' — Declared in bindings/nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@swc/core' — Declared in bindings/nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 26 significant file(s) lose their only recent owner: core/services/gcs-grpc/src/writer.rs, core/core/src/layers/simulate.rs, dev/src/release/bump.rs, core/services/gcs-grpc/src/backend.rs, core/core/src/raw/oio/copy/block_copy.rs, core/core/src/layers/capability_override.rs, core/services/gcs-grpc/src/core.rs, core/core/src/types/operator/uri.rs (+18 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 18 significant file(s) lose their only recent owner: bindings/dotnet/OpenDAL/Operator.cs, bindings/dotnet/OpenDAL/NativeMethods.cs, bindings/dotnet/src/buffer.rs, bindings/dotnet/OpenDAL/OperatorOutputStream.cs, bindings/dotnet/src/utils.rs, bindings/dotnet/src/result.rs, bindings/dotnet/OpenDAL/Interop/Buffers/WriteBuffer.cs, bindings/dotnet/OpenDAL/Utilities.cs (+10 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 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 (51 single-owned of 596 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 596 of the 951 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
Documentation: no contributor guidance bindings/go/README.md— The document ends before Contributing guidance, so this section is missing from the visible text. Add a 'Contributing' section with build/test/run instructions and PR guidelines.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 19 of 596 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 596 of the 951 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: core/edge/opfs_wasm32/src/lib.rs, bindings/java/src/main/java/org/apache/opendal/Capability.java, core/services/webhdfs/src/message.rs, REDACTED, bindings/c/src/layer.rs, bindings/java/src/main/java/org/apache/opendal/Metadata.java, bindings/haskell/src/types.rs, bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift (and 11 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 182/246 types (74%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.2 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 29313 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Silent fallback default on Err core/services/hdfs-native/src/reader.rs:64— `read_at` turns every `Err` into `Ok(Buffer::new())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `bindings/nodejs/generated.d.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a0f026-bda5-7cb6-a166-d6b13046eb25 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 372 · Warnings: 908 · Recommendations: 286 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 30-09-2026 @ 02:31 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.