Public report of unionlabs/union, published 25 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 04:52 UTC · Survey ID cd_5ab6253f1e324b1a894e3aaf15325449
unionlabs/union
Measured 25 October 2026, 22:55 UTC, at code version 031785b
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 228,483 lines of product code in 274 projects, tests not counted · Estimated rebuild effort: about 2.7 person-years · Weakest lens: Production Readiness, 28
Findings by how serious they are
1391 critical1613 serious228 minor
18 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
25 October 2026, 22:55 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
87of 87 dimensions measured by tools.
3091of 3232 findings point to an exact file and line, so you can open each one in the code. The other 141 concern the repository as a whole, such as missing documentation.
87dimensions across 8 lenses, read from 228,483 lines of product code in 274 projects.
unionlabs/union is rated At risk because critical security findings are open, most of them leaked passwords or keys. Its score is held back because nine passwords or keys sit in the current code and it has packages under a licence on your banned list. It scores 39 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 28, is the weakest lens and counts most in the score. The best first steps are replacing the nine exposed passwords or keys and switching the old ones off and replacing the six packages under a banned licence, each worth about 9 points. Raising Production Readiness to 70 would lift the score to about 48.
1,033 passwords or keys in the code's history, and nine in the code are open to anyone who can read the repository. 109 known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the 94 pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the 17 security weaknesses in the code. The 40 pieces of product code that depend on test code need their reference to the test project removed.
The product code is 228,483 lines, about €390,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 28 to 70, the lowest score rated Strong, the score would rise from 39 to about 48.
Code composition: what the lines of code are
Product code 50%Tests 50%
New since the last survey: 130 findings
These 130 critical or serious findings weren't in the previous survey, on 11 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Test Quality · Skipped test: noop ts-sdk-sui/test/Sui.test.ts
Test Quality · Skipped test: passes ts-sdk/test/ucs03/instruction.test.ts
Visual & motion safety · Animation without a prefers-reduced-motion guard app2/src/lib/dashboard/components/NewUser.svelte
Visual & motion safety · Animation without a prefers-reduced-motion guard app2/src/lib/dashboard/components/SideCard.svelte
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 1375 findings
These 1375 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one. The first 100 are listed here.
Explicit Debt · HackComment repeated across 14 files REDACTED
€130,000 to €650,000, for 2,156 to 6,840 hours of work, about 2.7 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 228,483 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 9 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Resolve the 4 No assertions finding(s) in Test Quality — start with Runtime.svelte.test.ts (2), effect.svelte.test.ts (2).
Raises the score by about 3 points · Low effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €390,000 to build again, about 2.7 person-years of work. Its weakest lens is Production Readiness, at 28 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 9 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for low effort, because it clears the 9 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — 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: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
1655 modules, with 3965 dependencies between them. 3 loops run through 108 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 1615 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
aptos_types.account uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break aptos_types.account, while a change to aptos_types.account can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: aptos_types.account uses a module listed above it, which is the healthy direction.
protos.cosmos.ics23.v1 uses protos.cometbft.crypto.v1, so a change to protos.cometbft.crypto.v1 can break protos.cosmos.ics23.v1, while a change to protos.cosmos.ics23.v1 can't break protos.cometbft.crypto.v1.
Position
Below the diagonal: protos.cosmos.ics23.v1 uses a module listed above it, which is the healthy direction.
protos.google.protobuf uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break protos.google.protobuf, while a change to protos.google.protobuf can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: protos.google.protobuf uses a module listed above it, which is the healthy direction.
unionlabs.bounded uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs.bounded, while a change to unionlabs.bounded can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs.bounded uses a module listed above it, which is the healthy direction.
unionlabs.id uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs.id, while a change to unionlabs.id can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs.id uses a module listed above it, which is the healthy direction.
unionlabs.never uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs.never, while a change to unionlabs.never can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs.never uses a module listed above it, which is the healthy direction.
unionlabs_primitives.bytes uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs_primitives.bytes, while a change to unionlabs_primitives.bytes can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs_primitives.bytes uses a module listed above it, which is the healthy direction.
12→19 unionlabs_primitives.bytes uses unionlabs_primitives.fixed_bytespart of a loop✕
Connections
1 pair of types, where a type in unionlabs_primitives.bytes uses a type in unionlabs_primitives.fixed_bytes.
unionlabs_primitives.bytes uses unionlabs_primitives.fixed_bytes, so a change to unionlabs_primitives.fixed_bytes can break unionlabs_primitives.bytes, while a change to unionlabs_primitives.bytes can't break unionlabs_primitives.fixed_bytes.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
unionlabs_primitives.uint uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs_primitives.uint, while a change to unionlabs_primitives.uint can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs_primitives.uint uses a module listed above it, which is the healthy direction.
depolama uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break depolama, while a change to depolama can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: depolama uses a module listed above it, which is the healthy direction.
depolama uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break depolama, while a change to depolama can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: depolama uses a module listed above it, which is the healthy direction.
depolama uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break depolama, while a change to depolama can't break unionlabs_primitives.bytes.
Position
Below the diagonal: depolama uses a module listed above it, which is the healthy direction.
ibc_union.events uses protos.google.protobuf, so a change to protos.google.protobuf can break ibc_union.events, while a change to ibc_union.events can't break protos.google.protobuf.
Position
Below the diagonal: ibc_union.events uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in ibc_union.events uses a type in unionlabs.id. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ibc_union.events uses unionlabs.id, so a change to unionlabs.id can break ibc_union.events, while a change to ibc_union.events can't break unionlabs.id.
Position
Below the diagonal: ibc_union.events uses a module listed above it, which is the healthy direction.
ibc_union.events uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break ibc_union.events, while a change to ibc_union.events can't break unionlabs_primitives.bytes.
Position
Below the diagonal: ibc_union.events uses a module listed above it, which is the healthy direction.
protos.atomone.gov.v1 uses protos.cosmos.base.query.v1beta1, so a change to protos.cosmos.base.query.v1beta1 can break protos.atomone.gov.v1, while a change to protos.atomone.gov.v1 can't break protos.cosmos.base.query.v1beta1.
Position
Below the diagonal: protos.atomone.gov.v1 uses a module listed above it, which is the healthy direction.
protos.atomone.gov.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.atomone.gov.v1, while a change to protos.atomone.gov.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.atomone.gov.v1 uses a module listed above it, which is the healthy direction.
16→29 protos.atomone.gov.v1 uses drippart of a loop✕
Connections
11 pairs of types, where a type in protos.atomone.gov.v1 uses a type in drip.
protos.atomone.gov.v1 uses token_factory_api, so a change to token_factory_api can break protos.atomone.gov.v1, while a change to protos.atomone.gov.v1 can't break token_factory_api.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
protos.babylon.epoching.v1 uses protos.cosmos.base.query.v1beta1, so a change to protos.cosmos.base.query.v1beta1 can break protos.babylon.epoching.v1, while a change to protos.babylon.epoching.v1 can't break protos.cosmos.base.query.v1beta1.
Position
Below the diagonal: protos.babylon.epoching.v1 uses a module listed above it, which is the healthy direction.
protos.babylon.epoching.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.babylon.epoching.v1, while a change to protos.babylon.epoching.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.babylon.epoching.v1 uses a module listed above it, which is the healthy direction.
17→29 protos.babylon.epoching.v1 uses drippart of a loop✕
Connections
1 pair of types, where a type in protos.babylon.epoching.v1 uses a type in drip.
protos.babylon.epoching.v1 uses drip, so a change to drip can break protos.babylon.epoching.v1, while a change to protos.babylon.epoching.v1 can't break drip.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→30 protos.babylon.epoching.v1 uses token_factory_apipart of a loop✕
Connections
3 pairs of types, where a type in protos.babylon.epoching.v1 uses a type in token_factory_api.
protos.babylon.epoching.v1 uses token_factory_api, so a change to token_factory_api can break protos.babylon.epoching.v1, while a change to protos.babylon.epoching.v1 can't break token_factory_api.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ucs00_pingpong.msg uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break ucs00_pingpong.msg, while a change to ucs00_pingpong.msg can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: ucs00_pingpong.msg uses a module listed above it, which is the healthy direction.
ucs00_pingpong.msg uses ucs00_pingpong.state, so a change to ucs00_pingpong.state can break ucs00_pingpong.msg, while a change to ucs00_pingpong.msg can't break ucs00_pingpong.state.
Position
Below the diagonal: ucs00_pingpong.msg uses a module listed above it, which is the healthy direction.
ucs00_pingpong.msg uses protos.google.protobuf, so a change to protos.google.protobuf can break ucs00_pingpong.msg, while a change to ucs00_pingpong.msg can't break protos.google.protobuf.
Position
Below the diagonal: ucs00_pingpong.msg uses a module listed above it, which is the healthy direction.
ucs00_pingpong.msg uses unionlabs.id, so a change to unionlabs.id can break ucs00_pingpong.msg, while a change to ucs00_pingpong.msg can't break unionlabs.id.
Position
Below the diagonal: ucs00_pingpong.msg uses a module listed above it, which is the healthy direction.
unionlabs_primitives.fixed_bytes uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs_primitives.fixed_bytes, while a change to unionlabs_primitives.fixed_bytes can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs_primitives.fixed_bytes uses a module listed above it, which is the healthy direction.
unionlabs_primitives.fixed_bytes uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break unionlabs_primitives.fixed_bytes, while a change to unionlabs_primitives.fixed_bytes can't break unionlabs_primitives.bytes.
Position
Below the diagonal: unionlabs_primitives.fixed_bytes uses a module listed above it, which is the healthy direction.
beacon_api_types.custom_types uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break beacon_api_types.custom_types, while a change to beacon_api_types.custom_types can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: beacon_api_types.custom_types uses a module listed above it, which is the healthy direction.
beacon_api_types.custom_types uses unionlabs_primitives.fixed_bytes, so a change to unionlabs_primitives.fixed_bytes can break beacon_api_types.custom_types, while a change to beacon_api_types.custom_types can't break unionlabs_primitives.fixed_bytes.
Position
Below the diagonal: beacon_api_types.custom_types uses a module listed above it, which is the healthy direction.
cometbls_light_client_types.chain_id uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break cometbls_light_client_types.chain_id, while a change to cometbls_light_client_types.chain_id can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: cometbls_light_client_types.chain_id uses a module listed above it, which is the healthy direction.
cometbls_light_client_types.chain_id uses unionlabs_primitives.fixed_bytes, so a change to unionlabs_primitives.fixed_bytes can break cometbls_light_client_types.chain_id, while a change to cometbls_light_client_types.chain_id can't break unionlabs_primitives.fixed_bytes.
Position
Below the diagonal: cometbls_light_client_types.chain_id uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1 uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break protos.cometbft.abci.v1, while a change to protos.cometbft.abci.v1 can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: protos.cometbft.abci.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1 uses protos.cometbft.crypto.v1, so a change to protos.cometbft.crypto.v1 can break protos.cometbft.abci.v1, while a change to protos.cometbft.abci.v1 can't break protos.cometbft.crypto.v1.
Position
Below the diagonal: protos.cometbft.abci.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.cometbft.abci.v1, while a change to protos.cometbft.abci.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.cometbft.abci.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1 uses protos.babylon.epoching.v1, so a change to protos.babylon.epoching.v1 can break protos.cometbft.abci.v1, while a change to protos.cometbft.abci.v1 can't break protos.babylon.epoching.v1.
Position
Below the diagonal: protos.cometbft.abci.v1 uses a module listed above it, which is the healthy direction.
22→23 protos.cometbft.abci.v1 uses protos.cometbft.abci.v1beta1part of a loop✕
Connections
3 pairs of types, where a type in protos.cometbft.abci.v1 uses a type in protos.cometbft.abci.v1beta1.
protos.cometbft.abci.v1 uses protos.cometbft.abci.v1beta1, so a change to protos.cometbft.abci.v1beta1 can break protos.cometbft.abci.v1, while a change to protos.cometbft.abci.v1 can't break protos.cometbft.abci.v1beta1.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
protos.cometbft.abci.v1beta1 uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break protos.cometbft.abci.v1beta1, while a change to protos.cometbft.abci.v1beta1 can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: protos.cometbft.abci.v1beta1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1beta1 uses protos.cometbft.crypto.v1, so a change to protos.cometbft.crypto.v1 can break protos.cometbft.abci.v1beta1, while a change to protos.cometbft.abci.v1beta1 can't break protos.cometbft.crypto.v1.
Position
Below the diagonal: protos.cometbft.abci.v1beta1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1beta1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.cometbft.abci.v1beta1, while a change to protos.cometbft.abci.v1beta1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.cometbft.abci.v1beta1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1beta1 uses protos.babylon.epoching.v1, so a change to protos.babylon.epoching.v1 can break protos.cometbft.abci.v1beta1, while a change to protos.cometbft.abci.v1beta1 can't break protos.babylon.epoching.v1.
Position
Below the diagonal: protos.cometbft.abci.v1beta1 uses a module listed above it, which is the healthy direction.
protos.cometbft.abci.v1beta1 uses protos.cometbft.abci.v1, so a change to protos.cometbft.abci.v1 can break protos.cometbft.abci.v1beta1, while a change to protos.cometbft.abci.v1beta1 can't break protos.cometbft.abci.v1.
Position
Below the diagonal: protos.cometbft.abci.v1beta1 uses a module listed above it, which is the healthy direction.
23→24 protos.cometbft.abci.v1beta1 uses protos.cometbft.types.v1part of a loop✕
Connections
4 pairs of types, where a type in protos.cometbft.abci.v1beta1 uses a type in protos.cometbft.types.v1.
protos.cometbft.abci.v1beta1 uses protos.cometbft.types.v1, so a change to protos.cometbft.types.v1 can break protos.cometbft.abci.v1beta1, while a change to protos.cometbft.abci.v1beta1 can't break protos.cometbft.types.v1.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
protos.cometbft.types.v1 uses protos.cometbft.crypto.v1, so a change to protos.cometbft.crypto.v1 can break protos.cometbft.types.v1, while a change to protos.cometbft.types.v1 can't break protos.cometbft.crypto.v1.
Position
Below the diagonal: protos.cometbft.types.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.types.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.cometbft.types.v1, while a change to protos.cometbft.types.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.cometbft.types.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.types.v1 uses protos.atomone.gov.v1, so a change to protos.atomone.gov.v1 can break protos.cometbft.types.v1, while a change to protos.cometbft.types.v1 can't break protos.atomone.gov.v1.
Position
Below the diagonal: protos.cometbft.types.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.types.v1 uses protos.babylon.epoching.v1, so a change to protos.babylon.epoching.v1 can break protos.cometbft.types.v1, while a change to protos.cometbft.types.v1 can't break protos.babylon.epoching.v1.
Position
Below the diagonal: protos.cometbft.types.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.types.v1 uses protos.cometbft.abci.v1beta1, so a change to protos.cometbft.abci.v1beta1 can break protos.cometbft.types.v1, while a change to protos.cometbft.types.v1 can't break protos.cometbft.abci.v1beta1.
Position
Below the diagonal: protos.cometbft.types.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.state.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.cometbft.state.v1, while a change to protos.cometbft.state.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.cometbft.state.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.state.v1 uses protos.cometbft.abci.v1, so a change to protos.cometbft.abci.v1 can break protos.cometbft.state.v1, while a change to protos.cometbft.state.v1 can't break protos.cometbft.abci.v1.
Position
Below the diagonal: protos.cometbft.state.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.state.v1 uses protos.cometbft.abci.v1beta1, so a change to protos.cometbft.abci.v1beta1 can break protos.cometbft.state.v1, while a change to protos.cometbft.state.v1 can't break protos.cometbft.abci.v1beta1.
Position
Below the diagonal: protos.cometbft.state.v1 uses a module listed above it, which is the healthy direction.
protos.cometbft.state.v1 uses protos.cometbft.types.v1, so a change to protos.cometbft.types.v1 can break protos.cometbft.state.v1, while a change to protos.cometbft.state.v1 can't break protos.cometbft.types.v1.
Position
Below the diagonal: protos.cometbft.state.v1 uses a module listed above it, which is the healthy direction.
unionlabs_primitives.bech32 uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break unionlabs_primitives.bech32, while a change to unionlabs_primitives.bech32 can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: unionlabs_primitives.bech32 uses a module listed above it, which is the healthy direction.
unionlabs_primitives.bech32 uses protos.cometbft.types.v1, so a change to protos.cometbft.types.v1 can break unionlabs_primitives.bech32, while a change to unionlabs_primitives.bech32 can't break protos.cometbft.types.v1.
Position
Below the diagonal: unionlabs_primitives.bech32 uses a module listed above it, which is the healthy direction.
voyager_vm uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break voyager_vm, while a change to voyager_vm can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: voyager_vm uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in voyager_vm uses a type in ucs00_pingpong.state.
The types involved
voyager_vm.Queue → ucs00_pingpong.state.Config
Direction
voyager_vm uses ucs00_pingpong.state, so a change to ucs00_pingpong.state can break voyager_vm, while a change to voyager_vm can't break ucs00_pingpong.state.
Position
Below the diagonal: voyager_vm uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in voyager_vm uses a type in protos.cometbft.types.v1.
The types involved
voyager_vm.Op → protos.cometbft.types.v1.Data
voyager_vm.Visit → protos.cometbft.types.v1.Data
Direction
voyager_vm uses protos.cometbft.types.v1, so a change to protos.cometbft.types.v1 can break voyager_vm, while a change to voyager_vm can't break protos.cometbft.types.v1.
Position
Below the diagonal: voyager_vm uses a module listed above it, which is the healthy direction.
lst_ocw uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break lst_ocw, while a change to lst_ocw can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: lst_ocw uses a module listed above it, which is the healthy direction.
lst_ocw uses unionlabs_primitives.bech32, so a change to unionlabs_primitives.bech32 can break lst_ocw, while a change to lst_ocw can't break unionlabs_primitives.bech32.
Position
Below the diagonal: lst_ocw uses a module listed above it, which is the healthy direction.
drip uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break drip, while a change to drip can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: drip uses a module listed above it, which is the healthy direction.
cometbft_rpc uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break cometbft_rpc, while a change to cometbft_rpc can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: cometbft_rpc uses a module listed above it, which is the healthy direction.
cometbft_rpc uses unionlabs.bounded, so a change to unionlabs.bounded can break cometbft_rpc, while a change to cometbft_rpc can't break unionlabs.bounded.
Position
Below the diagonal: cometbft_rpc uses a module listed above it, which is the healthy direction.
cometbft_rpc uses token_factory_api, so a change to token_factory_api can break cometbft_rpc, while a change to cometbft_rpc can't break token_factory_api.
Position
Below the diagonal: cometbft_rpc uses a module listed above it, which is the healthy direction.
protos.ibc.core.client.v1 uses protos.cosmos.base.query.v1beta1, so a change to protos.cosmos.base.query.v1beta1 can break protos.ibc.core.client.v1, while a change to protos.ibc.core.client.v1 can't break protos.cosmos.base.query.v1beta1.
Position
Below the diagonal: protos.ibc.core.client.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.core.client.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.ibc.core.client.v1, while a change to protos.ibc.core.client.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.ibc.core.client.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.core.client.v1 uses token_factory_api, so a change to token_factory_api can break protos.ibc.core.client.v1, while a change to protos.ibc.core.client.v1 can't break token_factory_api.
Position
Below the diagonal: protos.ibc.core.client.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.lightclients.gno.v1 uses protos.cometbft.crypto.v1, so a change to protos.cometbft.crypto.v1 can break protos.ibc.lightclients.gno.v1, while a change to protos.ibc.lightclients.gno.v1 can't break protos.cometbft.crypto.v1.
Position
Below the diagonal: protos.ibc.lightclients.gno.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.lightclients.gno.v1 uses protos.cosmos.ics23.v1, so a change to protos.cosmos.ics23.v1 can break protos.ibc.lightclients.gno.v1, while a change to protos.ibc.lightclients.gno.v1 can't break protos.cosmos.ics23.v1.
Position
Below the diagonal: protos.ibc.lightclients.gno.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.lightclients.gno.v1 uses protos.google.protobuf, so a change to protos.google.protobuf can break protos.ibc.lightclients.gno.v1, while a change to protos.ibc.lightclients.gno.v1 can't break protos.google.protobuf.
Position
Below the diagonal: protos.ibc.lightclients.gno.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.lightclients.gno.v1 uses protos.babylon.epoching.v1, so a change to protos.babylon.epoching.v1 can break protos.ibc.lightclients.gno.v1, while a change to protos.ibc.lightclients.gno.v1 can't break protos.babylon.epoching.v1.
Position
Below the diagonal: protos.ibc.lightclients.gno.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.lightclients.gno.v1 uses protos.cometbft.types.v1, so a change to protos.cometbft.types.v1 can break protos.ibc.lightclients.gno.v1, while a change to protos.ibc.lightclients.gno.v1 can't break protos.cometbft.types.v1.
Position
Below the diagonal: protos.ibc.lightclients.gno.v1 uses a module listed above it, which is the healthy direction.
protos.ibc.lightclients.gno.v1 uses protos.ibc.core.client.v1, so a change to protos.ibc.core.client.v1 can break protos.ibc.lightclients.gno.v1, while a change to protos.ibc.lightclients.gno.v1 can't break protos.ibc.core.client.v1.
Position
Below the diagonal: protos.ibc.lightclients.gno.v1 uses a module listed above it, which is the healthy direction.
voyager_primitives uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break voyager_primitives, while a change to voyager_primitives can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
voyager_primitives uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break voyager_primitives, while a change to voyager_primitives can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
voyager_primitives uses protos.google.protobuf, so a change to protos.google.protobuf can break voyager_primitives, while a change to voyager_primitives can't break protos.google.protobuf.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
voyager_primitives uses unionlabs.id, so a change to unionlabs.id can break voyager_primitives, while a change to voyager_primitives can't break unionlabs.id.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
voyager_primitives uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break voyager_primitives, while a change to voyager_primitives can't break unionlabs_primitives.bytes.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
voyager_primitives uses cometbls_light_client_types.chain_id, so a change to cometbls_light_client_types.chain_id can break voyager_primitives, while a change to voyager_primitives can't break cometbls_light_client_types.chain_id.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
voyager_primitives uses protos.ibc.core.client.v1, so a change to protos.ibc.core.client.v1 can break voyager_primitives, while a change to voyager_primitives can't break protos.ibc.core.client.v1.
Position
Below the diagonal: voyager_primitives uses a module listed above it, which is the healthy direction.
34→35 voyager_primitives uses ibc_classic_specpart of a loop✕
Connections
2 pairs of types, where a type in voyager_primitives uses a type in ibc_classic_spec.
voyager_primitives uses ibc_classic_spec, so a change to ibc_classic_spec can break voyager_primitives, while a change to voyager_primitives can't break ibc_classic_spec.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ibc_classic_spec uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break ibc_classic_spec, while a change to ibc_classic_spec can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: ibc_classic_spec uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in ibc_classic_spec uses a type in unionlabs.id. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ibc_classic_spec uses unionlabs.id, so a change to unionlabs.id can break ibc_classic_spec, while a change to ibc_classic_spec can't break unionlabs.id.
Position
Below the diagonal: ibc_classic_spec uses a module listed above it, which is the healthy direction.
ibc_classic_spec uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break ibc_classic_spec, while a change to ibc_classic_spec can't break unionlabs_primitives.bytes.
Position
Below the diagonal: ibc_classic_spec uses a module listed above it, which is the healthy direction.
ibc_classic_spec uses protos.ibc.core.client.v1, so a change to protos.ibc.core.client.v1 can break ibc_classic_spec, while a change to ibc_classic_spec can't break protos.ibc.core.client.v1.
Position
Below the diagonal: ibc_classic_spec uses a module listed above it, which is the healthy direction.
ibc_classic_spec uses voyager_primitives, so a change to voyager_primitives can break ibc_classic_spec, while a change to ibc_classic_spec can't break voyager_primitives.
Position
Below the diagonal: ibc_classic_spec uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break ibc_union_light_client, while a change to ibc_union_light_client can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break ibc_union_light_client, while a change to ibc_union_light_client can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses protos.google.protobuf, so a change to protos.google.protobuf can break ibc_union_light_client, while a change to ibc_union_light_client can't break protos.google.protobuf.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses unionlabs.id, so a change to unionlabs.id can break ibc_union_light_client, while a change to ibc_union_light_client can't break unionlabs.id.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break ibc_union_light_client, while a change to ibc_union_light_client can't break unionlabs_primitives.bytes.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses ibc_union.events, so a change to ibc_union.events can break ibc_union_light_client, while a change to ibc_union_light_client can't break ibc_union.events.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses ucs00_pingpong.msg, so a change to ucs00_pingpong.msg can break ibc_union_light_client, while a change to ibc_union_light_client can't break ucs00_pingpong.msg.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses protos.cometbft.types.v1, so a change to protos.cometbft.types.v1 can break ibc_union_light_client, while a change to ibc_union_light_client can't break protos.cometbft.types.v1.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
ibc_union_light_client uses protos.ibc.lightclients.gno.v1, so a change to protos.ibc.lightclients.gno.v1 can break ibc_union_light_client, while a change to ibc_union_light_client can't break protos.ibc.lightclients.gno.v1.
Position
Below the diagonal: ibc_union_light_client uses a module listed above it, which is the healthy direction.
voyager_client uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break voyager_client, while a change to voyager_client can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: voyager_client uses a module listed above it, which is the healthy direction.
voyager_client uses unionlabs_primitives.bytes, so a change to unionlabs_primitives.bytes can break voyager_client, while a change to voyager_client can't break unionlabs_primitives.bytes.
Position
Below the diagonal: voyager_client uses a module listed above it, which is the healthy direction.
voyager_client uses cometbls_light_client_types.chain_id, so a change to cometbls_light_client_types.chain_id can break voyager_client, while a change to voyager_client can't break cometbls_light_client_types.chain_id.
Position
Below the diagonal: voyager_client uses a module listed above it, which is the healthy direction.
voyager_client uses token_factory_api, so a change to token_factory_api can break voyager_client, while a change to voyager_client can't break token_factory_api.
Position
Below the diagonal: voyager_client uses a module listed above it, which is the healthy direction.
voyager_client uses protos.ibc.core.client.v1, so a change to protos.ibc.core.client.v1 can break voyager_client, while a change to voyager_client can't break protos.ibc.core.client.v1.
Position
Below the diagonal: voyager_client uses a module listed above it, which is the healthy direction.
voyager_client uses voyager_primitives, so a change to voyager_primitives can break voyager_client, while a change to voyager_client can't break voyager_primitives.
Position
Below the diagonal: voyager_client uses a module listed above it, which is the healthy direction.
voyager_rpc.types uses protos.cometbft.abci.v1.request, so a change to protos.cometbft.abci.v1.request can break voyager_rpc.types, while a change to voyager_rpc.types can't break protos.cometbft.abci.v1.request.
Position
Below the diagonal: voyager_rpc.types uses a module listed above it, which is the healthy direction.
voyager_rpc.types uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break voyager_rpc.types, while a change to voyager_rpc.types can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: voyager_rpc.types uses a module listed above it, which is the healthy direction.
voyager_rpc.types uses cometbls_light_client_types.chain_id, so a change to cometbls_light_client_types.chain_id can break voyager_rpc.types, while a change to voyager_rpc.types can't break cometbls_light_client_types.chain_id.
Position
Below the diagonal: voyager_rpc.types uses a module listed above it, which is the healthy direction.
voyager_rpc.types uses protos.cometbft.state.v1, so a change to protos.cometbft.state.v1 can break voyager_rpc.types, while a change to voyager_rpc.types can't break protos.cometbft.state.v1.
Position
Below the diagonal: voyager_rpc.types uses a module listed above it, which is the healthy direction.
voyager_rpc.types uses protos.ibc.core.client.v1, so a change to protos.ibc.core.client.v1 can break voyager_rpc.types, while a change to voyager_rpc.types can't break protos.ibc.core.client.v1.
Position
Below the diagonal: voyager_rpc.types uses a module listed above it, which is the healthy direction.
voyager_rpc.types uses voyager_primitives, so a change to voyager_primitives can break voyager_rpc.types, while a change to voyager_rpc.types can't break voyager_primitives.
Position
Below the diagonal: voyager_rpc.types uses a module listed above it, which is the healthy direction.
voyager_plugin uses protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk, so a change to protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk can break voyager_plugin, while a change to voyager_plugin can't break protos.cometbft.abci.v1beta1.response_apply_snapshot_chunk.
Position
Below the diagonal: voyager_plugin uses a module listed above it, which is the healthy direction.
voyager_plugin uses ucs00_pingpong.state, so a change to ucs00_pingpong.state can break voyager_plugin, while a change to voyager_plugin can't break ucs00_pingpong.state.
Position
Below the diagonal: voyager_plugin uses a module listed above it, which is the healthy direction.
voyager_plugin uses voyager_rpc.types, so a change to voyager_rpc.types can break voyager_plugin, while a change to voyager_plugin can't break voyager_rpc.types.
Position
Below the diagonal: voyager_plugin uses a module listed above it, which is the healthy direction.
voyager_plugin_attestor_evm.call uses ibc_classic_spec, so a change to ibc_classic_spec can break voyager_plugin_attestor_evm.call, while a change to voyager_plugin_attestor_evm.call can't break ibc_classic_spec.
Position
Below the diagonal: voyager_plugin_attestor_evm.call uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 48% · Weak · gated by R7 ·
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
A07:2025 — Authentication Failures
1043
High / Critical
A03:2025 — Software Supply Chain Failures
231
High / Critical
A05:2025 — Injection
132
High / Critical
A08:2025 — Software or Data Integrity Failures
1
High / Critical
Roadmap
Immediately resolve the nine leaked secrets, prioritizing the specified TypeScript files, and address the six banned license violations to secure the codebase. Strengthen dependency hygiene by removing unused packages and explicitly declaring imports, while shifting type- and test-only dependencies to development scopes. Finally, improve test reliability by adding coverage for unreachable production modules and fixing the four test cases that lack assertions.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 9 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
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 — 1391
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 — 1613
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 — 228
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 18
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. 87 of 87 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 87 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, 3091 of 3232 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.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for effect-svelte/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
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 54 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 59 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — 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: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for app2/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
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 app2/ was NOT MEASURED: the dependency install for app2/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 effect-svelte/ was NOT MEASURED: the dependency install for effect-svelte/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 sentinel2/ was NOT MEASURED: the dependency install for sentinel2/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 ts-sdk/ was NOT MEASURED: the dependency install for ts-sdk/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 ts-sdk-cosmos/ was NOT MEASURED: the dependency install for ts-sdk-cosmos/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 ts-sdk-evm/ was NOT MEASURED: the dependency install for ts-sdk-evm/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 ts-sdk-sui/ was NOT MEASURED: the dependency install for ts-sdk-sui/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 typescript-sdk/ was NOT MEASURED: the dependency install for typescript-sdk/ could not reach npm.jsr.io, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://npm.jsr.io/~/11/@jsr/rehype-pretty__transformers/0.13.4.tgz: Forbidden - 403), 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.
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 REDACTED, but the licence verdict published here was taken over its crate 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.
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 Go module (REDACTED/go.sum), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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. `app2/src/hooks.client.ts`, `app2/src/lib/components/layout/Sidebar/navigation.ts`, `app2/src/lib/constants/spender-addresses.ts`, `app2/src/lib/dashboard/client.ts`, `app2/src/lib/gasprice/error.ts`, … (+60 more) 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.
AC2 Forms & labels — 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. 103 further occurrence(s) are not listed individually; the score already reflects all 143.
AC6 Visual & motion safety — 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is depinject, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX8 Test isolation — 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. 47 further occurrence(s) are not listed individually; the score already reflects all 87.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Rust, Svelte components, solidity is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Rust, Svelte components, solidity is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
R10 Code Duplication — 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. 264 further occurrence(s) are not listed individually; the score already reflects all 304.
R4 Test Coverage — 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. 544 further occurrence(s) are not listed individually; the score already reflects all 584.
R7 Dead Code — 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. 414 further occurrence(s) are not listed individually; the score already reflects all 454.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 200 further occurrence(s) are not listed individually; the score already reflects all 240.
Repo exclusion declarations: 3 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
43 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was voyager::do_main at 52. A further 12 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 ibc_union::contract::execute at 35 — they are counted neither in the figure above nor in this dimension's score. 5 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: cosmwasm/core/src/contract.rs (ibc_union::contract::execute at 35), voyager/plugins/transaction/gno/src/main.rs (voyager_transaction_plugin_gno::process_msgs at 21), cosmwasm/access-manager/src/lib.rs (access_manager::query at 17), voyager/plugins/event-source/gno/src/ibc_events.rs (IbcEvent::from_gno_event at 16), voyager/plugins/transaction/evm/src/main.rs (voyager_transaction_plugin_evm::process_msgs at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 29 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with voyager::do_main (cyclomatic 52), v1_2_0.CreateUpgradeHandler (cyclomatic 47), cosmwasm_deployer::do_main (cyclomatic 43). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with v1_2_0.CreateUpgradeHandler (cognitive 88), Cmd::run (cognitive 81), cosmwasm_deployer::do_main (cognitive 72). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 41 FunctionTooLong finding(s) in God Classes — start with REDACTED (13), contract.rs (9), REDACTED (2). — One of this dimension's main actionable groups (41 warning-level).
Resolve the 39 FileTooLong finding(s) in God Classes — start with REDACTED (16), REDACTED (11), contract.rs (3). — One of this dimension's main actionable groups (39 warning-level).
Resolve the 36 MethodTooLong finding(s) in God Classes — start with REDACTED (24), REDACTED (5), call.rs (2). — One of this dimension's main actionable groups (36 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
470 duplicated block group(s) detected. A further 24 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 9 of the 494 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .ts (23% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 158 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 25 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with REDACTED (9), REDACTED (4), contract.rs (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 22 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with REDACTED (9), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 19 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with REDACTED (8), REDACTED (5), contract.rs (2). — One of this dimension's main actionable groups (19 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.0 / 10Stronggated by 32 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.
272 production modules (Cargo+npm+Go+Deno), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; 32 module(s) off the main sequence, with abstractness counted on 244 of the 272 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: gnark-key-parser · ×29
Unstable project access-manager
Unstable project ethereum-sync-protocol
Unstable project starknet-verifier
Off the main sequence: consensus-primitives · ×3
What to do
Resolve the 29 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 1 Unstable project access-manager finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project ethereum-sync-protocol finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED (2), cache.rs, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.9 / 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.
1355 test methods: 831 unit, 510 integration, 0 BDD, 14 e2e. The JavaScript/TypeScript suite contributes 54 `it`/`test` case(s) across 20 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 1290 `#[test]` function(s) across 192 file(s) declaring at least one; its unit/integration split is Cargo's own — 13 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 Go suite contributes 11 test case(s) across 6 `_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: 0 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.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality8.1 / 10Strong✓ 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.
7 skipped (5 with a documented reason), 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 54 tests. Measured on the JavaScript/TypeScript suite only — at least 59 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: interrupts on cleanup · ×4effect-svelte/src/lib/test/Runtime.svelte.test.ts:50
Skipped (documented): guarantees given HRP matches · ×5ts-sdk/test/schema/bech32.test.ts:54
What to do
Resolve the 4 No assertions finding(s) in Test Quality — start with Runtime.svelte.test.ts (2), effect.svelte.test.ts (2). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Skipped test finding(s) in Test Quality — start with Sui.test.ts, instruction.test.ts. — One of this dimension's main actionable groups (2 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 dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
36 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). 41 of 41 direct requirement(s) were graded against proxy.golang.org (0 not served there, 1 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
Outdated: cosmossdk.io/api · ×36
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 9 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 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.
6 of 1168 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 100 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares REDACTED and a Go module (REDACTED/go.sum), 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.
Banned license: cw-orch · ×6
What to do
Resolve the 6 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (6 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, REDACTED, upgrade.go. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.8 / 10Strong✓ 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.
153 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is cosmwasm/access-manager/src/tests.rs. Counted over 689 of the 1537 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 · ×5
Further sole-owners (lower concentration)
What to do
Resolve the 5 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (5 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
453 deducted task-comment markers across 228483 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
HackComment repeated across 14 filestypescript-sdk/playground/babylon-to-holesky.ts:12
What to do
Resolve the 394 TodoComment finding(s) in Explicit Debt — start with REDACTED (70), REDACTED (67), server.rs (12). — One of this dimension's main actionable groups (394 warning-level).
Resolve the 35 XxxComment finding(s) in Explicit Debt — start with Ucs03.ts (4), tokenOrder.ts (3), REDACTED (3). — One of this dimension's main actionable groups (35 warning-level).
Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with validator.rs (3), REDACTED (3), contract.rs. — One of this dimension's main actionable groups (7 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 115 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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.
1037 finding(s): 0 critical, 1037 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1007 REDACTED finding(s) in Secrets (history) — start with REDACTED (354), REDACTED (296), REDACTED (35). — One of this dimension's main actionable groups (1007 issue-level).
Resolve the 26 High secret finding(s) in Secrets (history) — start with REDACTED (25), REDACTED. — One of this dimension's main actionable groups (26 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).
132 finding(s): 0 critical, 117 high, 4 medium, 11 low. 94 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 73 file(s) — `app2/src/hooks.client.ts` (line 73, line 78), `app2/src/lib/components/layout/Sidebar/navigation.ts` (line 17), `app2/src/lib/constants/spender-addresses.ts` (lines 7–9), `app2/src/lib/dashboard/client.ts` (lines 10–35), `app2/src/lib/gasprice/error.ts` (line 7), … (+68 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 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
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 94 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (94 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 81 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (56), REDACTED (9), REDACTED (9). — One of this dimension's main actionable groups (81 issue-level).
Resolve the 19 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (19 issue-level).
Resolve the 7 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (7 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.
87 of 689 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ts-sdk/src/Ucs03.ts. Counted over 689 of the 1537 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned knowledge · ×5ts-sdk/src/Ucs03.ts:1
Orphaned file · ×8211-cometbls/store.go:1
Further orphaned files (smaller)
What to do
Resolve the 5 Orphaned knowledge finding(s) in Knowledge Freshness — start with Ucs03.ts, bitfield.rs, bn254.rs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 82 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (3), types.ts (3), transfer.ts (2). — One of this dimension's main actionable groups (82 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Boundary-crossing change coupling finding(s) in Change Coupling — start with client_state.rs (3), REDACTED, server.rs. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 10 Change coupling finding(s) in Change Coupling — start with REDACTED (3), contract.rs (2), lightclient.rs. — One of this dimension's main actionable groups (10 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — 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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.
Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d43_recommendation.md · top locations in Appendix A, every location in findings.md.
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 4 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.4 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×6) — app2/src/lib/components/AnimatedArrows.svelte:230, app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:571, app2/src/routes/explorer/orbital/charts/TerminalLog.svelte:384, …
Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). — app2/src/routes/yaps/YappersHero.svelte:91
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — site/src/components/Header.astro:65
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels4.5 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — app2/src/lib/components/AddressInput.svelte:140
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×36) — app2/src/lib/components/layout/AppErrors/index.svelte:19, app2/src/lib/components/layout/AppErrors/index.svelte:25, app2/src/lib/components/layout/AppErrors/index.svelte:31, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×3) — app2/src/lib/components/model/ErrorComponent.svelte:198, app2/src/lib/components/model/ErrorComponent.svelte:218, app2/src/lib/components/model/ErrorComponent.svelte:243
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×4) — app2/src/app.html:2, effect-svelte/src/app.html:2, site/src/layouts/BaseLayout.astro:47, …
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — site/src/components/typography/h3.astro:1
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. (×3) — app2/src/lib/components/model/BarChart.svelte:103, app2/src/lib/components/ui/Tooltip.svelte:254, app2/src/routes/yaps/YappersHero.svelte:83
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×8) — app2/src/lib/components/model/DustWithdrawalListItemComponent.svelte:75, app2/src/lib/components/model/PacketListItemComponent.svelte:36, app2/src/lib/components/model/StakingListItemComponent.svelte:120, …
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — app2/src/lib/components/ui/Modal.svelte:65, app2/src/lib/components/ui/Modal.svelte:73
This <div role="alertdialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — app2/src/lib/components/ui/Wallet/connect/metamask-mobile-alert.svelte:23
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
<div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×22) — app2/src/lib/components/stake/BondComponent.svelte:711, app2/src/lib/components/stake/ProxyDustRecovery.svelte:408, app2/src/lib/components/stake/QuickWithdrawComponent.svelte:503, …
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×2) — app2/src/lib/components/stake/StakingHistoryCard.svelte:83, app2/src/lib/components/stake/StakingHistoryCard.svelte:93
<svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×3) — app2/src/lib/components/stake/StatusDisplay.svelte:0, app2/src/routes/dashboard/rewards/+page.svelte:0, zkgm-dev/src/routes/+page.svelte:0
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×5) — app2/src/lib/components/ui/Wallet/connect/connection.svelte:164, app2/src/lib/dashboard/components/SocialConnections.svelte:30, app2/src/lib/dashboard/components/SocialConnections.svelte:85, …
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×4) — app2/src/lib/dashboard/components/DeleteAccountModal.svelte:116, app2/src/lib/dashboard/components/UnlinkAccountModal.svelte:123, ceremony/src/lib/components/Terminal/Code.svelte:127, …
<spinnericon> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — app2/src/lib/dashboard/components/NewUser.svelte:53, app2/src/lib/dashboard/components/SideCard.svelte:58
<select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — app2/src/routes/explorer/orbital/charts/LatencyChart.svelte:298, app2/src/routes/explorer/orbital/charts/LatencyChart.svelte:311
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 355 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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 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. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation0.0 / 10Critical✓ 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.
`arbitrum-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`base-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`base-verifier` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`berachain-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`bob-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`cometbls-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`cw-account` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`cw-escrow-vault` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`cw-unionversal-token` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`cw20-token-minter` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`gno-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ibc-solidity` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ibc-union` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ibc-union-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ibc-union-msg` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`osmosis-tokenfactory-token-minter` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`parlia-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`proof-lens-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`proof-lens-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`starknet-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`state-lens-ics23-ics23-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`state-lens-ics23-ics23-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`state-lens-ics23-mpt-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`state-lens-ics23-mpt-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`state-lens-ics23-smt-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`state-lens-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`tendermint-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`u` (production) references the test project `ibc-classic-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`u` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ucs00-pingpong` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ucs03-solvable` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ucs03-zkgm` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ucs03-zkgm-token-minter-api` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`ucs03-zkgmable` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`voyager` (production) references the test project `ibc-classic-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`voyager` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`voyager-client-bootstrap-module-arbitrum` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`voyager-client-bootstrap-module-attested` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`voyager-client-bootstrap-module-base` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`voyager-client-bootstrap-module-bob` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
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.
`evm_storage_verifier$module.get_node` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — lib/evm-storage-verifier/src/lib.rs:132
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing REDACTED) 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.
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 · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
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.
183 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 239 of 280 project(s) that lack one — worth up to 1.7 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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.
galoisd/README.md links to `./proot/api/v1/prover.proto`, but `galoisd/proot/api/v1/prover.proto` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — galoisd/README.md:106
cosmwasm/cw20-base/README.md links to `../../packages/cw20/README.md`, but `packages/cw20/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — cosmwasm/cw20-base/README.md:4
lib/beacon-api-types/README.md links to `lib/beacon-api/`, but `lib/beacon-api-types/lib/beacon-api` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — lib/beacon-api-types/README.md:5
What to do
Reconcile the README with reality: galoisd/README.md links to `./proot/api/v1/prover.proto`, but `galoisd/proot/api/v1/prover.proto` does not exist; cosmwasm/cw20-base/README.md links to `../../packages/cw20/README.md`, but `packages/cw20/README.md` does not exist; lib/beacon-api-types/README.md links to `lib/beacon-api/`, but `lib/beacon-api-types/lib/beacon-api` does not exist.
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.
4909/5060 types (97%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Go: an unexported name, or move it under `internal/`; Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
Only 127/138 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `app2`, `ceremony`, `cosmwasm/cw20-base`, `cosmwasm/cw20-wrapped-tokenfactory` and 6 more.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — drip/src/turnstile.rs:30
`reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×14) — lib/beacon-api/src/client.rs:42, voyager/modules/client-bootstrap/sui/src/main.rs:127, voyager/modules/proof/movement/src/main.rs:177, …
`ClientBuilder::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — mpc/shared/src/supabase.rs:56, mpc/shared/src/supabase.rs:195
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`Fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — sentinel2/src/helpers.ts:75
`Fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — sentinel2/src/helpers.ts:78
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 Safety10.0 / 10Exemplary✓ 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.
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.
33 duplicated blocks under the repository root have copies in at least two of the sibling directories app2, ceremony, effect-svelte, ts-sdk, ts-sdk-cosmos, ts-sdk-evm (+3 more sibling(s) not listed) — 27 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 33 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app2/src/lib/graphql/service.ts:37
9 of the duplicated blocks reported below have copies in at least two of the sibling directories transfer, transfer-ucs03-cosmos, transfer-ucs03-evm under app2/src/lib/services/. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app2/src/lib/services/transfer-ucs03-cosmos/state.ts:23
6 of the duplicated blocks reported below have copies in at least two of the sibling directories dust, packets, stakes, transfers, unstakes, withdrawals under app2/src/routes/explorer/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app2/src/routes/explorer/packets/+page.svelte:24
6 duplicated blocks under ts-sdk/src/ have copies in at least two of the sibling directories aptos, cosmos, evm, sui, ucs03 — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — ts-sdk/src/aptos/client.ts:47
5 duplicated blocks under app2/src/lib/transfer/ have copies in at least two of the sibling directories multisig, normal — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app2/src/lib/transfer/multisig/services/filling.ts:26
app2/src/lib/components/stake/BondComponent.svelte:151 · app2/src/lib/components/stake/UnbondComponent.svelte:129 — the two spans are one implementation copied and then locally edited — 1629 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/lib/components/stake/BondComponent.svelte:151
app2/src/lib/graphql/service.ts:37 · ts-sdk/src/Indexer.ts:83 — the two spans are one implementation copied and then locally edited — 1012 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/lib/graphql/service.ts:37
app2/src/lib/dashboard/services/add-cosmos-wallet.ts:18 · app2/src/lib/dashboard/services/add-evm-wallet.ts:16 — the two spans are one implementation copied and then locally edited — 913 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/lib/dashboard/services/add-cosmos-wallet.ts:18
ts-sdk-cosmos/src/internal/zkgmClient.ts:25 · ts-sdk-evm/src/internal/zkgmClient.ts:27 — the two spans are one implementation copied and then locally edited — 767 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ts-sdk-cosmos/src/internal/zkgmClient.ts:25
app2/src/lib/services/cosmos/chain-info/internal-chain-info.ts:1 · app2/src/lib/services/cosmos/chain-info/keplr-chain-info.ts:1 — these 2 files are line-for-line copies of one another — 136 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. — app2/src/lib/services/cosmos/chain-info/internal-chain-info.ts:1
app2/src/lib/components/stake/ProxyDustRecovery.svelte:122 · app2/src/lib/components/stake/WithdrawalComponent.svelte:186 — the two spans are one implementation copied and then locally edited — 677 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/lib/components/stake/ProxyDustRecovery.svelte:122
app2/src/lib/utils/effect.svelte.ts:2 · effect-svelte/src/lib/Runtime.svelte.ts:2 — these 2 files are line-for-line copies of one another — 118 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. — app2/src/lib/utils/effect.svelte.ts:2
app2/src/lib/dashboard/stores/achievements.svelte.ts:30 · app2/src/lib/dashboard/stores/missions.svelte.ts:9 — the two spans are one implementation copied and then locally edited — 540 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/lib/dashboard/stores/achievements.svelte.ts:30
app2/src/lib/transfer/multisig/services/filling.ts:26 · app2/src/lib/transfer/normal/services/filling.ts:21 — the two spans are one implementation copied and then locally edited — 862 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/lib/transfer/multisig/services/filling.ts:26
ts-sdk/src/internal/tokenOrder.ts:34 · ts-sdk/src/internal/zkgmClientRequest.ts:27 — the two spans are one implementation copied and then locally edited — 461 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ts-sdk/src/internal/tokenOrder.ts:34
ts-sdk/src/Ucs05.ts:118 · ts-sdk/src/schema/address.ts:59 — the two spans are one implementation copied and then locally edited — 615 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ts-sdk/src/Ucs05.ts:118
ts-sdk-sui/src/Sui.ts:477 · ts-sdk/src/sui/sui_coin.ts:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ts-sdk-sui/src/Sui.ts:477
typescript-sdk/playground/union-to-babylon-cw20.ts:1 · typescript-sdk/playground/union-to-holesky-cw20.ts:1 — these 2 files are line-for-line copies of one another — 71 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. — typescript-sdk/playground/union-to-babylon-cw20.ts:1
typescript-sdk/playground/babylon-to-holesky.ts:13 · typescript-sdk/playground/osmosis-to-holesky.ts:13 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — typescript-sdk/playground/babylon-to-holesky.ts:13
typescript-sdk/playground/holesky-to-babylon.ts:1 · typescript-sdk/playground/holesky-to-union.ts:1 — these 2 files are line-for-line copies of one another — 66 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. — typescript-sdk/playground/holesky-to-babylon.ts:1
REDACTED:13 · typescript-sdk/playground/union-to-babylon-cw20.ts:13 · typescript-sdk/playground/union-to-babylon.ts:13 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — REDACTED:13
typescript-sdk/playground/holesky-to-sepolia-legacy.ts:12 · typescript-sdk/playground/sepolia-to-holesky-legacy.ts:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — typescript-sdk/playground/holesky-to-sepolia-legacy.ts:12
typescript-sdk/playground/union-to-arbitrum-legacy.ts:14 · typescript-sdk/playground/union-to-berachain-legacy.ts:14 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — typescript-sdk/playground/union-to-arbitrum-legacy.ts:14
app2/src/routes/explorer/packets/+page.svelte:24 · app2/src/routes/explorer/transfers/+page.svelte:25 — the two spans are one implementation copied and then locally edited — 337 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/routes/explorer/packets/+page.svelte:24
app2/src/lib/dashboard/components/DeleteAccountModal.svelte:2 · app2/src/lib/dashboard/components/UnlinkAccountModal.svelte:2 — these 2 files are line-for-line copies of one another — 52 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. — app2/src/lib/dashboard/components/DeleteAccountModal.svelte:2
app2/src/lib/components/stake/BondComponent.svelte:364 · app2/src/lib/components/stake/QuickWithdrawComponent.svelte:272 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — app2/src/lib/components/stake/BondComponent.svelte:364
app2/src/lib/dashboard/stores/user.svelte.ts:339 · app2/src/lib/dashboard/stores/user.svelte.ts:432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — app2/src/lib/dashboard/stores/user.svelte.ts:339
typescript-sdk/playground/holesky-to-babylon.ts:13 · typescript-sdk/playground/holesky-to-stargaze.ts:13 · typescript-sdk/playground/holesky-to-union.ts:13 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — typescript-sdk/playground/holesky-to-babylon.ts:13
app2/src/routes/eudrop/claim/step/Step1.svelte:29 · app2/src/routes/liquid-staking/+page.svelte:88 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app2/src/routes/eudrop/claim/step/Step1.svelte:29
app2/src/routes/eudrop/claim/+page.svelte:62 · app2/src/routes/liquid-staking/+page.svelte:33 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — app2/src/routes/eudrop/claim/+page.svelte:62
ts-sdk-cosmos/src/Cosmos.ts:386 · ts-sdk/src/cosmos/query.ts:26 — the two spans are one implementation copied and then locally edited — 308 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — ts-sdk-cosmos/src/Cosmos.ts:386
app2/src/lib/dashboard/database.types.ts:419 · app2/src/lib/dashboard/database.types.ts:867 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — app2/src/lib/dashboard/database.types.ts:419
app2/src/routes/explorer/orbital/charts/AssetVolumeChart.svelte:18 · app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte:15 — the two spans are one implementation copied and then locally edited — 216 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/routes/explorer/orbital/charts/AssetVolumeChart.svelte:18
app2/src/routes/explorer/orbital/charts/PopularRoutesChart.svelte:15 · app2/src/routes/explorer/orbital/charts/WalletActivityChart.svelte:19 — the two spans are one implementation copied and then locally edited — 264 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — app2/src/routes/explorer/orbital/charts/PopularRoutesChart.svelte:15
app2/src/lib/stores/statistics.svelte.ts:32 · app2/src/lib/stores/statistics.svelte.ts:76 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — app2/src/lib/stores/statistics.svelte.ts:32
typescript-sdk/playground/holesky-to-sepolia.ts:38 · typescript-sdk/playground/sepolia-to-holesky.ts:36 — the two spans are one implementation copied and then locally edited — 267 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — typescript-sdk/playground/holesky-to-sepolia.ts:38
typescript-sdk/playground/aptos-to-aptos-legacy.ts:11 · typescript-sdk/playground/aptos-to-union-legacy.ts:11 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — typescript-sdk/playground/aptos-to-aptos-legacy.ts:11
ts-sdk/src/Aptos.ts:22 · ts-sdk/src/utils/aptos-wallet.ts:8 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ts-sdk/src/Aptos.ts:22
ts-sdk/src/Utils.ts:91 · ts-sdk/src/utils/extract-error-details.ts:1 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — ts-sdk/src/Utils.ts:91
ceremony/src/lib/components/Blink.svelte:2 · zkgm-dev/src/lib/components/Blink.svelte:2 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — ceremony/src/lib/components/Blink.svelte:2
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 54 and cognitive complexity 191; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sentinel2/src/escrow-supply-control-loop.ts:118
mapSupabaseErrorToCustomError has cyclomatic complexity 28 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/dashboard/errors.ts:57
getMessage has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/components/stake/StatusDisplay.svelte:108
(top-level) has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/dashboard/database.types.ts:1
(anonymous) has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:145
(anonymous) has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/stores/sorted-balances.svelte.ts:75
updateState has cyclomatic complexity 18 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ceremony/src/lib/state/contributor.svelte.ts:292
isCurrentPath has cyclomatic complexity 17 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/components/layout/Navigation.svelte:82
(anonymous) has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte:205
onSome has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/transfer/shared/services/filling/check-filling.ts:73
onmessage has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/routes/explorer/orbital/+page.svelte:76
updateAndDrawNodes has cyclomatic complexity 14 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:389
formatWaitTime has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ceremony/src/lib/utils/utils.ts:108
(anonymous) has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:86
(anonymous) has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — typescript-sdk/src/query/offchain/ucs03-channels.ts:75
(anonymous) has cyclomatic complexity 12 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sentinel2/src/check-balances.ts:179
(anonymous) has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app2/src/lib/components/ui/DateTimeComponent.svelte:40
(anonymous) has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — typescript-sdk/src/aptos/transfer.ts:106
(anonymous) has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ts-sdk/src/internal/tokenOrder.ts:135
(anonymous) has cyclomatic complexity 11 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sentinel2/src/check-ssl-certificates.ts:48
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.9 / 10Strong✓ 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.
ts-sdk/src/Ucs03.ts has 1871 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk/src/Ucs03.ts:1
ts-sdk/src/PriceOracle.ts has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk/src/PriceOracle.ts:1
app2/src/lib/stores/fee.svelte.ts has 710 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/stores/fee.svelte.ts:1
app2/src/lib/components/stake/BondComponent.svelte has 673 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/components/stake/BondComponent.svelte:1
ts-sdk-cosmos/src/Cosmos.ts has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk-cosmos/src/Cosmos.ts:1
app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte:1
ts-sdk-evm/src/internal/zkgmClient.ts has 626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk-evm/src/internal/zkgmClient.ts:1
ts-sdk-sui/src/Sui.ts has 625 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk-sui/src/Sui.ts:1
app2/src/lib/dashboard/components/WalletDialog.svelte has 621 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/dashboard/components/WalletDialog.svelte:1
ts-sdk-evm/src/Evm.ts has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk-evm/src/Evm.ts:1
sentinel2/src/escrow-supply-control-loop.ts has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sentinel2/src/escrow-supply-control-loop.ts:1
app2/src/lib/components/stake/UnbondComponent.svelte has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/components/stake/UnbondComponent.svelte:1
app2/src/lib/components/stake/StatusDisplay.svelte has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/components/stake/StatusDisplay.svelte:1
app2/src/lib/dashboard/stores/user.svelte.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/dashboard/stores/user.svelte.ts:1
app2/src/lib/transfer/shared/components/Receiver.svelte has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/transfer/shared/components/Receiver.svelte:1
app2/src/lib/dashboard/components/AchievementTabs.svelte has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/dashboard/components/AchievementTabs.svelte:1
ts-sdk/src/Staking.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk/src/Staking.ts:1
app2/src/routes/explorer/orbital/charts/LatencyChart.svelte has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/routes/explorer/orbital/charts/LatencyChart.svelte:1
app2/src/lib/transfer/normal/steps/ApprovalStep.svelte has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/transfer/normal/steps/ApprovalStep.svelte:1
app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:1
app2/src/lib/components/stake/QuickWithdrawComponent.svelte has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/components/stake/QuickWithdrawComponent.svelte:1
app2/src/lib/dashboard/queries/private.ts has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/dashboard/queries/private.ts:1
REDACTED has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
app2/src/lib/components/stake/WithdrawalComponent.svelte has 480 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/components/stake/WithdrawalComponent.svelte:1
ts-sdk/src/ucs03/fungible-asset-order.ts has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk/src/ucs03/fungible-asset-order.ts:1
ts-sdk/src/internal/tokenOrder.ts has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — ts-sdk/src/internal/tokenOrder.ts:1
app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte:1
app2/src/routes/eudrop/claim/step/Step5.svelte has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/routes/eudrop/claim/step/Step5.svelte:1
app2/src/routes/btcfi/step/Step3.svelte has 436 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/routes/btcfi/step/Step3.svelte:1
typescript-sdk/src/query/on-chain.ts has 419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — typescript-sdk/src/query/on-chain.ts:1
app2/src/lib/wallet/evm/wagmi-config.svelte.ts has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/wallet/evm/wagmi-config.svelte.ts:1
app2/src/lib/dashboard/queries/public.ts has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app2/src/lib/dashboard/queries/public.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage1.6 / 10Critical✓ 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. (×40) — app2/src/lib/dashboard/database.types.ts:1, typescript-sdk/src/abi/ucs-01.ts:1, app2/src/lib/stores/fee.svelte.ts:1, …
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 REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ 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.
58 file(s) (~2993 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: ceremony/src/routes/+layout.ts imports '../../.svelte-kit/types/src/routes/$types.ts', 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. — ceremony
8 file(s) (~1920 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — sentinel2
Unreachable from the 221 application, 51 tooling and 35 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×16) — app2/src/lib/dashboard/database.types.ts, app2/src/lib/stores/fee.svelte.ts, app2/src/lib/config/wallets/info.ts, …
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (app2/src/lib/dashboard/components/SocialConnections.svelte, app2/src/lib/dashboard/components/UnlinkAccountModal.svelte, app2/src/lib/dashboard/helpers.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/stores/user.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/shared/components/ChainAsset/RepresentationSelector.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 7 in-repo import(s) from 4 other file(s) do name it (app2/src/lib/dashboard/queries/index.ts, app2/src/lib/dashboard/stores/check.svelte.ts, app2/src/lib/dashboard/stores/user.svelte.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/queries/private.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (app2/src/lib/components/stake/BondComponent.svelte, app2/src/lib/components/stake/ProxyDustRecovery.svelte, app2/src/lib/components/stake/QuickWithdrawComponent.svelte and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/components/stake/StatusDisplay.svelte
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 4 in-repo import(s) from 2 other file(s) do name it (app2/src/lib/dashboard/queries/index.ts, app2/src/lib/dashboard/stores/wallets.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/queries/public.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/evm/config.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/wallet/evm/wagmi-config.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/normal/steps/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — app2/src/lib/transfer/normal/steps/ApprovalStep.svelte, app2/src/lib/transfer/normal/steps/SubmitStep.svelte
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/components/stake/BalanceCard.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/components/stake/ProxyDustRecovery.svelte
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/dashboard/components/WalletStats.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/components/WalletDialog.svelte
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (app2/src/lib/dashboard/components/WalletCard.svelte, app2/src/lib/dashboard/components/WalletDialog.svelte, app2/src/lib/dashboard/components/WalletDisplay.svelte and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/stores/wallets.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/dashboard/stores/user.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/stores/rewards.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/runtime.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/graphql/service.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (app2/src/lib/dashboard/queries/private.ts, app2/src/lib/dashboard/queries/public.ts, app2/src/lib/dashboard/stores/airdrop.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/services/cache.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/cosmos/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/wallet/cosmos/config.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/evm/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/wallet/evm/config.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/sui/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/wallet/sui/config.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/index.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/transfer/normal/index.svelte
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (app2/src/lib/dashboard/components/Mission.svelte, app2/src/lib/dashboard/stores/user.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/stores/missions.svelte.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/dashboard/components/WalletDialog.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/dashboard/services/add-cosmos-wallet.ts
no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/components/model/ErrorComponent.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app2/src/lib/components/ui/Tooltip.svelte
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
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 REDACTED — installs work only by hoisting accident. — vitest.setup.ts:1
Declared in REDACTED 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. (×3)
Every import is type-only — move it to devDependencies. — sentinel2/src/fund-babylon-accounts.ts:1
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.
app2/src/lib/services/evm/clients.ts → app2/src/lib/services/transfer/errors.ts → app2/src/lib/services/transfer-ucs03-evm/index.ts → app2/src/lib/services/transfer-ucs03-evm/approval.ts → app2/src/lib/services/evm/clients.ts (one verified cycle inside a mutually-dependent group of 6 files) — app2/src/lib/services/evm/clients.ts:14
sentinel2/src/check-balances.ts → sentinel2/src/sentinel2.ts → sentinel2/src/check-balances.ts (one verified cycle inside a mutually-dependent group of 6 files) — sentinel2/src/check-balances.ts:4
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
Set: Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy. Missing: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−2.0 on this card.) — vercel.json:1
What to do
Add Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/8 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`checkCosmosTokenType` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — typescript-sdk/src/query/on-chain.ts:201
`getCosmosHeight` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — typescript-sdk/src/query/on-chain.ts:224
`getCosmosTransactionReceipt` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — typescript-sdk/src/query/on-chain.ts:244
`getCosmosAccountTransactions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — typescript-sdk/src/query/on-chain.ts:269
`getAptosAccountTransactions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — typescript-sdk/src/query/on-chain.ts:295
`try` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — sentinel2/src/check-ssl-certificates.ts:24, app2/src/lib/dashboard/helpers.ts:169
`isValidImageUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — app2/src/lib/utils/avatar.ts:4
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`logDebug` at line 104 is called with an argument built by `JSON.stringify(x)` (line 105), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — app2/src/lib/gasprice/index.ts:104
`logDebug` at line 116 is called with an argument built by `JSON.stringify(x)` (line 116), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — app2/src/lib/gasprice/index.ts:116
`logDebug` at line 175 is called with an argument built by `JSON.stringify(x)` (line 175), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — app2/src/lib/gasprice/index.ts:175
`logDebug` at line 208 is called with an argument built by `JSON.stringify(atomic)` (line 209), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — app2/src/lib/gasprice/index.ts:208
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — sentinel2/src/check-balances.ts:104
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — app2/src/lib/wallet/sui/config.svelte.ts:243
`if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — 11-cometbls/store.go:169, 11-cometbls/store.go:316
What to do
Swallowed exception (empty catch)
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.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`trace!` at line 163 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/zkgm-filter/src/main.rs:163
`info!` at line 169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/zkgm-filter/src/main.rs:169
`error!` at line 361 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:361
`error!` at line 415 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:415
`error!` at line 419 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:419
`info!` at line 1033 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1033
`info!` at line 1582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1582
`info!` at line 1590 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1590
`warn!` at line 1680 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1680
`info!` at line 1757 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1757
`error!` at line 1776 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1776
`error!` at line 1783 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1783
`info!` at line 135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/call.rs:135
`warn!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/call.rs:159
`info!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/call.rs:185
`info!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/call.rs:202
`info!` at line 239 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/call.rs:239
`info!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/callback.rs:301
`error!` at line 397 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:397
`error!` at line 495 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:495
`error!` at line 499 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:499
`warn!` at line 592 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:592
`info!` at line 665 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:665
`error!` at line 688 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:688
`error!` at line 695 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction-batch/src/lib.rs:695
`debug!` at line 173 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/gno/src/main.rs:173
`error!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/gno/src/main.rs:228
`info!` at line 393 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/gno/src/main.rs:393
`warn!` at line 398 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/gno/src/main.rs:398
`info!` at line 849 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/gno/src/main.rs:849
`error!` at line 339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/cosmos/src/main.rs:339
`error!` at line 539 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/cosmos/src/main.rs:539
`warn!` at line 557 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/cosmos/src/main.rs:557
`warn!` at line 561 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/cosmos/src/main.rs:561
`warn!` at line 602 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/transaction/cosmos/src/main.rs:602
`warn!` at line 209 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/sui-packet-timeout/src/main.rs:209
`info!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/sui-packet-timeout/src/main.rs:329
`info!` at line 353 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/sui-packet-timeout/src/main.rs:353
`info!` at line 245 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/packet-timeout/src/main.rs:245
`info!` at line 263 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — voyager/plugins/packet-timeout/src/main.rs:263
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.4 `!` null assertions per 1k TypeScript source lines — 21 assertion(s) across the 57920 source line(s) of the 475 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: sentinel2/src/escrow-supply-control-loop.ts (10), ts-sdk/src/Ucs03.ts (2), app2/src/lib/utils/effect.svelte.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; Go, JavaScript, Rust, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust, TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .go, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 65 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
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
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 a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Go code has 10,437 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — 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.
AX8 · Test isolation· Production project references a test project · ×40
Production project references a test project: arbitrum-light-client-types → ibc-union-spec — `arbitrum-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: base-light-client-types → ibc-union-spec — `base-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: base-verifier → ibc-union-spec — `base-verifier` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: berachain-light-client-types → ibc-union-spec — `berachain-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: bob-light-client-types → ibc-union-spec — `bob-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: cometbls-light-client → ibc-union-spec — `cometbls-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: cw-account → ibc-union-spec — `cw-account` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: cw-escrow-vault → ibc-union-spec — `cw-escrow-vault` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: cw-unionversal-token → ibc-union-spec — `cw-unionversal-token` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: cw20-token-minter → ibc-union-spec — `cw20-token-minter` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: gno-light-client → ibc-union-spec — `gno-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ibc-solidity → ibc-union-spec — `ibc-solidity` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ibc-union → ibc-union-spec — `ibc-union` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ibc-union-light-client → ibc-union-spec — `ibc-union-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: ibc-union-msg → ibc-union-spec — `ibc-union-msg` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: osmosis-tokenfactory-token-minter → ibc-union-spec — `osmosis-tokenfactory-token-minter` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: parlia-light-client-types → ibc-union-spec — `parlia-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: proof-lens-light-client → ibc-union-spec — `proof-lens-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: proof-lens-light-client-types → ibc-union-spec — `proof-lens-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: starknet-light-client-types → ibc-union-spec — `starknet-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: state-lens-ics23-ics23-light-client → ibc-union-spec — `state-lens-ics23-ics23-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: state-lens-ics23-ics23-light-client-types → ibc-union-spec — `state-lens-ics23-ics23-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: state-lens-ics23-mpt-light-client → ibc-union-spec — `state-lens-ics23-mpt-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: state-lens-ics23-mpt-light-client-types → ibc-union-spec — `state-lens-ics23-mpt-light-client-types` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: state-lens-ics23-smt-light-client → ibc-union-spec — `state-lens-ics23-smt-light-client` (production) references the test project `ibc-union-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
+ 15 more in this group — see findings.md.
AC2 · Forms & labels· <label> that labels no control · ×36
<label> that labels no control app2/src/lib/components/layout/AppErrors/index.svelte:19— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/layout/AppErrors/index.svelte:25— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/layout/AppErrors/index.svelte:31— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/AddressComponent.svelte:80— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/AddressComponent.svelte:84— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/AddressComponent.svelte:91— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/AddressComponent.svelte:99— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/BlockHashComponent.svelte:55— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/BlockHashComponent.svelte:60— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/BlockHashComponent.svelte:68— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/BlockHeightComponent.svelte:55— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/BlockHeightComponent.svelte:61— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/BlockHeightComponent.svelte:69— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/ChainComponent.svelte:119— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/ChainComponent.svelte:123— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/ChainComponent.svelte:127— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/ChainComponent.svelte:133— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/ChainComponent.svelte:146— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/ChainComponent.svelte:157— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/PacketComponent.svelte:53— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/PacketComponent.svelte:62— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/PacketComponent.svelte:70— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/PacketComponent.svelte:78— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/PacketComponent.svelte:82— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control app2/src/lib/components/model/PacketComponent.svelte:86— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×7
Click handler on a non-interactive <div> app2/src/lib/components/model/DustWithdrawalListItemComponent.svelte:75— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> app2/src/lib/components/model/PacketListItemComponent.svelte:36— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> app2/src/lib/components/model/StakingListItemComponent.svelte:120— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> app2/src/lib/components/model/TransferListItemComponent.svelte:36— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> app2/src/lib/components/model/WithdrawalListItemComponent.svelte:57— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> app2/src/lib/components/ui/Tooltip.svelte:266— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> app2/src/routes/eudrop/claim/step/Step2.svelte:138— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D30 · Dependency Vulnerabilities· High vulnerability · ×7
Banned license: cw-orch — `cw-orch` 0.27.0 is published on crates.io under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
Banned license: cw-orch-contract-derive — `cw-orch-contract-derive` 0.21.1 is published on crates.io under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
Banned license: cw-orch-core — `cw-orch-core` 2.1.4 is published on crates.io under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
Banned license: cw-orch-fns-derive — `cw-orch-fns-derive` 0.23.1 is published on crates.io under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
Banned license: cw-orch-mock — `cw-orch-mock` 0.24.4 is published on crates.io under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
Banned license: cw-orch-traits — `cw-orch-traits` 0.25.0 is published on crates.io under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
Boundary-crossing change coupling: client_state.rs ↔ REDACTED lib/state-lens-ics23-mpt-light-client-types/src/client_state.rs:1— `lib/state-lens-ics23-mpt-light-client-types/src/client_state.rs` (context state-lens-ics23-mpt-light-client-types) and `voyager/modules/client/state-lens/ics23-mpt/src/main.rs` (context voyager) sit in DIFFERENT parts of the tree yet change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `5cc9050c` feat: state lens client migration and some fixes; `3cdc4990` feat(state-lens): use new client state encodings; `ded7880c` fix(state-lens): state lens client state encoding fixes & docs — run `git show` on any of them.
Boundary-crossing change coupling: client_state.rs ↔ REDACTED lib/state-lens-ics23-ics23-light-client-types/src/client_state.rs:1— `lib/state-lens-ics23-ics23-light-client-types/src/client_state.rs` (context state-lens-ics23-ics23-light-client-types) and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` (context voyager) sit in DIFFERENT parts of the tree yet 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, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `9c6d07e7` feat(cosmwasm): state-lens/ics23/ics23 client; `5cc9050c` feat: state lens client migration and some fixes; `3cdc4990` feat(state-lens): use new client state encodings — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ REDACTED lib/arbitrum-verifier/src/lib.rs:1— `lib/arbitrum-verifier/src/lib.rs` (context arbitrum-verifier) and `voyager/plugins/client-update/arbitrum/src/main.rs` (context voyager) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7930c918` feat: arb v2; `bd1cfda5` chore: clean up; `a0184eba` fix(arbitrum,voyager): verify _latestNodeCreated instead of _latestNo… — run `git show` on any of them.
Boundary-crossing change coupling: client_state.rs ↔ REDACTED lib/state-lens-ics23-mpt-light-client-types/src/client_state.rs:1— `lib/state-lens-ics23-mpt-light-client-types/src/client_state.rs` (context state-lens-ics23-mpt-light-client-types) and `voyager/plugins/client-update/state-lens/src/main.rs` (context voyager) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `ddcb0f13` feat(lightclients): use new client state type in state lens light cli…; `d14a5815` refactor(lightclients): consistent naming for state lens clients (at that commit the file was still `voyager/plugins/client-update/state-lens/evm/src/main.rs`); `da8b8e1e` feat(voyager): state lens bootstrap and more (at that commit the files were still `lib/state-lens/evm-light-client-types/src/client_state.rs` and `voyager/plugins/client-update/state-lens/evm/src/main.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: server.rs ↔ REDACTED lib/voyager-core/src/server.rs:1— `lib/voyager-core/src/server.rs` (context voyager-core) and `voyager/modules/client/ethereum/src/main.rs` (context voyager) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c1e3e0a0` feat(voyager): expose more codec functionality over jsonrpc; `8ad8ce3c` fix(voyager): queue packets behind correct update wait logic (at that commit the file was still `lib/voyager-message/src/rpc/server.rs`); `2a2f6906` feat(voyager): more things (at that commit the file was still `lib/voyager-message/src/rpc/server.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: call.rs ↔ REDACTED lib/voyager-message/src/call.rs:1— `lib/voyager-message/src/call.rs` (context voyager-message) and `voyager/modules/client/ethereum/src/main.rs` (context voyager) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `8ad8ce3c` fix(voyager): queue packets behind correct update wait logic; `2a2f6906` feat(voyager): more things; `7ae9655b` feat(voyager): replace u64 timestamp with Timestamp type across modules — run `git show` on any of them.
Orphaned knowledge ts-sdk/src/Ucs03.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/ssz/src/types/bitfield.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge lib/gnark-key-parser/src/bn254.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge sentinel2/src/escrow-supply-control-loop.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge typescript-sdk/src/abi/ucs-01.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC3 · Page structure· Document without a <title> · ×4
Document without a <title> app2/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> effect-svelte/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> site/src/layouts/BaseLayout.astro:47— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> zkgm-dev/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC2 · Forms & labels· <button> with no accessible text · ×3
<button> with no accessible text app2/src/lib/components/model/ErrorComponent.svelte:198— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text app2/src/lib/components/model/ErrorComponent.svelte:218— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text app2/src/lib/components/model/ErrorComponent.svelte:243— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×3
Hover-only interaction on <div> app2/src/lib/components/model/BarChart.svelte:103— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Hover-only interaction on <div> app2/src/lib/components/ui/Tooltip.svelte:254— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Hover-only interaction on <div> app2/src/routes/yaps/YappersHero.svelte:83— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Import cycle (3 files) ts-sdk/src/Batch.ts:13— ts-sdk/src/Batch.ts → ts-sdk/src/TokenOrder.ts → ts-sdk/src/index.ts → ts-sdk/src/Batch.ts (one verified cycle inside a mutually-dependent group of 6 files)
Import cycle (3 files) REDACTED:4— REDACTED → typescript-sdk/src/pfm.ts → typescript-sdk/src/mod.ts → REDACTED (one verified cycle inside a mutually-dependent group of 6 files)
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative site/src/components/Header.astro:65— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label app2/src/lib/components/AddressInput.svelte:140— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> app2/src/lib/components/ui/Switch.svelte:79— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AX9 · CQS / query purity· Query writes persistent state on the read path · ×1
Query writes persistent state on the read path: evm_storage_verifier$module.get_node lib/evm-storage-verifier/src/lib.rs:132— `evm_storage_verifier$module.get_node` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
TodoComment voyager/src/config.rs:38— // TODO: Specify per plugin — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/src/main.rs:5— // TODO: Make this workspace-wide — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/src/main.rs:327— // todo!(); — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/src/main.rs:788— // // TODO: Extract all logic here to a plugin — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/src/main.rs:815— // TODO: Also check if a specific height was passed and ensure that that height is also finalized — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch-proof-lens/src/lib.rs:291— // // TODO: Make this a better error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/lib.rs:319— // // TODO: Make this a better error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch-proof-lens/src/lib.rs:393— // TODO: Handle this more gracefully — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/lib.rs:430— // TODO: Handle this more gracefully — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/lib.rs:460— // TODO: Handle this more gracefully — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1478— // TODO: We can probably relax this in the future if we want to reuse this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/call.rs:112— // TODO: Check the same for exact heights? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/call.rs:791— // TODO: Make configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/call.rs:795— // TODO: Make configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/callback.rs:266— // TODO: We may need to sort packet messages when we support ordered channels — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/callback.rs:362— // TODO: We can probably relax this in the future if we want to reuse this module to work with all IBC messages — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction-batch/src/data.rs:31— // TODO: Add a "now" constructor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/sui/src/lib.rs:72— // TODO: change it later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/sui/src/main.rs:274— // TODO(aeryz): Regular recv_packet here. Note that this is not used by us, therefore I don't want to rush — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/sui/src/main.rs:311— // TODO(aeryz): Regular ack_packet here. Note that this is not used by us, therefore I don't want to rush — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/sui/src/main.rs:348— // TODO(aeryz): Regular timeout_packet here. Note that this is not used by us, therefore I don't want to rush — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/sui/src/main.rs:360— // TODO(aeryz): this is messing with the tx order, instead merge on each loop — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/sui/src/main.rs:368— // TODO(aeryz): we can also choose to include store_name here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/gno/src/main.rs:143— // TODO: Currently duplicated between here and the ethereum tx plugin, deduplicate — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment voyager/plugins/transaction/cosmos/src/main.rs:249— // TODO: Currently duplicated between here and the ethereum tx plugin, deduplicate — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
+ 369 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×56
FunctionTooLong: cosmwasm_deployer::do_main cosmwasm/deployer/src/main.rs:566— FunctionTooLong — cosmwasm_deployer::do_main runs 652 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 552 over it, 6.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: voyager::do_main voyager/src/main.rs:88— FunctionTooLong — voyager::do_main runs 514 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 414 over it, 5.14× 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: fee.svelte.createFeeStore app2/src/lib/stores/fee.svelte.ts:63— FunctionTooLong — createFeeStore runs 445 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 345 over it, 4.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ibc_union::contract::execute cosmwasm/core/src/contract.rs:68— FunctionTooLong — ibc_union::contract::execute runs 384 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 284 over it, 3.84× 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: matrix-cover.initWebGL site/src/lib/matrix-cover.ts:169— FunctionTooLong — initWebGL runs 366 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 266 over it, 3.66× 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: voyager_transaction_plugin_gno::process_msgs voyager/plugins/transaction/gno/src/main.rs:469— FunctionTooLong — voyager_transaction_plugin_gno::process_msgs runs 292 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 192 over it, 2.92× 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: move_bindgen::main tools/move-bindgen/src/main.rs:22— FunctionTooLong — move_bindgen::main runs 242 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 142 over it, 2.42× 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: cosmwasm_deployer::deploy_full cosmwasm/deployer/src/main.rs:1451— FunctionTooLong — cosmwasm_deployer::deploy_full runs 225 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 125 over it, 2.25× 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: v1_2_0.CreateUpgradeHandler uniond/app/upgrades/v1_2_0/upgrade.go:55— FunctionTooLong — CreateUpgradeHandler runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ucs03_zkgm::contract::execute cosmwasm/app/ucs03-zkgm/src/contract.rs:125— FunctionTooLong — ucs03_zkgm::contract::execute runs 191 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: voyager_transaction_plugin_aptos::process_msgs voyager/plugins/transaction/aptos/src/main.rs:286— FunctionTooLong — voyager_transaction_plugin_aptos::process_msgs runs 175 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 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: client.createEvmClient typescript-sdk/src/evm/client.ts:68— FunctionTooLong — createEvmClient runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× 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: cosmwasm_deployer::setup_roles cosmwasm/deployer/src/main.rs:1779— FunctionTooLong — cosmwasm_deployer::setup_roles runs 162 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 62 over it, 1.62× 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: ucs03_zkgm::contract::reply cosmwasm/app/ucs03-zkgm/src/contract.rs:2491— FunctionTooLong — ucs03_zkgm::contract::reply runs 161 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: voyager_transaction_plugin_evm::process_msgs voyager/plugins/transaction/evm/src/main.rs:616— FunctionTooLong — voyager_transaction_plugin_evm::process_msgs runs 157 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 57 over it, 1.57× 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: cmd.ExampleVerifyCmd galoisd/cmd/galoisd/cmd/example_verify.go:31— FunctionTooLong — ExampleVerifyCmd runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ucs03_zkgm::contract::execute_token_order_v1 cosmwasm/app/ucs03-zkgm/src/contract.rs:1919— FunctionTooLong — ucs03_zkgm::contract::execute_token_order_v1 runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: cw20_token_minter::contract::execute cosmwasm/cw20-token-minter/src/contract.rs:87— FunctionTooLong — cw20_token_minter::contract::execute runs 151 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 51 over it, 1.51× 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: voyager_transaction_plugin_cosmos::process_msgs voyager/plugins/transaction/cosmos/src/main.rs:654— FunctionTooLong — voyager_transaction_plugin_cosmos::process_msgs runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: zkgmClient.fromWallet ts-sdk-evm/src/internal/zkgmClient.ts:27— FunctionTooLong — fromWallet runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: client.createCosmosClient REDACTED:49— FunctionTooLong — createCosmosClient runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ucs03_zkgm::contract::execute_token_order_v2 cosmwasm/app/ucs03-zkgm/src/contract.rs:2133— FunctionTooLong — ucs03_zkgm::contract::execute_token_order_v2 runs 137 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 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: mpc_coordinator::main mpc/coordinator/src/main.rs:66— FunctionTooLong — mpc_coordinator::main runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: cw_unionversal_token::contract::execute cosmwasm/cw-unionversal-token/src/contract.rs:110— FunctionTooLong — cw_unionversal_token::contract::execute runs 133 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 33 over it, 1.33× 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: ibc_union_light_client::query cosmwasm/core/light-client-interface/src/lib.rs:593— FunctionTooLong — ibc_union_light_client::query 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.
+ 16 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file app2/src/lib/dashboard/database.types.ts:1— 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 typescript-sdk/src/abi/ucs-01.ts:1— 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 app2/src/lib/stores/fee.svelte.ts:1— 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 ts-sdk-cosmos/src/Cosmos.ts:1— 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 ts-sdk-sui/src/Sui.ts:1— 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 ts-sdk-evm/src/internal/zkgmClient.ts:1— 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 sentinel2/src/escrow-supply-control-loop.ts:1— 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 ts-sdk-evm/src/Evm.ts:1— 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 app2/src/lib/dashboard/stores/user.svelte.ts:1— 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 app2/src/lib/config/wallets/info.ts:1— 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 app2/src/lib/components/stake/BondComponent.svelte:1— 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 app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:1— 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 REDACTED:1— 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 app2/src/lib/dashboard/queries/private.ts:1— 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 app2/src/lib/components/stake/StatusDisplay.svelte:1— 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 app2/src/lib/components/stake/UnbondComponent.svelte:1— 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 typescript-sdk/src/query/on-chain.ts:1— 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 app2/src/routes/explorer/orbital/audio.ts:1— 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 app2/src/lib/dashboard/queries/public.ts:1— 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 app2/src/lib/wallet/evm/wagmi-config.svelte.ts:1— 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 typescript-sdk/src/cosmos/transfer.ts:1— 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 ts-sdk-sui/src/internal/zkgmClient.ts:1— 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 app2/src/lib/components/stake/WithdrawalComponent.svelte:1— 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 app2/src/lib/components/stake/QuickWithdrawComponent.svelte:1— 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 app2/src/lib/transfer/normal/steps/ApprovalStep.svelte:1— 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.
FileTooLong: dashboard/database.types.ts app2/src/lib/dashboard/database.types.ts— FileTooLong — 2615 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: Database (9-3010). The bar is 500 significant lines; this is 2115 over it, 5.23× 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/contract.rs cosmwasm/app/ucs03-zkgm/src/contract.rs— FileTooLong — 2575 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 65 free functions. The bar is 500 significant lines; this is 2075 over it, 5.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED cosmwasm/deployer/src/main.rs— FileTooLong — 1902 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 1402 over it, 3.80× 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/contract.rs cosmwasm/core/src/contract.rs— FileTooLong — 1756 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 51 free functions. The bar is 500 significant lines; this is 1256 over it, 3.51× 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: REDACTED voyager/plugins/transaction-batch-proof-lens/src/lib.rs— FileTooLong — 1318 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: Module (8 blocks, 75-1932). The bar is 500 significant lines; this is 818 over it, 2.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/Ucs03.ts ts-sdk/src/Ucs03.ts— FileTooLong — 1223 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 723 over it, 2.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED voyager/plugins/event-source/cosmwasm/src/main.rs— FileTooLong — 1032 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: Module (5 blocks, 64-1428). The bar is 500 significant lines; this is 532 over it, 2.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED lib/voyager-core/src/lib.rs— FileTooLong — 1015 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 515 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: REDACTED tools/union-test/src/lib.rs— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 61% of them inside a single declaration: TestContext (2 blocks, 471-1213). The bar is 500 significant lines; this is 435 over it, 1.87× 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 voyager/plugins/event-source/evm/src/main.rs— FileTooLong — 932 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: Module (5 blocks, 59-1345). The bar is 500 significant lines; this is 432 over it, 1.86× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/server.rs lib/voyager-core/src/server.rs— FileTooLong — 899 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 96% of them inside a single declaration: Server (4 blocks, 32-1224). The bar is 500 significant lines; this is 399 over it, 1.80× 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/evm.rs tools/union-test/src/evm.rs— FileTooLong — 874 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 75% of them inside a single declaration: Module (2 blocks, 36-966). The bar is 500 significant lines; this is 374 over it, 1.75× 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 voyager/plugins/event-source/gno/src/lib.rs— FileTooLong — 827 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: Module (5 blocks, 50-1301). The bar is 500 significant lines; this is 327 over it, 1.65× 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 lib/macros/src/lib.rs— FileTooLong — 781 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 281 over it, 1.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED voyager/plugins/event-source/sui/src/main.rs— FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: Module (4 blocks, 63-1027). The bar is 500 significant lines; this is 272 over it, 1.54× 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 — 720 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: PgQueue (3 blocks, 44-759). The bar is 500 significant lines; this is 220 over it, 1.44× 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 voyager/plugins/client-update/arbitrum/src/main.rs— FileTooLong — 700 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: Module (5 blocks, 50-959). The bar is 500 significant lines; this is 200 over it, 1.40× 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 voyager/src/main.rs— FileTooLong — 693 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 193 over it, 1.39× 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/cosmos.rs tools/union-test/src/cosmos.rs— FileTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: Module (2 blocks, 71-802). The bar is 500 significant lines; this is 187 over it, 1.37× 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/contract.rs cosmwasm/access-manager/src/contract.rs— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 48 free functions. The bar is 500 significant lines; this is 176 over it, 1.35× 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/zkgm.rs voyager/plugins/sui-ibc-app/src/zkgm.rs— FileTooLong — 652 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 152 over it, 1.30× 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: REDACTED voyager/modules/state/cosmwasm/src/main.rs— FileTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: Module (4 blocks, 51-799). The bar is 500 significant lines; this is 140 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED voyager/modules/state/evm/src/main.rs— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: Module (4 blocks, 48-860). The bar is 500 significant lines; this is 132 over it, 1.26× 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/call.rs voyager/plugins/transaction-batch/src/call.rs— FileTooLong — 629 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 129 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED voyager/plugins/transaction/cosmos/src/main.rs— FileTooLong — 608 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 108 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
MethodTooLong: Module.make_chain_event voyager/plugins/event-source/cosmwasm/src/main.rs:589— MethodTooLong — make_chain_event runs 638 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 538 over it, 6.38× 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: Module.make_full_event voyager/plugins/event-source/evm/src/main.rs:546— MethodTooLong — make_full_event runs 553 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 453 over it, 5.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Module.make_chain_event voyager/plugins/event-source/gno/src/lib.rs:446— MethodTooLong — make_chain_event runs 545 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 445 over it, 5.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Module.call voyager/plugins/event-source/sui/src/main.rs:457— MethodTooLong — call runs 441 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 341 over it, 4.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Module.call voyager/plugins/event-source/movement/src/main.rs:284— MethodTooLong — call runs 385 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 285 over it, 3.85× 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: MakeMsg.call voyager/plugins/transaction-batch/src/call.rs:294— MethodTooLong — call runs 318 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 218 over it, 3.18× 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: EngineBuilder.build lib/voyager-core/src/lib.rs:397— MethodTooLong — build runs 258 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 158 over it, 2.58× 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: Handler.call lib/voyager-core/src/lib.rs:791— MethodTooLong — call runs 225 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 125 over it, 2.25× 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: Module.fetch_l2_update voyager/plugins/client-update/arbitrum/src/main.rs:682— MethodTooLong — fetch_l2_update runs 214 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 114 over it, 2.14× 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: Module.call voyager/plugins/client-update/cometbls/src/main.rs:327— MethodTooLong — call runs 206 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 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Cmd.run tools/u/src/vanity/wrapped_token.rs:88— MethodTooLong — run runs 181 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 81 over it, 1.81× 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: Module.call voyager/plugins/packet-timeout/src/main.rs:155— MethodTooLong — call runs 177 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 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Module.fetch_update voyager/plugins/client-update/ethereum/src/main.rs:302— MethodTooLong — fetch_update runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Selector.extract_from_serialize lib/access-manager-types/src/lib.rs:278— MethodTooLong — extract_from_serialize runs 172 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 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Cmd.run tools/u/src/vanity/create3.rs:38— MethodTooLong — run runs 167 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 67 over it, 1.67× 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: Module.make_packet_event voyager/plugins/packet-index/src/main.rs:106— MethodTooLong — make_packet_event runs 167 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 67 over it, 1.67× 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: MakeTransactionBatchesWithUpdate.call voyager/plugins/transaction-batch/src/call.rs:55— MethodTooLong — call runs 154 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 54 over it, 1.54× 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: Module.fetch_update voyager/plugins/client-update/arbitrum/src/main.rs:459— MethodTooLong — fetch_update runs 152 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 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PgQueue.optimize REDACTED:567— MethodTooLong — optimize runs 146 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Module.fetch_l2_update voyager/plugins/client-update/bob/src/main.rs:489— MethodTooLong — fetch_l2_update runs 143 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 43 over it, 1.43× 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: Module.submit_transaction voyager/plugins/transaction/evm/src/main.rs:415— MethodTooLong — submit_transaction runs 141 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Module.fetch_update voyager/plugins/client-update/parlia/src/main.rs:226— MethodTooLong — fetch_update runs 139 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 39 over it, 1.39× 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: Module.process_msgs voyager/plugins/transaction/sui/src/main.rs:183— MethodTooLong — process_msgs 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.
MethodTooLong: Module.fetch_block voyager/plugins/event-source/cosmwasm/src/main.rs:393— MethodTooLong — fetch_block 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: proverServerBls12381.Poll galoisd/grpc/bls12381_server.go:99— MethodTooLong — Poll runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
XxxComment ts-sdk-sui/src/Sui.ts:354— /// XXX: pred cannot be curried for some reason or type inference breaks — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk-sui/src/internal/zkgmClient.ts:96— // XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk-cosmos/src/Cosmos.ts:497— // XXX — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/PriceOracle.ts:254— // XXX: reduce cache (?) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/Token.ts:151— // XXX: address incorrect semantically — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/TokenOrder.ts:203— // XXX: remove assertions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/Ucs03.ts:1359— // XXX: can only be `Call` or `TokenOrder` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/Ucs03.ts:1438— // XXX: call this `Root` and drop `Instruction` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/Ucs03.ts:1579— // XXX: narrow to exclude instruction — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/Ucs03.ts:1817— // XXX: choose decode given explicit opcode / version — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/Ucs05.ts:328— // XXX: THIS IS WRONG — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/ZkgmClientRequest.ts:101— // XXX: narrow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/ZkgmClientRequest.ts:116— // XXX: narrow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/schema/chain.ts:141— // XXX: don't mask error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/schema/fee.ts:64— // XXX: wrong — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/internal/tokenOrder.ts:151— // XXX: remove assertion — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/internal/tokenOrder.ts:156— // XXX: remove assertion — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment ts-sdk/src/internal/tokenOrder.ts:443— // XXX: remove in favor of pattern matching — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment effect-svelte/src/lib/SvelteConfigProvider.ts:23— // XXX: unsafe globalThis — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment app2/src/lib/runtime.ts:22— // XXX: ^ remove cast after handling layer construction errors — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment app2/src/lib/utils/index.ts:20— // XXX: remove in favor of schema validation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment app2/src/lib/transfer/shared/services/handlers/safe-hash.ts:4— // XXX: shouldn't be scheduled forever and shouldn't coerce to untagged error or die — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment app2/src/lib/transfer/shared/services/filling/check-allowance.ts:94— // XXX: make Address type more specific — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment app2/src/lib/transfer/shared/services/filling/check-allowance.ts:207— // XXX: less-bad-than-before type assertions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment app2/src/lib/transfer/shared/services/filling/check-balance.ts:63— // XXX: remove type coercion — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Off the main sequence: gnark-key-parser — gnark-key-parser: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: reconnecting-jsonrpc-ws-client — reconnecting-jsonrpc-ws-client: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: serde-utils — serde-utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 37 project(s), so it's rigid to change.
Off the main sequence: starknet-types — starknet-types: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: sui-utils — sui-utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: token-factory-api — token-factory-api: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: ucs04 — ucs04: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @unionlabs/sdk — @unionlabs/sdk: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: evm-storage-verifier — evm-storage-verifier: abstractness 0.00, instability 0.09, distance 0.91 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Off the main sequence: aptos-types — aptos-types: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: ethereum-light-client-types — ethereum-light-client-types: abstractness 0.00, instability 0.12, distance 0.88 — zone of pain — concrete and depended on by 30 project(s), so it's rigid to change.
Off the main sequence: unionlabs — unionlabs: abstractness 0.10, instability 0.03, distance 0.88 — zone of pain — concrete and depended on by 181 project(s), so it's rigid to change.
Off the main sequence: tendermint-light-client-types — tendermint-light-client-types: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: cometbft-types — cometbft-types: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Off the main sequence: cometbft-rpc — cometbft-rpc: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
Off the main sequence: beacon-api-types — beacon-api-types: abstractness 0.00, instability 0.19, distance 0.81 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: gno-verifier — gno-verifier: abstractness 1.00, instability 0.80, distance 0.80 — zone of uselessness — abstract and unstable, so it's likely unused.
Off the main sequence: voyager-plugin — voyager-plugin: abstractness 1.00, instability 0.80, distance 0.80 — zone of uselessness — abstract and unstable, so it's likely unused.
Off the main sequence: sui-light-client-types — sui-light-client-types: abstractness 0.00, instability 0.22, distance 0.78 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: ibc-union-msg — ibc-union-msg: abstractness 0.00, instability 0.24, distance 0.76 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: gno-light-client-types — gno-light-client-types: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: parlia-light-client-types — parlia-light-client-types: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: ucs03-solvable — ucs03-solvable: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: ucs03-zkgm-token-minter-api — ucs03-zkgm-token-minter-api: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: ucs03-zkgmable — ucs03-zkgmable: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
+ 4 more in this group — see findings.md.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×27
Animation without a prefers-reduced-motion guard app2/src/lib/components/stake/BondComponent.svelte:711— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/components/stake/ProxyDustRecovery.svelte:408— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/components/stake/QuickWithdrawComponent.svelte:503— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/components/stake/StatusDisplay.svelte— <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/components/stake/UnbondComponent.svelte:608— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/components/stake/WithdrawalComponent.svelte:514— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/dashboard/components/NewUser.svelte:53— <spinnericon> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/dashboard/components/SideCard.svelte:58— <spinnericon> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte:458— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/auth/+page.svelte:153— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/auth/sign-in/+page.svelte:94— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/btcfi/step/Step1.svelte:207— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/btcfi/step/Step3.svelte:309— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/dashboard/rewards/+page.svelte— <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step1.svelte:105— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step1.svelte:238— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step3.svelte:55— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step3.svelte:156— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step4.svelte:159— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step4.svelte:278— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step5.svelte:284— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step5.svelte:301— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/eudrop/claim/step/Step5.svelte:402— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/liquid-staking/step/LiquidStakingStep1.svelte:58— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard app2/src/routes/liquid-staking/step/LiquidStakingStep2.svelte:95— <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Duplicated block (8 lines × 2) cosmwasm/cw20-token-minter/src/contract.rs:309— cosmwasm/cw20-token-minter/src/contract.rs:309-316 | cosmwasm/cw20-token-minter/src/contract.rs:331-338 — both copies are in the same file, so extract the block into 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) cosmwasm/cw20-token-minter/src/contract.rs:364— cosmwasm/cw20-token-minter/src/contract.rs:364-371 | cosmwasm/osmosis-tokenfactory-token-minter/src/contract.rs:362-369 — 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) cosmwasm/lightclient/starknet/src/client.rs:40— cosmwasm/lightclient/starknet/src/client.rs:40-47 | cosmwasm/lightclient/starknet/src/client.rs:68-75 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/cometbft-rpc/src/lib.rs:50— lib/cometbft-rpc/src/lib.rs:50-57 | lib/gno-rpc/src/lib.rs:46-53 — before extracting anything, compare `lib/cometbft-rpc/src/lib.rs` and `lib/gno-rpc/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/cometbft-rpc/src/rpc_types.rs:167— lib/cometbft-rpc/src/rpc_types.rs:167-174 | lib/gno-rpc/src/rpc_types.rs:128-135 — 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) lib/move-bindgen-derive/src/lib.rs:60— lib/move-bindgen-derive/src/lib.rs:60-67 | lib/move-bindgen-derive/src/lib.rs:79-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) voyager/modules/client/gno/src/main.rs:194— voyager/modules/client/gno/src/main.rs:194-201 | voyager/modules/client/tendermint/src/main.rs:194-201 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/proof-lens/src/main.rs:188— voyager/modules/client/proof-lens/src/main.rs:188-195 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:191-198 — before extracting anything, compare `voyager/modules/client/proof-lens/src/main.rs` and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/finality/base/src/main.rs:150— voyager/modules/finality/base/src/main.rs:150-157 | voyager/modules/finality/bob/src/main.rs:150-157 — before extracting anything, compare `voyager/modules/finality/base/src/main.rs` and `voyager/modules/finality/bob/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (8 lines × 2) voyager/modules/state/cosmwasm/src/main.rs:139— voyager/modules/state/cosmwasm/src/main.rs:139-146 | voyager/modules/state/cosmwasm/src/main.rs:278-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) voyager/plugins/client-update/proof-lens/src/main.rs:258— voyager/plugins/client-update/proof-lens/src/main.rs:258-265 | voyager/plugins/client-update/state-lens/src/main.rs:268-275 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1016— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1016-1023 | voyager/plugins/transaction-batch/src/call.rs:101-108 — 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) cosmwasm/cw20-base/src/allowances.rs:250— cosmwasm/cw20-base/src/allowances.rs:250-257 | cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:261-268 — before extracting anything, compare `cosmwasm/cw20-base/src/allowances.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/gno-verifier/src/merkle.rs:39— lib/gno-verifier/src/merkle.rs:39-46 | lib/tendermint-verifier/src/merkle.rs:39-46 — 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) voyager/modules/client/attested/src/main.rs:68— voyager/modules/client/attested/src/main.rs:68-75 | voyager/modules/client/trusted-mpt/src/main.rs:70-77 — 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) voyager/modules/client/gno/src/main.rs:85— voyager/modules/client/gno/src/main.rs:85-92 | voyager/modules/client/tendermint/src/main.rs:85-92 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/gno/src/main.rs:109— voyager/modules/client/gno/src/main.rs:109-116 | voyager/modules/client/tendermint/src/main.rs:109-116 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/proof-lens/src/main.rs:89— voyager/modules/client/proof-lens/src/main.rs:89-96 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:92-99 — before extracting anything, compare `voyager/modules/client/proof-lens/src/main.rs` and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:169— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:169-176 | voyager/plugins/transaction-batch/src/lib.rs:162-169 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/unionlabs-primitives/src/uint.rs:168— lib/unionlabs-primitives/src/uint.rs:168-175 | lib/unionlabs/src/ibc/core/client/height.rs:271-279 — 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) mpc/client/src/ui.rs:101— mpc/client/src/ui.rs:101-108 | mpc/client/src/ui.rs:146-153 — both copies are in the same file, so extract the block into 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) 11-cometbls/zk_verifier.go:205— 11-cometbls/zk_verifier.go:205-212 | galoisd/grpc/server.go:211-218 — 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) galoisd/cmd/galoisd/cmd/phase1_init.go:148— galoisd/cmd/galoisd/cmd/phase1_init.go:148-155 | galoisd/cmd/galoisd/cmd/phase1_init.go:661-668 — both copies are in the same file, so extract the 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 `galoisd/cmd/galoisd/cmd/phase1_init.go:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) galoisd/pkg/emulated/g2.go:148— galoisd/pkg/emulated/g2.go:148-155 | galoisd/pkg/emulated/g2.go:167-174 — both copies are in the same file, so extract the block into 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) galoisd/cmd/galoisd/cmd/phase2_extract.go:13— galoisd/cmd/galoisd/cmd/phase2_extract.go:13-20 | galoisd/cmd/galoisd/cmd/phase2_init.go:11-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/cmd/galoisd/cmd/phase2_extract.go:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:483— cosmwasm/app/ucs03-zkgm/src/contract.rs:483-495 | cosmwasm/app/ucs03-zkgm/src/contract.rs:520-532 — both copies are in the same file, so extract the block into 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) cosmwasm/deployer/src/main.rs:1065— cosmwasm/deployer/src/main.rs:1065-1077 | cosmwasm/deployer/src/main.rs:1092-1104 — both copies are in the same file, so extract the block into 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) cosmwasm/lightclient/parlia/src/client.rs:45— cosmwasm/lightclient/parlia/src/client.rs:45-57 | cosmwasm/lightclient/parlia/src/client.rs:80-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) cosmwasm/lightclient/proof-lens/src/client.rs:43— cosmwasm/lightclient/proof-lens/src/client.rs:43-55 | cosmwasm/lightclient/proof-lens/src/client.rs:75-87 — both copies are in the same file, so extract the block into 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) cosmwasm/lightclient/state-lens-ics23-ics23/src/client.rs:140— cosmwasm/lightclient/state-lens-ics23-ics23/src/client.rs:140-152 | cosmwasm/lightclient/state-lens-ics23-smt/src/client.rs:111-123 — 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) lib/base-client/src/lib.rs:35— lib/base-client/src/lib.rs:35-47 | lib/bob-client/src/lib.rs:35-47 — before extracting anything, compare `lib/base-client/src/lib.rs` and `lib/bob-client/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/cometbft-types/src/types/validator_set.rs:44— lib/cometbft-types/src/types/validator_set.rs:44-56 | lib/cometbft-types/src/types/validator_set.rs:73-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/ics23/src/ibc_api.rs:44— lib/ics23/src/ibc_api.rs:44-56 | lib/ics23/src/ibc_api.rs:80-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/starknet-types/src/lib.rs:149— lib/starknet-types/src/lib.rs:149-161 | lib/unionlabs-primitives/src/uint.rs:105-117 — before extracting anything, compare `lib/starknet-types/src/lib.rs` and `lib/unionlabs-primitives/src/uint.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 (13 lines × 2) tools/union-test/src/lib.rs:835— tools/union-test/src/lib.rs:835-847 | tools/union-test/src/lib.rs:879-891 — both copies are in the same file, so extract the block into 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) voyager/modules/proof/evm-mpt/src/main.rs:58— voyager/modules/proof/evm-mpt/src/main.rs:58-70 | voyager/modules/proof/parlia/src/main.rs:56-68 — before extracting anything, compare `voyager/modules/proof/evm-mpt/src/main.rs` and `voyager/modules/proof/parlia/src/main.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 (13 lines × 2) voyager/modules/proof/movement/src/main.rs:59— voyager/modules/proof/movement/src/main.rs:59-71 | voyager/modules/state/movement/src/main.rs:65-77 — before extracting anything, compare `voyager/modules/proof/movement/src/main.rs` and `voyager/modules/state/movement/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) voyager/plugins/attestor/evm/src/main.rs:156— voyager/plugins/attestor/evm/src/main.rs:156-168 | voyager/plugins/transaction/cosmos/src/main.rs:141-153 — before extracting anything, compare `voyager/plugins/attestor/evm/src/main.rs` and `voyager/plugins/transaction/cosmos/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) voyager/plugins/attestor/evm/src/main.rs:207— voyager/plugins/attestor/evm/src/main.rs:207-219 | voyager/plugins/transaction/cosmos/src/main.rs:188-200 — before extracting anything, compare `voyager/plugins/attestor/evm/src/main.rs` and `voyager/plugins/transaction/cosmos/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) voyager/plugins/client-update/attested/src/main.rs:117— voyager/plugins/client-update/attested/src/main.rs:117-129 | voyager/plugins/client-update/movement/src/main.rs:200-212 — 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) voyager/plugins/client-update/proof-lens/src/main.rs:124— voyager/plugins/client-update/proof-lens/src/main.rs:124-136 | voyager/plugins/client-update/state-lens/src/main.rs:134-146 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:1024— voyager/plugins/event-source/cosmwasm/src/main.rs:1024-1036 | voyager/plugins/event-source/gno/src/lib.rs:870-882 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) voyager/plugins/event-source/evm/src/main.rs:783— voyager/plugins/event-source/evm/src/main.rs:783-795 | voyager/plugins/event-source/sui/src/main.rs:378-390 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/unionlabs/src/cosmwasm/wasm/msg_execute_contract/response.rs:18— lib/unionlabs/src/cosmwasm/wasm/msg_execute_contract/response.rs:18-30 | lib/unionlabs/src/cosmwasm/wasm/msg_migrate_contract/response.rs:18-30 — 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) lib/voyager-plugin-protocol/src/lib.rs:233— lib/voyager-plugin-protocol/src/lib.rs:233-245 | lib/voyager-plugin-protocol/src/lib.rs:253-265 — both copies are in the same file, so extract the block into 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) 11-cometbls/zk_verifier.go:162— 11-cometbls/zk_verifier.go:162-174 | galoisd/grpc/bls12381_server.go:67-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 (13 lines × 2) lib/ibc-union-spec/src/datagram.rs:72— lib/ibc-union-spec/src/datagram.rs:72-84 | lib/ibc-union-spec/src/event.rs:74-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:1746— cosmwasm/app/ucs03-zkgm/src/contract.rs:1746-1754 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1818-1826 — both copies are in the same file, so extract the block into 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) cosmwasm/deployer/src/main.rs:1596— cosmwasm/deployer/src/main.rs:1596-1604 | cosmwasm/deployer/src/main.rs:1710-1718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/cosmos-client/src/lib.rs:146— lib/cosmos-client/src/lib.rs:146-154 | lib/cosmos-client/src/lib.rs:249-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 (9 lines × 2) REDACTED:682— REDACTED:682-690 | REDACTED:713-721 — both copies are in the same file, so extract the block into 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) tools/union-test/src/evm.rs:572— tools/union-test/src/evm.rs:572-580 | tools/union-test/src/evm.rs:606-614 — both copies are in the same file, so extract the block into 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) voyager/modules/proof/cosmwasm/src/main.rs:56— voyager/modules/proof/cosmwasm/src/main.rs:56-64 | voyager/modules/proof/ethermint/src/main.rs:58-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 (9 lines × 2) voyager/modules/proof/evm-mpt/src/main.rs:98— voyager/modules/proof/evm-mpt/src/main.rs:98-106 | voyager/modules/proof/parlia/src/main.rs:96-104 — before extracting anything, compare `voyager/modules/proof/evm-mpt/src/main.rs` and `voyager/modules/proof/parlia/src/main.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 (9 lines × 2) voyager/modules/state/evm/src/main.rs:180— voyager/modules/state/evm/src/main.rs:180-188 | voyager/modules/state/evm/src/main.rs:210-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) voyager/modules/state/movement/src/main.rs:352— voyager/modules/state/movement/src/main.rs:352-360 | voyager/modules/state/sui/src/main.rs:428-436 — 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) voyager/plugins/event-source/evm/src/main.rs:588— voyager/plugins/event-source/evm/src/main.rs:588-596 | voyager/plugins/event-source/sui/src/main.rs:632-640 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:188— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:188-196 | voyager/plugins/transaction-batch/src/lib.rs:181-189 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/transaction/aptos/src/main.rs:158— voyager/plugins/transaction/aptos/src/main.rs:158-166 | voyager/plugins/transaction/sui/src/main.rs:454-462 — 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) cosmwasm/lightclient/ethereum/src/client.rs:63— cosmwasm/lightclient/ethereum/src/client.rs:63-71 | cosmwasm/lightclient/trusted-mpt/src/client.rs:43-52 — before extracting anything, compare `cosmwasm/lightclient/ethereum/src/client.rs` and `cosmwasm/lightclient/trusted-mpt/src/client.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 (9 lines × 2) lib/cometbft-types/src/types/canonical_vote.rs:24— lib/cometbft-types/src/types/canonical_vote.rs:24-33 | lib/galois-rpc/src/canonical_vote.rs:18-26 — 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) voyager/plugins/client-update/cometbls/src/main.rs:217— voyager/plugins/client-update/cometbls/src/main.rs:217-226 | voyager/plugins/client-update/cometbls/src/main.rs:381-389 — both copies are in the same file, so extract the block into 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) cosmwasm/core/src/contract.rs:1533— cosmwasm/core/src/contract.rs:1533-1541 | cosmwasm/core/src/contract.rs:1655-1664 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/starknet-types/src/lib.rs:172— lib/starknet-types/src/lib.rs:172-180 | lib/unionlabs-primitives/src/uint.rs:128-136 — before extracting anything, compare `lib/starknet-types/src/lib.rs` and `lib/unionlabs-primitives/src/uint.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 (9 lines × 2) galoisd/cmd/galoisd/cmd/phase2_contribute.go:11— galoisd/cmd/galoisd/cmd/phase2_contribute.go:11-19 | galoisd/cmd/galoisd/cmd/phase2_verify.go:11-19 — 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 `galoisd/cmd/galoisd/cmd/phase2_contribute.go:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) lib/ibc-union-spec/src/lib.rs:260— lib/ibc-union-spec/src/lib.rs:260-268 | lib/ibc-union-spec/src/lib.rs:282-290 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) cosmwasm/lightclient/base/src/client.rs:114— cosmwasm/lightclient/base/src/client.rs:114-127 | cosmwasm/lightclient/bob/src/client.rs:124-137 — before extracting anything, compare `cosmwasm/lightclient/base/src/client.rs` and `cosmwasm/lightclient/bob/src/client.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/lst/src/state.rs:224— cosmwasm/lst/src/state.rs:224-237 | cosmwasm/lst/src/state.rs:263-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 (14 lines × 2) lib/access-manager-types/src/lib.rs:465— lib/access-manager-types/src/lib.rs:465-478 | lib/access-manager-types/src/lib.rs:529-542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/cometbft-types/src/types/commit.rs:51— lib/cometbft-types/src/types/commit.rs:51-64 | lib/cometbft-types/src/types/commit.rs:82-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 (14 lines × 2) lib/cometbft-types/src/types/header.rs:268— lib/cometbft-types/src/types/header.rs:268-281 | lib/cometbft-types/src/types/header.rs:337-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 (14 lines × 2) lib/unionlabs/src/cosmos/ics23/non_existence_proof.rs:32— lib/unionlabs/src/cosmos/ics23/non_existence_proof.rs:32-45 | lib/unionlabs/src/union/ics23/non_existence_proof.rs:32-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) lib/voyager-client/src/lib.rs:427— lib/voyager-client/src/lib.rs:427-440 | lib/voyager-client/src/lib.rs:476-489 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/voyager-core/src/server.rs:530— lib/voyager-core/src/server.rs:530-543 | lib/voyager-core/src/server.rs:614-627 — both copies are in the same file, so extract the block into 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) voyager/modules/finality/arbitrum/src/main.rs:134— voyager/modules/finality/arbitrum/src/main.rs:134-147 | voyager/modules/finality/arbitrum/src/main.rs:151-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) voyager/modules/state/movement/src/client.rs:417— voyager/modules/state/movement/src/client.rs:417-430 | voyager/plugins/event-source/movement/src/client.rs:417-430 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/base/src/main.rs:123— voyager/plugins/client-update/base/src/main.rs:123-136 | voyager/plugins/client-update/bob/src/main.rs:116-129 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/base/src/main.rs:590— voyager/plugins/client-update/base/src/main.rs:590-603 | voyager/plugins/client-update/bob/src/main.rs:593-606 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/evm/src/main.rs:866— voyager/plugins/event-source/evm/src/main.rs:866-879 | voyager/plugins/event-source/evm/src/main.rs:920-933 — both copies are in the same file, so extract the block into 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) voyager/plugins/packet-timeout/src/main.rs:209— voyager/plugins/packet-timeout/src/main.rs:209-223 | voyager/plugins/packet-timeout/src/main.rs:394-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 (14 lines × 2) voyager/plugins/transaction/aptos/src/main.rs:172— voyager/plugins/transaction/aptos/src/main.rs:172-186 | voyager/plugins/transaction/sui/src/main.rs:468-481 — 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) voyager/modules/state/cosmwasm/src/main.rs:115— voyager/modules/state/cosmwasm/src/main.rs:115-128 | voyager/modules/state/cosmwasm/src/main.rs:254-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) galoisd/cmd/galoisd/cmd/export_vk.go:20— galoisd/cmd/galoisd/cmd/export_vk.go:20-33 | galoisd/cmd/galoisd/cmd/query_stats.go:20-33 — 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 `galoisd/cmd/galoisd/cmd/export_vk.go:20` 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.
Duplicated block (14 lines × 2) galoisd/cmd/galoisd/cmd/serve.go:33— galoisd/cmd/galoisd/cmd/serve.go:33-46 | galoisd/cmd/galoisd/cmd/serve_bls12381.go:31-44 — before extracting anything, compare `galoisd/cmd/galoisd/cmd/serve.go` and `galoisd/cmd/galoisd/cmd/serve_bls12381.go` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/cmd/galoisd/cmd/serve.go:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) cosmwasm/access-manager/src/contract.rs:254— cosmwasm/access-manager/src/contract.rs:254-264 | cosmwasm/access-manager/src/contract.rs:288-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/access-manager-types/src/lib.rs:426— lib/access-manager-types/src/lib.rs:426-436 | lib/access-manager-types/src/lib.rs:481-491 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/access-manager-types/src/lib.rs:497— lib/access-manager-types/src/lib.rs:497-507 | lib/access-manager-types/src/lib.rs:513-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/macros/src/lib.rs:678— lib/macros/src/lib.rs:678-688 | lib/macros/src/lib.rs:709-719 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/state-lens-ics23-ics23-light-client-types/src/client_state.rs:84— lib/state-lens-ics23-ics23-light-client-types/src/client_state.rs:84-94 | lib/state-lens-ics23-ics23-light-client-types/src/client_state.rs:97-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 (11 lines × 2) tools/u/src/vanity/create3.rs:43— tools/u/src/vanity/create3.rs:43-53 | tools/u/src/vanity/wrapped_token.rs:94-104 — before extracting anything, compare `tools/u/src/vanity/create3.rs` and `tools/u/src/vanity/wrapped_token.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:238— voyager/plugins/event-source/cosmwasm/src/main.rs:238-248 | voyager/plugins/event-source/gno/src/lib.rs:195-205 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/sui/src/main.rs:333— voyager/plugins/event-source/sui/src/main.rs:333-343 | voyager/plugins/event-source/sui/src/main.rs:634-644 — both copies are in the same file, so extract the block into 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1059— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1059-1069 | voyager/plugins/transaction-batch/src/callback.rs:64-74 — 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) cosmwasm/lightclient/base/src/client.rs:38— cosmwasm/lightclient/base/src/client.rs:38-48 | cosmwasm/lightclient/bob/src/client.rs:38-48 — before extracting anything, compare `cosmwasm/lightclient/base/src/client.rs` and `cosmwasm/lightclient/bob/src/client.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/lightclient/movement/src/contract.rs:30— cosmwasm/lightclient/movement/src/contract.rs:30-40 | cosmwasm/lightclient/state-lens-ics23-smt/src/contract.rs:33-43 — 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) cosmwasm/lightclient/parlia/src/store.rs:20— cosmwasm/lightclient/parlia/src/store.rs:20-30 | cosmwasm/lightclient/sui/src/client.rs:185-195 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) voyager/modules/client/gno/src/main.rs:204— voyager/modules/client/gno/src/main.rs:204-214 | voyager/modules/client/tendermint/src/main.rs:204-214 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/base-verifier/src/lib.rs:148— lib/base-verifier/src/lib.rs:148-158 | lib/bob-verifier/src/lib.rs:144-154 — before extracting anything, compare `lib/base-verifier/src/lib.rs` and `lib/bob-verifier/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/unionlabs-primitives/src/uint.rs:156— lib/unionlabs-primitives/src/uint.rs:156-166 | lib/unionlabs/src/ibc/core/client/height.rs:256-269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/unionlabs-primitives/src/bytes.rs:397— lib/unionlabs-primitives/src/bytes.rs:397-407 | lib/unionlabs-primitives/src/fixed_bytes.rs:424-434 — 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) galoisd/cmd/galoisd/cmd/serve.go:75— galoisd/cmd/galoisd/cmd/serve.go:75-85 | galoisd/cmd/galoisd/cmd/serve_bls12381.go:86-96 — before extracting anything, compare `galoisd/cmd/galoisd/cmd/serve.go` and `galoisd/cmd/galoisd/cmd/serve_bls12381.go` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/cmd/galoisd/cmd/serve.go:75` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `galoisd/cmd/galoisd/cmd/serve_bls12381.go:97` calls `Flags`, `String` and `galoisd/cmd/galoisd/cmd/serve.go:86` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Outbound HTTP without resilience drip/src/turnstile.rs:30— `Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience lib/beacon-api/src/client.rs:42— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience mpc/shared/src/supabase.rs:56— `ClientBuilder::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience mpc/shared/src/supabase.rs:195— `ClientBuilder::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/modules/client-bootstrap/sui/src/main.rs:127— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/modules/proof/movement/src/main.rs:177— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/modules/proof/sui/src/main.rs:152— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/modules/state/gno/src/main.rs:77— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/modules/state/movement/src/main.rs:282— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/modules/state/sui/src/main.rs:223— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/plugins/client-update/movement/src/main.rs:267— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/plugins/client-update/sui/src/main.rs:84— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/plugins/client-update/sui/src/main.rs:173— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/plugins/client-update/sui/src/main.rs:260— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/plugins/transaction/sui/src/main.rs:100— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/plugins/transaction/sui/src/main.rs:403— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience voyager/src/main.rs:774— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
ClassTooLong: Module voyager/plugins/transaction-batch-proof-lens/src/lib.rs:75— ClassTooLong — 1184 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 8 blocks, lines 75-1932. The bar is 400 significant lines; this is 784 over it, 2.96× 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: Module voyager/plugins/event-source/cosmwasm/src/main.rs:64— ClassTooLong — 956 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 5 blocks, lines 64-1428. The bar is 400 significant lines; this is 556 over it, 2.39× 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: Module voyager/plugins/event-source/evm/src/main.rs:59— ClassTooLong — 863 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 5 blocks, lines 59-1345. The bar is 400 significant lines; this is 463 over it, 2.16× 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: Server lib/voyager-core/src/server.rs:32— ClassTooLong — 862 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 4 blocks, lines 32-1224. The bar is 400 significant lines; this is 462 over it, 2.16× 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: Module voyager/plugins/event-source/gno/src/lib.rs:50— ClassTooLong — 766 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 5 blocks, lines 50-1301. The bar is 400 significant lines; this is 366 over it, 1.92× 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: Module voyager/plugins/event-source/sui/src/main.rs:63— ClassTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 4 blocks, lines 63-1027. The bar is 400 significant lines; this is 315 over it, 1.79× 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: Module tools/union-test/src/evm.rs:36— ClassTooLong — 657 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, 2 blocks, lines 36-966. The bar is 400 significant lines; this is 257 over it, 1.64× 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: Module voyager/plugins/client-update/arbitrum/src/main.rs:50— ClassTooLong — 640 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, 5 blocks, lines 50-959. The bar is 400 significant lines; this is 240 over it, 1.60× 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: TestContext tools/union-test/src/lib.rs:471— ClassTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 23 methods, 2 blocks, lines 471-1213. The bar is 400 significant lines; this is 169 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Module voyager/modules/state/cosmwasm/src/main.rs:51— ClassTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 11 methods, 4 blocks, lines 51-799. The bar is 400 significant lines; this is 167 over it, 1.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Module voyager/modules/state/evm/src/main.rs:48— ClassTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 4 blocks, lines 48-860. The bar is 400 significant lines; this is 159 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Module tools/union-test/src/cosmos.rs:71— ClassTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 71-802. The bar is 400 significant lines; this is 128 over it, 1.32× 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: Module voyager/plugins/event-source/movement/src/main.rs:67— ClassTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 6 blocks, lines 67-797. The bar is 400 significant lines; this is 122 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PgQueue REDACTED:44— ClassTooLong — 461 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 44-759. The bar is 400 significant lines; this is 61 over it, 1.15× 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: Module voyager/plugins/client-update/bob/src/main.rs:52— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 5 blocks, lines 52-668. The bar is 400 significant lines; this is 43 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Module voyager/plugins/client-update/base/src/main.rs:51— ClassTooLong — 417 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 5 blocks, lines 51-645. The bar is 400 significant lines; this is 17 over it, 1.04× 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.
Duplicated block (16 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:532— cosmwasm/app/ucs03-zkgm/src/contract.rs:532-547 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2922-2937 — both copies are in the same file, so extract the block into 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) voyager/modules/finality/arbitrum/src/main.rs:124— voyager/modules/finality/arbitrum/src/main.rs:124-139 | voyager/modules/finality/arbitrum/src/main.rs:188-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 (16 lines × 2) voyager/modules/finality/base/src/main.rs:93— voyager/modules/finality/base/src/main.rs:93-108 | voyager/modules/finality/base/src/main.rs:126-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) voyager/modules/finality/bob/src/main.rs:93— voyager/modules/finality/bob/src/main.rs:93-108 | voyager/modules/finality/bob/src/main.rs:126-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) voyager/plugins/client-update/arbitrum/src/main.rs:728— voyager/plugins/client-update/arbitrum/src/main.rs:728-743 | voyager/plugins/client-update/arbitrum/src/main.rs:843-858 — both copies are in the same file, so extract the block into 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) voyager/plugins/client-update/base/src/main.rs:355— voyager/plugins/client-update/base/src/main.rs:355-370 | voyager/plugins/client-update/bob/src/main.rs:345-360 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/ethereum/src/main.rs:127— voyager/plugins/client-update/ethereum/src/main.rs:127-142 | voyager/plugins/client-update/trusted-mpt/src/main.rs:120-135 — before extracting anything, compare `voyager/plugins/client-update/ethereum/src/main.rs` and `voyager/plugins/client-update/trusted-mpt/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (16 lines × 2) voyager/plugins/client-update/proof-lens/src/main.rs:232— voyager/plugins/client-update/proof-lens/src/main.rs:232-247 | voyager/plugins/client-update/state-lens/src/main.rs:242-257 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/proof-lens/src/main.rs:308— voyager/plugins/client-update/proof-lens/src/main.rs:308-323 | voyager/plugins/client-update/state-lens/src/main.rs:318-333 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/evm/src/main.rs:343— voyager/plugins/event-source/evm/src/main.rs:343-358 | voyager/plugins/event-source/starknet/src/main.rs:262-277 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/starknet/src/main.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 (16 lines × 2) voyager/plugins/event-source/movement/src/main.rs:635— voyager/plugins/event-source/movement/src/main.rs:635-650 | voyager/plugins/event-source/movement/src/main.rs:668-683 — both copies are in the same file, so extract the block into 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) voyager/plugins/event-source/sui/src/main.rs:777— voyager/plugins/event-source/sui/src/main.rs:777-792 | voyager/plugins/event-source/sui/src/main.rs:804-819 — both copies are in the same file, so extract the block into 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) voyager/plugins/sui-ibc-app/src/zkgm.rs:45— voyager/plugins/sui-ibc-app/src/zkgm.rs:45-60 | voyager/plugins/sui-ibc-app/src/zkgm.rs:177-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/base-client/src/lib.rs:12— lib/base-client/src/lib.rs:12-27 | lib/bob-client/src/lib.rs:12-27 — before extracting anything, compare `lib/base-client/src/lib.rs` and `lib/bob-client/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) galoisd/grpc/bls12381_server.go:359— galoisd/grpc/bls12381_server.go:359-374 | galoisd/grpc/bls12381_server.go:420-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) galoisd/grpc/server.go:583— galoisd/grpc/server.go:583-598 | galoisd/grpc/server.go:634-649 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×15
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×15
Duplicated block (12 lines × 2) cosmwasm/core/src/contract.rs:984— cosmwasm/core/src/contract.rs:984-995 | cosmwasm/core/src/contract.rs:1057-1068 — both copies are in the same file, so extract the block into 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) cosmwasm/cw-unionversal-token/src/contract.rs:243— cosmwasm/cw-unionversal-token/src/contract.rs:243-254 | cosmwasm/lightclient/bob/src/contract.rs:52-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 (12 lines × 2) cosmwasm/cw20-base/src/lib.rs:34— cosmwasm/cw20-base/src/lib.rs:34-45 | cosmwasm/cw20-wrapped-tokenfactory/src/lib.rs:25-36 — 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) lib/base-client/src/lib.rs:56— lib/base-client/src/lib.rs:56-67 | lib/bob-client/src/lib.rs:56-67 — before extracting anything, compare `lib/base-client/src/lib.rs` and `lib/bob-client/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/cosmos-signer/src/lib.rs:61— lib/cosmos-signer/src/lib.rs:61-72 | lib/gno-client/src/wallet.rs:75-86 — 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) tools/union-test/src/evm.rs:797— tools/union-test/src/evm.rs:797-808 | voyager/plugins/transaction/evm/src/main.rs:480-491 — 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) voyager/modules/client-bootstrap/ethereum/src/main.rs:205— voyager/modules/client-bootstrap/ethereum/src/main.rs:205-216 | voyager/modules/client-bootstrap/ethereum/src/main.rs:262-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 (12 lines × 2) voyager/modules/client-bootstrap/proof-lens/src/main.rs:113— voyager/modules/client-bootstrap/proof-lens/src/main.rs:113-124 | voyager/modules/client-bootstrap/state-lens/ics23-ics23/src/main.rs:112-123 — before extracting anything, compare `voyager/modules/client-bootstrap/proof-lens/src/main.rs` and `voyager/modules/client-bootstrap/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (12 lines × 2) voyager/plugins/client-update/base/src/main.rs:316— voyager/plugins/client-update/base/src/main.rs:316-327 | voyager/plugins/client-update/bob/src/main.rs:307-318 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/base/src/main.rs:330— voyager/plugins/client-update/base/src/main.rs:330-341 | voyager/plugins/client-update/bob/src/main.rs:321-332 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/movement/src/main.rs:260— voyager/plugins/event-source/movement/src/main.rs:260-271 | voyager/plugins/event-source/sui/src/main.rs:433-444 — before extracting anything, compare `voyager/plugins/event-source/movement/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (12 lines × 2) voyager/plugins/transaction/cosmos/src/main.rs:316— voyager/plugins/transaction/cosmos/src/main.rs:316-327 | voyager/plugins/transaction/gno/src/main.rs:205-216 — before extracting anything, compare `voyager/plugins/transaction/cosmos/src/main.rs` and `voyager/plugins/transaction/gno/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (12 lines × 2) cosmwasm/deployer/src/main.rs:712— cosmwasm/deployer/src/main.rs:712-726 | cosmwasm/deployer/src/main.rs:738-749 — both copies are in the same file, so extract the block into 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) galoisd/pkg/emulated/g2.go:318— galoisd/pkg/emulated/g2.go:318-329 | galoisd/pkg/emulated/g2.go:388-399 — both copies are in the same file, so extract the 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 `galoisd/pkg/emulated/g2.go:318` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 2) galoisd/pkg/lightclient/bls12381/circuit.go:70— galoisd/pkg/lightclient/bls12381/circuit.go:70-81 | galoisd/pkg/lightclient/common.go:45-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:930— cosmwasm/app/ucs03-zkgm/src/contract.rs:930-935 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1103-1108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/cometbft-types/src/types/header.rs:240— lib/cometbft-types/src/types/header.rs:240-245 | lib/cometbft-types/src/types/header.rs:309-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 (6 lines × 2) lib/starknet-types/src/lib.rs:183— lib/starknet-types/src/lib.rs:183-188 | lib/unionlabs-primitives/src/uint.rs:139-144 — before extracting anything, compare `lib/starknet-types/src/lib.rs` and `lib/unionlabs-primitives/src/uint.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 × 2) mpc/client/src/ui.rs:267— mpc/client/src/ui.rs:267-272 | mpc/client/src/ui.rs:324-329 — both copies are in the same file, so extract the block into 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) voyager/modules/client/proof-lens/src/main.rs:179— voyager/modules/client/proof-lens/src/main.rs:179-184 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:182-187 — before extracting anything, compare `voyager/modules/client/proof-lens/src/main.rs` and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1742— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1742-1747 | voyager/plugins/transaction-batch/src/lib.rs:650-655 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/lightclient/arbitrum/src/client.rs:194— cosmwasm/lightclient/arbitrum/src/client.rs:194-199 | cosmwasm/lightclient/bob/src/client.rs:77-82 — 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) lib/cometbft-rpc/src/lib.rs:425— lib/cometbft-rpc/src/lib.rs:425-430 | lib/gno-rpc/src/lib.rs:320-325 — before extracting anything, compare `lib/cometbft-rpc/src/lib.rs` and `lib/gno-rpc/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/cometbft-rpc/src/lib.rs:436— lib/cometbft-rpc/src/lib.rs:436-441 | lib/gno-rpc/src/lib.rs:331-336 — before extracting anything, compare `lib/cometbft-rpc/src/lib.rs` and `lib/gno-rpc/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/cometbft-rpc/src/lib.rs:449— lib/cometbft-rpc/src/lib.rs:449-454 | lib/gno-rpc/src/lib.rs:344-349 — before extracting anything, compare `lib/cometbft-rpc/src/lib.rs` and `lib/gno-rpc/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/gno/src/main.rs:94— voyager/modules/client/gno/src/main.rs:94-99 | voyager/modules/client/tendermint/src/main.rs:94-99 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/voyager-vm/src/lib.rs:290— lib/voyager-vm/src/lib.rs:290-295 | lib/voyager-vm/src/lib.rs:306-311 — both copies are in the same file, so extract the block into 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) voyager/plugins/client-update/base/src/main.rs:159— voyager/plugins/client-update/base/src/main.rs:159-164 | voyager/plugins/client-update/bob/src/main.rs:152-157 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) galoisd/cmd/galoisd/cmd/phase1_init.go:156— galoisd/cmd/galoisd/cmd/phase1_init.go:156-161 | galoisd/cmd/galoisd/cmd/phase1_init.go:669-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. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/cmd/galoisd/cmd/phase1_init.go:156` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) galoisd/pkg/emulated/g2.go:194— galoisd/pkg/emulated/g2.go:194-199 | galoisd/pkg/emulated/g2.go:202-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/pkg/emulated/g2.go:194` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×14
Duplicated block (18 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:559— cosmwasm/app/ucs03-zkgm/src/contract.rs:559-576 | cosmwasm/app/ucs03-zkgm/src/contract.rs:723-740 — both copies are in the same file, so extract the block into 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) cosmwasm/app/ucs03-zkgm/src/contract.rs:681— cosmwasm/app/ucs03-zkgm/src/contract.rs:681-698 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1166-1183 — both copies are in the same file, so extract the block into 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) cosmwasm/cw20-base/src/enumerable.rs:20— cosmwasm/cw20-base/src/enumerable.rs:20-37 | cosmwasm/cw20-wrapped-tokenfactory/src/enumerable.rs:20-37 — 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) cosmwasm/cw20-base/src/enumerable.rs:45— cosmwasm/cw20-base/src/enumerable.rs:45-62 | cosmwasm/cw20-wrapped-tokenfactory/src/enumerable.rs:45-62 — 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) cosmwasm/lightclient/gno/src/client.rs:121— cosmwasm/lightclient/gno/src/client.rs:121-138 | cosmwasm/lightclient/tendermint/src/client.rs:133-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18 lines × 2) voyager/plugins/client-update/arbitrum/src/main.rs:500— voyager/plugins/client-update/arbitrum/src/main.rs:500-517 | voyager/plugins/client-update/arbitrum/src/main.rs:586-603 — both copies are in the same file, so extract the block into 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) voyager/plugins/client-update/ethereum/src/main.rs:99— voyager/plugins/client-update/ethereum/src/main.rs:99-116 | voyager/plugins/client-update/trusted-mpt/src/main.rs:92-109 — before extracting anything, compare `voyager/plugins/client-update/ethereum/src/main.rs` and `voyager/plugins/client-update/trusted-mpt/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (18 lines × 2) voyager/plugins/client-update/proof-lens/src/main.rs:209— voyager/plugins/client-update/proof-lens/src/main.rs:209-226 | voyager/plugins/client-update/state-lens/src/main.rs:219-236 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/cosmwasm/src/main.rs:262— voyager/plugins/event-source/cosmwasm/src/main.rs:262-279 | voyager/plugins/event-source/gno/src/lib.rs:219-236 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/evm/src/main.rs:1108— voyager/plugins/event-source/evm/src/main.rs:1108-1125 | voyager/plugins/event-source/evm/src/main.rs:1149-1166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/gno-light-client-types/src/consensus_state.rs:37— lib/gno-light-client-types/src/consensus_state.rs:37-54 | lib/tendermint-light-client-types/src/consensus_state.rs:37-103 — 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) voyager/plugins/transaction/cosmos/src/call.rs:22— voyager/plugins/transaction/cosmos/src/call.rs:22-39 | voyager/plugins/transaction/gno/src/call.rs:22-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 (18 lines × 2) galoisd/grpc/bls12381_server.go:270— galoisd/grpc/bls12381_server.go:270-287 | galoisd/grpc/server.go:420-437 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/grpc/bls12381_server.go:270` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
Duplicated block (18 lines × 2) galoisd/grpc/bls12381_server.go:445— galoisd/grpc/bls12381_server.go:445-462 | galoisd/grpc/server.go:540-557 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) cosmwasm/lightclient/arbitrum/src/client.rs:88— cosmwasm/lightclient/arbitrum/src/client.rs:88-104 | cosmwasm/lightclient/arbitrum/src/client.rs:125-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) cosmwasm/lightclient/state-lens-ics23-mpt/src/client.rs:238— cosmwasm/lightclient/state-lens-ics23-mpt/src/client.rs:238-254 | cosmwasm/lightclient/trusted-mpt/src/client.rs:187-203 — before extracting anything, compare `cosmwasm/lightclient/state-lens-ics23-mpt/src/client.rs` and `cosmwasm/lightclient/trusted-mpt/src/client.rs` as WHOLE FILES: this scan already matched 3 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 (17 lines × 2) lib/cometbft-types/src/types/header.rs:187— lib/cometbft-types/src/types/header.rs:187-203 | lib/cometbft-types/src/types/header.rs:286-302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) voyager/modules/client-bootstrap/ethermint/src/main.rs:229— voyager/modules/client-bootstrap/ethermint/src/main.rs:229-245 | voyager/modules/client-bootstrap/tendermint/src/main.rs:263-279 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) voyager/modules/state/cosmwasm/src/main.rs:179— voyager/modules/state/cosmwasm/src/main.rs:179-195 | voyager/modules/state/cosmwasm/src/main.rs:308-324 — both copies are in the same file, so extract the block into 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) voyager/modules/state/movement/src/client.rs:330— voyager/modules/state/movement/src/client.rs:330-346 | voyager/plugins/event-source/movement/src/client.rs:330-346 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/trusted-mpt/src/main.rs:123— voyager/plugins/client-update/trusted-mpt/src/main.rs:123-139 | voyager/plugins/event-source/evm/src/main.rs:138-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:904— voyager/plugins/event-source/cosmwasm/src/main.rs:904-920 | voyager/plugins/event-source/evm/src/main.rs:955-971 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/evm/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/evm/src/main.rs:1054— voyager/plugins/event-source/evm/src/main.rs:1054-1070 | voyager/plugins/event-source/evm/src/main.rs:1279-1295 — both copies are in the same file, so extract the block into 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) voyager/plugins/sui-ibc-app/src/main.rs:250— voyager/plugins/sui-ibc-app/src/main.rs:250-266 | voyager/plugins/transaction/sui/src/main.rs:77-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 (17 lines × 2) lib/berachain-light-client-types/src/consensus_state.rs:32— lib/berachain-light-client-types/src/consensus_state.rs:32-48 | lib/state-lens-ics23-mpt-light-client-types/src/consensus_state.rs:37-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 (17 lines × 2) tools/u/src/zkgm/predict_proxy_account_address.rs:82— tools/u/src/zkgm/predict_proxy_account_address.rs:82-98 | tools/u/src/zkgm/predict_wrapped_token.rs:181-197 — 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 (17 lines × 2) uniond/app/upgrades/v1_2_0/upgrade.go:79— uniond/app/upgrades/v1_2_0/upgrade.go:79-95 | uniond/app/upgrades/v1_3_0/upgrade.go:78-94 — `uniond/app/upgrades/v1_2_0/upgrade.go` and `uniond/app/upgrades/v1_3_0/upgrade.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 71 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `uniond/app/upgrades/v1_2_0/upgrade.go:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 2) lib/cometbft-types/src/types/validator.rs:61— lib/cometbft-types/src/types/validator.rs:61-67 | lib/cometbft-types/src/types/validator.rs:76-82 — both copies are in the same file, so extract the block into 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) cosmwasm/cw-escrow-vault/src/contract.rs:71— cosmwasm/cw-escrow-vault/src/contract.rs:71-77 | cosmwasm/cw-unionversal-token/src/contract.rs:101-107 — before extracting anything, compare `cosmwasm/cw-escrow-vault/src/contract.rs` and `cosmwasm/cw-unionversal-token/src/contract.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) lib/cometbft-rpc/src/rpc_types.rs:50— lib/cometbft-rpc/src/rpc_types.rs:50-56 | lib/gno-rpc/src/rpc_types.rs:35-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/cosmos-client/src/gas.rs:25— lib/cosmos-client/src/gas.rs:25-31 | lib/gno-client/src/gas.rs:22-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/cosmos-client/src/lib.rs:389— lib/cosmos-client/src/lib.rs:389-395 | lib/gno-client/src/lib.rs:325-331 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) tools/union-test/src/cosmos.rs:906— tools/union-test/src/cosmos.rs:906-912 | voyager/plugins/event-source/cosmwasm/src/ibc_events.rs:205-211 — 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) tools/union-test/src/cosmos.rs:917— tools/union-test/src/cosmos.rs:917-923 | voyager/plugins/event-source/cosmwasm/src/ibc_events.rs:216-222 — 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) voyager/modules/client/gno/src/main.rs:123— voyager/modules/client/gno/src/main.rs:123-129 | voyager/modules/client/tendermint/src/main.rs:123-129 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/gno/src/main.rs:166— voyager/modules/client/gno/src/main.rs:166-172 | voyager/modules/client/tendermint/src/main.rs:166-172 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/gno/src/main.rs:184— voyager/modules/client/gno/src/main.rs:184-190 | voyager/modules/client/tendermint/src/main.rs:184-190 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/proof-lens/src/main.rs:37— voyager/modules/client/proof-lens/src/main.rs:37-43 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:40-46 — before extracting anything, compare `voyager/modules/client/proof-lens/src/main.rs` and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) galoisd/pkg/emulated/g2.go:312— galoisd/pkg/emulated/g2.go:312-318 | galoisd/pkg/emulated/g2.go:344-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 (7 lines × 2) uniond/app/upgrades/v1_2_0/upgrade.go:56— uniond/app/upgrades/v1_2_0/upgrade.go:56-62 | uniond/app/upgrades/v1_3_0/upgrade.go:62-68 — `uniond/app/upgrades/v1_2_0/upgrade.go` and `uniond/app/upgrades/v1_3_0/upgrade.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 71 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `uniond/app/upgrades/v1_2_0/upgrade.go:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) cosmwasm/deployer/src/main.rs:2080— cosmwasm/deployer/src/main.rs:2080-2094 | cosmwasm/lst-ocw/src/main.rs:116-130 — 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) lib/cosmos-client/src/gas/fixed.rs:26— lib/cosmos-client/src/gas/fixed.rs:26-40 | lib/gno-client/src/gas/fixed.rs:26-40 — 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) lib/evm-storage-verifier/src/lib.rs:85— lib/evm-storage-verifier/src/lib.rs:85-99 | lib/evm-storage-verifier/src/lib.rs:116-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) voyager/modules/finality/base/src/main.rs:101— voyager/modules/finality/base/src/main.rs:101-115 | voyager/modules/finality/bob/src/main.rs:101-115 — before extracting anything, compare `voyager/modules/finality/base/src/main.rs` and `voyager/modules/finality/bob/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (15 lines × 2) voyager/modules/state/evm/src/main.rs:548— voyager/modules/state/evm/src/main.rs:548-562 | voyager/modules/state/evm/src/main.rs:701-715 — both copies are in the same file, so extract the block into 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) voyager/modules/state/movement/src/client.rs:481— voyager/modules/state/movement/src/client.rs:481-495 | voyager/plugins/event-source/movement/src/client.rs:481-495 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/cosmwasm/src/main.rs:169— voyager/plugins/event-source/cosmwasm/src/main.rs:169-183 | voyager/plugins/event-source/gno/src/lib.rs:139-153 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/sui/src/main.rs:705— voyager/plugins/event-source/sui/src/main.rs:705-719 | voyager/plugins/event-source/sui/src/main.rs:728-742 — both copies are in the same file, so extract the block into 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) voyager/plugins/transaction/sui/src/main.rs:104— voyager/plugins/transaction/sui/src/main.rs:104-118 | voyager/plugins/transaction/sui/src/main.rs:407-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) lib/ucs03-zkgm-packet/src/token_order.rs:174— lib/ucs03-zkgm-packet/src/token_order.rs:174-188 | lib/ucs03-zkgm-packet/src/token_order.rs:226-240 — both copies are in the same file, so extract the block into 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) voyager/modules/client-bootstrap/movement/src/main.rs:160— voyager/modules/client-bootstrap/movement/src/main.rs:160-174 | voyager/modules/proof/movement/src/main.rs:124-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 (15 lines × 2) galoisd/cmd/galoisd/cmd/example_prove.go:214— galoisd/cmd/galoisd/cmd/example_prove.go:214-228 | galoisd/cmd/galoisd/cmd/example_verify.go:186-200 — before extracting anything, compare `galoisd/cmd/galoisd/cmd/example_prove.go` and `galoisd/cmd/galoisd/cmd/example_verify.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 151 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) cosmwasm/core/light-client-interface/src/lib.rs:559— cosmwasm/core/light-client-interface/src/lib.rs:559-568 | cosmwasm/core/light-client-interface/src/lib.rs:575-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 (10 lines × 2) lib/beacon-api/src/client.rs:357— lib/beacon-api/src/client.rs:357-366 | lib/beacon-api/src/client.rs:379-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 (10 lines × 2) voyager/modules/client-bootstrap/sui/src/main.rs:129— voyager/modules/client-bootstrap/sui/src/main.rs:129-138 | voyager/plugins/client-update/sui/src/main.rs:261-270 — 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) voyager/modules/finality/arbitrum/src/main.rs:198— voyager/modules/finality/arbitrum/src/main.rs:198-207 | voyager/modules/finality/arbitrum/src/main.rs:210-219 — both copies are in the same file, so extract the block into 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) voyager/plugins/client-update/arbitrum/src/main.rs:330— voyager/plugins/client-update/arbitrum/src/main.rs:330-339 | voyager/plugins/client-update/arbitrum/src/main.rs:413-422 — both copies are in the same file, so extract the block into 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) voyager/plugins/event-source/evm/src/main.rs:260— voyager/plugins/event-source/evm/src/main.rs:260-269 | voyager/plugins/event-source/starknet/src/main.rs:185-194 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/starknet/src/main.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 lines × 2) voyager/plugins/transaction/cosmos/src/main.rs:477— voyager/plugins/transaction/cosmos/src/main.rs:477-486 | voyager/plugins/transaction/gno/src/main.rs:372-381 — before extracting anything, compare `voyager/plugins/transaction/cosmos/src/main.rs` and `voyager/plugins/transaction/gno/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (10 lines × 2) cosmwasm/lightclient/base/src/client.rs:55— cosmwasm/lightclient/base/src/client.rs:55-64 | cosmwasm/lightclient/bob/src/client.rs:55-64 — before extracting anything, compare `cosmwasm/lightclient/base/src/client.rs` and `cosmwasm/lightclient/bob/src/client.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:119— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:119-128 | voyager/plugins/transaction-batch/src/lib.rs:91-100 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/evm/src/main.rs:1010— voyager/plugins/event-source/evm/src/main.rs:1010-1019 | voyager/plugins/event-source/evm/src/main.rs:1040-1049 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/starknet-types/src/lib.rs:139— lib/starknet-types/src/lib.rs:139-148 | lib/unionlabs-primitives/src/uint.rs:95-104 — before extracting anything, compare `lib/starknet-types/src/lib.rs` and `lib/unionlabs-primitives/src/uint.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 (10 lines × 2) voyager/modules/state/evm/src/main.rs:358— voyager/modules/state/evm/src/main.rs:358-367 | voyager/modules/state/evm/src/main.rs:382-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Focus outline removed inline app2/src/lib/components/ui/Wallet/connect/connection.svelte:164— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/lib/dashboard/components/DeleteAccountModal.svelte:116— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/lib/dashboard/components/SocialConnections.svelte:30— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/lib/dashboard/components/SocialConnections.svelte:85— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/lib/dashboard/components/SocialConnections.svelte:141— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/lib/dashboard/components/UnlinkAccountModal.svelte:123— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/routes/explorer/orbital/charts/LatencyChart.svelte:298— <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline app2/src/routes/explorer/orbital/charts/LatencyChart.svelte:311— <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline ceremony/src/lib/components/Terminal/Button.svelte:5— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline ceremony/src/lib/components/Terminal/Code.svelte:127— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline ceremony/src/lib/components/address/AddressForm.svelte:116— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Module::call (cognitive 59) voyager/plugins/transaction/cosmos/src/main.rs:474— Module::call has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (31 pts), match/switch 6 (24 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 41). 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.
Module::wait_for_event (cognitive 33) tools/union-test/src/cosmos.rs:189— Module::wait_for_event has cognitive complexity 33 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 3 (12 pts), match/switch 1 (6 pts) (nesting depth added 24). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Module::fetch_block (cognitive 31) voyager/plugins/event-source/cosmwasm/src/main.rs:393— Module::fetch_block has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 5 (9 pts), loops 4 (7 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.
Module::fetch_get_logs (cognitive 31) voyager/plugins/event-source/evm/src/main.rs:394— Module::fetch_get_logs has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (28 pts), match/switch 2 (3 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Module::call (cognitive 30) voyager/plugins/client-update/cometbls/src/main.rs:327— Module::call has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 3 (6 pts), loops 1 (2 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Module::fetch_update (cognitive 26) voyager/plugins/client-update/parlia/src/main.rs:226— Module::fetch_update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Module::check_send_packet (cognitive 24) voyager/plugins/zkgm-filter/src/main.rs:536— Module::check_send_packet has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Module::submit_transaction (cognitive 20) voyager/plugins/transaction/evm/src/main.rs:415— Module::submit_transaction has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 1 (2 pts), boolean chains 1, 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.
Module::run_pass_internal (cognitive 20) voyager/plugins/transaction-batch/src/lib.rs:384— Module::run_pass_internal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 2 (5 pts), boolean chains 1, 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.
Module::wait_for_event (cognitive 18) tools/union-test/src/evm.rs:143— Module::wait_for_event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 3 (6 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Module::make_batch_transaction (cognitive 17) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1274— Module::make_batch_transaction has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 4 (7 pts), 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.
Change coupling: contract.rs ↔ error.rs cosmwasm/app/ucs03-zkgm/src/contract.rs:1— `cosmwasm/app/ucs03-zkgm/src/contract.rs` and `cosmwasm/cw20-token-minter/src/error.rs` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — 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 `db24560b` feat(zkgm): generalized wrapped event & thread order path to solver (at that commit the file was still `cosmwasm/ibc-union/app/ucs03-zkgm/src/contract.rs`); `1390b57b` chore: make predict wrapped denom query take string path (at that commit the file was still `cosmwasm/ibc-union/app/ucs03-zkgm/src/contract.rs`); `ecaf167c` feat(zkgm): add predictable contract addresses to cw20 (at that commit the file was still `cosmwasm/ibc-union/app/ucs03-zkgm/src/contract.rs`) — run `git show` on any of them.
Change coupling: REDACTED ↔ queries.ts REDACTED:1— `REDACTED` and `ceremony/src/lib/supabase/queries.ts` change together 65% of the time (15 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 15 shared commits counted here, the most recent 3 are `751ebe58` feat(ceremony): preparing queue; `9ea17027` feat(ceremony): add missed slot; `0163e2aa` feat(ceremony): save progress — run `git show` on any of them.
Change coupling: REDACTED ↔ FeeDetails.svelte app2/src/lib/gasprice/index.ts:1— `app2/src/lib/gasprice/index.ts` and `app2/src/lib/transfer/shared/components/FeeDetails.svelte` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `5b85e317` feat(app): add transparent fee calc; `0c95997a` feat(app2): consider L1 data fee for BOB; `214b077a` chore(app2): fix build and correct fee logging — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED ceremony/src/lib/client/index.ts:1— `ceremony/src/lib/client/index.ts` and `REDACTED` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `9ea17027` feat(ceremony): add missed slot; `7ef6b5d1` feat(ceremony): contributors; `cf870c79` fix(ceremony): prepare for next steps — run `git show` on any of them.
Change coupling: lightclient.rs ↔ REDACTED cosmwasm/core/msg/src/lightclient.rs:1— `cosmwasm/core/msg/src/lightclient.rs` and `cosmwasm/lightclient/berachain/src/client.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a4791dd9` feat(voyager): status query (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/lightclient.rs` and `cosmwasm/ibc-union/lightclient/berachain/src/client.rs`); `c32c07ff` feat(ibc-union): cosmwasm: add caller/relayer on callbacks (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/lightclient.rs` and `cosmwasm/ibc-union/lightclient/berachain/src/client.rs`); `3b391828` chore: api improvements (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/lightclient.rs` and `cosmwasm/ibc-union/lightclient/berachain/src/client.rs`) — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED typescript-sdk/src/evm/client.ts:1— `typescript-sdk/src/evm/client.ts` and `REDACTED` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a2bd8afd` fix(typescript-sdk): type errors for modules that will be upgraded la…; `f67b5012` fix(typescript-sdk): use ucs03 on evm; `8ed94b2a` chore: more neverthrow-ify (at that commit the file was still `typescript-sdk/src/client/evm.ts`) — run `git show` on any of them.
Change coupling: msg.rs ↔ query.rs cosmwasm/core/msg/src/msg.rs:1— `cosmwasm/core/msg/src/msg.rs` and `cosmwasm/core/msg/src/query.rs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `b1f24275` feat(cosmwasm): add access management to core and zkgm (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/msg.rs` and `cosmwasm/ibc-union/core/msg/src/query.rs`); `c16a3111` feat(core): proof commitments (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/msg.rs` and `cosmwasm/ibc-union/core/msg/src/query.rs`); `849237ac` feat(ibc-union): add cw-orch (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/msg.rs` and `cosmwasm/ibc-union/core/msg/src/query.rs`) — run `git show` on any of them.
Change coupling: index.svelte ↔ check-filling.ts app2/src/lib/transfer/normal/index.svelte:1— `app2/src/lib/transfer/normal/index.svelte` and `app2/src/lib/transfer/shared/services/filling/check-filling.ts` change together 50% of the time (11 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `5f7983f4` fix(app): eth -> u token order; `64d943d0` fix(app2): allow no fee; `4396e6a9` feat(app2): wip fee intent — run `git show` on any of them.
Change coupling: contract.rs ↔ REDACTED cosmwasm/core/src/contract.rs:1— `cosmwasm/core/src/contract.rs` and `cosmwasm/lightclient/berachain/src/client.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `a4791dd9` feat(voyager): status query (at that commit the files were still `cosmwasm/ibc-union/core/src/contract.rs` and `cosmwasm/ibc-union/lightclient/berachain/src/client.rs`); `c32c07ff` feat(ibc-union): cosmwasm: add caller/relayer on callbacks (at that commit the files were still `cosmwasm/ibc-union/core/src/contract.rs` and `cosmwasm/ibc-union/lightclient/berachain/src/client.rs`); `ea46998b` chore: reflect the changes to all of the clients (at that commit the files were still `cosmwasm/ibc-union/core/src/contract.rs` and `cosmwasm/ibc-union/lightclient/berachain/src/client.rs`) — run `git show` on any of them.
Change coupling: module.rs ↔ REDACTED cosmwasm/core/msg/src/module.rs:1— `cosmwasm/core/msg/src/module.rs` and `cosmwasm/core/src/lib.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — 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 5 shared commits counted here, the most recent 3 are `849237ac` feat(ibc-union): add cw-orch (at that commit the files were still `cosmwasm/ibc-union/core/msg/src/module.rs` and `cosmwasm/ibc-union/core/src/lib.rs`); `7716514a` feat(union-ibc): extract msgs/queries to independent crate (at that commit the files were still `cosmwasm/union-ibc-msg/src/module.rs` and `cosmwasm/union-ibc/src/lib.rs`); `c344c751` feat(union-ibc): add `GetChannel` and `GetChannels` queries (at that commit the files were still `cosmwasm/union-ibc/src/module/msg.rs` and `cosmwasm/union-ibc/src/lib.rs`) — run `git show` on any of them.
Module::call (cyclomatic 35) voyager/plugins/event-source/movement/src/main.rs:284— Module::call has cyclomatic complexity 35 (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.
Module::fetch_get_logs (cyclomatic 29) voyager/plugins/event-source/evm/src/main.rs:394— Module::fetch_get_logs 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.
Module::make_full_event (cyclomatic 25) voyager/plugins/event-source/evm/src/main.rs:546— Module::make_full_event has cyclomatic complexity 25 (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.
Module::call (cyclomatic 22) voyager/plugins/transaction/cosmos/src/main.rs:474— Module::call has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Module::call (cyclomatic 21) voyager/plugins/event-source/sui/src/main.rs:457— Module::call has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Module::process_msgs (cyclomatic 19) voyager/plugins/transaction/sui/src/main.rs:183— Module::process_msgs has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Module::fetch_block (cyclomatic 18) voyager/plugins/event-source/cosmwasm/src/main.rs:393— Module::fetch_block has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Module::call (cyclomatic 17) voyager/plugins/client-update/cometbls/src/main.rs:327— Module::call 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.
Duplicated block (19 lines × 2) cosmwasm/core/src/contract.rs:1197— cosmwasm/core/src/contract.rs:1197-1215 | cosmwasm/core/src/contract.rs:1256-1274 — both copies are in the same file, so extract the block into 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) cosmwasm/cw20-base/src/contract.rs:501— cosmwasm/cw20-base/src/contract.rs:501-519 | cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs:276-294 — before extracting anything, compare `cosmwasm/cw20-base/src/contract.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 2) tools/union-test/src/cosmos.rs:105— tools/union-test/src/cosmos.rs:105-123 | voyager/plugins/transaction/cosmos/src/main.rs:179-197 — before extracting anything, compare `tools/union-test/src/cosmos.rs` and `voyager/plugins/transaction/cosmos/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (19 lines × 2) voyager/modules/finality/movement/src/main.rs:148— voyager/modules/finality/movement/src/main.rs:148-166 | voyager/modules/state/movement/src/main.rs:139-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 (19 lines × 2) voyager/modules/proof/movement/src/main.rs:177— voyager/modules/proof/movement/src/main.rs:177-195 | voyager/modules/state/movement/src/main.rs:282-300 — before extracting anything, compare `voyager/modules/proof/movement/src/main.rs` and `voyager/modules/state/movement/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 2) voyager/modules/state/movement/src/client.rs:501— voyager/modules/state/movement/src/client.rs:501-519 | voyager/plugins/event-source/movement/src/client.rs:501-519 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 2) lib/voyager-core/src/cache.rs:214— lib/voyager-core/src/cache.rs:214-232 | lib/voyager-core/src/cache.rs:281-299 — both copies are in the same file, so extract the block into 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) uniond/app/upgrades/v1_2_0/upgrade.go:101— uniond/app/upgrades/v1_2_0/upgrade.go:101-119 | uniond/app/upgrades/v1_3_0/upgrade.go:100-118 — `uniond/app/upgrades/v1_2_0/upgrade.go` and `uniond/app/upgrades/v1_3_0/upgrade.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 71 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `uniond/app/upgrades/v1_2_0/upgrade.go:101` 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×8
Async function without AbortSignal: checkCosmosTokenType typescript-sdk/src/query/on-chain.ts:201— `checkCosmosTokenType` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getCosmosHeight typescript-sdk/src/query/on-chain.ts:224— `getCosmosHeight` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getCosmosTransactionReceipt typescript-sdk/src/query/on-chain.ts:244— `getCosmosTransactionReceipt` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getCosmosAccountTransactions typescript-sdk/src/query/on-chain.ts:269— `getCosmosAccountTransactions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getAptosAccountTransactions typescript-sdk/src/query/on-chain.ts:295— `getAptosAccountTransactions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: try sentinel2/src/check-ssl-certificates.ts:24— `try` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: isValidImageUrl app2/src/lib/utils/avatar.ts:4— `isValidImageUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: try app2/src/lib/dashboard/helpers.ts:169— `try` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
FixmeComment lib/unionlabs/src/cosmos/staking/validator.rs:29— // FIXME: This is actually cosmos.Int — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/unionlabs/src/cosmos/staking/validator.rs:45— // FIXME: This is actually cosmos.Int — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/unionlabs/src/cosmos/staking/validator.rs:32— // FIXME: This is actually cosmos.Dec — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cosmwasm/osmosis-tokenfactory-token-minter/src/contract.rs:204— // FIXME: no longer true on babylon/osmosis? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cosmwasm/lightclient/starknet/src/client.rs:104— // FIXME: expose the ctx to this call to allow threading this call to L1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cosmwasm/lightclient/berachain/src/client.rs:86— // FIXME: expose the ctx to this call to allow threading this call to L1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cosmwasm/lightclient/ethermint/src/client.rs:155— // FIXME: read latest consensus to verify if client expired — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (22 lines × 2) lib/cometbft-rpc/src/lib.rs:59— lib/cometbft-rpc/src/lib.rs:59-80 | lib/gno-rpc/src/lib.rs:55-76 — before extracting anything, compare `lib/cometbft-rpc/src/lib.rs` and `lib/gno-rpc/src/lib.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 lines × 2) voyager/modules/state/cosmwasm/src/main.rs:771— voyager/modules/state/cosmwasm/src/main.rs:771-792 | voyager/modules/state/gno/src/main.rs:771-792 — before extracting anything, compare `voyager/modules/state/cosmwasm/src/main.rs` and `voyager/modules/state/gno/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (22 lines × 2) voyager/modules/state/gno/src/main.rs:547— voyager/modules/state/gno/src/main.rs:547-568 | voyager/modules/state/gno/src/main.rs:608-629 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) voyager/plugins/client-update/base/src/main.rs:396— voyager/plugins/client-update/base/src/main.rs:396-417 | voyager/plugins/client-update/base/src/main.rs:510-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:290— voyager/plugins/event-source/cosmwasm/src/main.rs:290-311 | voyager/plugins/event-source/gno/src/lib.rs:247-268 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 lines × 2) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1748— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1748-1769 | voyager/plugins/transaction-batch/src/lib.rs:656-677 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 lines × 2) galoisd/grpc/bls12381_server.go:100— galoisd/grpc/bls12381_server.go:100-121 | galoisd/grpc/server.go:300-321 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/grpc/bls12381_server.go:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) voyager/modules/state/cosmwasm/src/main.rs:786— voyager/modules/state/cosmwasm/src/main.rs:786-798 | voyager/modules/state/evm/src/main.rs:827-839 | voyager/modules/state/gno/src/main.rs:786-798 — before extracting anything, compare `voyager/modules/state/cosmwasm/src/main.rs` and `voyager/modules/state/gno/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (13 lines × 3) voyager/plugins/client-update/arbitrum/src/main.rs:173— voyager/plugins/client-update/arbitrum/src/main.rs:173-185 | voyager/plugins/client-update/ethereum/src/main.rs:207-219 | voyager/plugins/client-update/trusted-mpt/src/main.rs:184-196 — before extracting anything, compare `voyager/plugins/client-update/ethereum/src/main.rs` and `voyager/plugins/client-update/trusted-mpt/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (13 lines × 3) voyager/plugins/event-source/movement/src/main.rs:442— voyager/plugins/event-source/movement/src/main.rs:442-454 | voyager/plugins/event-source/movement/src/main.rs:458-470 | voyager/plugins/event-source/movement/src/main.rs:474-486 — 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) voyager/plugins/event-source/movement/src/main.rs:535— voyager/plugins/event-source/movement/src/main.rs:535-547 | voyager/plugins/event-source/movement/src/main.rs:578-590 | voyager/plugins/event-source/movement/src/main.rs:621-633 — 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) voyager/plugins/transaction-batch/src/call.rs:639— voyager/plugins/transaction-batch/src/call.rs:639-651 | voyager/plugins/transaction-batch/src/call.rs:691-703 | voyager/plugins/transaction-batch/src/call.rs:732-744 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/unionlabs/src/cosmos/crypto/bn254.rs:20— lib/unionlabs/src/cosmos/crypto/bn254.rs:20-32 | lib/unionlabs/src/cosmos/crypto/ed25519.rs:20-32 | lib/unionlabs/src/cosmos/crypto/secp256k1.rs:20-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (13 lines × 3) 11-cometbls/zk_verifier.go:191— 11-cometbls/zk_verifier.go:191-203 | galoisd/cmd/galoisd/cmd/example_verify.go:203-215 | galoisd/grpc/server.go:197-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.
AC1 · Text alternatives· <canvas> without a text alternative · ×6
<canvas> without a text alternative app2/src/lib/components/AnimatedArrows.svelte:230— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:571— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative app2/src/routes/explorer/orbital/charts/TerminalLog.svelte:384— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative site/src/components/MatrixCover.astro:6— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative site/src/components/PdfViewer.svelte:445— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative site/src/components/Spline.svelte:15— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
ucs03_zkgm::contract::reply (cognitive 44) cosmwasm/app/ucs03-zkgm/src/contract.rs:2491— ucs03_zkgm::contract::reply has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (28 pts), match/switch 6 (12 pts), loops 1 (4 pts) (nesting depth added 25). 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.
ucs03_zkgm::contract::execute (cognitive 29) cosmwasm/app/ucs03-zkgm/src/contract.rs:125— ucs03_zkgm::contract::execute has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 6 (14 pts) (nesting depth added 14). 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.
ucs03_zkgm::contract::acknowledge_internal (cognitive 20) cosmwasm/app/ucs03-zkgm/src/contract.rs:768— ucs03_zkgm::contract::acknowledge_internal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (3 pts), loops 1 (2 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ucs03_zkgm::contract::execute_token_order_v2 (cognitive 19) cosmwasm/app/ucs03-zkgm/src/contract.rs:2133— ucs03_zkgm::contract::execute_token_order_v2 has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4 (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.
ucs03_zkgm::contract::acknowledge_token_order_v2 (cognitive 18) cosmwasm/app/ucs03-zkgm/src/contract.rs:974— ucs03_zkgm::contract::acknowledge_token_order_v2 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (2 pts) (nesting depth added 10). 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.
ucs03_zkgm::contract::execute_token_order_v1 (cognitive 16) cosmwasm/app/ucs03-zkgm/src/contract.rs:1919— ucs03_zkgm::contract::execute_token_order_v1 has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (24 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:884— cosmwasm/app/ucs03-zkgm/src/contract.rs:884-907 | cosmwasm/app/ucs03-zkgm/src/contract.rs:939-962 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) lib/macros/src/lib.rs:487— lib/macros/src/lib.rs:487-510 | lib/macros/src/lib.rs:583-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) lib/voyager-core/src/lib.rs:926— lib/voyager-core/src/lib.rs:926-949 | lib/voyager-core/src/lib.rs:981-1004 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:698— voyager/plugins/event-source/cosmwasm/src/main.rs:698-721 | voyager/plugins/event-source/gno/src/lib.rs:555-578 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:731— voyager/plugins/event-source/cosmwasm/src/main.rs:731-754 | voyager/plugins/event-source/gno/src/lib.rs:588-611 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:764— voyager/plugins/event-source/cosmwasm/src/main.rs:764-787 | voyager/plugins/event-source/gno/src/lib.rs:621-644 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) tools/u/src/vanity/create3.rs:60— tools/u/src/vanity/create3.rs:60-80 | tools/u/src/vanity/wrapped_token.rs:111-131 — before extracting anything, compare `tools/u/src/vanity/create3.rs` and `tools/u/src/vanity/wrapped_token.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 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 (21 lines × 2) tools/union-test/src/lib.rs:1130— tools/union-test/src/lib.rs:1130-1150 | tools/union-test/src/lib.rs:1172-1192 — both copies are in the same file, so extract the block into 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) voyager/plugins/client-update/base/src/main.rs:563— voyager/plugins/client-update/base/src/main.rs:563-583 | voyager/plugins/client-update/bob/src/main.rs:561-581 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/cosmwasm/src/main.rs:1032— voyager/plugins/event-source/cosmwasm/src/main.rs:1032-1052 | voyager/plugins/event-source/cosmwasm/src/main.rs:1184-1204 — both copies are in the same file, so extract the block into 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) voyager/plugins/transaction/aptos/src/main.rs:433— voyager/plugins/transaction/aptos/src/main.rs:433-453 | voyager/plugins/transaction/aptos/src/main.rs:479-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) voyager/src/main.rs:506— voyager/src/main.rs:506-526 | voyager/src/main.rs:560-580 — both copies are in the same file, so extract the block into 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) cosmwasm/cw20-base/src/allowances.rs:137— cosmwasm/cw20-base/src/allowances.rs:137-152 | cosmwasm/cw20-base/src/allowances.rs:210-226 — both copies are in the same file, so extract the block into 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) cosmwasm/cw20-base/src/contract.rs:238— cosmwasm/cw20-base/src/contract.rs:238-253 | cosmwasm/cw20-base/src/contract.rs:340-356 — both copies are in the same file, so extract the block into 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) voyager/plugins/client-update/cometbls/src/main.rs:259— voyager/plugins/client-update/cometbls/src/main.rs:259-274 | voyager/plugins/client-update/cometbls/src/main.rs:404-420 — both copies are in the same file, so extract the block into 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) voyager/plugins/event-source/movement/src/main.rs:488— voyager/plugins/event-source/movement/src/main.rs:488-503 | voyager/plugins/event-source/movement/src/main.rs:516-532 — both copies are in the same file, so extract the block into 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) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1801— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1801-1817 | voyager/plugins/transaction-batch/src/lib.rs:716-731 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–17 lines × 2) lib/ibc-classic-spec/src/lib.rs:656— lib/ibc-classic-spec/src/lib.rs:656-671 | lib/ibc-classic-spec/src/lib.rs:675-691 — both copies are in the same file, so extract the block into 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 × 3) lib/ethereum-sync-protocol-types/src/light_client_update.rs:33— lib/ethereum-sync-protocol-types/src/light_client_update.rs:33-42 | lib/ethereum-sync-protocol-types/src/light_client_update.rs:47-56 | lib/ethereum-sync-protocol-types/src/light_client_update.rs:61-70 — 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) voyager/plugins/event-source/evm/src/main.rs:771— voyager/plugins/event-source/evm/src/main.rs:771-780 | voyager/plugins/event-source/evm/src/main.rs:829-838 | voyager/plugins/event-source/evm/src/main.rs:888-897 — 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) voyager/plugins/sui-ibc-app/src/zkgm.rs:117— voyager/plugins/sui-ibc-app/src/zkgm.rs:117-126 | voyager/plugins/sui-ibc-app/src/zkgm.rs:247-256 | voyager/plugins/sui-ibc-app/src/zkgm.rs:353-362 — 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) cosmwasm/access-managed/src/lib.rs:145— cosmwasm/access-managed/src/lib.rs:145-154 | cosmwasm/on-zkgm-call-proxy/src/lib.rs:157-166 | cosmwasm/proxy-account-factory/src/lib.rs:135-144 — 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) voyager/modules/client/movement/src/main.rs:141— voyager/modules/client/movement/src/main.rs:141-150 | voyager/modules/client/movement/src/main.rs:176-185 | voyager/modules/client/movement/src/main.rs:190-199 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/ibc-classic-spec/src/lib.rs:715— lib/ibc-classic-spec/src/lib.rs:715-724 | lib/ibc-classic-spec/src/lib.rs:730-739 | lib/ibc-classic-spec/src/lib.rs:746-755 — 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) cosmwasm/app/ucs03-zkgm/src/contract.rs:280— cosmwasm/app/ucs03-zkgm/src/contract.rs:280-287 | cosmwasm/core/src/contract.rs:107-114 | cosmwasm/cw-escrow-vault/src/contract.rs:191-198 — 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) voyager/plugins/event-source/evm/src/main.rs:828— voyager/plugins/event-source/evm/src/main.rs:828-835 | voyager/plugins/event-source/evm/src/main.rs:887-894 | voyager/plugins/event-source/evm/src/main.rs:941-948 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) lib/voyager-message/src/call.rs:45— lib/voyager-message/src/call.rs:45-52 | lib/voyager-message/src/callback.rs:21-28 | lib/voyager-message/src/data.rs:25-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) voyager/modules/client/base/src/main.rs:66— voyager/modules/client/base/src/main.rs:66-73 | voyager/modules/client/ethereum/src/main.rs:63-70 | voyager/modules/client/parlia/src/main.rs:63-70 — before extracting anything, compare `voyager/modules/client/base/src/main.rs` and `voyager/modules/client/ethereum/src/main.rs` as WHOLE FILES: this scan already matched 5 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 × 3) voyager/modules/client/proof-lens/src/main.rs:110— voyager/modules/client/proof-lens/src/main.rs:110-117 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:113-120 | voyager/modules/client/state-lens/ics23-smt/src/main.rs:110-117 — before extracting anything, compare `voyager/modules/client/proof-lens/src/main.rs` and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/cw20-base/src/contract.rs:246— cosmwasm/cw20-base/src/contract.rs:246-254 | cosmwasm/cw20-base/src/contract.rs:319-326 | cosmwasm/cw20-base/src/contract.rs:349-357 — 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.
Cmd::run (cognitive 81) tools/u/src/vanity/create3.rs:38— Cmd::run has cognitive complexity 81 (threshold 15). Drivers by points: if/else 30 (65 pts), boolean chains 8, loops 5 (8 pts) (nesting depth added 38). 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.
Cmd::run (cognitive 71) tools/u/src/vanity/wrapped_token.rs:88— Cmd::run has cognitive complexity 71 (threshold 15). Drivers by points: if/else 32 (58 pts), boolean chains 8, loops 4 (5 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cmd::run (cognitive 19) tools/u/src/vanity/instantiate2_address.rs:31— Cmd::run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 5 (8 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.
Cmd::run (cognitive 17) tools/u/src/zkgm/predict_proxy_account_address.rs:54— Cmd::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (7 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cmd::run (cognitive 17) tools/u/src/zkgm/predict_wrapped_token.rs:139— Cmd::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (7 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (33 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:1756— cosmwasm/app/ucs03-zkgm/src/contract.rs:1756-1788 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1828-1860 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (33 lines × 2) cosmwasm/lightclient/movement/src/client.rs:225— cosmwasm/lightclient/movement/src/client.rs:225-257 | cosmwasm/lightclient/state-lens-ics23-smt/src/client.rs:161-193 — 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 lines × 2) lib/voyager-vm/src/in_memory.rs:63— lib/voyager-vm/src/in_memory.rs:63-95 | lib/voyager-vm/src/in_memory.rs:147-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 (33 lines × 2) voyager/modules/proof/movement/src/main.rs:198— voyager/modules/proof/movement/src/main.rs:198-230 | voyager/modules/state/movement/src/main.rs:303-335 — before extracting anything, compare `voyager/modules/proof/movement/src/main.rs` and `voyager/modules/state/movement/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (33 lines × 2) voyager/plugins/event-source/gno/src/lib.rs:1100— voyager/plugins/event-source/gno/src/lib.rs:1100-1132 | voyager/plugins/event-source/gno/src/lib.rs:1198-1230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) lib/gno-verifier/src/verify.rs:93— lib/gno-verifier/src/verify.rs:93-117 | lib/tendermint-verifier/src/verify.rs:94-118 — before extracting anything, compare `lib/gno-verifier/src/verify.rs` and `lib/tendermint-verifier/src/verify.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (25 lines × 2) lib/gno-verifier/src/verify.rs:243— lib/gno-verifier/src/verify.rs:243-267 | lib/tendermint-verifier/src/verify.rs:149-173 — before extracting anything, compare `lib/gno-verifier/src/verify.rs` and `lib/tendermint-verifier/src/verify.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (25 lines × 2) voyager/modules/client-bootstrap/proof-lens/src/main.rs:137— voyager/modules/client-bootstrap/proof-lens/src/main.rs:137-161 | voyager/modules/client-bootstrap/state-lens/ics23-ics23/src/main.rs:136-160 — before extracting anything, compare `voyager/modules/client-bootstrap/proof-lens/src/main.rs` and `voyager/modules/client-bootstrap/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (25 lines × 2) voyager/plugins/client-update/bob/src/main.rs:386— voyager/plugins/client-update/bob/src/main.rs:386-410 | voyager/plugins/client-update/bob/src/main.rs:503-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:606— voyager/plugins/event-source/cosmwasm/src/main.rs:606-630 | voyager/plugins/event-source/gno/src/lib.rs:463-487 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (23 lines × 2) tools/u/src/vanity/create3.rs:237— tools/u/src/vanity/create3.rs:237-259 | tools/u/src/vanity/instantiate2_address.rs:149-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (23 lines × 2) voyager/modules/client-bootstrap/base/src/main.rs:132— voyager/modules/client-bootstrap/base/src/main.rs:132-154 | voyager/modules/client-bootstrap/bob/src/main.rs:132-154 — before extracting anything, compare `voyager/modules/client-bootstrap/base/src/main.rs` and `voyager/modules/client-bootstrap/bob/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (23 lines × 2) voyager/modules/state/movement/src/client.rs:161— voyager/modules/state/movement/src/client.rs:161-183 | voyager/plugins/event-source/movement/src/client.rs:161-183 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (23 lines × 2) voyager/modules/state/movement/src/client.rs:277— voyager/modules/state/movement/src/client.rs:277-299 | voyager/plugins/event-source/movement/src/client.rs:277-299 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (23 lines × 2) voyager/plugins/client-update/base/src/main.rs:178— voyager/plugins/client-update/base/src/main.rs:178-200 | voyager/plugins/client-update/bob/src/main.rs:171-193 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/state/movement/src/client.rs:371— voyager/modules/state/movement/src/client.rs:371-390 | voyager/plugins/event-source/movement/src/client.rs:371-390 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/client-update/arbitrum/src/main.rs:822— voyager/plugins/client-update/arbitrum/src/main.rs:822-841 | voyager/plugins/client-update/arbitrum/src/main.rs:937-956 — both copies are in the same file, so extract the block into 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) voyager/plugins/event-source/cosmwasm/src/main.rs:923— voyager/plugins/event-source/cosmwasm/src/main.rs:923-942 | voyager/plugins/event-source/cosmwasm/src/main.rs:980-999 — both copies are in the same file, so extract the block into 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) voyager/plugins/event-source/gno/src/lib.rs:1173— voyager/plugins/event-source/gno/src/lib.rs:1173-1192 | voyager/plugins/event-source/gno/src/lib.rs:1271-1290 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) lib/cometbft-types/src/p2p/default_node_info_other.rs:23— lib/cometbft-types/src/p2p/default_node_info_other.rs:23-65 | lib/gno-types/src/node_info_other.rs:23-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 3) cosmwasm/core/src/contract.rs:1369— cosmwasm/core/src/contract.rs:1369-1385 | cosmwasm/core/src/contract.rs:1459-1475 | cosmwasm/core/src/contract.rs:1544-1560 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 3) tools/union-test/src/lib.rs:768— tools/union-test/src/lib.rs:768-784 | tools/union-test/src/lib.rs:814-830 | tools/union-test/src/lib.rs:1081-1097 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 3) voyager/modules/state/cosmwasm/src/main.rs:763— voyager/modules/state/cosmwasm/src/main.rs:763-779 | voyager/modules/state/evm/src/main.rs:804-820 | voyager/modules/state/gno/src/main.rs:763-779 — before extracting anything, compare `voyager/modules/state/cosmwasm/src/main.rs` and `voyager/modules/state/gno/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (17 lines × 3) lib/arbitrum-light-client-types/src/consensus_state.rs:30— lib/arbitrum-light-client-types/src/consensus_state.rs:30-46 | lib/base-light-client-types/src/consensus_state.rs:29-45 | lib/bob-light-client-types/src/consensus_state.rs:29-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (17 lines × 3) lib/voyager-core/src/lib.rs:513— lib/voyager-core/src/lib.rs:513-529 | lib/voyager-core/src/lib.rs:549-565 | lib/voyager-core/src/lib.rs:687-719 — 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) cosmwasm/app/ucs03-zkgm/src/contract.rs:485— cosmwasm/app/ucs03-zkgm/src/contract.rs:485-493 | cosmwasm/app/ucs03-zkgm/src/contract.rs:522-530 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2876-2884 — 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) voyager/plugins/sui-ibc-app/src/zkgm.rs:65— voyager/plugins/sui-ibc-app/src/zkgm.rs:65-73 | voyager/plugins/sui-ibc-app/src/zkgm.rs:198-206 | voyager/plugins/sui-ibc-app/src/zkgm.rs:311-319 — 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) voyager/plugins/sui-ibc-app/src/zkgm.rs:157— voyager/plugins/sui-ibc-app/src/zkgm.rs:157-165 | voyager/plugins/sui-ibc-app/src/zkgm.rs:285-293 | voyager/plugins/sui-ibc-app/src/zkgm.rs:391-399 — 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) voyager/modules/client/gno/src/main.rs:151— voyager/modules/client/gno/src/main.rs:151-159 | voyager/modules/client/state-lens/ics23-smt/src/main.rs:154-162 | voyager/modules/client/tendermint/src/main.rs:151-159 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) lib/ibc-union-spec/src/lib.rs:134— lib/ibc-union-spec/src/lib.rs:134-142 | lib/ibc-union-spec/src/lib.rs:148-156 | lib/ibc-union-spec/src/lib.rs:162-170 — 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) mpc/client/src/ui.rs:138— mpc/client/src/ui.rs:138-144 | mpc/client/src/ui.rs:187-193 | mpc/client/src/ui.rs:199-205 — 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) tools/union-test/src/cosmos.rs:84— tools/union-test/src/cosmos.rs:84-90 | voyager/plugins/attestor/evm/src/main.rs:144-150 | voyager/plugins/transaction/cosmos/src/main.rs:129-135 — before extracting anything, compare `tools/union-test/src/cosmos.rs` and `voyager/plugins/transaction/cosmos/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (7 lines × 3) lib/unionlabs/src/cosmos/ics23/compressed_non_existence_proof.rs:59— lib/unionlabs/src/cosmos/ics23/compressed_non_existence_proof.rs:59-65 | lib/unionlabs/src/cosmos/ics23/non_existence_proof.rs:49-55 | lib/unionlabs/src/union/ics23/non_existence_proof.rs:49-55 — 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) voyager/modules/client/gno/src/main.rs:175— voyager/modules/client/gno/src/main.rs:175-181 | voyager/modules/client/state-lens/ics23-smt/src/main.rs:176-182 | voyager/modules/client/tendermint/src/main.rs:175-181 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) galoisd/cmd/galoisd/cmd/phase1_init.go:779— galoisd/cmd/galoisd/cmd/phase1_init.go:779-785 | galoisd/cmd/galoisd/cmd/phase1_init.go:793-799 | galoisd/cmd/galoisd/cmd/phase1_init.go:809-815 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 2) tools/u/src/vanity/create3.rs:87— tools/u/src/vanity/create3.rs:87-91 | tools/u/src/vanity/wrapped_token.rs:138-142 — before extracting anything, compare `tools/u/src/vanity/create3.rs` and `tools/u/src/vanity/wrapped_token.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) cosmwasm/core/light-client-interface/src/state.rs:18— cosmwasm/core/light-client-interface/src/state.rs:18-22 | cosmwasm/core/src/state.rs:66-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/gno-types/src/block_id.rs:54— lib/gno-types/src/block_id.rs:54-58 | lib/gno-types/src/part_set_header.rs:48-52 — 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) lib/sui-light-client-types/src/checkpoint_summary.rs:119— lib/sui-light-client-types/src/checkpoint_summary.rs:119-123 | lib/sui-light-client-types/src/object.rs:19-23 — 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) voyager/plugins/client-update/cometbls/src/callback.rs:140— voyager/plugins/client-update/cometbls/src/callback.rs:140-144 | voyager/plugins/client-update/cometbls/src/callback.rs:147-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.
No assertions: interrupts on cleanup effect-svelte/src/lib/test/Runtime.svelte.test.ts:50— 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: is interruptible effect-svelte/src/lib/test/Runtime.svelte.test.ts:72— 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: interrupts on cleanup app2/src/lib/utils/effect.svelte.test.ts:42— 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: is interruptible app2/src/lib/utils/effect.svelte.test.ts:64— 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 (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) cosmwasm/core/src/contract.rs:1341— cosmwasm/core/src/contract.rs:1341-1420 | cosmwasm/core/src/contract.rs:1433-1502 | cosmwasm/core/src/contract.rs:1512-1583 | cosmwasm/core/src/contract.rs:1635-1709 — 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) voyager/modules/state/sui/src/main.rs:211— voyager/modules/state/sui/src/main.rs:211-264 | voyager/plugins/client-update/sui/src/main.rs:66-111 | voyager/plugins/transaction/sui/src/main.rs:76-146 | voyager/plugins/transaction/sui/src/main.rs:369-444 — 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) voyager/plugins/sui-ibc-app/src/main.rs:323— voyager/plugins/sui-ibc-app/src/main.rs:323-336 | voyager/plugins/transaction/cosmos/src/main.rs:638-651 | voyager/plugins/transaction/evm/src/main.rs:398-411 | voyager/plugins/transaction/gno/src/main.rs:453-466 — 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) voyager/plugins/transaction/sui/src/move_api.rs:181— voyager/plugins/transaction/sui/src/move_api.rs:181-205 | voyager/plugins/transaction/sui/src/move_api.rs:212-239 | voyager/plugins/transaction/sui/src/move_api.rs:246-271 | voyager/plugins/transaction/sui/src/move_api.rs:278-301 — 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.
Duplicated block (31 lines × 2) lib/gno-verifier/src/verify.rs:33— lib/gno-verifier/src/verify.rs:33-63 | lib/tendermint-verifier/src/verify.rs:37-67 — before extracting anything, compare `lib/gno-verifier/src/verify.rs` and `lib/tendermint-verifier/src/verify.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (31 lines × 2) voyager/plugins/client-update/arbitrum/src/main.rs:520— voyager/plugins/client-update/arbitrum/src/main.rs:520-550 | voyager/plugins/client-update/arbitrum/src/main.rs:606-636 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) voyager/plugins/client-update/base/src/main.rs:421— voyager/plugins/client-update/base/src/main.rs:421-451 | voyager/plugins/client-update/bob/src/main.rs:414-444 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (31 lines × 2) voyager/plugins/transaction/cosmos/src/main.rs:441— voyager/plugins/transaction/cosmos/src/main.rs:441-471 | voyager/plugins/transaction/gno/src/main.rs:336-366 — before extracting anything, compare `voyager/plugins/transaction/cosmos/src/main.rs` and `voyager/plugins/transaction/gno/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (27 lines × 2) cosmwasm/cw20-base/src/allowances.rs:20— cosmwasm/cw20-base/src/allowances.rs:20-46 | cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:23-49 — before extracting anything, compare `cosmwasm/cw20-base/src/allowances.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (27 lines × 2) lib/gno-verifier/src/merkle.rs:11— lib/gno-verifier/src/merkle.rs:11-37 | lib/tendermint-verifier/src/merkle.rs:11-37 — 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 (27 lines × 2) voyager/plugins/event-source/movement/src/main.rs:549— voyager/plugins/event-source/movement/src/main.rs:549-575 | voyager/plugins/event-source/movement/src/main.rs:592-618 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1069— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1069-1095 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1322-1348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) voyager/modules/finality/cometbls/src/main.rs:121— voyager/modules/finality/cometbls/src/main.rs:121-146 | voyager/modules/finality/tendermint/src/main.rs:127-152 — 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 (26 lines × 2) voyager/plugins/client-update/arbitrum/src/main.rs:746— voyager/plugins/client-update/arbitrum/src/main.rs:746-771 | voyager/plugins/client-update/arbitrum/src/main.rs:861-886 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:635— voyager/plugins/event-source/cosmwasm/src/main.rs:635-660 | voyager/plugins/event-source/gno/src/lib.rs:492-517 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (26 lines × 2) galoisd/grpc/bls12381_server.go:290— galoisd/grpc/bls12381_server.go:290-315 | galoisd/grpc/server.go:499-524 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 3) cosmwasm/lightclient/ethereum/src/client.rs:223— cosmwasm/lightclient/ethereum/src/client.rs:223-237 | cosmwasm/lightclient/state-lens-ics23-mpt/src/client.rs:195-209 | cosmwasm/lightclient/trusted-mpt/src/client.rs:156-170 — before extracting anything, compare `cosmwasm/lightclient/ethereum/src/client.rs` and `cosmwasm/lightclient/trusted-mpt/src/client.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 (15 lines × 3) lib/beacon-api-types/src/bellatrix/execution_payload_header.rs:123— lib/beacon-api-types/src/bellatrix/execution_payload_header.rs:123-137 | lib/beacon-api-types/src/capella/execution_payload_header.rs:126-140 | lib/beacon-api-types/src/deneb/execution_payload_header.rs:132-146 — 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 (15 lines × 3) voyager/plugins/event-source/cosmwasm/src/main.rs:1085— voyager/plugins/event-source/cosmwasm/src/main.rs:1085-1099 | voyager/plugins/event-source/cosmwasm/src/main.rs:1153-1167 | voyager/plugins/event-source/gno/src/lib.rs:931-945 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 3) voyager/plugins/transaction-batch/src/call.rs:304— voyager/plugins/transaction-batch/src/call.rs:304-318 | voyager/plugins/transaction-batch/src/call.rs:370-384 | voyager/plugins/transaction-batch/src/call.rs:435-449 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) tools/union-test/src/cosmos.rs:113— tools/union-test/src/cosmos.rs:113-124 | voyager/plugins/attestor/evm/src/main.rs:206-217 | voyager/plugins/transaction/cosmos/src/main.rs:187-198 — before extracting anything, compare `tools/union-test/src/cosmos.rs` and `voyager/plugins/transaction/cosmos/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (12 lines × 3) voyager/modules/client-bootstrap/arbitrum/src/main.rs:193— voyager/modules/client-bootstrap/arbitrum/src/main.rs:193-204 | voyager/modules/client-bootstrap/base/src/main.rs:134-145 | voyager/modules/client-bootstrap/bob/src/main.rs:134-145 — before extracting anything, compare `voyager/modules/client-bootstrap/base/src/main.rs` and `voyager/modules/client-bootstrap/bob/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (12 lines × 3) voyager/modules/state/movement/src/main.rs:338— voyager/modules/state/movement/src/main.rs:338-349 | voyager/modules/state/sui/src/main.rs:405-416 | voyager/plugins/event-source/movement/src/main.rs:804-815 — 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 (12 lines × 3) voyager/plugins/event-source/evm/src/main.rs:784— voyager/plugins/event-source/evm/src/main.rs:784-795 | voyager/plugins/event-source/evm/src/main.rs:842-853 | voyager/plugins/event-source/sui/src/main.rs:379-390 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) drip/src/main.rs:720— drip/src/main.rs:720-730 | drip/src/main.rs:759-769 | drip/src/main.rs:797-807 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) lib/beacon-api-types/src/bellatrix/execution_payload_header.rs:82— lib/beacon-api-types/src/bellatrix/execution_payload_header.rs:82-92 | lib/beacon-api-types/src/capella/execution_payload_header.rs:84-94 | lib/beacon-api-types/src/deneb/execution_payload_header.rs:90-100 — 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) voyager/modules/proof/evm-mpt/src/main.rs:57— voyager/modules/proof/evm-mpt/src/main.rs:57-67 | voyager/modules/proof/parlia/src/main.rs:55-65 | voyager/modules/state/evm/src/main.rs:86-96 — before extracting anything, compare `voyager/modules/proof/evm-mpt/src/main.rs` and `voyager/modules/proof/parlia/src/main.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 × 3) voyager/plugins/client-update/arbitrum/src/main.rs:108— voyager/plugins/client-update/arbitrum/src/main.rs:108-118 | voyager/plugins/client-update/base/src/main.rs:175-185 | voyager/plugins/client-update/bob/src/main.rs:168-178 — before extracting anything, compare `voyager/plugins/client-update/arbitrum/src/main.rs` and `voyager/plugins/client-update/base/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) mpc/client/src/ui.rs:138— mpc/client/src/ui.rs:138-144 | mpc/client/src/ui.rs:163-169 | mpc/client/src/ui.rs:175-181 | mpc/client/src/ui.rs:187-193 — 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) voyager/modules/finality/arbitrum/src/main.rs:91— voyager/modules/finality/arbitrum/src/main.rs:91-97 | voyager/modules/finality/base/src/main.rs:68-74 | voyager/modules/finality/bob/src/main.rs:68-74 | voyager/plugins/client-update/arbitrum/src/main.rs:113-119 — before extracting anything, compare `voyager/modules/finality/base/src/main.rs` and `voyager/modules/finality/bob/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (7 lines × 4) cosmwasm/access-managed/src/lib.rs:101— cosmwasm/access-managed/src/lib.rs:101-107 | cosmwasm/core/src/contract.rs:2220-2226 | cosmwasm/cw-escrow-vault/src/contract.rs:282-288 | cosmwasm/cw-unionversal-token/src/contract.rs:344-350 — before extracting anything, compare `cosmwasm/cw-escrow-vault/src/contract.rs` and `cosmwasm/cw-unionversal-token/src/contract.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) lib/cosmwasm-event/src/lib.rs:8— lib/cosmwasm-event/src/lib.rs:8-14 | lib/macros/src/lib.rs:36-42 | lib/macros/src/lib.rs:1111-1117 | lib/move-bindgen-derive/src/lib.rs:10-16 — 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.
Duplicated block (6 lines × 3) cosmwasm/app/ucs03-zkgm/src/contract.rs:3103— cosmwasm/app/ucs03-zkgm/src/contract.rs:3103-3108 | cosmwasm/cw-escrow-vault/src/contract.rs:64-69 | cosmwasm/cw-unionversal-token/src/contract.rs:94-99 — before extracting anything, compare `cosmwasm/cw-escrow-vault/src/contract.rs` and `cosmwasm/cw-unionversal-token/src/contract.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) lib/voyager-vm/src/in_memory.rs:63— lib/voyager-vm/src/in_memory.rs:63-68 | lib/voyager-vm/src/in_memory.rs:147-152 | lib/voyager-vm/src/in_memory.rs:251-256 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) voyager/modules/client/proof-lens/src/main.rs:155— voyager/modules/client/proof-lens/src/main.rs:155-160 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:158-163 | voyager/modules/client/state-lens/ics23-mpt/src/main.rs:164-169 — before extracting anything, compare `voyager/modules/client/proof-lens/src/main.rs` and `voyager/modules/client/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/gno/src/main.rs:38— voyager/modules/client/gno/src/main.rs:38-43 | voyager/modules/client/state-lens/ics23-smt/src/main.rs:38-43 | voyager/modules/client/tendermint/src/main.rs:38-43 — before extracting anything, compare `voyager/modules/client/gno/src/main.rs` and `voyager/modules/client/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Low cohesion: TestContext (LCOM4 12) tools/union-test/src/lib.rs:471— TestContext's methods fall into 12 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 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WorkerClient (LCOM4 6) lib/voyager-plugin-protocol/src/lib.rs:178— WorkerClient's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Cache (LCOM4 4) lib/voyager-core/src/cache.rs:16— Cache's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Module (LCOM4 4) voyager/plugins/transaction/gno/src/main.rs:53— Module's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×3
Modal dialog does not manage focus app2/src/lib/components/ui/Modal.svelte:65— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus app2/src/lib/components/ui/Modal.svelte:73— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus app2/src/lib/components/ui/Wallet/connect/metamask-mobile-alert.svelte:23— This <div role="alertdialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Hotspot: tools/u/src/main.rs tools/u/src/main.rs:114— tools/u/src/main.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in u::main at line 114. 1 of those changes was a fix/bug commit, 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-04-26..2026-07-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-26 13:20:01 -05:00' --until='2026-07-25 13:20:01 -05:00' --full-history --no-merges -- tools/u/src/main.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: voyager/plugins/event-source/gno/src/lib.rs voyager/plugins/event-source/gno/src/lib.rs:446— voyager/plugins/event-source/gno/src/lib.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Module::make_chain_event at line 446. 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-04-26..2026-07-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-26 13:20:01 -05:00' --until='2026-07-25 13:20:01 -05:00' --full-history --no-merges -- voyager/plugins/event-source/gno/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: uniond/app/upgrades/v1_3_0/upgrade.go uniond/app/upgrades/v1_3_0/upgrade.go:61— uniond/app/upgrades/v1_3_0/upgrade.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in v1_3_0.CreateUpgradeHandler at line 61. 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-04-26..2026-07-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-26 13:20:01 -05:00' --until='2026-07-25 13:20:01 -05:00' --full-history --no-merges -- uniond/app/upgrades/v1_3_0/upgrade.go`: 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.
HackComment ts-sdk/src/ucs03/fungible-asset-order.ts:329— // HACK: special cased for muno for now — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment ts-sdk/src/ucs03/fungible-asset-order.ts:457— // HACK: special cased for muno for now — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment cosmwasm/app/ucs03-zkgm/src/contract.rs:3139— // HACK(benluelo): This previously returned hex bytes, but was accidentally changed. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Duplicated block (40 lines × 2) cosmwasm/cw20-base/src/allowances.rs:56— cosmwasm/cw20-base/src/allowances.rs:56-95 | cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:60-99 — before extracting anything, compare `cosmwasm/cw20-base/src/allowances.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (40 lines × 2) voyager/modules/client-bootstrap/proof-lens/src/main.rs:54— voyager/modules/client-bootstrap/proof-lens/src/main.rs:54-93 | voyager/modules/client-bootstrap/state-lens/ics23-ics23/src/main.rs:61-100 — before extracting anything, compare `voyager/modules/client-bootstrap/proof-lens/src/main.rs` and `voyager/modules/client-bootstrap/state-lens/ics23-ics23/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (40 lines × 2) voyager/modules/client/cometbls/src/main.rs:341— voyager/modules/client/cometbls/src/main.rs:341-380 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:255-294 — 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 × 3) cosmwasm/app/ucs03-zkgm/src/contract.rs:898— cosmwasm/app/ucs03-zkgm/src/contract.rs:898-913 | cosmwasm/app/ucs03-zkgm/src/contract.rs:953-968 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1126-1141 — 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) voyager/modules/state/sui/src/main.rs:218— voyager/modules/state/sui/src/main.rs:218-233 | voyager/plugins/client-update/sui/src/main.rs:79-94 | voyager/plugins/transaction/sui/src/main.rs:95-110 — 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 (16 lines × 3) voyager/plugins/event-source/cosmwasm/src/main.rs:792— voyager/plugins/event-source/cosmwasm/src/main.rs:792-807 | voyager/plugins/event-source/cosmwasm/src/main.rs:840-855 | voyager/plugins/event-source/cosmwasm/src/main.rs:888-903 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) voyager/plugins/client-update/berachain/src/main.rs:173— voyager/plugins/client-update/berachain/src/main.rs:173-186 | voyager/plugins/client-update/ethermint/src/main.rs:149-162 | voyager/plugins/client-update/tendermint/src/main.rs:152-165 — before extracting anything, compare `voyager/plugins/client-update/ethermint/src/main.rs` and `voyager/plugins/client-update/tendermint/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) voyager/plugins/event-source/evm/src/main.rs:676— voyager/plugins/event-source/evm/src/main.rs:676-689 | voyager/plugins/event-source/evm/src/main.rs:714-727 | voyager/plugins/event-source/evm/src/main.rs:752-765 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) voyager/modules/state/evm/src/main.rs:494— voyager/modules/state/evm/src/main.rs:494-507 | voyager/modules/state/evm/src/main.rs:575-588 | voyager/modules/state/evm/src/main.rs:655-668 — 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–13 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:1290— cosmwasm/app/ucs03-zkgm/src/contract.rs:1290-1302 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2761-2771 — both copies are in the same file, so extract the block into 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 × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:1800— cosmwasm/app/ucs03-zkgm/src/contract.rs:1800-1810 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1938-1950 — both copies are in the same file, so extract the block into 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 × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:2179— cosmwasm/app/ucs03-zkgm/src/contract.rs:2179-2189 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2258-2270 — both copies are in the same file, so extract the block into 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) tools/u/src/main.rs:148— tools/u/src/main.rs:148-159 | tools/u/src/main.rs:177-187 — both copies are in the same file, so extract the block into 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) voyager/modules/state/sui/src/main.rs:114— voyager/modules/state/sui/src/main.rs:114-124 | voyager/plugins/sui-packet-timeout/src/main.rs:419-430 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11–12 lines × 2) voyager/src/main.rs:494— voyager/src/main.rs:494-504 | voyager/src/main.rs:547-558 — both copies are in the same file, so extract the block into 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 × 3) cosmwasm/app/ucs03-zkgm/src/contract.rs:3512— cosmwasm/app/ucs03-zkgm/src/contract.rs:3512-3516 | cosmwasm/cw20-token-minter/src/contract.rs:313-317 | cosmwasm/cw20-token-minter/src/contract.rs:335-339 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 3) drip/src/main.rs:702— drip/src/main.rs:702-706 | drip/src/main.rs:742-746 | drip/src/main.rs:780-784 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) lib/voyager-core/src/lib.rs:1126— lib/voyager-core/src/lib.rs:1126-1130 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1060-1064 | voyager/plugins/transaction-batch/src/callback.rs:65-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.
Low contrast Tailwind colour pair (3.7:1) app2/src/lib/components/stake/StakingHistoryCard.svelte:83— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.7:1) app2/src/lib/components/stake/StakingHistoryCard.svelte:93— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Cmd::run (cyclomatic 33) tools/u/src/vanity/wrapped_token.rs:88— Cmd::run has cyclomatic complexity 33 (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.
Cmd::run (cyclomatic 32) tools/u/src/vanity/create3.rs:38— Cmd::run 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.
ucs03_zkgm::contract::execute (cyclomatic 29) cosmwasm/app/ucs03-zkgm/src/contract.rs:125— ucs03_zkgm::contract::execute has cyclomatic complexity 29 (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.
ucs03_zkgm::contract::reply (cyclomatic 22) cosmwasm/app/ucs03-zkgm/src/contract.rs:2491— ucs03_zkgm::contract::reply has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cosmwasm_deployer::do_main (cognitive 72) cosmwasm/deployer/src/main.rs:566— cosmwasm_deployer::do_main has cognitive complexity 72 (threshold 15). Drivers by points: if/else 34 (61 pts), loops 3 (8 pts), match/switch 2 (3 pts) (nesting depth added 33). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
cosmwasm_deployer::deploy_full (cognitive 23) cosmwasm/deployer/src/main.rs:1451— cosmwasm_deployer::deploy_full has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 1 (3 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.
InMemoryQueue::process (cognitive 23) lib/voyager-vm/src/in_memory.rs:105— InMemoryQueue::process has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (10 pts), loops 2 (8 pts), if/else 1 (5 pts) (nesting depth added 16). 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.
InMemoryQueue::optimize (cognitive 16) lib/voyager-vm/src/in_memory.rs:211— InMemoryQueue::optimize has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/voyager-plugin/src/lib.rs:86— lib/voyager-plugin/src/lib.rs:86-114 | lib/voyager-plugin/src/lib.rs:123-151 | lib/voyager-plugin/src/lib.rs:160-188 | lib/voyager-plugin/src/lib.rs:197-225 | lib/voyager-plugin/src/lib.rs:234-262 — 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) voyager/plugins/event-source/cosmwasm/src/main.rs:218— voyager/plugins/event-source/cosmwasm/src/main.rs:218-248 | voyager/plugins/event-source/evm/src/main.rs:239-269 | voyager/plugins/event-source/gno/src/lib.rs:175-205 | voyager/plugins/event-source/starknet/src/main.rs:164-194 | voyager/plugins/event-source/sui/src/main.rs:424-444 — 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 (70 lines × 2) voyager/plugins/client-update/proof-lens/src/main.rs:138— voyager/plugins/client-update/proof-lens/src/main.rs:138-207 | voyager/plugins/client-update/state-lens/src/main.rs:148-217 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (70 lines × 2) galoisd/cmd/galoisd/cmd/example_prove.go:127— galoisd/cmd/galoisd/cmd/example_prove.go:127-196 | galoisd/cmd/galoisd/cmd/example_verify.go:101-170 — before extracting anything, compare `galoisd/cmd/galoisd/cmd/example_prove.go` and `galoisd/cmd/galoisd/cmd/example_verify.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/cmd/galoisd/cmd/example_prove.go:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (36 lines × 2) voyager/modules/proof/cosmwasm/src/main.rs:101— voyager/modules/proof/cosmwasm/src/main.rs:101-136 | voyager/modules/proof/ethermint/src/main.rs:106-141 — 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 (36 lines × 2) voyager/modules/state/cosmwasm/src/main.rs:197— voyager/modules/state/cosmwasm/src/main.rs:197-232 | voyager/modules/state/cosmwasm/src/main.rs:326-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 (29 lines × 2) lib/cometbft-types/src/types/commit_sig.rs:151— lib/cometbft-types/src/types/commit_sig.rs:151-179 | lib/cometbft-types/src/types/commit_sig.rs:200-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (29 lines × 2) tools/u/src/arbitrum/v1.rs:40— tools/u/src/arbitrum/v1.rs:40-68 | tools/u/src/arbitrum/v2.rs:45-73 — 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 (28 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:662— voyager/plugins/event-source/cosmwasm/src/main.rs:662-689 | voyager/plugins/event-source/gno/src/lib.rs:519-546 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) uniond/app/upgrades/v1_2_0/upgrade.go:403— uniond/app/upgrades/v1_2_0/upgrade.go:403-430 | uniond/app/upgrades/v1_3_0/upgrade.go:185-212 — `uniond/app/upgrades/v1_2_0/upgrade.go` and `uniond/app/upgrades/v1_3_0/upgrade.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 71 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `uniond/app/upgrades/v1_2_0/upgrade.go:403` 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.
Duplicated block (16 lines × 5) voyager/plugins/event-source/cosmwasm/src/main.rs:1237— voyager/plugins/event-source/cosmwasm/src/main.rs:1237-1252 | voyager/plugins/event-source/cosmwasm/src/main.rs:1324-1339 | voyager/plugins/event-source/cosmwasm/src/main.rs:1410-1425 | voyager/plugins/event-source/gno/src/lib.rs:1181-1196 | voyager/plugins/event-source/gno/src/lib.rs:1279-1294 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 5) lib/voyager-plugin/src/lib.rs:99— lib/voyager-plugin/src/lib.rs:99-114 | lib/voyager-plugin/src/lib.rs:136-151 | lib/voyager-plugin/src/lib.rs:173-188 | lib/voyager-plugin/src/lib.rs:210-225 | lib/voyager-plugin/src/lib.rs:247-262 — 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 (14–15 lines × 2) cosmwasm/cw20-base/src/allowances.rs:105— cosmwasm/cw20-base/src/allowances.rs:105-119 | cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:110-123 — before extracting anything, compare `cosmwasm/cw20-base/src/allowances.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 2) voyager/plugins/transaction-batch/src/call.rs:639— voyager/plugins/transaction-batch/src/call.rs:639-652 | voyager/plugins/transaction-batch/src/call.rs:690-704 — both copies are in the same file, so extract the block into 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–14 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:625— cosmwasm/app/ucs03-zkgm/src/contract.rs:625-636 | cosmwasm/app/ucs03-zkgm/src/contract.rs:803-816 — both copies are in the same file, so extract the block into 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–14 lines × 2) cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs:353— cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs:353-366 | cosmwasm/osmosis-tokenfactory-token-minter/src/contract.rs:368-379 — 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–13 lines × 3) cosmwasm/cw20-base/src/allowances.rs:138— cosmwasm/cw20-base/src/allowances.rs:138-149 | cosmwasm/cw20-base/src/allowances.rs:173-185 | cosmwasm/cw20-base/src/allowances.rs:211-223 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 3) drip/src/main.rs:53— drip/src/main.rs:53-65 | mpc/coordinator/src/main.rs:68-79 | tools/u/src/main.rs:117-129 — 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 (12–13 lines × 2) cosmwasm/cw20-base/src/contract.rs:378— cosmwasm/cw20-base/src/contract.rs:378-390 | cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs:242-253 — before extracting anything, compare `cosmwasm/cw20-base/src/contract.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/state/evm/src/main.rs:516— voyager/modules/state/evm/src/main.rs:516-527 | voyager/modules/state/evm/src/main.rs:677-689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 4) voyager/modules/state/movement/src/client.rs:96— voyager/modules/state/movement/src/client.rs:96-107 | voyager/modules/state/movement/src/client.rs:454-465 | voyager/plugins/event-source/movement/src/client.rs:96-107 | voyager/plugins/event-source/movement/src/client.rs:454-465 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/lightclient/ethereum/src/client.rs:268— cosmwasm/lightclient/ethereum/src/client.rs:268-279 | cosmwasm/lightclient/state-lens-ics23-mpt/src/client.rs:220-231 | cosmwasm/lightclient/state-lens-ics23-smt/src/client.rs:195-206 | cosmwasm/lightclient/trusted-mpt/src/client.rs:204-215 — before extracting anything, compare `cosmwasm/lightclient/ethereum/src/client.rs` and `cosmwasm/lightclient/trusted-mpt/src/client.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 (10 lines × 4) voyager/modules/state/sui/src/main.rs:226— voyager/modules/state/sui/src/main.rs:226-235 | voyager/plugins/client-update/sui/src/main.rs:87-96 | voyager/plugins/transaction/sui/src/main.rs:103-112 | voyager/plugins/transaction/sui/src/main.rs:406-415 — 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.
Duplicated block (10 lines × 4) galoisd/grpc/bls12381_server.go:369— galoisd/grpc/bls12381_server.go:369-378 | galoisd/grpc/bls12381_server.go:430-439 | galoisd/grpc/server.go:593-602 | galoisd/grpc/server.go:644-653 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) voyager/modules/client-bootstrap/arbitrum/src/main.rs:107— voyager/modules/client-bootstrap/arbitrum/src/main.rs:107-115 | voyager/modules/client-bootstrap/base/src/main.rs:69-77 | voyager/modules/client-bootstrap/bob/src/main.rs:69-77 | voyager/modules/client-bootstrap/parlia/src/main.rs:59-67 | voyager/plugins/client-update/parlia/src/main.rs:90-98 — before extracting anything, compare `voyager/modules/client-bootstrap/base/src/main.rs` and `voyager/modules/client-bootstrap/bob/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (9 lines × 5) voyager/plugins/event-source/cosmwasm/src/main.rs:158— voyager/plugins/event-source/cosmwasm/src/main.rs:158-166 | voyager/plugins/event-source/evm/src/main.rs:108-116 | voyager/plugins/event-source/gno/src/lib.rs:128-136 | voyager/plugins/event-source/starknet/src/main.rs:115-123 | voyager/plugins/event-source/sui/src/main.rs:91-99 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/evm/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/cw20-base/src/allowances.rs:146— cosmwasm/cw20-base/src/allowances.rs:146-154 | cosmwasm/cw20-base/src/allowances.rs:220-228 | cosmwasm/cw20-base/src/contract.rs:243-251 | cosmwasm/cw20-base/src/contract.rs:346-354 — 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 (9 lines × 4) cosmwasm/lightclient/proof-lens/src/client.rs:136— cosmwasm/lightclient/proof-lens/src/client.rs:136-144 | cosmwasm/lightclient/state-lens-ics23-ics23/src/client.rs:113-121 | cosmwasm/lightclient/state-lens-ics23-mpt/src/client.rs:88-96 | cosmwasm/lightclient/state-lens-ics23-smt/src/client.rs:90-98 — 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 × 7) voyager/modules/client-bootstrap/arbitrum/src/main.rs:110— voyager/modules/client-bootstrap/arbitrum/src/main.rs:110-117 | voyager/modules/client-bootstrap/bob/src/main.rs:72-79 | voyager/modules/client-bootstrap/ethereum/src/main.rs:112-119 | voyager/modules/client-bootstrap/parlia/src/main.rs:62-69 | voyager/modules/client-bootstrap/trusted-mpt/src/main.rs:57-64 | voyager/modules/finality/ethereum/src/main.rs:155-162 | voyager/modules/finality/trusted-evm/src/main.rs:51-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times.
Duplicated block (8 lines × 7) voyager/plugins/transaction/sui/src/move_api.rs:34— voyager/plugins/transaction/sui/src/move_api.rs:34-41 | voyager/plugins/transaction/sui/src/move_api.rs:58-65 | voyager/plugins/transaction/sui/src/move_api.rs:83-90 | voyager/plugins/transaction/sui/src/move_api.rs:106-113 | voyager/plugins/transaction/sui/src/move_api.rs:132-139 | voyager/plugins/transaction/sui/src/move_api.rs:157-164 | voyager/plugins/transaction/sui/src/move_api.rs:308-315 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) voyager/plugins/sui-ibc-app/src/main.rs:329— voyager/plugins/sui-ibc-app/src/main.rs:329-336 | voyager/plugins/transaction/cosmos/src/main.rs:644-651 | voyager/plugins/transaction/evm/src/main.rs:404-411 | voyager/plugins/transaction/gno/src/main.rs:459-466 — before extracting anything, compare `voyager/plugins/transaction/cosmos/src/main.rs` and `voyager/plugins/transaction/gno/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (8 lines × 4) voyager/plugins/transaction/sui/src/move_api.rs:182— voyager/plugins/transaction/sui/src/move_api.rs:182-189 | voyager/plugins/transaction/sui/src/move_api.rs:213-220 | voyager/plugins/transaction/sui/src/move_api.rs:247-254 | voyager/plugins/transaction/sui/src/move_api.rs:279-286 — 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–8 lines × 2) voyager/plugins/packet-timeout/src/main.rs:104— voyager/plugins/packet-timeout/src/main.rs:104-110 | voyager/plugins/sui-packet-timeout/src/main.rs:131-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 (7–8 lines × 2) galoisd/grpc/bls12381_server.go:341— galoisd/grpc/bls12381_server.go:341-347 | galoisd/grpc/server.go:565-572 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/grpc/bls12381_server.go:341` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
Duplicated block (5 lines × 4) mpc/client/src/ui.rs:90— mpc/client/src/ui.rs:90-94 | mpc/client/src/ui.rs:138-142 | mpc/client/src/ui.rs:187-191 | mpc/client/src/ui.rs:199-203 — 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) voyager/plugins/sui-ibc-app/src/main.rs:324— voyager/plugins/sui-ibc-app/src/main.rs:324-328 | voyager/plugins/transaction/cosmos/src/main.rs:639-643 | voyager/plugins/transaction/evm/src/main.rs:399-403 | voyager/plugins/transaction/gno/src/main.rs:454-458 — before extracting anything, compare `voyager/plugins/transaction/cosmos/src/main.rs` and `voyager/plugins/transaction/gno/src/main.rs` as WHOLE FILES: this scan already matched 5 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.
Sync-over-async blocking sentinel2/src/helpers.ts:75— `Fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking sentinel2/src/helpers.ts:78— `Fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
R10 · Code Duplication· Duplicated block with local edits (104 matched lines × 2 locations) · ×2
Duplicated block with local edits (104 matched lines × 2 locations) app2/src/lib/dashboard/stores/achievements.svelte.ts:30— app2/src/lib/dashboard/stores/achievements.svelte.ts:30 · app2/src/lib/dashboard/stores/missions.svelte.ts:9 — the two spans are one implementation copied and then locally edited — 540 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (104 matched lines × 2 locations) app2/src/lib/transfer/multisig/services/filling.ts:26— app2/src/lib/transfer/multisig/services/filling.ts:26 · app2/src/lib/transfer/normal/services/filling.ts:21 — the two spans are one implementation copied and then locally edited — 862 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (56 lines × 2 locations) typescript-sdk/playground/holesky-to-sepolia-legacy.ts:12— typescript-sdk/playground/holesky-to-sepolia-legacy.ts:12 · typescript-sdk/playground/sepolia-to-holesky-legacy.ts:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (56 lines × 2 locations) typescript-sdk/playground/union-to-arbitrum-legacy.ts:14— typescript-sdk/playground/union-to-arbitrum-legacy.ts:14 · typescript-sdk/playground/union-to-berachain-legacy.ts:14 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×2
Duplicated block with local edits (42 matched lines × 2 locations) app2/src/routes/explorer/orbital/charts/AssetVolumeChart.svelte:18— app2/src/routes/explorer/orbital/charts/AssetVolumeChart.svelte:18 · app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte:15 — the two spans are one implementation copied and then locally edited — 216 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (42 matched lines × 2 locations) app2/src/routes/explorer/orbital/charts/PopularRoutesChart.svelte:15— app2/src/routes/explorer/orbital/charts/PopularRoutesChart.svelte:15 · app2/src/routes/explorer/orbital/charts/WalletActivityChart.svelte:19 — the two spans are one implementation copied and then locally edited — 264 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (39 lines × 2 locations) ts-sdk/src/Aptos.ts:22— ts-sdk/src/Aptos.ts:22 · ts-sdk/src/utils/aptos-wallet.ts:8 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (39 lines × 2 locations) ts-sdk/src/Utils.ts:91— ts-sdk/src/Utils.ts:91 · ts-sdk/src/utils/extract-error-details.ts:1 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Dead file (~266 LoC) app2/src/lib/wallet/cosmos/config.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/cosmos/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~266 LoC) app2/src/lib/wallet/evm/config.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/evm/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~263 LoC) app2/src/lib/transfer/normal/index.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/index.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~263 LoC) app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Swallowed exception (empty catch) sentinel2/src/check-balances.ts:104— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) app2/src/lib/wallet/sui/config.svelte.ts:243— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (caught, then discarded) 11-cometbls/store.go:169— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 11-cometbls/store.go:316— `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC1 · Text alternatives· <video> without a captions track · ×1
<video> without a captions track app2/src/routes/yaps/YappersHero.svelte:91— Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
Empty <h3> heading site/src/components/typography/h3.astro:1— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
voyager::do_main (cyclomatic 52) voyager/src/main.rs:88— voyager::do_main has cyclomatic complexity 52 (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.
v1_2_0.CreateUpgradeHandler (cyclomatic 47) uniond/app/upgrades/v1_2_0/upgrade.go:55— v1_2_0.CreateUpgradeHandler has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to one function literal inside it that branches (line 56). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
cosmwasm_deployer::do_main (cyclomatic 43) cosmwasm/deployer/src/main.rs:566— cosmwasm_deployer::do_main has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App.prepForZeroHeightGenesis (cyclomatic 32) uniond/app/export.go:54— App.prepForZeroHeightGenesis has cyclomatic complexity 32 (threshold 15). Of this number, 22 points are the body's own statements and 10 belong to 4 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.
JsonSchemaToNixosModuleOptions::visit_schema_object (cyclomatic 30) tools/json-schema-to-nixos-module-options/src/main.rs:61— JsonSchemaToNixosModuleOptions::visit_schema_object has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
matrix-cover.initWebGL (cyclomatic 30) site/src/lib/matrix-cover.ts:169— matrix-cover.initWebGL has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (drawScene, onResize, updateMousePosition, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
errors.mapSupabaseErrorToCustomError (cyclomatic 28) app2/src/lib/dashboard/errors.ts:57— errors.mapSupabaseErrorToCustomError has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
proverServerBls12381.Poll (cyclomatic 27) galoisd/grpc/bls12381_server.go:99— proverServerBls12381.Poll has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 121, 262). 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.
import-contentful-export.renderNode (cyclomatic 25) site/scripts/import-contentful-export.mjs:257— import-contentful-export.renderNode has cyclomatic complexity 25 (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.
client.createCosmosClient (cyclomatic 25) REDACTED:49— client.createCosmosClient has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 136, 51, 100). 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.
cmd.initTestnetFiles (cyclomatic 23) REDACTED:163— cmd.initTestnetFiles has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Handler::call (cyclomatic 22) lib/voyager-core/src/lib.rs:791— Handler::call has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
move_bindgen::main (cyclomatic 20) tools/move-bindgen/src/main.rs:22— move_bindgen::main 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.
u::main (cyclomatic 20) tools/u/src/main.rs:114— u::main has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
proverServer.Poll (cyclomatic 20) galoisd/grpc/server.go:299— proverServer.Poll has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 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.
sorted-balances.svelte.getSortedTokens (cyclomatic 20) app2/src/lib/stores/sorted-balances.svelte.ts:28— sorted-balances.svelte.getSortedTokens has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 75). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
check-filling.getFillingState (cyclomatic 20) app2/src/lib/transfer/shared/services/filling/check-filling.ts:59— check-filling.getFillingState has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 73). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
voyager_vm::process (cyclomatic 19) lib/voyager-vm/src/lib.rs:242— voyager_vm::process has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
mpc_client::ui::run_ui (cyclomatic 19) mpc/client/src/ui.rs:209— mpc_client::ui::run_ui has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
macros::derive_debug (cyclomatic 18) lib/macros/src/lib.rs:44— macros::derive_debug has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
EngineBuilder::build (cyclomatic 18) lib/voyager-core/src/lib.rs:397— EngineBuilder::build 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.
Contributor.updateState (cyclomatic 18) ceremony/src/lib/state/contributor.svelte.ts:292— Contributor.updateState has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Op::normalize::go (cyclomatic 17) lib/voyager-vm/src/lib.rs:383— Op::normalize::go has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
tidy::main (cyclomatic 17) tools/tidy/src/main.rs:20— tidy::main 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.
cmd.ExampleVerifyCmd (cyclomatic 17) galoisd/cmd/galoisd/cmd/example_verify.go:31— cmd.ExampleVerifyCmd has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 36). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
cmd.ReadPtau (cyclomatic 17) galoisd/cmd/galoisd/cmd/phase1_init.go:272— cmd.ReadPtau has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
cmd.ExampleProveCmd (cyclomatic 16) galoisd/cmd/galoisd/cmd/example_prove.go:56— cmd.ExampleProveCmd has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 61). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
grpc.loadOrCreateBls12381 (cyclomatic 16) galoisd/grpc/bls12381_server.go:329— grpc.loadOrCreateBls12381 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.
examples-to-pages.examplesToPages (cyclomatic 16) docs/integrations/examples-to-pages.ts:26— examples-to-pages.examplesToPages has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 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.
client.createEvmClient (cyclomatic 16) typescript-sdk/src/evm/client.ts:68— client.createEvmClient has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 252, 131, 214, …). 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.
ucs03-channels.getQuoteToken (cyclomatic 16) typescript-sdk/src/query/offchain/ucs03-channels.ts:66— ucs03-channels.getQuoteToken has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HackComment repeated across 14 files typescript-sdk/playground/babylon-to-holesky.ts:12— The identical HackComment appears in 14 files (14 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 14 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// hack to encode bigints to json". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
v1_2_0.CreateUpgradeHandler (cognitive 88) uniond/app/upgrades/v1_2_0/upgrade.go:55— v1_2_0.CreateUpgradeHandler has cognitive complexity 88 (threshold 15). Drivers by points: if/else 42 (78 pts), loops 6 (10 pts) (nesting depth added 40). None of this is in the body itself: all 88 points belong to one function literal inside it that branches (line 56). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
voyager::do_main (cognitive 65) voyager/src/main.rs:88— voyager::do_main has cognitive complexity 65 (threshold 15). Drivers by points: if/else 18 (37 pts), match/switch 14 (28 pts) (nesting depth added 33). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JsonSchemaToNixosModuleOptions::visit_schema_object (cognitive 61) tools/json-schema-to-nixos-module-options/src/main.rs:61— JsonSchemaToNixosModuleOptions::visit_schema_object has cognitive complexity 61 (threshold 15). Drivers by points: match/switch 7 (28 pts), if/else 8 (26 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 42). 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.
matrix-cover.initWebGL (cognitive 42) site/src/lib/matrix-cover.ts:169— matrix-cover.initWebGL has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (31 pts), loops 4 (5 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 13). Most of this is not in the body itself: 9 of the 42 points are its own statements and the rest belongs to 6 function items inside it that branch (drawScene, onResize, initShaderProgram, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
move_bindgen::main (cognitive 41) tools/move-bindgen/src/main.rs:22— move_bindgen::main has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 9 (16 pts), boolean chains 3 (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.
cmd.initTestnetFiles (cognitive 40) REDACTED:163— cmd.initTestnetFiles has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19 (35 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proverServerBls12381.Poll (cognitive 39) galoisd/grpc/bls12381_server.go:99— proverServerBls12381.Poll has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (32 pts), loops 2 (4 pts), match/switch 2 (3 pts) (nesting depth added 12). Of this number, 19 points are the body's own statements and 20 belong to 2 function literals inside it that branch. 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.
App.prepForZeroHeightGenesis (cognitive 39) uniond/app/export.go:54— App.prepForZeroHeightGenesis has cognitive complexity 39 (threshold 15). Drivers by points: if/else 24 (32 pts), loops 6, boolean chains 1 (nesting depth added 8). Of this number, 29 points are the body's own statements and 10 belong to 4 function literals inside it that branch. 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.
v1_3_0.CreateUpgradeHandler (cognitive 33) uniond/app/upgrades/v1_3_0/upgrade.go:61— v1_3_0.CreateUpgradeHandler has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 3 (6 pts) (nesting depth added 18). None of this is in the body itself: all 33 points belong to one function literal inside it that branches (line 62). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Handler::call (cognitive 32) lib/voyager-core/src/lib.rs:791— Handler::call has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 5 (10 pts) (nesting depth added 14). 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.
client.createCosmosClient (cognitive 32) REDACTED:49— client.createCosmosClient has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (24 pts), ternaries 4 (7 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 32 points belong to 3 function literals inside it that branch (lines 136, 51, 100). 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.
FromRawAttrs::parse (cognitive 31) lib/macros/src/lib.rs:827— FromRawAttrs::parse has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (28 pts), match/switch 1 (2 pts), 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.
voyager_vm::process (cognitive 31) lib/voyager-vm/src/lib.rs:242— voyager_vm::process has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 6 (15 pts) (nesting depth added 18). 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.
tidy::main (cognitive 31) tools/tidy/src/main.rs:20— tidy::main has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 3 (6 pts), loops 3 (5 pts), boolean chains 2 (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.
proverServer.Poll (cognitive 31) galoisd/grpc/server.go:299— proverServer.Poll has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (25 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 11). Of this number, 19 points are the body's own statements and 12 belong to 2 function literals inside it that branch. 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.
grpc.loadOrCreateBls12381 (cognitive 30) galoisd/grpc/bls12381_server.go:329— grpc.loadOrCreateBls12381 has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (30 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.
mpc_coordinator::main (cognitive 29) mpc/coordinator/src/main.rs:66— mpc_coordinator::main has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (21 pts), match/switch 3 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 16). 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.
cw20_token_minter::contract::execute (cognitive 28) cosmwasm/cw20-token-minter/src/contract.rs:87— cw20_token_minter::contract::execute has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 4 (8 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
grpc.loadOrCreate (cognitive 28) galoisd/grpc/server.go:559— grpc.loadOrCreate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (28 pts) (nesting depth added 15). 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.
drip::poll_loop (cognitive 27) drip/src/main.rs:127— drip::poll_loop has cognitive complexity 27 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 4 (9 pts), match/switch 2 (6 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Model::parse (cognitive 24) lib/macros/src/lib.rs:754— Model::parse has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 3 (8 pts), 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.
cw_unionversal_token::contract::execute (cognitive 23) cosmwasm/cw-unionversal-token/src/contract.rs:110— cw_unionversal_token::contract::execute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 5 (10 pts), loops 1 (3 pts) (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.
EngineBuilder::build (cognitive 23) lib/voyager-core/src/lib.rs:397— EngineBuilder::build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 4, match/switch 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
voyager_plugin_protocol::lazarus_pit (cognitive 22) lib/voyager-plugin-protocol/src/lib.rs:648— voyager_plugin_protocol::lazarus_pit has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 1 (4 pts), loops 2 (3 pts) (nesting depth added 14). 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.
cmd.ExampleVerifyCmd (cognitive 22) galoisd/cmd/galoisd/cmd/example_verify.go:31— cmd.ExampleVerifyCmd has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), loops 2 (nesting depth added 6). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 36). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
run-ibc-checks.checkPackets (cognitive 22) sentinel2/src/run-ibc-checks.ts:116— run-ibc-checks.checkPackets has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 12). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 122). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
cw_escrow_vault::contract::execute (cognitive 21) cosmwasm/cw-escrow-vault/src/contract.rs:80— cw_escrow_vault::contract::execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 3 (5 pts), loops 1 (3 pts) (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.
Mutation::send (cognitive 21) drip/src/main.rs:543— Mutation::send has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 2, 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.
cmd.ExampleProveCmd (cognitive 21) galoisd/cmd/galoisd/cmd/example_prove.go:56— cmd.ExampleProveCmd has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 2 (nesting depth added 6). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 61). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
errors.mapSupabaseErrorToCustomError (cognitive 21) app2/src/lib/dashboard/errors.ts:57— errors.mapSupabaseErrorToCustomError has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (10 pts), match/switch 1 (nesting depth added 5). 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.
cmd.ReadPtau (cognitive 20) galoisd/cmd/galoisd/cmd/phase1_init.go:272— cmd.ReadPtau has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (19 pts), loops 1 (nesting depth added 4). 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.
sorted-balances.svelte.getSortedTokens (cognitive 20) app2/src/lib/stores/sorted-balances.svelte.ts:28— sorted-balances.svelte.getSortedTokens has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 9, ternaries 1 (2 pts) (nesting depth added 1). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 75). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
RlpNodeCodec::decode_plan (cognitive 19) lib/evm-storage-verifier/src/rlp_node_codec.rs:134— RlpNodeCodec::decode_plan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 8). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
PgQueue::optimize (cognitive 19) REDACTED:567— PgQueue::optimize has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (11 pts), if/else 2 (5 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MakeTransactionBatchesWithUpdate::call (cognitive 19) voyager/plugins/transaction-batch/src/call.rs:55— MakeTransactionBatchesWithUpdate::call has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (5 pts), loops 1 (2 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
client.createSupabaseClient (cognitive 19) ceremony/src/lib/supabase/client.ts:7— client.createSupabaseClient has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 19 points belong to 4 function items inside it that branch (getClient::refreshSession, getClient, a function literal at line 65, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
voyager_sui_ibc_app_plugin_zkgm::zkgm::register_tokens_if_zkgm (cognitive 18) voyager/plugins/sui-ibc-app/src/zkgm.rs:851— voyager_sui_ibc_app_plugin_zkgm::zkgm::register_tokens_if_zkgm has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dashboard.handleAuthChange (cognitive 18) app2/src/lib/dashboard/stores/user.svelte.ts:230— Dashboard.handleAuthChange has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (18 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.
check-filling.getFillingState (cognitive 18) app2/src/lib/transfer/shared/services/filling/check-filling.ts:59— check-filling.getFillingState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, boolean chains 4. Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 73). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
examples-to-pages.examplesToPages (cognitive 18) docs/integrations/examples-to-pages.ts:26— examples-to-pages.examplesToPages has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, loops 1 (2 pts), ternaries 2, error handling 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 8 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.
client.createEvmClient (cognitive 18) typescript-sdk/src/evm/client.ts:68— client.createEvmClient has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 2 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 252, 131, 214, …). 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.
ucs03-channels.getQuoteToken (cognitive 18) typescript-sdk/src/query/offchain/ucs03-channels.ts:66— ucs03-channels.getQuoteToken has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ics23::verify::verify_non_existence (cognitive 17) lib/ics23/src/verify.rs:109— ics23::verify::verify_non_existence has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, match/switch 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.
Op::normalize::go (cognitive 17) lib/voyager-vm/src/lib.rs:383— Op::normalize::go has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 6 (13 pts), if/else 2 (4 pts) (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
cmd.NewTestnetMultiNodeCmd (cognitive 17) REDACTED:67— cmd.NewTestnetMultiNodeCmd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (8 pts) (nesting depth added 8). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 82). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
mpc_client::ui::run_ui (cognitive 16) mpc/client/src/ui.rs:209— mpc_client::ui::run_ui has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 2 (6 pts), loops 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
cmd.initAppForTestnet (cognitive 16) uniond/cmd/uniond/cmd/testnet.go:82— cmd.initAppForTestnet has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
execute.executeCosmWasmInstructions (cognitive 16) app2/src/lib/services/transfer-ucs03-cosmos/execute.ts:10— execute.executeCosmWasmInstructions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 6 belong to 5 function literals inside it that branch. 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.
utils.formatWaitTime (cognitive 16) ceremony/src/lib/utils/utils.ts:108— utils.formatWaitTime has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 6, boolean chains 2 (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.
TooManyFields: App uniond/app/app.go:112— TooManyFields — 33 stored fields beside 20 methods. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication· Near-duplicate member family (3 members, 19 shared lines) · ×1
Near-duplicate member family (3 members, 19 shared lines) voyager/modules/finality/arbitrum/src/main.rs:80— voyager/modules/finality/arbitrum/src/main.rs:80-110 | voyager/modules/finality/base/src/main.rs:57-86 | voyager/modules/finality/bob/src/main.rs:57-86 — These 3 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 11 shared lines) · ×1
Near-duplicate member family (3 members, 11 shared lines) lib/beacon-api-types/src/bellatrix/execution_payload_header.rs:81— lib/beacon-api-types/src/bellatrix/execution_payload_header.rs:81-116 | lib/beacon-api-types/src/capella/execution_payload_header.rs:83-119 | lib/beacon-api-types/src/deneb/execution_payload_header.rs:89-127 — These 3 members are variants of one another: a block of 11 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 (392 shared lines) voyager/plugins/event-source/cosmwasm/src/main.rs:595— voyager/plugins/event-source/cosmwasm/src/main.rs:595-1427 | voyager/plugins/event-source/gno/src/lib.rs:452-1300 — These two members are variants of one another: 392 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 (150 shared lines) galoisd/cmd/galoisd/cmd/example_prove.go:56— galoisd/cmd/galoisd/cmd/example_prove.go:56-235 | galoisd/cmd/galoisd/cmd/example_verify.go:31-244 — These two members are variants of one another: 150 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 (137 shared lines) voyager/plugins/client-update/proof-lens/src/main.rs:100— voyager/plugins/client-update/proof-lens/src/main.rs:100-247 | voyager/plugins/client-update/state-lens/src/main.rs:110-257 — These two members are variants of one another: 137 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 (100 shared lines) galoisd/grpc/bls12381_server.go:99— galoisd/grpc/bls12381_server.go:99-287 | galoisd/grpc/server.go:299-437 — These two members are variants of one another: 100 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 (75 shared lines) voyager/modules/state/cosmwasm/src/main.rs:114— voyager/modules/state/cosmwasm/src/main.rs:114-246 | voyager/modules/state/cosmwasm/src/main.rs:253-375 — These two members are variants of one another: 75 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 (66 shared lines) voyager/plugins/client-update/base/src/main.rs:388— voyager/plugins/client-update/base/src/main.rs:388-485 | voyager/plugins/client-update/bob/src/main.rs:378-478 — These two members are variants of one another: 66 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 (57 shared lines) tools/u/src/vanity/create3.rs:38— tools/u/src/vanity/create3.rs:38-270 | tools/u/src/vanity/wrapped_token.rs:88-343 — These two members are variants of one another: 57 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 (54 shared lines) voyager/plugins/client-update/base/src/main.rs:502— voyager/plugins/client-update/base/src/main.rs:502-644 | voyager/plugins/client-update/bob/src/main.rs:495-667 — These two members are variants of one another: 54 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 (41 shared lines) voyager/modules/state/evm/src/main.rs:493— voyager/modules/state/evm/src/main.rs:493-567 | voyager/modules/state/evm/src/main.rs:654-720 — These two members are variants of one another: 41 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 (27 shared lines) galoisd/grpc/bls12381_server.go:329— galoisd/grpc/bls12381_server.go:329-442 | galoisd/grpc/server.go:559-656 — These two members are variants of one another: 27 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) cosmwasm/cw20-base/src/allowances.rs:136— cosmwasm/cw20-base/src/allowances.rs:136-164 | cosmwasm/cw20-base/src/allowances.rs:209-248 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) tools/u/src/arbitrum/v1.rs:32— tools/u/src/arbitrum/v1.rs:32-72 | tools/u/src/arbitrum/v2.rs:37-82 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) voyager/modules/state/movement/src/client.rs:77— voyager/modules/state/movement/src/client.rs:77-107 | voyager/modules/state/movement/src/client.rs:304-346 | voyager/modules/state/movement/src/client.rs:398-430 | voyager/modules/state/movement/src/client.rs:435-465 | voyager/modules/state/movement/src/client.rs:472-495 | voyager/plugins/event-source/movement/src/client.rs:77-107 | voyager/plugins/event-source/movement/src/client.rs:304-346 | voyager/plugins/event-source/movement/src/client.rs:398-430 | voyager/plugins/event-source/movement/src/client.rs:435-465 | voyager/plugins/event-source/movement/src/client.rs:472-495 — 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.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) voyager/modules/client-bootstrap/cometbls/src/main.rs:47— voyager/modules/client-bootstrap/cometbls/src/main.rs:47-79 | voyager/modules/client-bootstrap/ethermint/src/main.rs:54-88 | voyager/modules/client-bootstrap/tendermint/src/main.rs:63-94 | voyager/modules/finality/cometbls/src/main.rs:36-62 | voyager/modules/finality/tendermint/src/main.rs:36-62 | voyager/plugins/client-update/cometbls/src/main.rs:91-132 | voyager/plugins/client-update/ethermint/src/main.rs:60-91 | voyager/plugins/client-update/tendermint/src/main.rs:63-94 | voyager/plugins/event-source/cosmwasm/src/main.rs:121-156 — These 9 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 9 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 9 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) voyager/modules/state/movement/src/client.rs:119— voyager/modules/state/movement/src/client.rs:119-183 | voyager/modules/state/movement/src/client.rs:200-299 | voyager/modules/state/movement/src/client.rs:354-390 | voyager/modules/state/movement/src/client.rs:499-519 | voyager/plugins/event-source/movement/src/client.rs:119-183 | voyager/plugins/event-source/movement/src/client.rs:200-299 | voyager/plugins/event-source/movement/src/client.rs:354-390 | voyager/plugins/event-source/movement/src/client.rs:499-519 — 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.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) voyager/plugins/sui-ibc-app/src/zkgm.rs:93— voyager/plugins/sui-ibc-app/src/zkgm.rs:93-131 | voyager/plugins/sui-ibc-app/src/zkgm.rs:140-170 | voyager/plugins/sui-ibc-app/src/zkgm.rs:225-261 | voyager/plugins/sui-ibc-app/src/zkgm.rs:270-298 | voyager/plugins/sui-ibc-app/src/zkgm.rs:336-367 | voyager/plugins/sui-ibc-app/src/zkgm.rs:376-404 — 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 (137 lines × 2) voyager/plugins/client-update/proof-lens/src/main.rs:327— voyager/plugins/client-update/proof-lens/src/main.rs:327-463 | voyager/plugins/client-update/state-lens/src/main.rs:337-473 — before extracting anything, compare `voyager/plugins/client-update/proof-lens/src/main.rs` and `voyager/plugins/client-update/state-lens/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 298 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (64 lines × 2) voyager/plugins/event-source/cosmwasm/src/main.rs:320— voyager/plugins/event-source/cosmwasm/src/main.rs:320-383 | voyager/plugins/event-source/gno/src/lib.rs:270-333 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (57 lines × 2) lib/base-verifier/src/lib.rs:47— lib/base-verifier/src/lib.rs:47-103 | lib/bob-verifier/src/lib.rs:45-101 — before extracting anything, compare `lib/base-verifier/src/lib.rs` and `lib/bob-verifier/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (51 lines × 2) voyager/modules/client/cometbls/src/main.rs:383— voyager/modules/client/cometbls/src/main.rs:383-433 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:297-347 — 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 (44 lines × 2) lib/voyager-plugin/src/lib.rs:365— lib/voyager-plugin/src/lib.rs:365-408 | voyager/src/metrics.rs:64-107 — 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 (39 lines × 2) cosmwasm/cw-escrow-vault/src/contract.rs:87— cosmwasm/cw-escrow-vault/src/contract.rs:87-125 | cosmwasm/cw-unionversal-token/src/contract.rs:129-167 — before extracting anything, compare `cosmwasm/cw-escrow-vault/src/contract.rs` and `cosmwasm/cw-unionversal-token/src/contract.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (38 lines × 3) voyager/plugins/transaction-batch/src/call.rs:320— voyager/plugins/transaction-batch/src/call.rs:320-357 | voyager/plugins/transaction-batch/src/call.rs:386-423 | voyager/plugins/transaction-batch/src/call.rs:450-487 — 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 (35 lines × 2) voyager/plugins/event-source/evm/src/main.rs:195— voyager/plugins/event-source/evm/src/main.rs:195-229 | voyager/plugins/event-source/sui/src/main.rs:289-323 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (32–34 lines × 3) voyager/plugins/event-source/evm/src/main.rs:172— voyager/plugins/event-source/evm/src/main.rs:172-203 | voyager/plugins/event-source/movement/src/main.rs:170-203 | voyager/plugins/event-source/sui/src/main.rs:266-297 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (32 lines × 2) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1665— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1665-1696 | voyager/plugins/transaction-batch/src/lib.rs:577-608 — before extracting anything, compare `voyager/plugins/transaction-batch-proof-lens/src/lib.rs` and `voyager/plugins/transaction-batch/src/lib.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (31 lines × 3) voyager/plugins/client-update/arbitrum/src/main.rs:189— voyager/plugins/client-update/arbitrum/src/main.rs:189-219 | voyager/plugins/client-update/base/src/main.rs:258-288 | voyager/plugins/client-update/bob/src/main.rs:250-280 — before extracting anything, compare `voyager/plugins/client-update/arbitrum/src/main.rs` and `voyager/plugins/client-update/base/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–30 lines × 4) voyager/plugins/event-source/cosmwasm/src/main.rs:1268— voyager/plugins/event-source/cosmwasm/src/main.rs:1268-1295 | voyager/plugins/event-source/cosmwasm/src/main.rs:1354-1381 | voyager/plugins/event-source/gno/src/lib.rs:1123-1152 | voyager/plugins/event-source/gno/src/lib.rs:1221-1250 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–30 lines × 2) voyager/modules/state/evm/src/main.rs:230— voyager/modules/state/evm/src/main.rs:230-244 | voyager/modules/state/evm/src/main.rs:286-315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (28 lines × 3) voyager/plugins/transaction-batch/src/call.rs:498— voyager/plugins/transaction-batch/src/call.rs:498-525 | voyager/plugins/transaction-batch/src/call.rs:544-571 | voyager/plugins/transaction-batch/src/call.rs:584-611 — 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 (23–26 lines × 2) lib/tendermint-verifier/src/verify.rs:210— lib/tendermint-verifier/src/verify.rs:210-232 | lib/tendermint-verifier/src/verify.rs:295-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24–25 lines × 2) tools/union-test/src/evm.rs:823— tools/union-test/src/evm.rs:823-847 | voyager/plugins/transaction/evm/src/main.rs:578-601 — 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 (24 lines × 6) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:494— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:494-517 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:547-570 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:599-622 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:655-678 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:718-741 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:774-797 — 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 (24 lines × 3) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:824— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:824-847 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:886-909 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:937-960 — 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 (21–24 lines × 2) cosmwasm/deployer/src/main.rs:778— cosmwasm/deployer/src/main.rs:778-801 | cosmwasm/deployer/src/main.rs:855-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 (18–23 lines × 3) voyager/plugins/client-update/cometbls/src/main.rs:92— voyager/plugins/client-update/cometbls/src/main.rs:92-114 | voyager/plugins/client-update/ethermint/src/main.rs:61-78 | voyager/plugins/client-update/tendermint/src/main.rs:64-81 — before extracting anything, compare `voyager/plugins/client-update/cometbls/src/main.rs` and `voyager/plugins/client-update/ethermint/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (21–23 lines × 2) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1081— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1081-1103 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1545-1565 — both copies are in the same file, so extract the block into 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–21 lines × 2) cosmwasm/app/ucs03-zkgm/src/contract.rs:802— cosmwasm/app/ucs03-zkgm/src/contract.rs:802-814 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1281-1301 — both copies are in the same file, so extract the block into 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–21 lines × 2) lib/base-verifier/src/lib.rs:108— lib/base-verifier/src/lib.rs:108-125 | lib/bob-verifier/src/lib.rs:101-121 — before extracting anything, compare `lib/base-verifier/src/lib.rs` and `lib/bob-verifier/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–20 lines × 6) voyager/plugins/client-update/base/src/main.rs:389— voyager/plugins/client-update/base/src/main.rs:389-407 | voyager/plugins/client-update/base/src/main.rs:503-521 | voyager/plugins/client-update/bob/src/main.rs:379-397 | voyager/plugins/client-update/bob/src/main.rs:496-514 | voyager/plugins/client-update/proof-lens/src/main.rs:101-120 | voyager/plugins/client-update/state-lens/src/main.rs:111-130 — before extracting anything, compare `voyager/plugins/client-update/base/src/main.rs` and `voyager/plugins/client-update/bob/src/main.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) tools/u/src/vanity/create3.rs:230— tools/u/src/vanity/create3.rs:230-249 | tools/u/src/vanity/instantiate2_address.rs:142-161 | tools/u/src/vanity/wrapped_token.rs:307-326 — before extracting anything, compare `tools/u/src/vanity/create3.rs` and `tools/u/src/vanity/wrapped_token.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 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 (19 lines × 4) voyager/plugins/event-source/gno/src/lib.rs:677— voyager/plugins/event-source/gno/src/lib.rs:677-695 | voyager/plugins/event-source/gno/src/lib.rs:726-744 | voyager/plugins/event-source/gno/src/lib.rs:775-793 | voyager/plugins/event-source/gno/src/lib.rs:825-843 — 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–19 lines × 3) cosmwasm/app/ucs03-zkgm/src/contract.rs:2112— cosmwasm/app/ucs03-zkgm/src/contract.rs:2112-2130 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2399-2413 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2474-2488 — 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 (19 lines × 3) voyager/modules/finality/arbitrum/src/main.rs:81— voyager/modules/finality/arbitrum/src/main.rs:81-99 | voyager/modules/finality/base/src/main.rs:58-76 | voyager/modules/finality/bob/src/main.rs:58-76 — before extracting anything, compare `voyager/modules/finality/base/src/main.rs` and `voyager/modules/finality/bob/src/main.rs` as WHOLE FILES: this scan already matched 4 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 (18–19 lines × 2) tools/union-test/src/lib.rs:693— tools/union-test/src/lib.rs:693-710 | tools/union-test/src/lib.rs:906-924 — both copies are in the same file, so extract the block into 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 × 9) voyager/plugins/transaction-batch-proof-lens/src/lib.rs:500— voyager/plugins/transaction-batch-proof-lens/src/lib.rs:500-517 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:553-570 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:605-622 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:661-678 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:724-741 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:780-797 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:830-847 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:892-909 | voyager/plugins/transaction-batch-proof-lens/src/lib.rs:943-960 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16–18 lines × 4) tools/union-test/src/lib.rs:691— tools/union-test/src/lib.rs:691-707 | tools/union-test/src/lib.rs:904-921 | tools/union-test/src/lib.rs:948-965 | tools/union-test/src/lib.rs:1083-1098 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 4) voyager/plugins/client-update/cometbls/src/main.rs:101— voyager/plugins/client-update/cometbls/src/main.rs:101-118 | voyager/plugins/client-update/ethermint/src/main.rs:65-82 | voyager/plugins/client-update/tendermint/src/main.rs:68-85 | voyager/plugins/event-source/cosmwasm/src/main.rs:126-143 — before extracting anything, compare `voyager/plugins/client-update/cometbls/src/main.rs` and `voyager/plugins/client-update/ethermint/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (18 lines × 3) tools/union-test/src/lib.rs:770— tools/union-test/src/lib.rs:770-787 | tools/union-test/src/lib.rs:816-833 | tools/union-test/src/lib.rs:860-877 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17–18 lines × 3) voyager/plugins/event-source/cosmwasm/src/main.rs:1107— voyager/plugins/event-source/cosmwasm/src/main.rs:1107-1123 | voyager/plugins/event-source/cosmwasm/src/main.rs:1261-1278 | voyager/plugins/event-source/cosmwasm/src/main.rs:1347-1364 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–17 lines × 8) voyager/plugins/event-source/cosmwasm/src/main.rs:1038— voyager/plugins/event-source/cosmwasm/src/main.rs:1038-1052 | voyager/plugins/event-source/cosmwasm/src/main.rs:1110-1123 | voyager/plugins/event-source/cosmwasm/src/main.rs:1190-1204 | voyager/plugins/event-source/cosmwasm/src/main.rs:1264-1279 | voyager/plugins/event-source/cosmwasm/src/main.rs:1350-1365 | voyager/plugins/event-source/gno/src/lib.rs:884-898 | voyager/plugins/event-source/gno/src/lib.rs:1118-1134 | voyager/plugins/event-source/gno/src/lib.rs:1216-1232 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–17 lines × 4) voyager/plugins/event-source/evm/src/main.rs:189— voyager/plugins/event-source/evm/src/main.rs:189-203 | voyager/plugins/event-source/movement/src/main.rs:187-203 | voyager/plugins/event-source/sui/src/main.rs:283-297 | voyager/plugins/event-source/sui/src/main.rs:387-400 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/sui/src/main.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 4) voyager/plugins/event-source/gno/src/lib.rs:653— voyager/plugins/event-source/gno/src/lib.rs:653-669 | voyager/plugins/event-source/gno/src/lib.rs:701-717 | voyager/plugins/event-source/gno/src/lib.rs:750-766 | voyager/plugins/event-source/gno/src/lib.rs:800-816 — 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 (16 lines × 9) voyager/plugins/event-source/cosmwasm/src/main.rs:676— voyager/plugins/event-source/cosmwasm/src/main.rs:676-691 | voyager/plugins/event-source/cosmwasm/src/main.rs:709-724 | voyager/plugins/event-source/cosmwasm/src/main.rs:742-757 | voyager/plugins/event-source/cosmwasm/src/main.rs:775-790 | voyager/plugins/event-source/cosmwasm/src/main.rs:822-837 | voyager/plugins/event-source/gno/src/lib.rs:533-548 | voyager/plugins/event-source/gno/src/lib.rs:566-581 | voyager/plugins/event-source/gno/src/lib.rs:599-614 | voyager/plugins/event-source/gno/src/lib.rs:632-647 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 7) tools/union-test/src/lib.rs:691— tools/union-test/src/lib.rs:691-706 | tools/union-test/src/lib.rs:770-785 | tools/union-test/src/lib.rs:816-831 | tools/union-test/src/lib.rs:860-875 | tools/union-test/src/lib.rs:904-919 | tools/union-test/src/lib.rs:948-963 | tools/union-test/src/lib.rs:1083-1098 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 4) voyager/plugins/client-update/arbitrum/src/main.rs:568— voyager/plugins/client-update/arbitrum/src/main.rs:568-583 | voyager/plugins/client-update/arbitrum/src/main.rs:654-669 | voyager/plugins/client-update/base/src/main.rs:469-484 | voyager/plugins/client-update/bob/src/main.rs:462-477 — before extracting anything, compare `voyager/plugins/client-update/arbitrum/src/main.rs` and `voyager/plugins/client-update/base/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–16 lines × 2) cosmwasm/cw20-base/src/contract.rs:393— cosmwasm/cw20-base/src/contract.rs:393-408 | cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs:256-269 — before extracting anything, compare `cosmwasm/cw20-base/src/contract.rs` and `cosmwasm/cw20-wrapped-tokenfactory/src/contract.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:139— cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:139-153 | cosmwasm/cw20-wrapped-tokenfactory/src/allowances.rs:225-240 — both copies are in the same file, so extract the block into 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 × 13) voyager/plugins/event-source/cosmwasm/src/main.rs:677— voyager/plugins/event-source/cosmwasm/src/main.rs:677-691 | voyager/plugins/event-source/cosmwasm/src/main.rs:710-724 | voyager/plugins/event-source/cosmwasm/src/main.rs:743-757 | voyager/plugins/event-source/cosmwasm/src/main.rs:776-790 | voyager/plugins/event-source/cosmwasm/src/main.rs:823-837 | voyager/plugins/event-source/gno/src/lib.rs:534-548 | voyager/plugins/event-source/gno/src/lib.rs:567-581 | voyager/plugins/event-source/gno/src/lib.rs:600-614 | voyager/plugins/event-source/gno/src/lib.rs:633-647 | voyager/plugins/event-source/gno/src/lib.rs:681-695 | voyager/plugins/event-source/gno/src/lib.rs:730-744 | voyager/plugins/event-source/gno/src/lib.rs:779-793 | voyager/plugins/event-source/gno/src/lib.rs:829-843 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 12) voyager/plugins/event-source/cosmwasm/src/main.rs:803— voyager/plugins/event-source/cosmwasm/src/main.rs:803-816 | voyager/plugins/event-source/cosmwasm/src/main.rs:851-864 | voyager/plugins/event-source/cosmwasm/src/main.rs:899-912 | voyager/plugins/event-source/cosmwasm/src/main.rs:964-977 | voyager/plugins/event-source/cosmwasm/src/main.rs:1048-1062 | voyager/plugins/event-source/cosmwasm/src/main.rs:1119-1133 | voyager/plugins/event-source/cosmwasm/src/main.rs:1200-1214 | voyager/plugins/event-source/evm/src/main.rs:792-805 | voyager/plugins/event-source/evm/src/main.rs:850-863 | voyager/plugins/event-source/evm/src/main.rs:904-917 | voyager/plugins/event-source/evm/src/main.rs:950-963 | voyager/plugins/event-source/gno/src/lib.rs:894-908 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/evm/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 4) voyager/plugins/event-source/cosmwasm/src/main.rs:949— voyager/plugins/event-source/cosmwasm/src/main.rs:949-962 | voyager/plugins/event-source/cosmwasm/src/main.rs:1103-1117 | voyager/plugins/event-source/cosmwasm/src/main.rs:1257-1271 | voyager/plugins/event-source/cosmwasm/src/main.rs:1343-1357 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13–15 lines × 2) voyager/plugins/event-source/sui/src/main.rs:881— voyager/plugins/event-source/sui/src/main.rs:881-895 | voyager/plugins/event-source/sui/src/main.rs:921-933 — both copies are in the same file, so extract the block into 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 × 9) voyager/modules/client-bootstrap/cometbls/src/main.rs:60— voyager/modules/client-bootstrap/cometbls/src/main.rs:60-73 | voyager/modules/client-bootstrap/ethermint/src/main.rs:67-80 | voyager/modules/client-bootstrap/tendermint/src/main.rs:71-84 | voyager/modules/finality/cometbls/src/main.rs:44-57 | voyager/modules/finality/tendermint/src/main.rs:44-57 | voyager/plugins/client-update/cometbls/src/main.rs:109-122 | voyager/plugins/client-update/ethermint/src/main.rs:73-86 | voyager/plugins/client-update/tendermint/src/main.rs:76-89 | voyager/plugins/event-source/cosmwasm/src/main.rs:134-147 — before extracting anything, compare `voyager/plugins/client-update/cometbls/src/main.rs` and `voyager/plugins/client-update/ethermint/src/main.rs` as WHOLE FILES: this scan already matched 3 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 (13–14 lines × 5) voyager/plugins/event-source/evm/src/main.rs:588— voyager/plugins/event-source/evm/src/main.rs:588-600 | voyager/plugins/event-source/evm/src/main.rs:624-636 | voyager/plugins/event-source/evm/src/main.rs:660-673 | voyager/plugins/event-source/evm/src/main.rs:698-711 | voyager/plugins/event-source/evm/src/main.rs:736-749 — 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–14 lines × 3) tools/union-test/src/evm.rs:582— tools/union-test/src/evm.rs:582-595 | tools/union-test/src/evm.rs:616-629 | tools/union-test/src/evm.rs:953-965 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10–14 lines × 2) tools/union-test/src/evm.rs:466— tools/union-test/src/evm.rs:466-479 | tools/union-test/src/evm.rs:484-493 — both copies are in the same file, so extract the block into 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 × 8) voyager/plugins/event-source/evm/src/main.rs:607— voyager/plugins/event-source/evm/src/main.rs:607-619 | voyager/plugins/event-source/evm/src/main.rs:681-693 | voyager/plugins/event-source/evm/src/main.rs:719-731 | voyager/plugins/event-source/evm/src/main.rs:757-769 | voyager/plugins/event-source/evm/src/main.rs:814-826 | voyager/plugins/event-source/evm/src/main.rs:873-885 | voyager/plugins/event-source/evm/src/main.rs:927-939 | voyager/plugins/event-source/evm/src/main.rs:981-993 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 6) voyager/plugins/event-source/evm/src/main.rs:1060— voyager/plugins/event-source/evm/src/main.rs:1060-1072 | voyager/plugins/event-source/evm/src/main.rs:1093-1105 | voyager/plugins/event-source/evm/src/main.rs:1135-1147 | voyager/plugins/event-source/evm/src/main.rs:1177-1189 | voyager/plugins/event-source/evm/src/main.rs:1285-1297 | voyager/plugins/event-source/evm/src/main.rs:1327-1339 — 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 (13 lines × 4) cosmwasm/core/src/contract.rs:1372— cosmwasm/core/src/contract.rs:1372-1384 | cosmwasm/core/src/contract.rs:1462-1474 | cosmwasm/core/src/contract.rs:1547-1559 | cosmwasm/core/src/contract.rs:1669-1681 — 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 × 6) tools/union-test/src/lib.rs:689— tools/union-test/src/lib.rs:689-700 | tools/union-test/src/lib.rs:725-736 | tools/union-test/src/lib.rs:858-869 | tools/union-test/src/lib.rs:902-913 | tools/union-test/src/lib.rs:946-957 | tools/union-test/src/lib.rs:983-994 — 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 (11 lines × 9) voyager/plugins/event-source/evm/src/main.rs:590— voyager/plugins/event-source/evm/src/main.rs:590-600 | voyager/plugins/event-source/evm/src/main.rs:626-636 | voyager/plugins/event-source/evm/src/main.rs:663-673 | voyager/plugins/event-source/evm/src/main.rs:701-711 | voyager/plugins/event-source/evm/src/main.rs:739-749 | voyager/plugins/event-source/gno/src/lib.rs:659-669 | voyager/plugins/event-source/gno/src/lib.rs:707-717 | voyager/plugins/event-source/gno/src/lib.rs:756-766 | voyager/plugins/event-source/gno/src/lib.rs:806-816 — before extracting anything, compare `voyager/plugins/event-source/evm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.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 × 6) voyager/modules/state/movement/src/client.rs:94— voyager/modules/state/movement/src/client.rs:94-104 | voyager/modules/state/movement/src/client.rs:415-425 | voyager/modules/state/movement/src/client.rs:452-462 | voyager/plugins/event-source/movement/src/client.rs:94-104 | voyager/plugins/event-source/movement/src/client.rs:415-425 | voyager/plugins/event-source/movement/src/client.rs:452-462 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/state/movement/src/client.rs:165— voyager/modules/state/movement/src/client.rs:165-175 | voyager/modules/state/movement/src/client.rs:281-291 | voyager/plugins/event-source/movement/src/client.rs:165-175 | voyager/plugins/event-source/movement/src/client.rs:281-291 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 2) cosmwasm/cw20-base/src/allowances.rs:182— cosmwasm/cw20-base/src/allowances.rs:182-190 | cosmwasm/cw20-base/src/contract.rs:271-281 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 12) voyager/plugins/event-source/cosmwasm/src/main.rs:603— voyager/plugins/event-source/cosmwasm/src/main.rs:603-612 | voyager/plugins/event-source/cosmwasm/src/main.rs:632-641 | voyager/plugins/event-source/cosmwasm/src/main.rs:663-672 | voyager/plugins/event-source/cosmwasm/src/main.rs:695-704 | voyager/plugins/event-source/cosmwasm/src/main.rs:728-737 | voyager/plugins/event-source/cosmwasm/src/main.rs:761-770 | voyager/plugins/event-source/gno/src/lib.rs:460-469 | voyager/plugins/event-source/gno/src/lib.rs:489-498 | voyager/plugins/event-source/gno/src/lib.rs:520-529 | voyager/plugins/event-source/gno/src/lib.rs:552-561 | voyager/plugins/event-source/gno/src/lib.rs:585-594 | voyager/plugins/event-source/gno/src/lib.rs:618-627 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/gno/src/lib.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 444 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/state/movement/src/client.rs:168— voyager/modules/state/movement/src/client.rs:168-177 | voyager/modules/state/movement/src/client.rs:284-293 | voyager/modules/state/movement/src/client.rs:375-384 | voyager/plugins/event-source/movement/src/client.rs:168-177 | voyager/plugins/event-source/movement/src/client.rs:284-293 | voyager/plugins/event-source/movement/src/client.rs:375-384 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) lib/access-manager-types/src/lib.rs:430— lib/access-manager-types/src/lib.rs:430-439 | lib/access-manager-types/src/lib.rs:453-462 | lib/access-manager-types/src/lib.rs:485-494 | lib/access-manager-types/src/lib.rs:501-510 | lib/access-manager-types/src/lib.rs:517-526 — 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–10 lines × 3) cosmwasm/app/ucs03-zkgm/src/contract.rs:1799— cosmwasm/app/ucs03-zkgm/src/contract.rs:1799-1807 | cosmwasm/app/ucs03-zkgm/src/contract.rs:1937-1946 | cosmwasm/app/ucs03-zkgm/src/contract.rs:2148-2155 — 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 × 6) voyager/modules/state/movement/src/client.rs:120— voyager/modules/state/movement/src/client.rs:120-128 | voyager/modules/state/movement/src/client.rs:201-209 | voyager/modules/state/movement/src/client.rs:355-363 | voyager/plugins/event-source/movement/src/client.rs:120-128 | voyager/plugins/event-source/movement/src/client.rs:201-209 | voyager/plugins/event-source/movement/src/client.rs:355-363 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 8) voyager/modules/state/movement/src/client.rs:170— voyager/modules/state/movement/src/client.rs:170-178 | voyager/modules/state/movement/src/client.rs:286-294 | voyager/modules/state/movement/src/client.rs:377-385 | voyager/modules/state/movement/src/client.rs:507-514 | voyager/plugins/event-source/movement/src/client.rs:170-178 | voyager/plugins/event-source/movement/src/client.rs:286-294 | voyager/plugins/event-source/movement/src/client.rs:377-385 | voyager/plugins/event-source/movement/src/client.rs:507-514 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 6) voyager/plugins/sui-ibc-app/src/zkgm.rs:94— voyager/plugins/sui-ibc-app/src/zkgm.rs:94-101 | voyager/plugins/sui-ibc-app/src/zkgm.rs:141-148 | voyager/plugins/sui-ibc-app/src/zkgm.rs:226-233 | voyager/plugins/sui-ibc-app/src/zkgm.rs:271-278 | voyager/plugins/sui-ibc-app/src/zkgm.rs:337-344 | voyager/plugins/sui-ibc-app/src/zkgm.rs:377-384 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 5) voyager/modules/client-bootstrap/ethereum/src/main.rs:110— voyager/modules/client-bootstrap/ethereum/src/main.rs:110-117 | voyager/modules/client-bootstrap/trusted-mpt/src/main.rs:55-62 | voyager/modules/finality/ethereum/src/main.rs:153-160 | voyager/modules/finality/trusted-evm/src/main.rs:49-56 | voyager/plugins/event-source/evm/src/main.rs:135-142 — 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 (7 lines × 10) voyager/modules/state/movement/src/client.rs:78— voyager/modules/state/movement/src/client.rs:78-84 | voyager/modules/state/movement/src/client.rs:305-311 | voyager/modules/state/movement/src/client.rs:399-405 | voyager/modules/state/movement/src/client.rs:436-442 | voyager/modules/state/movement/src/client.rs:473-479 | voyager/plugins/event-source/movement/src/client.rs:78-84 | voyager/plugins/event-source/movement/src/client.rs:305-311 | voyager/plugins/event-source/movement/src/client.rs:399-405 | voyager/plugins/event-source/movement/src/client.rs:436-442 | voyager/plugins/event-source/movement/src/client.rs:473-479 — before extracting anything, compare `voyager/modules/state/movement/src/client.rs` and `voyager/plugins/event-source/movement/src/client.rs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/plugins/event-source/cosmwasm/src/main.rs:219— voyager/plugins/event-source/cosmwasm/src/main.rs:219-225 | voyager/plugins/event-source/evm/src/main.rs:240-246 | voyager/plugins/event-source/gno/src/lib.rs:176-182 | voyager/plugins/event-source/starknet/src/main.rs:165-171 | voyager/plugins/event-source/sui/src/main.rs:425-431 — before extracting anything, compare `voyager/plugins/event-source/cosmwasm/src/main.rs` and `voyager/plugins/event-source/evm/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (61 lines × 2) lib/base-light-client-types/src/header.rs:88— lib/base-light-client-types/src/header.rs:88-148 | lib/bob-light-client-types/src/header.rs:88-148 — 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 × 6) voyager/modules/client-bootstrap/movement/src/main.rs:119— voyager/modules/client-bootstrap/movement/src/main.rs:119-133 | voyager/modules/finality/movement/src/main.rs:98-112 | voyager/modules/proof/movement/src/main.rs:94-108 | voyager/modules/state/movement/src/main.rs:100-114 | voyager/plugins/client-update/movement/src/main.rs:155-169 | voyager/plugins/event-source/movement/src/main.rs:148-162 — before extracting anything, compare `voyager/modules/proof/movement/src/main.rs` and `voyager/modules/state/movement/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) voyager/modules/client/arbitrum/src/main.rs:117— voyager/modules/client/arbitrum/src/main.rs:117-123 | voyager/modules/client/base/src/main.rs:110-116 | voyager/modules/client/bob/src/main.rs:112-118 | voyager/modules/client/ethereum/src/main.rs:107-113 | voyager/modules/client/ethermint/src/main.rs:110-116 | voyager/modules/client/parlia/src/main.rs:107-113 | voyager/modules/client/trusted-mpt/src/main.rs:114-120 — before extracting anything, compare `voyager/modules/client/base/src/main.rs` and `voyager/modules/client/ethereum/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (5 lines × 11) voyager/modules/client/arbitrum/src/main.rs:130— voyager/modules/client/arbitrum/src/main.rs:130-134 | voyager/modules/client/base/src/main.rs:123-127 | voyager/modules/client/bob/src/main.rs:125-129 | voyager/modules/client/ethereum/src/main.rs:120-124 | voyager/modules/client/ethermint/src/main.rs:123-127 | voyager/modules/client/parlia/src/main.rs:120-124 | voyager/modules/client/proof-lens/src/main.rs:170-174 | voyager/modules/client/state-lens/ics23-ics23/src/main.rs:173-177 | voyager/modules/client/state-lens/ics23-smt/src/main.rs:169-173 | voyager/modules/client/sui/src/main.rs:132-136 | voyager/modules/client/trusted-mpt/src/main.rs:127-131 — before extracting anything, compare `voyager/modules/client/base/src/main.rs` and `voyager/modules/client/ethereum/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (5 lines × 8) voyager/modules/client/arbitrum/src/main.rs:137— voyager/modules/client/arbitrum/src/main.rs:137-141 | voyager/modules/client/attested/src/main.rs:132-136 | voyager/modules/client/base/src/main.rs:130-134 | voyager/modules/client/bob/src/main.rs:132-136 | voyager/modules/client/ethereum/src/main.rs:127-131 | voyager/modules/client/ethermint/src/main.rs:130-134 | voyager/modules/client/parlia/src/main.rs:127-131 | voyager/modules/client/sui/src/main.rs:139-143 — before extracting anything, compare `voyager/modules/client/base/src/main.rs` and `voyager/modules/client/ethereum/src/main.rs` as WHOLE FILES: this scan already matched 5 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 (5 lines × 7) voyager/modules/client/arbitrum/src/main.rs:151— voyager/modules/client/arbitrum/src/main.rs:151-155 | voyager/modules/client/attested/src/main.rs:146-150 | voyager/modules/client/base/src/main.rs:144-148 | voyager/modules/client/bob/src/main.rs:146-150 | voyager/modules/client/ethereum/src/main.rs:141-145 | voyager/modules/client/sui/src/main.rs:153-157 | voyager/modules/client/trusted-mpt/src/main.rs:148-152 — before extracting anything, compare `voyager/modules/client/base/src/main.rs` and `voyager/modules/client/ethereum/src/main.rs` as WHOLE FILES: this scan already matched 5 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 × 5) voyager/plugins/client-update/arbitrum/src/main.rs:257— voyager/plugins/client-update/arbitrum/src/main.rs:257-267 | voyager/plugins/client-update/base/src/main.rs:124-136 | voyager/plugins/client-update/bob/src/main.rs:117-129 | voyager/plugins/client-update/ethereum/src/main.rs:106-116 | voyager/plugins/client-update/trusted-mpt/src/main.rs:99-109 — before extracting anything, compare `voyager/plugins/client-update/arbitrum/src/main.rs` and `voyager/plugins/client-update/base/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (65–66 lines × 2) galoisd/cmd/galoisd/cmd/example_prove.go:60— galoisd/cmd/galoisd/cmd/example_prove.go:60-125 | galoisd/cmd/galoisd/cmd/example_verify.go:35-99 — before extracting anything, compare `galoisd/cmd/galoisd/cmd/example_prove.go` and `galoisd/cmd/galoisd/cmd/example_verify.go` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/cmd/galoisd/cmd/example_prove.go:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (60 lines × 2) galoisd/grpc/bls12381_server.go:205— galoisd/grpc/bls12381_server.go:205-264 | galoisd/grpc/server.go:355-414 — before extracting anything, compare `galoisd/grpc/bls12381_server.go` and `galoisd/grpc/server.go` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 162 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `galoisd/grpc/bls12381_server.go:205` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (30–31 lines × 2) galoisd/cmd/galoisd/cmd/serve.go:44— galoisd/cmd/galoisd/cmd/serve.go:44-73 | galoisd/cmd/galoisd/cmd/serve_bls12381.go:54-84 — before extracting anything, compare `galoisd/cmd/galoisd/cmd/serve.go` and `galoisd/cmd/galoisd/cmd/serve_bls12381.go` as WHOLE FILES: this scan already matched 3 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9–10 lines × 3) galoisd/cmd/galoisd/cmd/phase1_init.go:209— galoisd/cmd/galoisd/cmd/phase1_init.go:209-217 | galoisd/cmd/galoisd/cmd/phase1_init.go:821-829 | galoisd/cmd/galoisd/cmd/phase1_init.go:840-849 — 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 `galoisd/cmd/galoisd/cmd/phase1_init.go:209` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `galoisd/cmd/galoisd/cmd/phase1_init.go:830` calls `Printf`, `String` and `galoisd/cmd/galoisd/cmd/phase1_init.go:219` 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 (4–10 lines × 6) lib/ibc-union-spec/src/lib.rs:188— lib/ibc-union-spec/src/lib.rs:188-197 | lib/ibc-union-spec/src/lib.rs:226-229 | lib/ibc-union-spec/src/lib.rs:248-251 | lib/ibc-union-spec/src/lib.rs:270-273 | lib/ibc-union-spec/src/lib.rs:293-302 | lib/ibc-union-spec/src/lib.rs:314-323 — 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 (2–9 lines × 3) lib/ibc-union-spec/src/lib.rs:178— lib/ibc-union-spec/src/lib.rs:178-186 | lib/ibc-union-spec/src/lib.rs:291-292 | lib/ibc-union-spec/src/lib.rs:304-312 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 5) lib/ibc-union-spec/src/lib.rs:192— lib/ibc-union-spec/src/lib.rs:192-197 | lib/ibc-union-spec/src/lib.rs:231-236 | lib/ibc-union-spec/src/lib.rs:253-258 | lib/ibc-union-spec/src/lib.rs:275-280 | lib/ibc-union-spec/src/lib.rs:297-302 — 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 (6 lines × 4) lib/ibc-union-spec/src/lib.rs:127— lib/ibc-union-spec/src/lib.rs:127-132 | lib/ibc-union-spec/src/lib.rs:141-146 | lib/ibc-union-spec/src/lib.rs:155-160 | lib/ibc-union-spec/src/lib.rs:169-174 — 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.
Duplication concentrated across 9 sibling directories (33 clone groups) app2/src/lib/graphql/service.ts:37— 33 duplicated blocks under the repository root have copies in at least two of the sibling directories app2, ceremony, effect-svelte, ts-sdk, ts-sdk-cosmos, ts-sdk-evm (+3 more sibling(s) not listed) — 27 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 33 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 33 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 33 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (9 clone groups) app2/src/lib/services/transfer-ucs03-cosmos/state.ts:23— 9 of the duplicated blocks reported below have copies in at least two of the sibling directories transfer, transfer-ucs03-cosmos, transfer-ucs03-evm under app2/src/lib/services/. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (6 clone groups) app2/src/routes/explorer/packets/+page.svelte:24— 6 of the duplicated blocks reported below have copies in at least two of the sibling directories dust, packets, stakes, transfers, unstakes, withdrawals under app2/src/routes/explorer/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (6 clone groups) ts-sdk/src/aptos/client.ts:47— 6 duplicated blocks under ts-sdk/src/ have copies in at least two of the sibling directories aptos, cosmos, evm, sui, ucs03 — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (5 clone groups) app2/src/lib/transfer/multisig/services/filling.ts:26— 5 duplicated blocks under app2/src/lib/transfer/ have copies in at least two of the sibling directories multisig, normal — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (283 matched lines × 2 locations) · ×1
Duplicated block with local edits (283 matched lines × 2 locations) app2/src/lib/components/stake/BondComponent.svelte:151— app2/src/lib/components/stake/BondComponent.svelte:151 · app2/src/lib/components/stake/UnbondComponent.svelte:129 — the two spans are one implementation copied and then locally edited — 1629 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (175 matched lines × 2 locations) · ×1
Duplicated block with local edits (175 matched lines × 2 locations) app2/src/lib/graphql/service.ts:37— app2/src/lib/graphql/service.ts:37 · ts-sdk/src/Indexer.ts:83 — the two spans are one implementation copied and then locally edited — 1012 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (172 matched lines × 2 locations) · ×1
Duplicated block with local edits (172 matched lines × 2 locations) app2/src/lib/dashboard/services/add-cosmos-wallet.ts:18— app2/src/lib/dashboard/services/add-cosmos-wallet.ts:18 · app2/src/lib/dashboard/services/add-evm-wallet.ts:16 — the two spans are one implementation copied and then locally edited — 913 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (149 matched lines × 2 locations) · ×1
Duplicated block with local edits (149 matched lines × 2 locations) ts-sdk-cosmos/src/internal/zkgmClient.ts:25— ts-sdk-cosmos/src/internal/zkgmClient.ts:25 · ts-sdk-evm/src/internal/zkgmClient.ts:27 — the two spans are one implementation copied and then locally edited — 767 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (136 identical lines × 2 files) app2/src/lib/services/cosmos/chain-info/internal-chain-info.ts:1— app2/src/lib/services/cosmos/chain-info/internal-chain-info.ts:1 · app2/src/lib/services/cosmos/chain-info/keplr-chain-info.ts:1 — these 2 files are line-for-line copies of one another — 136 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.
R10 · Code Duplication· Duplicated block with local edits (128 matched lines × 2 locations) · ×1
Duplicated block with local edits (128 matched lines × 2 locations) app2/src/lib/components/stake/ProxyDustRecovery.svelte:122— app2/src/lib/components/stake/ProxyDustRecovery.svelte:122 · app2/src/lib/components/stake/WithdrawalComponent.svelte:186 — the two spans are one implementation copied and then locally edited — 677 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (118 identical lines × 2 files) app2/src/lib/utils/effect.svelte.ts:2— app2/src/lib/utils/effect.svelte.ts:2 · effect-svelte/src/lib/Runtime.svelte.ts:2 — these 2 files are line-for-line copies of one another — 118 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.
R10 · Code Duplication· Duplicated block with local edits (94 matched lines × 2 locations) · ×1
Duplicated block with local edits (94 matched lines × 2 locations) ts-sdk/src/internal/tokenOrder.ts:34— ts-sdk/src/internal/tokenOrder.ts:34 · ts-sdk/src/internal/zkgmClientRequest.ts:27 — the two spans are one implementation copied and then locally edited — 461 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (81 matched lines × 2 locations) · ×1
Duplicated block with local edits (81 matched lines × 2 locations) ts-sdk/src/Ucs05.ts:118— ts-sdk/src/Ucs05.ts:118 · ts-sdk/src/schema/address.ts:59 — the two spans are one implementation copied and then locally edited — 615 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (76 lines × 2 locations) ts-sdk-sui/src/Sui.ts:477— ts-sdk-sui/src/Sui.ts:477 · ts-sdk/src/sui/sui_coin.ts:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Wholesale file copy (71 identical lines × 2 files) typescript-sdk/playground/union-to-babylon-cw20.ts:1— typescript-sdk/playground/union-to-babylon-cw20.ts:1 · typescript-sdk/playground/union-to-holesky-cw20.ts:1 — these 2 files are line-for-line copies of one another — 71 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.
Duplicated block (70 lines × 2 locations) typescript-sdk/playground/babylon-to-holesky.ts:13— typescript-sdk/playground/babylon-to-holesky.ts:13 · typescript-sdk/playground/osmosis-to-holesky.ts:13 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Wholesale file copy (66 identical lines × 2 files) typescript-sdk/playground/holesky-to-babylon.ts:1— typescript-sdk/playground/holesky-to-babylon.ts:1 · typescript-sdk/playground/holesky-to-union.ts:1 — these 2 files are line-for-line copies of one another — 66 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.
Duplicated block (56 lines × 3 locations) REDACTED:13— REDACTED:13 · typescript-sdk/playground/union-to-babylon-cw20.ts:13 · typescript-sdk/playground/union-to-babylon.ts:13 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) app2/src/routes/explorer/packets/+page.svelte:24— app2/src/routes/explorer/packets/+page.svelte:24 · app2/src/routes/explorer/transfers/+page.svelte:25 — the two spans are one implementation copied and then locally edited — 337 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (52 identical lines × 2 files) app2/src/lib/dashboard/components/DeleteAccountModal.svelte:2— app2/src/lib/dashboard/components/DeleteAccountModal.svelte:2 · app2/src/lib/dashboard/components/UnlinkAccountModal.svelte:2 — these 2 files are line-for-line copies of one another — 52 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.
Duplicated block (50 lines × 2 locations) app2/src/lib/components/stake/BondComponent.svelte:364— app2/src/lib/components/stake/BondComponent.svelte:364 · app2/src/lib/components/stake/QuickWithdrawComponent.svelte:272 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (45 lines × 2 locations) app2/src/lib/dashboard/stores/user.svelte.ts:339— app2/src/lib/dashboard/stores/user.svelte.ts:339 · app2/src/lib/dashboard/stores/user.svelte.ts:432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (45 lines × 3 locations) typescript-sdk/playground/holesky-to-babylon.ts:13— typescript-sdk/playground/holesky-to-babylon.ts:13 · typescript-sdk/playground/holesky-to-stargaze.ts:13 · typescript-sdk/playground/holesky-to-union.ts:13 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (44 lines × 2 locations) app2/src/routes/eudrop/claim/step/Step1.svelte:29— app2/src/routes/eudrop/claim/step/Step1.svelte:29 · app2/src/routes/liquid-staking/+page.svelte:88 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (43 lines × 2 locations) app2/src/routes/eudrop/claim/+page.svelte:62— app2/src/routes/eudrop/claim/+page.svelte:62 · app2/src/routes/liquid-staking/+page.svelte:33 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) ts-sdk-cosmos/src/Cosmos.ts:386— ts-sdk-cosmos/src/Cosmos.ts:386 · ts-sdk/src/cosmos/query.ts:26 — the two spans are one implementation copied and then locally edited — 308 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (42 lines × 2 locations) app2/src/lib/dashboard/database.types.ts:419— app2/src/lib/dashboard/database.types.ts:419 · app2/src/lib/dashboard/database.types.ts:867 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (41 lines × 2 locations) app2/src/lib/stores/statistics.svelte.ts:32— app2/src/lib/stores/statistics.svelte.ts:32 · app2/src/lib/stores/statistics.svelte.ts:76 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) typescript-sdk/playground/holesky-to-sepolia.ts:38— typescript-sdk/playground/holesky-to-sepolia.ts:38 · typescript-sdk/playground/sepolia-to-holesky.ts:36 — the two spans are one implementation copied and then locally edited — 267 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (40 lines × 2 locations) typescript-sdk/playground/aptos-to-aptos-legacy.ts:11— typescript-sdk/playground/aptos-to-aptos-legacy.ts:11 · typescript-sdk/playground/aptos-to-union-legacy.ts:11 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (38 lines × 2 locations) ceremony/src/lib/components/Blink.svelte:2— ceremony/src/lib/components/Blink.svelte:2 · zkgm-dev/src/lib/components/Blink.svelte:2 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function (anonymous) (cyclomatic 54, cognitive 191) sentinel2/src/escrow-supply-control-loop.ts:118— (anonymous) has cyclomatic complexity 54 and cognitive complexity 191; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function mapSupabaseErrorToCustomError (cyclomatic 28, cognitive 21) app2/src/lib/dashboard/errors.ts:57— mapSupabaseErrorToCustomError has cyclomatic complexity 28 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getMessage (cyclomatic 27, cognitive 26) app2/src/lib/components/stake/StatusDisplay.svelte:108— getMessage has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (top-level) (cyclomatic 22, cognitive 21) app2/src/lib/dashboard/database.types.ts:1— (top-level) has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 28) REDACTED:145— (anonymous) has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 20) app2/src/lib/stores/sorted-balances.svelte.ts:75— (anonymous) has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateState (cyclomatic 18, cognitive 9) ceremony/src/lib/state/contributor.svelte.ts:292— updateState has cyclomatic complexity 18 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isCurrentPath (cyclomatic 17, cognitive 48) app2/src/lib/components/layout/Navigation.svelte:82— isCurrentPath has cyclomatic complexity 17 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 25) app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte:205— (anonymous) has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onSome (cyclomatic 16, cognitive 14) app2/src/lib/transfer/shared/services/filling/check-filling.ts:73— onSome has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onmessage (cyclomatic 16, cognitive 14) app2/src/routes/explorer/orbital/+page.svelte:76— onmessage has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateAndDrawNodes (cyclomatic 14, cognitive 26) app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:389— updateAndDrawNodes has cyclomatic complexity 14 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function formatWaitTime (cyclomatic 14, cognitive 16) ceremony/src/lib/utils/utils.ts:108— formatWaitTime has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 12) REDACTED:86— (anonymous) has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 15) typescript-sdk/src/query/offchain/ucs03-channels.ts:75— (anonymous) has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 31) sentinel2/src/check-balances.ts:179— (anonymous) has cyclomatic complexity 12 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 20) app2/src/lib/components/ui/DateTimeComponent.svelte:40— (anonymous) has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 14) typescript-sdk/src/aptos/transfer.ts:106— (anonymous) has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 11) ts-sdk/src/internal/tokenOrder.ts:135— (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 11, cognitive 33) sentinel2/src/check-ssl-certificates.ts:48— (anonymous) has cyclomatic complexity 11 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
ts-sdk/src/Ucs03.ts: 1871 lines of code ts-sdk/src/Ucs03.ts:1— ts-sdk/src/Ucs03.ts has 1871 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
ts-sdk/src/PriceOracle.ts: 755 lines of code ts-sdk/src/PriceOracle.ts:1— ts-sdk/src/PriceOracle.ts has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/stores/fee.svelte.ts · ×1
app2/src/lib/stores/fee.svelte.ts: 710 lines of code app2/src/lib/stores/fee.svelte.ts:1— app2/src/lib/stores/fee.svelte.ts has 710 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/components/stake/BondComponent.svelte · ×1
app2/src/lib/components/stake/BondComponent.svelte: 673 lines of code app2/src/lib/components/stake/BondComponent.svelte:1— app2/src/lib/components/stake/BondComponent.svelte has 673 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· ts-sdk-cosmos/src/Cosmos.ts · ×1
ts-sdk-cosmos/src/Cosmos.ts: 672 lines of code ts-sdk-cosmos/src/Cosmos.ts:1— ts-sdk-cosmos/src/Cosmos.ts has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte · ×1
app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte: 633 lines of code app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte:1— app2/src/routes/explorer/orbital/charts/ChainFlowChart.svelte has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· ts-sdk-evm/src/internal/zkgmClient.ts · ×1
ts-sdk-evm/src/internal/zkgmClient.ts: 626 lines of code ts-sdk-evm/src/internal/zkgmClient.ts:1— ts-sdk-evm/src/internal/zkgmClient.ts has 626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
ts-sdk-sui/src/Sui.ts: 625 lines of code ts-sdk-sui/src/Sui.ts:1— ts-sdk-sui/src/Sui.ts has 625 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/dashboard/components/WalletDialog.svelte · ×1
app2/src/lib/dashboard/components/WalletDialog.svelte: 621 lines of code app2/src/lib/dashboard/components/WalletDialog.svelte:1— app2/src/lib/dashboard/components/WalletDialog.svelte has 621 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
ts-sdk-evm/src/Evm.ts: 613 lines of code ts-sdk-evm/src/Evm.ts:1— ts-sdk-evm/src/Evm.ts has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· sentinel2/src/escrow-supply-control-loop.ts · ×1
sentinel2/src/escrow-supply-control-loop.ts: 611 lines of code sentinel2/src/escrow-supply-control-loop.ts:1— sentinel2/src/escrow-supply-control-loop.ts has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/components/stake/UnbondComponent.svelte · ×1
app2/src/lib/components/stake/UnbondComponent.svelte: 597 lines of code app2/src/lib/components/stake/UnbondComponent.svelte:1— app2/src/lib/components/stake/UnbondComponent.svelte has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/components/stake/StatusDisplay.svelte · ×1
app2/src/lib/components/stake/StatusDisplay.svelte: 596 lines of code app2/src/lib/components/stake/StatusDisplay.svelte:1— app2/src/lib/components/stake/StatusDisplay.svelte has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/dashboard/stores/user.svelte.ts · ×1
app2/src/lib/dashboard/stores/user.svelte.ts: 590 lines of code app2/src/lib/dashboard/stores/user.svelte.ts:1— app2/src/lib/dashboard/stores/user.svelte.ts has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/transfer/shared/components/Receiver.svelte · ×1
app2/src/lib/transfer/shared/components/Receiver.svelte: 590 lines of code app2/src/lib/transfer/shared/components/Receiver.svelte:1— app2/src/lib/transfer/shared/components/Receiver.svelte has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/dashboard/components/AchievementTabs.svelte · ×1
app2/src/lib/dashboard/components/AchievementTabs.svelte: 578 lines of code app2/src/lib/dashboard/components/AchievementTabs.svelte:1— app2/src/lib/dashboard/components/AchievementTabs.svelte has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
ts-sdk/src/Staking.ts: 566 lines of code ts-sdk/src/Staking.ts:1— ts-sdk/src/Staking.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/routes/explorer/orbital/charts/LatencyChart.svelte · ×1
app2/src/routes/explorer/orbital/charts/LatencyChart.svelte: 561 lines of code app2/src/routes/explorer/orbital/charts/LatencyChart.svelte:1— app2/src/routes/explorer/orbital/charts/LatencyChart.svelte has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/transfer/normal/steps/ApprovalStep.svelte · ×1
app2/src/lib/transfer/normal/steps/ApprovalStep.svelte: 522 lines of code app2/src/lib/transfer/normal/steps/ApprovalStep.svelte:1— app2/src/lib/transfer/normal/steps/ApprovalStep.svelte has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte · ×1
app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte: 500 lines of code app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte:1— app2/src/routes/explorer/orbital/charts/NetworkVisualizer.svelte has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/components/stake/QuickWithdrawComponent.svelte · ×1
app2/src/lib/components/stake/QuickWithdrawComponent.svelte: 498 lines of code app2/src/lib/components/stake/QuickWithdrawComponent.svelte:1— app2/src/lib/components/stake/QuickWithdrawComponent.svelte has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/dashboard/queries/private.ts · ×1
app2/src/lib/dashboard/queries/private.ts: 498 lines of code app2/src/lib/dashboard/queries/private.ts:1— app2/src/lib/dashboard/queries/private.ts has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 482 lines of code REDACTED:1— REDACTED has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/components/stake/WithdrawalComponent.svelte · ×1
app2/src/lib/components/stake/WithdrawalComponent.svelte: 480 lines of code app2/src/lib/components/stake/WithdrawalComponent.svelte:1— app2/src/lib/components/stake/WithdrawalComponent.svelte has 480 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· ts-sdk/src/ucs03/fungible-asset-order.ts · ×1
ts-sdk/src/ucs03/fungible-asset-order.ts: 455 lines of code ts-sdk/src/ucs03/fungible-asset-order.ts:1— ts-sdk/src/ucs03/fungible-asset-order.ts has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· ts-sdk/src/internal/tokenOrder.ts · ×1
ts-sdk/src/internal/tokenOrder.ts: 450 lines of code ts-sdk/src/internal/tokenOrder.ts:1— ts-sdk/src/internal/tokenOrder.ts has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte · ×1
app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte: 449 lines of code app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte:1— app2/src/lib/transfer/shared/components/ChainAsset/ChainSelector.svelte has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/routes/eudrop/claim/step/Step5.svelte · ×1
app2/src/routes/eudrop/claim/step/Step5.svelte: 438 lines of code app2/src/routes/eudrop/claim/step/Step5.svelte:1— app2/src/routes/eudrop/claim/step/Step5.svelte has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/routes/btcfi/step/Step3.svelte · ×1
app2/src/routes/btcfi/step/Step3.svelte: 436 lines of code app2/src/routes/btcfi/step/Step3.svelte:1— app2/src/routes/btcfi/step/Step3.svelte has 436 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· typescript-sdk/src/query/on-chain.ts · ×1
typescript-sdk/src/query/on-chain.ts: 419 lines of code typescript-sdk/src/query/on-chain.ts:1— typescript-sdk/src/query/on-chain.ts has 419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/wallet/evm/wagmi-config.svelte.ts · ×1
app2/src/lib/wallet/evm/wagmi-config.svelte.ts: 412 lines of code app2/src/lib/wallet/evm/wagmi-config.svelte.ts:1— app2/src/lib/wallet/evm/wagmi-config.svelte.ts has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· app2/src/lib/dashboard/queries/public.ts · ×1
app2/src/lib/dashboard/queries/public.ts: 408 lines of code app2/src/lib/dashboard/queries/public.ts:1— app2/src/lib/dashboard/queries/public.ts has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~3130 LoC) app2/src/lib/dashboard/database.types.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~763 LoC) app2/src/lib/stores/fee.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~635 LoC) app2/src/lib/dashboard/stores/user.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (app2/src/lib/dashboard/components/SocialConnections.svelte, app2/src/lib/dashboard/components/UnlinkAccountModal.svelte, app2/src/lib/dashboard/helpers.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~550 LoC) app2/src/lib/config/wallets/info.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~547 LoC) app2/src/lib/components/stake/BondComponent.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~518 LoC) REDACTED— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/shared/components/ChainAsset/RepresentationSelector.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~516 LoC) app2/src/lib/dashboard/queries/private.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 7 in-repo import(s) from 4 other file(s) do name it (app2/src/lib/dashboard/queries/index.ts, app2/src/lib/dashboard/stores/check.svelte.ts, app2/src/lib/dashboard/stores/user.svelte.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~510 LoC) app2/src/lib/components/stake/StatusDisplay.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (app2/src/lib/components/stake/BondComponent.svelte, app2/src/lib/components/stake/ProxyDustRecovery.svelte, app2/src/lib/components/stake/QuickWithdrawComponent.svelte and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~476 LoC) app2/src/lib/components/stake/UnbondComponent.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~423 LoC) app2/src/lib/dashboard/queries/public.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 4 in-repo import(s) from 2 other file(s) do name it (app2/src/lib/dashboard/queries/index.ts, app2/src/lib/dashboard/stores/wallets.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~420 LoC) app2/src/lib/wallet/evm/wagmi-config.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/evm/config.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~408 LoC) app2/src/lib/components/stake/WithdrawalComponent.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~395 LoC) app2/src/lib/components/stake/QuickWithdrawComponent.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~389 LoC) app2/src/lib/transfer/normal/steps/ApprovalStep.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/normal/steps/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~387 LoC) app2/src/lib/services/incentive.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~351 LoC) app2/src/lib/components/stake/ProxyDustRecovery.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/components/stake/BalanceCard.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~346 LoC) app2/src/lib/constants/chain-logos.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~336 LoC) app2/src/lib/transfer/shared/components/Receiver.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~314 LoC) app2/src/lib/transfer/normal/steps/SubmitStep.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/transfer/normal/steps/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~308 LoC) app2/src/lib/dashboard/components/AchievementTabs.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~305 LoC) app2/src/lib/transfer/shared/services/filling/create-context.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~296 LoC) app2/src/lib/dashboard/components/WalletDialog.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/dashboard/components/WalletStats.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~290 LoC) app2/src/lib/dashboard/stores/wallets.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (app2/src/lib/dashboard/components/WalletCard.svelte, app2/src/lib/dashboard/components/WalletDialog.svelte, app2/src/lib/dashboard/components/WalletDisplay.svelte and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~289 LoC) app2/src/lib/dashboard/stores/rewards.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/dashboard/stores/user.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~286 LoC) app2/src/lib/graphql/service.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/runtime.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~282 LoC) app2/src/lib/services/cosmos/chain-info/hyperweb-chain-info.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~281 LoC) app2/src/lib/transfer/shared/data/raw-transfer-data.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~279 LoC) app2/src/lib/dashboard/services/cache.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (app2/src/lib/dashboard/queries/private.ts, app2/src/lib/dashboard/queries/public.ts, app2/src/lib/dashboard/stores/airdrop.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~264 LoC) app2/src/lib/wallet/sui/config.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/wallet/sui/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~253 LoC) app2/src/lib/dashboard/stores/missions.svelte.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (app2/src/lib/dashboard/components/Mission.svelte, app2/src/lib/dashboard/stores/user.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~252 LoC) app2/src/lib/dashboard/services/add-cosmos-wallet.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/dashboard/components/WalletDialog.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~250 LoC) app2/src/lib/components/ui/Tooltip.svelte— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app2/src/lib/components/model/ErrorComponent.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~241 LoC) app2/src/lib/transfer/shared/services/filling/check-allowance.ts— no import path from any entry point (221 application, 51 tooling, 35 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@cosmjs/amino' — Declared in REDACTED 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 '@safe-global/safe-gateway-typescript-sdk' — Declared in REDACTED 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 'bs58' — Declared in REDACTED 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.
Orphaned file 11-cometbls/store.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ts-sdk/src/internal/tokenOrder.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/ssz/src/tree_hash/merkleize_padded.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file typescript-sdk/src/cosmos/transfer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 11-cometbls/client_state.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file typescript-sdk/src/aptos/transfer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file typescript-sdk/src/query/on-chain.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ts-sdk/src/Indexer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/evm-storage-verifier/src/rlp_node_codec.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cosmwasm/lightclient/cometbls/src/storage.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app2/src/lib/services/cosmos/chain-info/hyperweb-chain-info.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sentinel2/src/check-balances.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app2/src/lib/dashboard/services/add-cosmos-wallet.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app2/src/lib/dashboard/services/cache.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cosmwasm/cw20-base/src/allowances.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ts-sdk/src/internal/zkgmClientRequest.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ts-sdk/src/Token.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app2/src/lib/dashboard/stores/rewards.svelte.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/aptos-verifier/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sentinel2/src/db-queries.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file voyager/modules/proof/movement/src/main.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app2/src/lib/dashboard/stores/missions.svelte.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file tools/union-test/src/channel_provider.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file typescript-sdk/src/types.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging voyager/plugins/zkgm-filter/src/main.rs:163— `trace!` at line 163 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/zkgm-filter/src/main.rs:169— `info!` at line 169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:361— `error!` at line 361 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:415— `error!` at line 415 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:419— `error!` at line 419 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1033— `info!` at line 1033 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1582— `info!` at line 1582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1590— `info!` at line 1590 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1680— `warn!` at line 1680 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1757— `info!` at line 1757 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1776— `error!` at line 1776 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1783— `error!` at line 1783 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/call.rs:135— `info!` at line 135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/call.rs:159— `warn!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/call.rs:185— `info!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/call.rs:202— `info!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/call.rs:239— `info!` at line 239 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/callback.rs:301— `info!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:397— `error!` at line 397 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:495— `error!` at line 495 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:499— `error!` at line 499 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:592— `warn!` at line 592 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:665— `info!` at line 665 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:688— `error!` at line 688 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging voyager/plugins/transaction-batch/src/lib.rs:695— `error!` at line 695 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Duplicated predicate galoisd/cmd/galoisd/cmd/serve.go:55— `logLevel > int(zerolog.PanicLevel) || logLevel < int(zerolog.TraceLevel)` appears character-identically in 2 files — galoisd/cmd/galoisd/cmd/serve.go, galoisd/cmd/galoisd/cmd/serve_bls12381.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ts-sdk/src/sui/channel-balance.ts:44— `!result || result.length === 0 || !result[0].returnValues || !result[0].returnValues[0]` appears character-identically in 2 files — ts-sdk/src/sui/channel-balance.ts, ts-sdk/src/sui/quote-token.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate app2/src/lib/services/cosmos/clients.ts:69— `connectionStatus !== "connected" || !connectedWallet` appears character-identically in 2 files — app2/src/lib/services/cosmos/clients.ts, app2/src/lib/services/transfer-ucs03-cosmos/chain.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ts-sdk-evm/src/Evm.ts:406— `gasTokenMeta && gasTokenMeta.address.toLowerCase() === tokenAddress.toLowerCase()` appears character-identically in 2 files — ts-sdk-evm/src/Evm.ts, ts-sdk/src/evm/erc20.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate app2/src/lib/services/transfer-ucs03-evm/state.ts:71— `state._tag === "TransferReceipt" && state.state._tag === "Complete" && state.state.exit._tag === "Success"` appears character-identically in 2 files — app2/src/lib/services/transfer-ucs03-evm/state.ts, app2/src/lib/services/transfer/state.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate app2/src/lib/services/transfer-ucs03-cosmos/state.ts:46— `state.state._tag === "Complete" && state.state.exit._tag === "Failure"` appears character-identically in 3 files — app2/src/lib/services/transfer-ucs03-cosmos/state.ts, app2/src/lib/services/transfer-ucs03-evm/state.ts, app2/src/lib/services/transfer/state.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate app2/src/lib/wallet/cosmos/config.svelte.ts:54— `this.connectedWallet && this.connectionStatus === "connected"` appears character-identically in 2 files — app2/src/lib/wallet/cosmos/config.svelte.ts, app2/src/lib/wallet/sui/config.svelte.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ts-sdk/src/internal/tokenOrder.ts:80— `typeof u === "object" && u !== null && TypeId in u` appears character-identically in 2 files — ts-sdk/src/internal/tokenOrder.ts, ts-sdk/src/internal/zkgmClientRequest.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate voyager/plugins/transaction-batch-proof-lens/src/lib.rs:1677— `!overdue_events.is_empty() && overdue_events.len() + events.len() < client_config.min_batch_size` appears character-identically in 2 files — voyager/plugins/transaction-batch-proof-lens/src/lib.rs, voyager/plugins/transaction-batch/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/ethereum-sync-protocol/src/lib.rs:303— `fs.fork(Forks::Deneb) && epoch >= fork.epoch` appears character-identically in 2 files — lib/ethereum-sync-protocol/src/lib.rs, lib/ethereum-sync-protocol/src/utils.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/ethereum-sync-protocol/src/lib.rs:295— `fs.fork(Forks::Electra) && epoch >= fork.epoch` appears character-identically in 2 files — lib/ethereum-sync-protocol/src/lib.rs, lib/ethereum-sync-protocol/src/utils.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/ethereum-sync-protocol/src/lib.rs:286— `fs.fork(Forks::Fulu) && epoch >= fork.epoch` appears character-identically in 2 files — lib/ethereum-sync-protocol/src/lib.rs, lib/ethereum-sync-protocol/src/utils.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/u/src/vanity/create3.rs:164— `full_bytes_match && high_nibble == nibble` appears character-identically in 2 files — tools/u/src/vanity/create3.rs, tools/u/src/vanity/wrapped_token.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/u/src/vanity/create3.rs:239— `handle.join() && thread_result.is_some()` appears character-identically in 3 files — tools/u/src/vanity/create3.rs, tools/u/src/vanity/instantiate2_address.rs, tools/u/src/vanity/wrapped_token.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/u/src/vanity/create3.rs:47— `p.starts_with("0x") || p.starts_with("0X")` appears character-identically in 2 files — tools/u/src/vanity/create3.rs, tools/u/src/vanity/wrapped_token.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/u/src/vanity/create3.rs:147— `prefix_bytes.is_empty() && prefix_nibble.is_none()` appears character-identically in 2 files — tools/u/src/vanity/create3.rs, tools/u/src/vanity/wrapped_token.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/u/src/vanity/create3.rs:74— `s.starts_with("0x") || s.starts_with("0X")` appears character-identically in 2 files — tools/u/src/vanity/create3.rs, tools/u/src/vanity/wrapped_token.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate tools/u/src/vanity/create3.rs:172— `suffix_bytes.is_empty() && suffix_leading_nibble.is_none()` appears character-identically in 2 files — tools/u/src/vanity/create3.rs, tools/u/src/vanity/wrapped_token.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 107 significant file(s) lose their only recent owner: cosmwasm/access-manager/src/tests.rs, voyager/plugins/transaction-batch-proof-lens/src/lib.rs, lib/arbitrum-verifier/src/lib.rs, voyager/plugins/event-source/evm/src/main.rs, voyager/plugins/event-source/gno/src/lib.rs, voyager/plugins/transaction/cosmos/src/main.rs, lib/voyager-core/src/server.rs, cosmwasm/access-manager/src/contract.rs (+99 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 16 significant file(s) lose their only recent owner: lib/sui-light-client-types/src/transaction_effects.rs, voyager/plugins/sui-packet-timeout/src/main.rs, lib/sui-light-client-types/src/checkpoint_summary.rs, voyager/plugins/transaction/sui/src/move_api.rs, voyager/plugins/client-update/sui/src/main.rs, voyager/plugins/sui-ibc-app/src/main.rs, lib/gnark-key-parser/src/bls12381.rs, 11-cometbls/update.go (+8 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 13 significant file(s) lose their only recent owner: app2/src/lib/dashboard/database.types.ts, app2/src/routes/explorer/orbital/audio.ts, app2/src/lib/wallet/evm/config.svelte.ts, app2/src/lib/dashboard/queries/public.ts, ceremony/src/lib/stores/state.svelte.ts, ceremony/src/lib/state/contributor.svelte.ts, app2/src/lib/transfer/shared/data/raw-transfer-data.svelte.ts, app2/src/lib/dashboard/errors.ts (+5 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 7 significant file(s) lose their only recent owner: ts-sdk/src/PriceOracle.ts, ts-sdk-cosmos/src/Cosmos.ts, app2/src/lib/utils/effect.svelte.ts, ts-sdk/src/ZkgmClient.ts, app2/src/lib/logging/tracing.ts, ts-sdk-evm/src/EvmZkgmClient.ts, ts-sdk/src/Call.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 4 significant file(s) lose their only recent owner: tools/union-test/src/channel_provider.rs, ts-sdk/src/sui/sui_coin.ts, ts-sdk/src/aptos/contract.ts, ts-sdk/src/sui/client.ts. Pair on, review, or document these before any departure.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×4
Diagnostic log message is built whether or not it is wanted app2/src/lib/gasprice/index.ts:104— `logDebug` at line 104 is called with an argument built by `JSON.stringify(x)` (line 105), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted app2/src/lib/gasprice/index.ts:116— `logDebug` at line 116 is called with an argument built by `JSON.stringify(x)` (line 116), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted app2/src/lib/gasprice/index.ts:175— `logDebug` at line 175 is called with an argument built by `JSON.stringify(x)` (line 175), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted app2/src/lib/gasprice/index.ts:208— `logDebug` at line 208 is called with an argument built by `JSON.stringify(atomic)` (line 209), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because logDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
README/code drift galoisd/README.md:106— galoisd/README.md links to `./proot/api/v1/prover.proto`, but `galoisd/proot/api/v1/prover.proto` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift cosmwasm/cw20-base/README.md:4— cosmwasm/cw20-base/README.md links to `../../packages/cw20/README.md`, but `packages/cw20/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift lib/beacon-api-types/README.md:5— lib/beacon-api-types/README.md links to `lib/beacon-api/`, but `lib/beacon-api-types/lib/beacon-api` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 355 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
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 (153 single-owned of 689 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 689 of the 1537 production source files in this repository met that bar). They are anonymized user #6 (2 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (1 file(s)), anonymized user #10 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: uniond/app/upgrades/v1_3_0/upgrade.go, uniond/app/wasm.go, galoisd/pkg/emulated/g2.go, typescript-sdk/src/query/on-chain.ts, devnet-compose/src/main.rs, tools/u/src/slot.rs.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 274 project(s) overshoot their size bounds, lowering Project Cohesion to 9.8/10. The most over is `app2` (22170 LoC, 270 module-visible types across 47 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 82 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: 11-cometbls/store.go, ts-sdk/src/internal/tokenOrder.ts, lib/ssz/src/tree_hash/merkleize_padded.rs, typescript-sdk/src/cosmos/transfer.ts, 11-cometbls/client_state.go, typescript-sdk/src/aptos/transfer.ts, typescript-sdk/src/query/on-chain.ts, ts-sdk/src/Indexer.ts (and 74 more) (87 orphaned of 689 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 689 of the 1537 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 4909/5060 types (97%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 127/138 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `app2`, `ceremony`, `cosmwasm/cw20-base`, `cosmwasm/cw20-wrapped-tokenfactory` and 6 more.
R8 · Dependency Hygiene· Type-only dependency '@cosmjs/cosmwasm-stargate' in production deps · ×1
Type-only dependency '@cosmjs/cosmwasm-stargate' in production deps sentinel2/src/fund-babylon-accounts.ts:1— Every import is type-only — move it to devDependencies.
Security headers incomplete vercel.json:1— Set: Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy. Missing: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/8 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) reduce the strict null checking score — ~0.4 `!` null assertions per 1k TypeScript source lines — 21 assertion(s) across the 57920 source line(s) of the 475 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: sentinel2/src/escrow-supply-control-loop.ts (10), ts-sdk/src/Ucs03.ts (2), app2/src/lib/utils/effect.svelte.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated: cosmossdk.io/api — `cosmossdk.io/api` is required at v0.7.6 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get cosmossdk.io/api@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/client/v2 — `cosmossdk.io/client/v2` is required at v2.0.0-beta.5 in REDACTED, but v2.11.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/client/v2@v2.11.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/core — `cosmossdk.io/core` is required at v0.11.0 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get cosmossdk.io/core@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/depinject — `cosmossdk.io/depinject` is required at v1.1.0 in REDACTED, but v1.2.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/depinject@v1.2.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/errors — `cosmossdk.io/errors` is required at v1.0.1 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/errors@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/errors — `cosmossdk.io/errors` is required at v1.0.1 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/errors@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/log — `cosmossdk.io/log` is required at v1.5.0 in REDACTED, but v1.6.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/log@v1.6.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/log — `cosmossdk.io/log` is required at v1.3.1 in REDACTED, but v1.6.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/log@v1.6.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/math — `cosmossdk.io/math` is required at v1.5.0 in REDACTED, but v1.5.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/math@v1.5.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/math — `cosmossdk.io/math` is required at v1.3.0 in REDACTED, but v1.5.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/math@v1.5.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/store — `cosmossdk.io/store` is required at v1.1.0 in REDACTED, but v1.1.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/store@v1.1.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: cosmossdk.io/x/upgrade — `cosmossdk.io/x/upgrade` is required at v0.1.4 in REDACTED, but v0.2.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get cosmossdk.io/x/upgrade@v0.2.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/CosmWasm/wasmvm/v2 — `github.com/CosmWasm/wasmvm/v2` is required at v2.2.1 in REDACTED, but v2.3.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/CosmWasm/wasmvm/v2@v2.3.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cometbft/cometbft — `github.com/cometbft/cometbft` is required at v0.38.7 in REDACTED, but v1.0.1 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/cometbft/cometbft@v1.0.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cosmos/cosmos-db — `github.com/cosmos/cosmos-db` is required at v1.1.1 in REDACTED, but v1.1.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cosmos/cosmos-db@v1.1.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cosmos/cosmos-sdk — `github.com/cosmos/cosmos-sdk` is required at v0.50.6 in REDACTED, but v0.55.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cosmos/cosmos-sdk@v0.55.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cosmos/gogoproto — `github.com/cosmos/gogoproto` is required at v1.7.0 in REDACTED, but v1.7.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cosmos/gogoproto@v1.7.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cosmos/gogoproto — `github.com/cosmos/gogoproto` is required at v1.4.12 in REDACTED, but v1.7.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cosmos/gogoproto@v1.7.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cosmos/ibc-go/v8 — `github.com/cosmos/ibc-go/v8` is required at v8.3.1 in REDACTED, but v8.8.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cosmos/ibc-go/v8@v8.8.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/cosmos/ics23/go — `github.com/cosmos/ics23/go` is required at v0.10.0 in REDACTED, but v0.11.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/cosmos/ics23/go@v0.11.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/holiman/uint256 — `github.com/holiman/uint256` is required at v1.2.3 in REDACTED, but v1.3.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/holiman/uint256@v1.3.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/rs/zerolog — `github.com/rs/zerolog` is required at v1.33.0 in REDACTED, but v1.35.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/rs/zerolog@v1.35.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/cast — `github.com/spf13/cast` is required at v1.7.1 in REDACTED, but v1.10.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/cast@v1.10.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/cobra — `github.com/spf13/cobra` is required at v1.8.0 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/cobra@v1.10.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/spf13/cobra — `github.com/spf13/cobra` is required at v1.8.1 in REDACTED, but v1.10.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/spf13/cobra@v1.10.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Skipped (documented): guarantees given HRP matches ts-sdk/test/schema/bech32.test.ts:54— Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
Skipped (documented): should return all token metadata ts-sdk/test/evm/erc20.test.ts:113— Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
Skipped (documented): ignore app2/src/lib/utils/effect.svelte.test.ts:87— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): none app2/src/lib/utils/effect.svelte.test.ts:88— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): error (default) app2/src/lib/utils/effect.svelte.test.ts:89— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Off the main sequence: consensus-primitives — consensus-primitives: abstractness 0.00, instability 0.00, distance 1.00 — 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: mpc-shared — mpc-shared: abstractness 0.00, instability 0.00, distance 1.00 — 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: unionlabs-primitives — unionlabs-primitives: abstractness 0.20, instability 0.00, distance 0.80 — 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.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 65 file(s) — `app2/src/hooks.client.ts`, `app2/src/lib/components/layout/Sidebar/navigation.ts`, `app2/src/lib/constants/spender-addresses.ts`, `app2/src/lib/dashboard/client.ts`, `app2/src/lib/gasprice/error.ts`, … (+60 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17546-bb66-7d7d-b4ed-d60c74862742 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 1391 · Warnings: 1613 · Recommendations: 184 · Info: 44 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 25-10-2026 @ 22:55 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.