Public report of airswap/airswap-web, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 21:39 UTC · Survey ID cd_6f6f87f2fae3453ea1054c10d16f4946
airswap/airswap-web
Measured 16 November 2026, 21:39 UTC, at code version ad1e959
Bus factor is not measured: No living knowledge left to concentrate.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 34,863 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 18.9
Findings by how serious they are
102 critical366 serious272 minor
9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 21:39 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
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. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
64of 64 dimensions measured by tools.
698of 740 findings point to an exact file and line, so you can open each one in the code. The other 42 concern the repository as a whole, such as missing documentation.
64dimensions across 7 lenses, read from 34,863 lines of product code in 1 project.
airswap/airswap-web is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code, and it has packages under a licence on your banned list. It scores 32.5 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 18.9, is the weakest lens and counts most in the score. The best first step is replacing the ten packages under a banned licence, worth about 11.4 points. Replacing the 48 deprecated dependencies comes next, worth about 7.7 points. Raising Production Readiness to 70 would lift the score to about 43.9.
Sixty-seven known security holes in the packages the code depends on can be used by attackers. Ten packages carry licence risk, and seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, replacing or clearing the banned-licence packages and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed. The seven uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 34,863 lines, about €34,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 18.9 to 70, the lowest score rated Strong, the score would rise from 32.5 to about 43.9.
Code composition: what the lines of code are
Product code 97%Tests 3%
Rebuild cost: about €34,000 · Estimate
Cost to rebuild
€11,000 to €56,000, for 186 to 589 hours of work, about 0.2 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 32. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 34,863 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 10 Banned license finding(s) in License Compliance — start with package.json (9), REDACTED.
Raises the score by about 11.4 points · Medium effort · License Compliance
2
Resolve the 48 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (48).
Raises the score by about 7.7 points · Medium effort · Dependency Hygiene
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Procfile.
Raises the score by about 2.9 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €34,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 18.9 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 10 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 11.4 points for medium effort, because it clears the 10 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 586 lines over the last 90 days, which is about 2,377 lines a year. At that pace, the extra work comes to an estimated 0.2 to 0.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: 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.
357 modules, with 124 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 317 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.
components.@widgets.MyLimitOrdersWidget.hooks uses entities.DelegateRule.DelegateRule, so a change to entities.DelegateRule.DelegateRule can break components.@widgets.MyLimitOrdersWidget.hooks, while a change to components.@widgets.MyLimitOrdersWidget.hooks can't break entities.DelegateRule.DelegateRule.
Position
Below the diagonal: components.@widgets.MyLimitOrdersWidget.hooks uses a module listed above it, which is the healthy direction.
components.@widgets.MyLimitOrdersWidget.hooks uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.MyLimitOrdersWidget.hooks, while a change to components.@widgets.MyLimitOrdersWidget.hooks can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.MyLimitOrdersWidget.hooks uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget.entities.MyOrder uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break components.@widgets.MyOrdersWidget.entities.MyOrder, while a change to components.@widgets.MyOrdersWidget.entities.MyOrder can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: components.@widgets.MyOrdersWidget.entities.MyOrder uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget.entities.MyOrder uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.MyOrdersWidget.entities.MyOrder, while a change to components.@widgets.MyOrdersWidget.entities.MyOrder can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.MyOrdersWidget.entities.MyOrder uses a module listed above it, which is the healthy direction.
components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus, while a change to components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus uses a module listed above it, which is the healthy direction.
components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus uses types.orderTypes, so a change to types.orderTypes can break components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus, while a change to components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus can't break types.orderTypes.
Position
Below the diagonal: components.@widgets.OrderDetailWidget.subcomponents.FilledAndStatus.FilledAndStatus uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus uses a type in types.orderStatus.
components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus, while a change to components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus uses a type in types.orderTypes.
components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus uses types.orderTypes, so a change to types.orderTypes can break components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus, while a change to components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus can't break types.orderTypes.
Position
Below the diagonal: components.@widgets.OrderDetailWidget.subcomponents.RecipientAndStatus.RecipientAndStatus uses a module listed above it, which is the healthy direction.
components.TokenList.helpers uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break components.TokenList.helpers, while a change to components.TokenList.helpers can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: components.TokenList.helpers uses a module listed above it, which is the healthy direction.
components.TokenList.helpers uses features.balances.balancesSlice, so a change to features.balances.balancesSlice can break components.TokenList.helpers, while a change to components.TokenList.helpers can't break features.balances.balancesSlice.
Position
Below the diagonal: components.TokenList.helpers uses a module listed above it, which is the healthy direction.
components.TransactionsTab.helpers uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break components.TransactionsTab.helpers, while a change to components.TransactionsTab.helpers can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: components.TransactionsTab.helpers uses a module listed above it, which is the healthy direction.
components.TransactionsTab.helpers uses types.transactionTypes, so a change to types.transactionTypes can break components.TransactionsTab.helpers, while a change to components.TransactionsTab.helpers can't break types.transactionTypes.
Position
Below the diagonal: components.TransactionsTab.helpers uses a module listed above it, which is the healthy direction.
entities.AppTokenInfo uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break entities.AppTokenInfo, while a change to entities.AppTokenInfo can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: entities.AppTokenInfo uses a module listed above it, which is the healthy direction.
entities.AppTokenInfo uses features.balances.balancesSlice, so a change to features.balances.balancesSlice can break entities.AppTokenInfo, while a change to entities.AppTokenInfo can't break features.balances.balancesSlice.
Position
Below the diagonal: entities.AppTokenInfo uses a module listed above it, which is the healthy direction.
entities.ApprovalEntity uses features.balances.balancesApi, so a change to features.balances.balancesApi can break entities.ApprovalEntity, while a change to entities.ApprovalEntity can't break features.balances.balancesApi.
Position
Below the diagonal: entities.ApprovalEntity uses a module listed above it, which is the healthy direction.
entities.ApprovalEntity uses features.balances.balancesSlice, so a change to features.balances.balancesSlice can break entities.ApprovalEntity, while a change to entities.ApprovalEntity can't break features.balances.balancesSlice.
Position
Below the diagonal: entities.ApprovalEntity uses a module listed above it, which is the healthy direction.
entities.FullSwapERC20Event uses types.transactionTypes, so a change to types.transactionTypes can break entities.FullSwapERC20Event, while a change to entities.FullSwapERC20Event can't break types.transactionTypes.
Position
Below the diagonal: entities.FullSwapERC20Event uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction.SubmittedTransaction uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break entities.SubmittedTransaction.SubmittedTransaction, while a change to entities.SubmittedTransaction.SubmittedTransaction can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: entities.SubmittedTransaction.SubmittedTransaction uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction.SubmittedTransaction uses entities.DelegateRule.DelegateRule, so a change to entities.DelegateRule.DelegateRule can break entities.SubmittedTransaction.SubmittedTransaction, while a change to entities.SubmittedTransaction.SubmittedTransaction can't break entities.DelegateRule.DelegateRule.
Position
Below the diagonal: entities.SubmittedTransaction.SubmittedTransaction uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction.SubmittedTransaction uses types.transactionTypes, so a change to types.transactionTypes can break entities.SubmittedTransaction.SubmittedTransaction, while a change to entities.SubmittedTransaction.SubmittedTransaction can't break types.transactionTypes.
Position
Below the diagonal: entities.SubmittedTransaction.SubmittedTransaction uses a module listed above it, which is the healthy direction.
entities.WETHEvent uses entities.WETHEvent.WETHEvent, so a change to entities.WETHEvent.WETHEvent can break entities.WETHEvent, while a change to entities.WETHEvent can't break entities.WETHEvent.WETHEvent.
Position
Below the diagonal: entities.WETHEvent uses a module listed above it, which is the healthy direction.
entities.WETHEvent uses types.transactionTypes, so a change to types.transactionTypes can break entities.WETHEvent, while a change to entities.WETHEvent can't break types.transactionTypes.
Position
Below the diagonal: entities.WETHEvent uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses a type in entities.DelegateRule.DelegateRule.
components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses entities.DelegateRule.DelegateRule, so a change to entities.DelegateRule.DelegateRule can break components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList, while a change to components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList can't break entities.DelegateRule.DelegateRule.
Position
Below the diagonal: components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses a module listed above it, which is the healthy direction.
components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList, while a change to components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses a type in components.@widgets.MyOrdersWidget.entities.MyOrder.
components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses components.@widgets.MyOrdersWidget.entities.MyOrder, so a change to components.@widgets.MyOrdersWidget.entities.MyOrder can break components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList, while a change to components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList can't break components.@widgets.MyOrdersWidget.entities.MyOrder.
Position
Below the diagonal: components.@widgets.MyLimitOrdersWidget.subcomponents.MyLimitOrdersList uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.MyOrdersWidget, while a change to components.@widgets.MyOrdersWidget can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.MyOrdersWidget uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget uses components.@widgets.MyOrdersWidget.entities.MyOrder, so a change to components.@widgets.MyOrdersWidget.entities.MyOrder can break components.@widgets.MyOrdersWidget, while a change to components.@widgets.MyOrdersWidget can't break components.@widgets.MyOrdersWidget.entities.MyOrder.
Position
Below the diagonal: components.@widgets.MyOrdersWidget uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget.entities uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break components.@widgets.MyOrdersWidget.entities, while a change to components.@widgets.MyOrdersWidget.entities can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: components.@widgets.MyOrdersWidget.entities uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget.entities uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.MyOrdersWidget.entities, while a change to components.@widgets.MyOrdersWidget.entities can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.MyOrdersWidget.entities uses a module listed above it, which is the healthy direction.
components.@widgets.MyOrdersWidget.entities uses components.@widgets.MyOrdersWidget.entities.MyOrder, so a change to components.@widgets.MyOrdersWidget.entities.MyOrder can break components.@widgets.MyOrdersWidget.entities, while a change to components.@widgets.MyOrdersWidget.entities can't break components.@widgets.MyOrdersWidget.entities.MyOrder.
Position
Below the diagonal: components.@widgets.MyOrdersWidget.entities uses a module listed above it, which is the healthy direction.
components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList uses types.orderStatus, so a change to types.orderStatus can break components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList, while a change to components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList can't break types.orderStatus.
Position
Below the diagonal: components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList uses a type in components.@widgets.MyOrdersWidget.entities.MyOrder.
components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList uses components.@widgets.MyOrdersWidget.entities.MyOrder, so a change to components.@widgets.MyOrdersWidget.entities.MyOrder can break components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList, while a change to components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList can't break components.@widgets.MyOrdersWidget.entities.MyOrder.
Position
Below the diagonal: components.@widgets.MyOtcOrdersWidget.subcomponents.MyOtcOrdersList uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.TransactionsTab.subcomponents.AnimatedWalletTransaction.AnimatedWalletTransaction uses a type in entities.SubmittedTransaction.SubmittedTransaction.
components.TransactionsTab.subcomponents.AnimatedWalletTransaction.AnimatedWalletTransaction uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break components.TransactionsTab.subcomponents.AnimatedWalletTransaction.AnimatedWalletTransaction, while a change to components.TransactionsTab.subcomponents.AnimatedWalletTransaction.AnimatedWalletTransaction can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: components.TransactionsTab.subcomponents.AnimatedWalletTransaction.AnimatedWalletTransaction uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.TransactionsTab.subcomponents.WalletTransaction.WalletTransaction uses a type in entities.SubmittedTransaction.SubmittedTransaction.
components.TransactionsTab.subcomponents.WalletTransaction.WalletTransaction uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break components.TransactionsTab.subcomponents.WalletTransaction.WalletTransaction, while a change to components.TransactionsTab.subcomponents.WalletTransaction.WalletTransaction can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: components.TransactionsTab.subcomponents.WalletTransaction.WalletTransaction uses a module listed above it, which is the healthy direction.
entities.ApproveEvent uses types.transactionTypes, so a change to types.transactionTypes can break entities.ApproveEvent, while a change to entities.ApproveEvent can't break types.transactionTypes.
Position
Below the diagonal: entities.ApproveEvent uses a module listed above it, which is the healthy direction.
entities.ApproveEvent uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break entities.ApproveEvent, while a change to entities.ApproveEvent can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: entities.ApproveEvent uses a module listed above it, which is the healthy direction.
entities.CancelEvent uses types.transactionTypes, so a change to types.transactionTypes can break entities.CancelEvent, while a change to entities.CancelEvent can't break types.transactionTypes.
Position
Below the diagonal: entities.CancelEvent uses a module listed above it, which is the healthy direction.
entities.CancelEvent uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break entities.CancelEvent, while a change to entities.CancelEvent can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: entities.CancelEvent uses a module listed above it, which is the healthy direction.
entities.DelegateRule uses entities.DelegateRule.DelegateRule, so a change to entities.DelegateRule.DelegateRule can break entities.DelegateRule, while a change to entities.DelegateRule can't break entities.DelegateRule.DelegateRule.
Position
Below the diagonal: entities.DelegateRule uses a module listed above it, which is the healthy direction.
entities.DelegateRule uses types.transactionTypes, so a change to types.transactionTypes can break entities.DelegateRule, while a change to entities.DelegateRule can't break types.transactionTypes.
Position
Below the diagonal: entities.DelegateRule uses a module listed above it, which is the healthy direction.
entities.DelegateRule uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break entities.DelegateRule, while a change to entities.DelegateRule can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: entities.DelegateRule uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break entities.SubmittedTransaction, while a change to entities.SubmittedTransaction can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: entities.SubmittedTransaction uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction uses entities.DelegateRule.DelegateRule, so a change to entities.DelegateRule.DelegateRule can break entities.SubmittedTransaction, while a change to entities.SubmittedTransaction can't break entities.DelegateRule.DelegateRule.
Position
Below the diagonal: entities.SubmittedTransaction uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction uses types.transactionTypes, so a change to types.transactionTypes can break entities.SubmittedTransaction, while a change to entities.SubmittedTransaction can't break types.transactionTypes.
Position
Below the diagonal: entities.SubmittedTransaction uses a module listed above it, which is the healthy direction.
entities.SubmittedTransaction uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break entities.SubmittedTransaction, while a change to entities.SubmittedTransaction can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: entities.SubmittedTransaction uses a module listed above it, which is the healthy direction.
features.orders uses entities.AppTokenInfo.AppTokenInfo, so a change to entities.AppTokenInfo.AppTokenInfo can break features.orders, while a change to features.orders can't break entities.AppTokenInfo.AppTokenInfo.
Position
Below the diagonal: features.orders uses a module listed above it, which is the healthy direction.
features.orders uses types.transactionTypes, so a change to types.transactionTypes can break features.orders, while a change to features.orders can't break types.transactionTypes.
Position
Below the diagonal: features.orders uses a module listed above it, which is the healthy direction.
features.orders uses entities.SubmittedTransaction.SubmittedTransaction, so a change to entities.SubmittedTransaction.SubmittedTransaction can break features.orders, while a change to features.orders can't break entities.SubmittedTransaction.SubmittedTransaction.
Position
Below the diagonal: features.orders uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
103
High / Critical
A05:2025 — Injection
13
High / Critical
Roadmap
Top priorities: Resolve the 10 Banned license finding(s) in License Compliance — start with package.json (9), REDACTED; Resolve the 48 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (48); Adopt pino (or winston) and log at meaningful points in the services you run.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 10 Banned license finding(s) in License Compliance — start with package.json (9), REDACTED.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
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 — 102
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 — 366
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 — 272
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 64 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, 698 of 740 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.ts, .tsx) and the coverage collector does support this ecosystem — it drives jest, vitest and mocha — but the runner its test command uses is one the coverage collector has no executor for (`@craco/craco`). Read from the manifests: the root package has a `scripts.test` of `craco test` and declares `@craco/craco`. Not scored — this is a gap in the analyzer's runner coverage, not a missing .ts/.tsx runner and not a defect in this repository.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts, .tsx) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but the runner its test command uses is one the re-runner has no executor for (`@craco/craco`). Read from the manifests: the root package has a `scripts.test` of `craco test` and declares `@craco/craco`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's runner coverage, not a missing .ts/.tsx runner and not a finding about this repository.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 125 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 125 of the 644 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (34817 LoC, 546 module-visible types across 228 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
AX7 Slice cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> airswap-web@0.1.0 start / > craco start / sh: 1: craco: not found" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> airswap-web@0.1.0 start / > craco start / sh: 1: craco: not found" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 471 further occurrence(s) are not listed individually; the score already reflects all 511.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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 (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
19 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SwapWidget.SwapWidget at 79. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being getOrdersFromSwapLogs.getOrdersFromSwapLogs at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/features/transactions/helpers/getOrdersFromSwapLogs.ts (getOrdersFromSwapLogs.getOrdersFromSwapLogs 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.
+ 14 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 19 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SwapWidget.SwapWidget (cyclomatic 79), OtcOrderDetailWidget.OtcOrderDetailWidget (cyclomatic 71), LimitOrderDetailWidget.LimitOrderDetailWidget (cyclomatic 54). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 19 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with OtcOrderDetailWidget.OtcOrderDetailWidget (cognitive 63), SwapWidget.SwapWidget (cognitive 61), LimitOrderDetailWidget.LimitOrderDetailWidget (cognitive 46). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 7.2 to about 8.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.3 / 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 20 FunctionTooLong finding(s) in God Classes — start with ActionButtons.tsx (2), MakeWidget.tsx, SwapWidget.tsx. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with MakeWidget.tsx, SwapWidget.tsx, LimitOrderDetailWidget.tsx. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 FileTooLong finding(s) in God Classes — start with MakeWidget.tsx, SwapWidget.tsx. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
1 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 69 tests.
Skipped test: should render a partial wallet address when providedsrc/components/WalletButton/WalletButton.spec.tsx:13
No assertions: should increment index by 3 after 3 secondsrc/components/Timer/Timer.spec.tsx:8
What to do
Resolve the 1 Skipped test finding(s) in Test Quality — start with WalletButton.spec.tsx. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No assertions finding(s) in Test Quality — start with Timer.spec.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
42 outdated direct production npm dependency(ies) of 67 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry 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, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 48 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (48). — One of this dimension's main actionable groups (48 recommendation-level).
Resolve the 9 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (9). — One of this dimension's main actionable groups (9 recommendation-level).
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.
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.
10 of 1554 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1554 package(s) this repository's committed lockfile installs for a consumer — its 67 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 14 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 12 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules).
Resolve the 10 Banned license finding(s) in License Compliance — start with package.json (9), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
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 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with MakeWidget.tsx, quotesHooks.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_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.
19 deducted task-comment markers across 34817 LoC (0.1/KLoC) → score 9.9. 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.
Resolve the 18 TodoComment finding(s) in Explicit Debt — start with useSwapLogs.ts (2), LimitOrderDetailWidget.tsx (2), useAppRouteParams.ts. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with OrderSubmittedScreen.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Procfile. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the namessrc/components/TokenList/TokenList.tsx:45
What to do
Resolve the 4 redundant comment finding(s) in Comment Value — start with useWindowSize.ts (2), ExtendedPricingHelpers.ts, balancesApi.ts. — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability9.0 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
39 % of calls cross a namespace and 0 % go through an interface, but 48 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
13 finding(s): 0 critical, 9 high, 4 medium, 0 low. 7 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. 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
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
No action in Static Analysis (SAST) — all 7 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 (7 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 52 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (52). — One of this dimension's main actionable groups (52 issue-level).
Resolve the 12 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
Resolve the 2 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 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.
125 of 125 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/components/@widgets/MakeWidget/MakeWidget.tsx. Counted over 125 of the 644 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3src/components/@widgets/MakeWidget/MakeWidget.tsx:1
Dormant codebase
What to do
Resolve the 122 Orphaned file finding(s) in Knowledge Freshness — start with index.ts (5), ActionButtons.tsx (3), Order.tsx (2). — One of this dimension's main actionable groups (122 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with MakeWidget.tsx, SwapWidget.tsx, LimitOrderDetailWidget.tsx. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase 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 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with WalletButton.tsx, OtcOrderDetailWidget.tsx, MakeWidget.tsx. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 6 Change coupling finding(s) in Change Coupling — start with TokenList.tsx, MyOrdersList.tsx, CancelWidget.tsx. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 67 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
End-of-life runtime: Node.js 18.nvmrc:1
What to do
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels6.3 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — src/components/Dropdown/Dropdown.tsx:88
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>. — public/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — public/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — public/whitepaper.htm:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — public/whitepaper.htm:79, public/whitepaper.htm:458
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 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.
`a.list-group-item-success:focus, a.list-group-item-success:hover, button.list-group-item-success:focus, button.list-group-item-success:hover` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/whitepaper/whitepaper.css:4932
`a.list-group-item-info:focus, a.list-group-item-info:hover, button.list-group-item-info:focus, button.list-group-item-info:hover` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/whitepaper/whitepaper.css:4955
`a.list-group-item-warning:focus, a.list-group-item-warning:hover, button.list-group-item-warning:focus, button.list-group-item-warning:hover` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/whitepaper/whitepaper.css:4978
`a.list-group-item-danger:focus, a.list-group-item-danger:hover, button.list-group-item-danger:focus, button.list-group-item-danger:hover` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — public/whitepaper/whitepaper.css:5001
`a:not([href]):not([tabindex]):focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:236
`.btn.focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:2780
`.show > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:3312
`.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:3432
`.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:5089
`.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:5118
`.carousel-control-prev:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/whitepaper/whitepaper.css:5558
`button:focus:enabled` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/components/@widgets/OrderDetailWidget/subcomponents/OrderRecipientInfo/OrderRecipientInfo.styles.tsx:43
`.collapsing` moves (`transition: height 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/whitepaper/whitepaper.css:3225
`.progress-bar-animated` moves (`animation: progress-bar-stripes 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/whitepaper/whitepaper.css:4839
`.modal.fade .modal-dialog` moves (`transition: transform 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/whitepaper/whitepaper.css:5092
`.carousel-item` moves (`transition: transform 0.6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — public/whitepaper/whitepaper.css:5482, public/whitepaper/whitepaper.css:5489
`div` moves (`transition: transform 0.3s cubic-bezier(0.68, 0.007, 0.488, 0.997)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/styled-components/Overlay/Overlay.tsx:14
`div` moves (`animation: _______ 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/styled-components/Overlay/Overlay.tsx:64
`div` moves (`animation: __________ 0.35s ease-in-out infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/components/TokenSelect/TokenSelect.styles.tsx:175
`.css-in-js` moves (`animation: _______ 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/components/LoadingSpinner/LoadingSpinner.styles.tsx:22
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. 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.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`useBalances` (slice 'balances') depends on `selectActiveTokens` from slice 'metadata'. — src/features/balances/balancesHooks.ts:23
`useBalances` (slice 'balances') depends on `useLatestSucceededTransaction` from slice 'transactions'. — src/features/balances/balancesHooks.ts:24
`getSlice` (slice 'balances') depends on `walletDisconnected` from slice 'web3'. — src/features/balances/balancesSlice.ts:116
`getSlice` (slice 'balances') depends on `walletChanged` from slice 'web3'. — src/features/balances/balancesSlice.ts:119
`cancelLimitOrder` (slice 'cancelLimit') depends on `submitTransaction` from slice 'transactions'. — src/features/cancelLimit/cancelLimitActions.ts:50
`cancelLimitOrder` (slice 'cancelLimit') depends on `setError` from slice 'takeLimit'. — src/features/cancelLimit/cancelLimitActions.ts:66
`submitDelegateRuleToStore` (slice 'delegateRules') depends on `setTransactions` from slice 'transactions'. — src/features/delegateRules/delegateRulesActions.ts:54
`delegateRulesSlice` (slice 'delegateRules') depends on `walletDisconnected` from slice 'web3'. — src/features/delegateRules/delegateRulesSlice.ts:65
`delegateRulesSlice` (slice 'delegateRules') depends on `walletChanged` from slice 'web3'. — src/features/delegateRules/delegateRulesSlice.ts:66
`useHistoricalDelegateRules` (slice 'delegateRules') depends on `selectAllTokenInfo` from slice 'metadata'. — src/features/delegateRules/hooks/useHistoricalDelegateRules.ts:20
`gasCostSlice` (slice 'gasCost') depends on `walletDisconnected` from slice 'web3'. — src/features/gasCost/gasCostSlice.ts:81
`createDelegateRule` (slice 'makeOrder') depends on `submitTransaction` from slice 'transactions'. — src/features/makeOrder/makeOrderActions.ts:120
`createOtcFullOrder` (slice 'makeOrder') depends on `sendOrderToIndexers` from slice 'indexer'. — src/features/makeOrder/makeOrderActions.ts:203
`writeActiveTokensToLocalStorage` (slice 'metadata') depends on `Web3State` from slice 'web3'. — src/features/metadata/metadataActions.ts:82
`useMetadata` (slice 'metadata') depends on `selectAllSupportedTokens` from slice 'registry'. — src/features/metadata/metadataHooks.ts:31
`useMetadata` (slice 'metadata') depends on `fetchSupportedTokens` from slice 'registry'. — src/features/metadata/metadataHooks.ts:90
`metadataSlice` (slice 'metadata') depends on `walletChanged` from slice 'web3'. — src/features/metadata/metadataSlice.ts:106
`metadataSlice` (slice 'metadata') depends on `chainIdChanged` from slice 'web3'. — src/features/metadata/metadataSlice.ts:112
`metadataSlice` (slice 'metadata') depends on `walletDisconnected` from slice 'web3'. — src/features/metadata/metadataSlice.ts:120
`selectAllTokenInfo` (slice 'metadata') depends on `selectChainId` from slice 'web3'. — src/features/metadata/metadataSlice.ts:151
`myOtcOrdersSlice` (slice 'myOtcOrders') depends on `walletDisconnected` from slice 'web3'. — src/features/myOtcOrders/myOtcOrdersSlice.ts:89
`myOtcOrdersSlice` (slice 'myOtcOrders') depends on `walletChanged` from slice 'web3'. — src/features/myOtcOrders/myOtcOrdersSlice.ts:90
`myOtcOrdersSlice` (slice 'myOtcOrders') depends on `setOtcOrder` from slice 'makeOrder'. — src/features/myOtcOrders/myOtcOrdersSlice.ts:92
`handleSubmittedSetRuleOrder` (slice 'orders') depends on `submitDelegateRuleToStore` from slice 'delegateRules'. — src/features/orders/ordersActions.ts:146
`handleSubmittedUnsetRuleOrder` (slice 'orders') depends on `unsetDelegateRuleFromStore` from slice 'delegateRules'. — src/features/orders/ordersActions.ts:161
`handleOrderError` (slice 'orders') depends on `declineTransaction` from slice 'transactions'. — src/features/orders/ordersActions.ts:185
`deposit` (slice 'orders') depends on `submitTransaction` from slice 'transactions'. — src/features/orders/ordersActions.ts:232
`takeErc20` (slice 'orders') depends on `revertTransaction` from slice 'transactions'. — src/features/orders/ordersActions.ts:374
`ordersSlice` (slice 'orders') depends on `walletDisconnected` from slice 'web3'. — src/features/orders/ordersSlice.ts:47
`useQuotesDebug` (slice 'quotes') depends on `selectAllTokenInfo` from slice 'metadata'. — src/features/quotes/hooks/useQuotesDebug.ts:43
`getBestOrder` (slice 'quotes') depends on `orderSortingFunction` from slice 'orders'. — src/features/quotes/quotesApi.ts:102
`useQuotes` (slice 'quotes') depends on `selectTradeTerms` from slice 'tradeTerms'. — src/features/quotes/quotesHooks.ts:58
`useQuotes` (slice 'quotes') depends on `selectProtocolFee` from slice 'metadata'. — src/features/quotes/quotesHooks.ts:59
`useQuotes` (slice 'quotes') depends on `getGasPrice` from slice 'gasCost'. — src/features/quotes/quotesHooks.ts:144
`registrySlice` (slice 'registry') depends on `walletDisconnected` from slice 'web3'. — src/features/registry/registrySlice.ts:57
`registrySlice` (slice 'registry') depends on `chainIdChanged` from slice 'web3'. — src/features/registry/registrySlice.ts:58
`takeLimitOrder` (slice 'takeLimit') depends on `submitTransaction` from slice 'transactions'. — src/features/takeLimit/takeLimitActions.ts:160
`cancelOrder` (slice 'takeOtc') depends on `getNonceUsed` from slice 'orders'. — src/features/takeOtc/takeOtcActions.ts:73
`cancelOrder` (slice 'takeOtc') depends on `removeOtcUserOrder` from slice 'myOtcOrders'. — src/features/takeOtc/takeOtcActions.ts:80
`cancelOrder` (slice 'takeOtc') depends on `revertTransaction` from slice 'transactions'. — src/features/takeOtc/takeOtcActions.ts:96
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
This repository serves requests — express() (index.js:4) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — index.js:4
What to do
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`onBaseAmountChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:468
`onChangeTokenClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:469
`onMaxButtonClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:470
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — src/components/WalletButton/WalletButton.spec.tsx:13
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 106 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
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.
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.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
README.md names Node.js 16, but the repository declares engines `18.19.0`, pinned 18. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:12
What to do
Reconcile the README with reality: README.md names Node.js 16, but the repository declares engines `18.19.0`, pinned 18.
No logging call was found in the 643 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:2
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:16
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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 we 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.
`fetch(` 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. (×3) — src/entities/GasPrice/GasPriceService.ts:15, src/entities/GasPrice/GasPriceService.ts:42, src/serviceWorker.ts:108
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) 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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
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 — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
24 duplicated blocks under src/components/ have copies in at least two of the sibling directories @reviewScreens, @widgets, ApprovalSubmittedScreen, AvailableOrdersWidget, ChainSelectionPopover, ChainSelector (+17 more sibling(s) not listed) — 12 of them are reported below, and 12 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 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 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 24 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. — src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:19
18 duplicated blocks under src/components/@widgets/ have copies in at least two of the sibling directories ApprovalsWidget, CancelWidget, LimitOrderDetailWidget, MakeWidget, MyLimitOrdersWidget, MyOrdersWidget (+4 more sibling(s) not listed) — 8 of them are reported below, and 10 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 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 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 18 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. — src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:382
17 duplicated blocks under src/ have copies in at least two of the sibling directories components, contexts, entities, features, helpers, hooks (+2 more sibling(s) not listed) — 5 of them are reported below, and 12 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 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. — src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41
9 duplicated blocks under src/features/ have copies in at least two of the sibling directories balances, cancelLimit, delegateRules, makeOrder, metadata, myOtcOrders (+3 more sibling(s) not listed) — 4 of them are reported below, and 5 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 9 and which does not depend on how exactly each block's copies still match. 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. — src/features/delegateRules/hooks/useSetRuleLogs.ts:30
src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:382 · src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:370 — the two spans are one implementation copied and then locally edited — 757 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. — src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:382
src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:47 · src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:50 — the two spans are one implementation copied and then locally edited — 653 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. — src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:47
src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:45 · src/components/@reviewScreens/WrapReview/WrapReview.tsx:37 — the two spans are one implementation copied and then locally edited — 479 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. — src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:45
src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:19 · src/features/transactions/hooks/useLatestUnsetRuleFromEvents.ts:18 — 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. — src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:19
src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx:68 · src/components/@widgets/MyOtcOrdersWidget/MyOtcOrdersWidget.tsx:76 — the two spans are one implementation copied and then locally edited — 297 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. — src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx:68
src/components/@widgets/MyLimitOrdersWidget/subcomponents/MyLimitOrdersList/MyLimitOrdersList.tsx:27 · src/components/@widgets/MyOtcOrdersWidget/subcomponents/MyOtcOrdersList/MyOtcOrdersList.tsx:30 — the two spans are one implementation copied and then locally edited — 315 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. — src/components/@widgets/MyLimitOrdersWidget/subcomponents/MyLimitOrdersList/MyLimitOrdersList.tsx:27
src/features/transactions/hooks/useLatestSwapErc20FromEvents.ts:14 · src/features/transactions/hooks/useLatestSwapFromEvents.ts:14 — the two spans are one implementation copied and then locally edited — 294 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. — src/features/transactions/hooks/useLatestSwapErc20FromEvents.ts:14
src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:19 · src/components/UnsetRuleScreen/UnsetRuleScreen.tsx:19 — 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. — src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:19
src/features/orders/ordersActions.ts:196 · src/features/orders/ordersActions.ts:244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/features/orders/ordersActions.ts:196
src/components/DepositSubmittedScreen/DepositSubmittedScreen.tsx:21 · src/components/SubmittedCancellationScreen/SubmittedCancellationScreen.tsx:24 — 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. — src/components/DepositSubmittedScreen/DepositSubmittedScreen.tsx:21
src/features/transactions/helpers/getOrdersFromSwapErc20Logs.ts:15 · src/features/transactions/helpers/getOrdersFromSwapLogs.ts:12 — the two spans are one implementation copied and then locally edited — 258 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. — src/features/transactions/helpers/getOrdersFromSwapErc20Logs.ts:15
src/features/delegateRules/hooks/useSetRuleLogs.ts:30 · src/features/transactions/hooks/useSwapLogs.ts:24 — the two spans are one implementation copied and then locally edited — 210 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. — src/features/delegateRules/hooks/useSetRuleLogs.ts:30
src/components/ApprovalSubmittedScreen/ApprovalSubmittedScreen.tsx:37 · src/components/DepositSubmittedScreen/DepositSubmittedScreen.tsx:29 · src/components/SubmittedCancellationScreen/SubmittedCancellationScreen.tsx:32 — the 3 copies are spread across 3 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. 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. — src/components/ApprovalSubmittedScreen/ApprovalSubmittedScreen.tsx:37
src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41 · src/hooks/useApprovalPending.ts:37 · src/hooks/useCancellationPending.ts:25 — the 3 copies are spread across 3 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. — src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41
src/features/makeOrder/makeOrderActions.ts:180 · src/features/makeOrder/makeOrderActions.ts:244 — 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. — src/features/makeOrder/makeOrderActions.ts:180
src/components/@widgets/MakeWidget/MakeWidget.tsx:773 · src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:564 — 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. — src/components/@widgets/MakeWidget/MakeWidget.tsx:773
src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.tsx:16 · src/pages/OtcOrderDetail/subcomponents/InvalidOrder/InvalidOrder.tsx:19 — 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. — src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.tsx:16
src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:22 · src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:59 — 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. — src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:22
src/components/Toasts/ConfirmationToast.tsx:22 · src/components/Toasts/ErrorToast.tsx:22 — 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. — src/components/Toasts/ConfirmationToast.tsx:22
src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:14 · src/features/transactions/hooks/useLatestDepositOrWithdrawFromEvents.ts:13 · src/features/transactions/hooks/useLatestSetRuleFromEvents.ts:13 · src/features/transactions/hooks/useLatestUnsetRuleFromEvents.ts:13 — the 4 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 4 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. — src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:14
src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41 · src/hooks/useApprovalPending.ts:37 · src/hooks/useCancellationPending.ts:25 · src/hooks/useDepositPending.ts:24 — the 4 copies are spread across 4 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. — src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41
src/entities/OrderERC20/OrderERC20Service.ts:22 · src/features/orders/ordersHelpers.ts:96 — the two spans are one implementation copied and then locally edited — 96 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. — src/entities/OrderERC20/OrderERC20Service.ts:22
src/pages/LimitOrderDetail/LimitOrderDetail.tsx:71 · src/pages/OtcOrderDetail/OtcOrderDetail.tsx:41 — 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. — src/pages/LimitOrderDetail/LimitOrderDetail.tsx:71
src/components/ChainSelectionPopover/ChainSelectionPopover.styles.tsx:4 · src/components/SettingsPopover/SettingsPopover.styles.tsx:11 — the two spans are one implementation copied and then locally edited — 146 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. — src/components/ChainSelectionPopover/ChainSelectionPopover.styles.tsx:4
src/features/transactions/hooks/useLatestCancelFromEvents.ts:48 · src/features/transactions/hooks/useLatestSwapErc20FromEvents.ts:64 · src/features/transactions/hooks/useLatestSwapFromEvents.ts:74 — the 3 copies are spread across 3 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. — src/features/transactions/hooks/useLatestCancelFromEvents.ts:48
src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:64 · src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:93 — 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. — src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:64
src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.styles.tsx:1 · src/pages/OtcOrderDetail/subcomponents/InvalidOrder/InvalidOrder.styles.tsx:1 — the two spans are one implementation copied and then locally edited — 78 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. — src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.styles.tsx:1
src/components/ChainSelectionPopover/subcomponents/PopoverSection/PopoverSection.tsx:15 · src/components/SettingsPopover/subcomponents/PopoverSection/PopoverSection.tsx:15 — 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. — src/components/ChainSelectionPopover/subcomponents/PopoverSection/PopoverSection.tsx:15
src/components/OrderSubmittedScreen/OrderSubmittedScreen.tsx:97 · src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:51 · src/components/UnsetRuleScreen/UnsetRuleScreen.tsx:51 — the 3 copies are spread across 3 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. — src/components/OrderSubmittedScreen/OrderSubmittedScreen.tsx:97
src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:177 · src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:177
src/entities/SubmittedTransaction/SubmittedTransactionTransformers.ts:37 · src/entities/SubmittedTransaction/SubmittedTransactionTransformers.ts:60 — 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. — src/entities/SubmittedTransaction/SubmittedTransactionTransformers.ts:37
src/features/cancelLimit/cancelLimitSlice.ts:20 · src/features/takeLimit/takeLimitSlice.ts:36 — the two spans are one implementation copied and then locally edited — 68 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. — src/features/cancelLimit/cancelLimitSlice.ts:20
src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx:96 · src/components/AvailableOrdersWidget/subcomponents/AvailableOrdersList/AvailableOrdersList.tsx:71 — the two spans are one implementation copied and then locally edited — 78 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. — src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx:96
src/components/Content/Introduction.tsx:4 · src/components/Content/Organization.tsx:4 · src/components/Content/Products.tsx:4 — 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. — src/components/Content/Introduction.tsx:4
src/components/@widgets/CancelWidget/CancelWidget.tsx:103 · src/components/@widgets/SwapWidget/SwapWidget.tsx:653 — 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. — src/components/@widgets/CancelWidget/CancelWidget.tsx:103
src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:116 · src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:133 — 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. — src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:116
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 · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx:6 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx:6
src/components/@widgets/ApprovalsWidget/helpers.ts:1 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/@widgets/ApprovalsWidget/helpers.ts:1
src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalListItem/ApprovalListItem.tsx:9 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalListItem/ApprovalListItem.tsx:9
src/components/ApprovalNotice/helpers.ts:5 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/ApprovalNotice/helpers.ts:5
src/components/SwapInputs/hooks/useTokenMaxInfoText.ts:6 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/SwapInputs/hooks/useTokenMaxInfoText.ts:6
src/components/Toasts/TransactionToast.tsx:7 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/Toasts/TransactionToast.tsx:7
src/components/TokenList/subcomponents/TokensAndCollectionsList/TokensAndCollectionsList.tsx:4 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/components/TokenList/subcomponents/TokensAndCollectionsList/TokensAndCollectionsList.tsx:4
src/entities/AppTokenInfo/AppTokenInfoHelpers.ts:4 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/entities/AppTokenInfo/AppTokenInfoHelpers.ts:4
src/features/balances/balancesApi.ts:12 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/features/balances/balancesApi.ts:12
src/features/transactions/hooks/useLatestApproveFromEvents.ts:8 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/features/transactions/hooks/useLatestApproveFromEvents.ts:8
src/hooks/useValidAddress.ts:6 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/hooks/useValidAddress.ts:6
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
MakeWidget has cyclomatic complexity 38 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 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. — src/components/@widgets/MakeWidget/MakeWidget.tsx:118
OtcOrderDetailWidget has cyclomatic complexity 36 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 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. — src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:106
SwapWidget has cyclomatic complexity 33 and cognitive complexity 23; 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. — src/components/@widgets/SwapWidget/SwapWidget.tsx:110
SwapInputs has cyclomatic complexity 30 and cognitive complexity 22; 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. — src/components/SwapInputs/SwapInputs.tsx:50
TokenSelect has cyclomatic complexity 22 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. — src/components/TokenSelect/TokenSelect.tsx:116
renderScreens has cyclomatic complexity 21 and cognitive complexity 24; 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. — src/components/@widgets/MakeWidget/MakeWidget.tsx:583
(anonymous) has cyclomatic complexity 21 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 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. — src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:71
LimitOrderDetailWidget has cyclomatic complexity 21 and cognitive complexity 18; 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. — src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:97
(anonymous) has cyclomatic complexity 20 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 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. — src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx:52
WalletTransaction has cyclomatic complexity 19 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 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. — src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:42
getHumanReadableNumber has cyclomatic complexity 18 and cognitive complexity 29; 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. — src/helpers/getHumanReadableNumber.ts:7
(anonymous) has cyclomatic complexity 17 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. — src/hooks/useShouldDepositNativeTokenAmount.ts:31
(anonymous) has cyclomatic complexity 16 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 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. — src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:67
(anonymous) has cyclomatic complexity 15 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. — src/features/quotes/quotesHooks.ts:47
(anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:65
renderScreens has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:428
(anonymous) has cyclomatic complexity 14 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. — src/helpers/toMaxAllowedDecimalsNumberString.ts:9
stringToSignificantDecimals has cyclomatic complexity 13 and cognitive complexity 18; 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. — src/helpers/stringToSignificantDecimals.ts:5
(anonymous) has cyclomatic complexity 13 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. (×2) — src/components/@widgets/MakeWidget/helpers/index.ts:22, src/components/ErrorList/helpers/index.ts:6
ActionButtons has cyclomatic complexity 13 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. — src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:42
getTimeAgoTranslation has cyclomatic complexity 12 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. — src/components/TransactionsTab/helpers/getTimeAgoTranslation.ts:7
(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. (×2) — src/entities/OrderERC20/OrderERC20Helpers.ts:11, src/entities/OrderERC20/OrderERC20Helpers.ts:30
ApprovalListItem has cyclomatic complexity 12 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. — src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalListItem/ApprovalListItem.tsx:45
(anonymous) has cyclomatic complexity 12 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. — src/components/ApprovalNotice/helpers.ts:106
findTokenFromAndTokenToAddress has cyclomatic complexity 11 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 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. — src/components/@widgets/SwapWidget/helpers/findTokenFromAndTokenToAddress.ts:7
OrderStatusInfo has cyclomatic complexity 11 and cognitive complexity 10; 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. — src/components/@widgets/OrderDetailWidget/subcomponents/OrderStatusInfo/OrderStatusInfo.tsx:21
renderScreens has cyclomatic complexity 11 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. — src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:410
InfoSection has cyclomatic complexity 11 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. — src/components/@widgets/SwapWidget/subcomponents/InfoSection/InfoSection.tsx:31
(anonymous) has cyclomatic complexity 11 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. — src/hooks/useAllowance.ts:59
Do you agree with this assessment?
R3 · Large Files9.6 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
src/components/@widgets/MakeWidget/MakeWidget.tsx has 766 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/@widgets/MakeWidget/MakeWidget.tsx:1
src/components/@widgets/SwapWidget/SwapWidget.tsx has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/@widgets/SwapWidget/SwapWidget.tsx:1
src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx has 571 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:1
src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx has 551 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:1
src/features/orders/ordersActions.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/features/orders/ordersActions.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.8 / 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) — src/components/@widgets/MakeWidget/MakeWidget.tsx:1, src/components/@widgets/SwapWidget/SwapWidget.tsx:1, src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `lint` script (`eslint "./src/**/*.{ts,tsx}"`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — package.json:9
The root package declares the lint script `lint` (`eslint "./src/**/*.{ts,tsx}"`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `.` (or the workspace's task runner). — package.json:9
What to do
Add `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code7.1 / 10Strong✓ 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.
Unreachable from the 3 application, 9 tooling and 17 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (3 application, 9 tooling, 17 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 (×22) — src/components/Toasts/TransactionToast.tsx, src/components/WalletButton/WalletButton.styles.tsx, src/features/balances/balancesHelpers.ts, …
no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/InformationModals/subcomponents/GuideButton/GuideButton.tsx) — 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 — src/components/InformationModals/subcomponents/GuideButton/GuideButton.styles.tsx
no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/TokenList/subcomponents/TokenDeleteButton/TokenDeleteButton.tsx) — 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 — src/components/TokenList/subcomponents/TokenDeleteButton/TokenDeleteButton.styles.tsx
no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/@widgets/MakeWidget/subcomponents/InputSection/InputSection.tsx) — 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 — src/components/@widgets/MakeWidget/subcomponents/InputSection/InputSection.styles.tsx
no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/@widgets/SwapWidget/subcomponents/ClearServerButton/ClearServerButton.tsx) — 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 — src/components/@widgets/SwapWidget/subcomponents/ClearServerButton/ClearServerButton.styles.tsx
no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/components/Content/Introduction.tsx, src/components/Content/Organization.tsx, src/components/Content/Products.tsx) — 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 — src/components/Content/Content.style.tsx
no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/TransactionsTab/subcomponents/WalletLink/WalletLink.tsx) — 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 — src/components/TransactionsTab/subcomponents/WalletLink/WalletLink.styles.tsx
Nothing imports this binding — it is safe to review for removal. (×11) — src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalsListSortButtons/ApprovalsListSortButtons.styles.tsx:12, src/components/@widgets/MakeWidget/MakeWidget.styles.tsx:112, src/components/@widgets/MakeWidget/subcomponents/ExpirySelector/ExpirySelector.styles.tsx:24, …
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 package.json — installs work only by hoisting accident. (×7) — src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:4, src/features/delegateRules/hooks/useSetRuleLogs.ts:4, src/components/@widgets/CancelWidget/CancelWidget.tsx:6, …
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×7) — package.json:19, package.json:36, package.json:40, …
Only test files import it (first: src/components/Timer/Timer.spec.tsx:1) — move it to devDependencies. — package.json:28
Only test files import it (first: src/components/WalletButton/WalletButton.spec.tsx:2) — move it to devDependencies. — package.json:29
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports2.7 / 10Weak✓ Tool-verified
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
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.
`https://www.googletagmanager.com/gtag/js?id=G-XSB2E7X42G` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — public/index.html:35
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — index.js:14
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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.
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.
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/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) 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.
`geDefisaverGasPriceApiCall` 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 })`. — src/entities/GasPrice/GasPriceService.ts:12
`getEtherscanGasPriceApiCall` 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 })`. — src/entities/GasPrice/GasPriceService.ts:35
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 value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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. — src/helpers/switchToDefaultChain.ts:8
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 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.
~2.4 `!` null assertions per 1k TypeScript source lines — 100 assertion(s) across the 41044 source line(s) of the 642 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: src/components/@widgets/SwapWidget/SwapWidget.tsx (22), src/components/@widgets/MakeWidget/MakeWidget.tsx (20), src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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 — 3 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.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 59 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> airswap-web@0.1.0 start / > craco start / sh: 1: craco: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not included — no executor for the `@craco/craco` test runner
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
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.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D21 Naming Consistency — Naming consistency does not read htm, html yet; not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. 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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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.
D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
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 — no executor for the `@craco/craco` test runner
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a yarn 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.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. 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.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Banned license: @web3-react/abstract-connector package.json:36— `@web3-react/abstract-connector` 6.0.7 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/coinbase-wallet package.json:37— `@web3-react/coinbase-wallet` 8.2.3 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/core package.json:38— `@web3-react/core` 8.2.3 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/gnosis-safe package.json:39— `@web3-react/gnosis-safe` 8.2.4 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/injected-connector package.json:40— `@web3-react/injected-connector` 6.0.7 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/metamask package.json:41— `@web3-react/metamask` 8.2.4 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/store package.json:42— `@web3-react/store` 8.2.3 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/types package.json:43— `@web3-react/types` 8.2.3 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @web3-react/walletconnect-v2 package.json:44— `@web3-react/walletconnect-v2` 8.5.1 is published on registry.npmjs.org under `GPL-3.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: rpc-websockets REDACTED:12278— `rpc-websockets` 7.11.0 is published on registry.npmjs.org under `LGPL-3.0-only`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Boundary-crossing change coupling: WalletButton.tsx ↔ Wallet.tsx src/components/WalletButton/WalletButton.tsx:1— `src/components/WalletButton/WalletButton.tsx` (context components) and `src/features/wallet/Wallet.tsx` (context features) sit in DIFFERENT parts of the tree yet change together 93% of the time (13 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 13 shared commits counted here, the most recent 3 are `9aa03bfb` 725: Improved clearing store when switching between wallets (#727); `0ef6d80e` Highlight wallet pill when transactions pending (#312); `5bdbaf61` Refactored wallet buttons, added wallet show button on not connected … — run `git show` on any of them.
Boundary-crossing change coupling: OtcOrderDetailWidget.tsx ↔ takeOtcActions.ts src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:1— `src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx` (context components) and `src/features/takeOtc/takeOtcActions.ts` (context features) sit in DIFFERENT parts of the tree yet change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `2169f2b8` Adding FullOrder | FullOrderERC20 types; `aa7e8417` updated @airswap/libraries to 5.0.11; `e675abee` Progress adding support for FullOrder — run `git show` on any of them.
Boundary-crossing change coupling: MakeWidget.tsx ↔ takeOtcActions.ts src/components/@widgets/MakeWidget/MakeWidget.tsx:1— `src/components/@widgets/MakeWidget/MakeWidget.tsx` (context components) and `src/features/takeOtc/takeOtcActions.ts` (context features) sit in DIFFERENT parts of the tree yet change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 `2169f2b8` Adding FullOrder | FullOrderERC20 types; `aa7e8417` updated @airswap/libraries to 5.0.11; `e675abee` Progress adding support for FullOrder — run `git show` on any of them.
Boundary-crossing change coupling: WidgetFrame.styles.tsx ↔ GlobalStyle.ts src/components/WidgetFrame/WidgetFrame.styles.tsx:1— `src/components/WidgetFrame/WidgetFrame.styles.tsx` (context components) and `src/style/GlobalStyle.ts` (context style) 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 — 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 `9a2dee91` Added BlurredOverlay to Page (woohoo, it works!); `75a18e22` Feature/259 new design (#266); `b2d1b165` [Alpha] Content side bar (#132) (at that commit the file was still `src/components/TradeContainer/TradeContainer.styles.tsx`) — run `git show` on any of them.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> public/index.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>.
D30 · Dependency Vulnerabilities· High vulnerability · ×1
Unlisted import '@airswap/utils' src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@ethersproject/contracts' src/features/delegateRules/hooks/useSetRuleLogs.ts:4— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@ethersproject/providers' src/components/@widgets/CancelWidget/CancelWidget.tsx:6— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@ethersproject/units' src/components/TokenList/helpers/sort.ts:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@openzeppelin/contracts' src/features/orders/ordersHelpers.ts:20— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react-router' src/pages/LimitOrderDetail/LimitOrderDetail.tsx:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Cross-slice coupling: balances → metadata src/features/balances/balancesHooks.ts:23— `useBalances` (slice 'balances') depends on `selectActiveTokens` from slice 'metadata'.
Cross-slice coupling: balances → transactions src/features/balances/balancesHooks.ts:24— `useBalances` (slice 'balances') depends on `useLatestSucceededTransaction` from slice 'transactions'.
Cross-slice coupling: balances → web3 src/features/balances/balancesSlice.ts:116— `getSlice` (slice 'balances') depends on `walletDisconnected` from slice 'web3'.
Cross-slice coupling: balances → web3 src/features/balances/balancesSlice.ts:119— `getSlice` (slice 'balances') depends on `walletChanged` from slice 'web3'.
Cross-slice coupling: cancelLimit → transactions src/features/cancelLimit/cancelLimitActions.ts:50— `cancelLimitOrder` (slice 'cancelLimit') depends on `submitTransaction` from slice 'transactions'.
Cross-slice coupling: cancelLimit → takeLimit src/features/cancelLimit/cancelLimitActions.ts:66— `cancelLimitOrder` (slice 'cancelLimit') depends on `setError` from slice 'takeLimit'.
Cross-slice coupling: delegateRules → transactions src/features/delegateRules/delegateRulesActions.ts:54— `submitDelegateRuleToStore` (slice 'delegateRules') depends on `setTransactions` from slice 'transactions'.
Cross-slice coupling: delegateRules → web3 src/features/delegateRules/delegateRulesSlice.ts:65— `delegateRulesSlice` (slice 'delegateRules') depends on `walletDisconnected` from slice 'web3'.
Cross-slice coupling: delegateRules → web3 src/features/delegateRules/delegateRulesSlice.ts:66— `delegateRulesSlice` (slice 'delegateRules') depends on `walletChanged` from slice 'web3'.
Cross-slice coupling: delegateRules → metadata src/features/delegateRules/hooks/useHistoricalDelegateRules.ts:20— `useHistoricalDelegateRules` (slice 'delegateRules') depends on `selectAllTokenInfo` from slice 'metadata'.
Cross-slice coupling: gasCost → web3 src/features/gasCost/gasCostSlice.ts:81— `gasCostSlice` (slice 'gasCost') depends on `walletDisconnected` from slice 'web3'.
Cross-slice coupling: makeOrder → transactions src/features/makeOrder/makeOrderActions.ts:120— `createDelegateRule` (slice 'makeOrder') depends on `submitTransaction` from slice 'transactions'.
Cross-slice coupling: makeOrder → indexer src/features/makeOrder/makeOrderActions.ts:203— `createOtcFullOrder` (slice 'makeOrder') depends on `sendOrderToIndexers` from slice 'indexer'.
Cross-slice coupling: metadata → web3 src/features/metadata/metadataActions.ts:82— `writeActiveTokensToLocalStorage` (slice 'metadata') depends on `Web3State` from slice 'web3'.
Cross-slice coupling: metadata → registry src/features/metadata/metadataHooks.ts:31— `useMetadata` (slice 'metadata') depends on `selectAllSupportedTokens` from slice 'registry'.
Cross-slice coupling: metadata → registry src/features/metadata/metadataHooks.ts:90— `useMetadata` (slice 'metadata') depends on `fetchSupportedTokens` from slice 'registry'.
Cross-slice coupling: metadata → web3 src/features/metadata/metadataSlice.ts:106— `metadataSlice` (slice 'metadata') depends on `walletChanged` from slice 'web3'.
Cross-slice coupling: metadata → web3 src/features/metadata/metadataSlice.ts:112— `metadataSlice` (slice 'metadata') depends on `chainIdChanged` from slice 'web3'.
Cross-slice coupling: metadata → web3 src/features/metadata/metadataSlice.ts:120— `metadataSlice` (slice 'metadata') depends on `walletDisconnected` from slice 'web3'.
Cross-slice coupling: metadata → web3 src/features/metadata/metadataSlice.ts:151— `selectAllTokenInfo` (slice 'metadata') depends on `selectChainId` from slice 'web3'.
Cross-slice coupling: myOtcOrders → web3 src/features/myOtcOrders/myOtcOrdersSlice.ts:89— `myOtcOrdersSlice` (slice 'myOtcOrders') depends on `walletDisconnected` from slice 'web3'.
Cross-slice coupling: myOtcOrders → web3 src/features/myOtcOrders/myOtcOrdersSlice.ts:90— `myOtcOrdersSlice` (slice 'myOtcOrders') depends on `walletChanged` from slice 'web3'.
Cross-slice coupling: myOtcOrders → makeOrder src/features/myOtcOrders/myOtcOrdersSlice.ts:92— `myOtcOrdersSlice` (slice 'myOtcOrders') depends on `setOtcOrder` from slice 'makeOrder'.
Cross-slice coupling: orders → delegateRules src/features/orders/ordersActions.ts:146— `handleSubmittedSetRuleOrder` (slice 'orders') depends on `submitDelegateRuleToStore` from slice 'delegateRules'.
Cross-slice coupling: orders → delegateRules src/features/orders/ordersActions.ts:161— `handleSubmittedUnsetRuleOrder` (slice 'orders') depends on `unsetDelegateRuleFromStore` from slice 'delegateRules'.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file src/components/@widgets/MakeWidget/MakeWidget.tsx: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 src/components/@widgets/SwapWidget/SwapWidget.tsx: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 src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx: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 src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx: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 src/features/orders/ordersActions.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 src/style/reset.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 src/components/TokenSelect/TokenSelect.styles.tsx: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 src/features/makeOrder/makeOrderActions.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 src/features/quotes/quotesHooks.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 src/components/TokenSelect/TokenSelect.tsx: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 src/features/transactions/transactionsHelpers.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 src/features/quotes/quotesActions.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 src/components/TokenList/TokenList.tsx: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 src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx: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 src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx: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 src/components/TransactionsTab/TransactionsTab.styles.tsx: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 src/components/TokenList/subcomponents/TokenButton/TokenButton.styles.tsx: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 src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx: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 src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx: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 src/components/TransactionsTab/TransactionsTab.tsx: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 src/components/SwapInputs/SwapInputs.tsx: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 src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx: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 src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx: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 src/components/Dropdown/Dropdown.styles.tsx: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 src/components/ApprovalNotice/helpers.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.
+ 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×27
FunctionTooLong: MakeWidget.MakeWidget src/components/@widgets/MakeWidget/MakeWidget.tsx:118— FunctionTooLong — MakeWidget runs 547 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 447 over it, 5.47× 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: SwapWidget.SwapWidget src/components/@widgets/SwapWidget/SwapWidget.tsx:110— FunctionTooLong — SwapWidget runs 433 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 333 over it, 4.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: LimitOrderDetailWidget.LimitOrderDetailWidget src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:97— FunctionTooLong — LimitOrderDetailWidget runs 408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 308 over it, 4.08× 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: OtcOrderDetailWidget.OtcOrderDetailWidget src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:106— FunctionTooLong — OtcOrderDetailWidget runs 385 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: quotesHooks.useQuotes src/features/quotes/quotesHooks.ts:47— FunctionTooLong — useQuotes runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: TakeOrderReview.TakeOrderReview src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:56— FunctionTooLong — TakeOrderReview 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: MakeOrderReview.MakeOrderReview src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:53— FunctionTooLong — MakeOrderReview runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.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: WalletTransaction.WalletTransaction src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:42— FunctionTooLong — WalletTransaction runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TokenSelect.TokenSelect src/components/TokenSelect/TokenSelect.tsx:116— FunctionTooLong — TokenSelect runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: ActionButtons.ActionButtons src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:42— FunctionTooLong — ActionButtons runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TransactionsTab.TransactionsTab src/components/TransactionsTab/TransactionsTab.tsx:46— FunctionTooLong — TransactionsTab runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) 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: Order.Order src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx:52— FunctionTooLong — Order runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: TokenList.TokenList src/components/TokenList/TokenList.tsx:66— FunctionTooLong — TokenList runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ApprovalsWidget.ApprovalsWidget src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx:42— FunctionTooLong — ApprovalsWidget runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: MyOrdersList.MyOrdersList src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx:35— FunctionTooLong — MyOrdersList runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× 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: ApproveReview.ApproveReview src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:52— FunctionTooLong — ApproveReview runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: WrapReview.WrapReview src/components/@reviewScreens/WrapReview/WrapReview.tsx:44— FunctionTooLong — WrapReview runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useQuotesDebug.useQuotesDebug src/features/quotes/hooks/useQuotesDebug.ts:14— FunctionTooLong — useQuotesDebug runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: ActionButtons.ActionButtons src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:33— FunctionTooLong — ActionButtons runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: balancesApi.getThunk src/features/balances/balancesApi.ts:208— FunctionTooLong — getThunk runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TodoComment src/hooks/useAppRouteParams.ts:25— // TODO: Add isLimitOrder to AppRouteParams — 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 src/helpers/getFullSwapERC20.ts:6— // TODO: Remove this function when this issue is resolved: — 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 src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:45— // TODO: #1047, remove this once we have a contract for all chains
TodoComment src/features/transactions/hooks/useLatestSetRuleFromEvents.ts:43— // TODO: #1047, remove this once we have a contract for all chains
TodoComment src/features/transactions/hooks/useLatestUnsetRuleFromEvents.ts:44— // TODO: #1047, remove this once we have a contract for all chains
TodoComment src/features/transactions/hooks/useSwapLogs.ts:119— // TODO: #1047, remove this once we have a contract for all chains
TodoComment src/features/delegateRules/hooks/useSetRuleLogs.ts:92— // TODO: #1047, remove this once we have a contract for all chains
TodoComment src/features/transactions/hooks/useLatestSwapFromEvents.ts:57— // TODO: This needs to be swapped to FullOrder, convert to ERC20 for now — 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 src/features/transactions/hooks/useSwapLogs.ts:51— // TODO: Swap.deployedBlocks is empty right now, replace 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 src/features/takeOtc/takeOtcActions.ts:41— // TODO: Replace with decompressFullOrder — 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 src/features/metadata/metadataHooks.ts:70— // TODO: Fetch unknown when active tokens are added — 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 src/components/WalletButton/WalletButton.spec.tsx:10— // TODO: this doesn't work because of the `react-blockies` package - not — 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 src/components/ApprovalNotice/ApprovalNotice.tsx:81— // TODO: clean this up — 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 src/components/@widgets/SwapWidget/subcomponents/InfoSection/InfoSection.tsx:25— // TODO: Enable these once we reinstate these features — 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 src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/helpers/index.ts:29— // TODO: sort on order canceled or not — 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 src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx:105— // TODO: fix action for AppTokenInfo — 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 src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:338— // TODO: Support AppTokenInfo — 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 src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:356— // TODO: Support AppTokenInfo — 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.
Boundary violation [package:third-party-deep-import] src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx:6— src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx:6 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/@widgets/ApprovalsWidget/helpers.ts:1— src/components/@widgets/ApprovalsWidget/helpers.ts:1 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalListItem/ApprovalListItem.tsx:9— src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalListItem/ApprovalListItem.tsx:9 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/ApprovalNotice/helpers.ts:5— src/components/ApprovalNotice/helpers.ts:5 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/SwapInputs/hooks/useTokenMaxInfoText.ts:6— src/components/SwapInputs/hooks/useTokenMaxInfoText.ts:6 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/Toasts/TransactionToast.tsx:7— src/components/Toasts/TransactionToast.tsx:7 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/components/TokenList/subcomponents/TokensAndCollectionsList/TokensAndCollectionsList.tsx:4— src/components/TokenList/subcomponents/TokensAndCollectionsList/TokensAndCollectionsList.tsx:4 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/entities/AppTokenInfo/AppTokenInfoHelpers.ts:4— src/entities/AppTokenInfo/AppTokenInfoHelpers.ts:4 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/features/balances/balancesApi.ts:12— src/features/balances/balancesApi.ts:12 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/features/transactions/hooks/useLatestApproveFromEvents.ts:8— src/features/transactions/hooks/useLatestApproveFromEvents.ts:8 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/hooks/useValidAddress.ts:6— src/hooks/useValidAddress.ts:6 imports ethers/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×9
Animation without a prefers-reduced-motion guard public/whitepaper/whitepaper.css:3225— `.collapsing` moves (`transition: height 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard public/whitepaper/whitepaper.css:4839— `.progress-bar-animated` moves (`animation: progress-bar-stripes 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard public/whitepaper/whitepaper.css:5092— `.modal.fade .modal-dialog` moves (`transition: transform 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard public/whitepaper/whitepaper.css:5482— `.carousel-item` moves (`transition: transform 0.6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard public/whitepaper/whitepaper.css:5489— `.carousel-item` moves (`transition: transform 0.6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/styled-components/Overlay/Overlay.tsx:14— `div` moves (`transition: transform 0.3s cubic-bezier(0.68, 0.007, 0.488, 0.997)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/styled-components/Overlay/Overlay.tsx:64— `div` moves (`animation: _______ 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/TokenSelect/TokenSelect.styles.tsx:175— `div` moves (`animation: __________ 0.35s ease-in-out infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/LoadingSpinner/LoadingSpinner.styles.tsx:22— `.css-in-js` moves (`animation: _______ 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×8
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:236— `a:not([href]):not([tabindex]):focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:2780— `.btn.focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:3312— `.show > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:3432— `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:5089— `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:5118— `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement public/whitepaper/whitepaper.css:5558— `.carousel-control-prev:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/components/@widgets/OrderDetailWidget/subcomponents/OrderRecipientInfo/OrderRecipientInfo.styles.tsx:43— `button:focus:enabled` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Change coupling: TokenList.tsx ↔ TokenButton.tsx src/components/TokenList/TokenList.tsx:1— `src/components/TokenList/TokenList.tsx` and `src/components/TokenList/subcomponents/TokenButton/TokenButton.tsx` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `a8aa55e2` Added CollectionNftButton; `52e18ee5` Added TokensAndCollectionList; `12e28f42` Token import button now imports all nft tokens — run `git show` on any of them.
Change coupling: MyOrdersList.tsx ↔ MyOrdersListSortButtons.tsx src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx:1— `src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx` and `src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersListSortButtons/MyOrdersListSortButtons.tsx` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `f40a4cb6` Added sorting for "for" column; `19e753e2` Added FadedScrollContainer to MyOrdersList; `4402febb` Added hasForColumn — run `git show` on any of them.
Change coupling: CancelWidget.tsx ↔ OtcOrderDetailWidget.tsx src/components/@widgets/CancelWidget/CancelWidget.tsx:1— `src/components/@widgets/CancelWidget/CancelWidget.tsx` and `src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `2169f2b8` Adding FullOrder | FullOrderERC20 types; `e675abee` Progress adding support for FullOrder; `0a68d7dc` Added useLimitOrderStatus and useFilledStatus hooks — run `git show` on any of them.
Change coupling: MyOrderTransformers.ts ↔ MyOtcOrdersWidget.tsx src/components/@widgets/MyOrdersWidget/entities/MyOrderTransformers.ts:1— `src/components/@widgets/MyOrdersWidget/entities/MyOrderTransformers.ts` and `src/components/@widgets/MyOtcOrdersWidget/MyOtcOrdersWidget.tsx` 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 — 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 `fcbd4d97` Added getOrdersWithApprovalWarnings; `22e48a8c` Added IconWarning; `2169f2b8` Adding FullOrder | FullOrderERC20 types — run `git show` on any of them.
Change coupling: MyOrdersListSortButtons.tsx ↔ Order.tsx src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersListSortButtons/MyOrdersListSortButtons.tsx:1— `src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersListSortButtons/MyOrdersListSortButtons.tsx` and `src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f40a4cb6` Added sorting for "for" column; `4402febb` Added hasForColumn; `22e48a8c` Added IconWarning — run `git show` on any of them.
Change coupling: TransactionLink.tsx ↔ WalletTransaction.tsx src/components/TransactionLink/TransactionLink.tsx:1— `src/components/TransactionLink/TransactionLink.tsx` and `src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx` 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 — 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 `89cf8961` 807: Fixed transaction link in WalletTransaction (#808); `f07651fd` Fixes#770 - Add a link to block explorer on Order Completed screen (#…; `db87da79` [Feature] New design for transactions tab (#267) (at that commit the file was still `src/components/TransactionsTab/subcomponents/TransactionLink/TransactionLink.tsx`) — run `git show` on any of them.
ClassTooLong: MakeWidget src/components/@widgets/MakeWidget/MakeWidget.tsx:1— ClassTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 147 over it, 1.37× 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: SwapWidget src/components/@widgets/SwapWidget/SwapWidget.tsx:1— ClassTooLong — 433 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 33 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LimitOrderDetailWidget src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:1— ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 8 over it, 1.02× 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.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×3
Markup wires an event to an empty handler src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:468— `onBaseAmountChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:469— `onChangeTokenClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:470— `onMaxButtonClick` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Outbound HTTP without resilience src/entities/GasPrice/GasPriceService.ts:15— `fetch(` 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 src/entities/GasPrice/GasPriceService.ts:42— `fetch(` 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 src/serviceWorker.ts:108— `fetch(` 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.
Duplicated block (18 lines × 2 locations) src/components/ChainSelectionPopover/subcomponents/PopoverSection/PopoverSection.tsx:15— src/components/ChainSelectionPopover/subcomponents/PopoverSection/PopoverSection.tsx:15 · src/components/SettingsPopover/subcomponents/PopoverSection/PopoverSection.tsx:15 — 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 (18 lines × 2 locations) src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:177— src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:177 · src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:198 — both copies are in the same file, so extract the block into 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 locations) src/entities/SubmittedTransaction/SubmittedTransactionTransformers.ts:37— src/entities/SubmittedTransaction/SubmittedTransactionTransformers.ts:37 · src/entities/SubmittedTransaction/SubmittedTransactionTransformers.ts:60 — 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.
Dead file (~22 LoC) src/components/Content/Introduction.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~22 LoC) src/components/Content/Organization.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~22 LoC) src/components/Content/Products.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~15 LoC) src/components/@widgets/SwapWidget/subcomponents/ClearServerButton/ClearServerButton.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/@widgets/SwapWidget/subcomponents/ClearServerButton/ClearServerButton.tsx) — 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 (~15 LoC) src/components/Content/Content.style.tsx— no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/components/Content/Introduction.tsx, src/components/Content/Organization.tsx, src/components/Content/Products.tsx) — 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 (~15 LoC) src/components/TransactionsTab/subcomponents/WalletLink/WalletLink.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/TransactionsTab/subcomponents/WalletLink/WalletLink.tsx) — 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
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark public/whitepaper.htm:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Hotspot: src/components/@widgets/MakeWidget/MakeWidget.tsx src/components/@widgets/MakeWidget/MakeWidget.tsx:118— src/components/@widgets/MakeWidget/MakeWidget.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 101 in MakeWidget.MakeWidget at line 118. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-07-08..2025-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-07-08 19:46:31 +02:00' --until='2025-10-06 19:46:31 +02:00' --full-history --no-merges -- src/components/@widgets/MakeWidget/MakeWidget.tsx`: 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: src/features/quotes/quotesHooks.ts src/features/quotes/quotesHooks.ts:47— src/features/quotes/quotesHooks.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in quotesHooks.useQuotes at line 47. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-07-08..2025-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-07-08 19:46:31 +02:00' --until='2025-10-06 19:46:31 +02:00' --full-history --no-merges -- src/features/quotes/quotesHooks.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: MakeWidget/MakeWidget.tsx src/components/@widgets/MakeWidget/MakeWidget.tsx— FileTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: MakeWidget (118-845). The bar is 500 significant lines; this is 158 over it, 1.32× 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: SwapWidget/SwapWidget.tsx src/components/@widgets/SwapWidget/SwapWidget.tsx— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: SwapWidget (110-690). The bar is 500 significant lines; this is 38 over it, 1.08× 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.
Duplicated block (25 lines × 2 locations) src/components/@widgets/MakeWidget/MakeWidget.tsx:773— src/components/@widgets/MakeWidget/MakeWidget.tsx:773 · src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:564 — 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 (25 lines × 2 locations) src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.tsx:16— src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.tsx:16 · src/pages/OtcOrderDetail/subcomponents/InvalidOrder/InvalidOrder.tsx:19 — 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.
Duplicated block (23 lines × 2 locations) src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:22— src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:22 · src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:59 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 2 locations) src/components/Toasts/ConfirmationToast.tsx:22— src/components/Toasts/ConfirmationToast.tsx:22 · src/components/Toasts/ErrorToast.tsx:22 — 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 (16 lines × 2 locations) src/components/@widgets/CancelWidget/CancelWidget.tsx:103— src/components/@widgets/CancelWidget/CancelWidget.tsx:103 · src/components/@widgets/SwapWidget/SwapWidget.tsx:653 — 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.
Duplicated block (16 lines × 2 locations) src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:116— src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:116 · src/components/@widgets/SwapWidget/subcomponents/ActionButtons/ActionButtons.tsx:133 — 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.
Complex function (anonymous) (cyclomatic 13, cognitive 12) src/components/@widgets/MakeWidget/helpers/index.ts:22— (anonymous) has cyclomatic complexity 13 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 12) src/components/ErrorList/helpers/index.ts:6— (anonymous) has cyclomatic complexity 13 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 12, cognitive 11) src/entities/OrderERC20/OrderERC20Helpers.ts:11— (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 12, cognitive 11) src/entities/OrderERC20/OrderERC20Helpers.ts:30— (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.
Dead file (~26 LoC) src/components/@widgets/MakeWidget/subcomponents/InputSection/InputSection.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~26 LoC) src/components/TransactionsTab/subcomponents/WalletLink/WalletLink.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~23 LoC) src/components/@widgets/SwapWidget/subcomponents/ClearServerButton/ClearServerButton.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~23 LoC) src/hooks/useTokenAmountError.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~11 LoC) src/components/@widgets/OtcOrderDetailWidget/hooks/useDecompressOrderFromURL.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~11 LoC) src/types/chainParams.ts— no import path from any entry point (3 application, 9 tooling, 17 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
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: geDefisaverGasPriceApiCall src/entities/GasPrice/GasPriceService.ts:12— `geDefisaverGasPriceApiCall` 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: getEtherscanGasPriceApiCall src/entities/GasPrice/GasPriceService.ts:35— `getEtherscanGasPriceApiCall` 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 })`.
AC2 · Forms & labels· <Select> field component without a label · ×1
<Select> field component without a label src/components/Dropdown/Dropdown.tsx:88— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×1
Heading level jumps from h1 to h4 public/whitepaper.htm:79— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h2 to h4 · ×1
Heading level jumps from h2 to h4 public/whitepaper.htm:458— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast colour pair in CSS (4.2:1) public/whitepaper/whitepaper.css:4932— `a.list-group-item-success:focus, a.list-group-item-success:hover, button.list-group-item-success:focus, button.list-group-item-success:hover` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) public/whitepaper/whitepaper.css:4955— `a.list-group-item-info:focus, a.list-group-item-info:hover, button.list-group-item-info:focus, button.list-group-item-info:hover` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.3:1) public/whitepaper/whitepaper.css:4978— `a.list-group-item-warning:focus, a.list-group-item-warning:hover, button.list-group-item-warning:focus, button.list-group-item-warning:hover` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) public/whitepaper/whitepaper.css:5001— `a.list-group-item-danger:focus, a.list-group-item-danger:hover, button.list-group-item-danger:focus, button.list-group-item-danger:hover` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
No authorization index.js:4— This repository serves requests — express() (index.js:4) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
SwapWidget.SwapWidget (cyclomatic 79) src/components/@widgets/SwapWidget/SwapWidget.tsx:110— SwapWidget.SwapWidget has cyclomatic complexity 79 (threshold 15). Of this number, 33 points are the body's own statements and 46 belong to 18 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
OtcOrderDetailWidget.OtcOrderDetailWidget (cyclomatic 71) src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:106— OtcOrderDetailWidget.OtcOrderDetailWidget has cyclomatic complexity 71 (threshold 15). Of this number, 36 points are the body's own statements and 35 belong to 7 function items inside it that branch. 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.
LimitOrderDetailWidget.LimitOrderDetailWidget (cyclomatic 54) src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:97— LimitOrderDetailWidget.LimitOrderDetailWidget has cyclomatic complexity 54 (threshold 15). Of this number, 21 points are the body's own statements and 33 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
quotesHooks.useQuotes (cyclomatic 49) src/features/quotes/quotesHooks.ts:47— quotesHooks.useQuotes has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 15 of the 49 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 125, 224, 173, …). 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.
MakeWidget.MakeWidget (cyclomatic 38) src/components/@widgets/MakeWidget/MakeWidget.tsx:118— MakeWidget.MakeWidget has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (MakeWidget.MakeWidget::renderScreens) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SwapInputs.SwapInputs (cyclomatic 34) src/components/SwapInputs/SwapInputs.tsx:50— SwapInputs.SwapInputs has cyclomatic complexity 34 (threshold 15). Of this number, 30 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
useQuotesDebug.useQuotesDebug (cyclomatic 34) src/features/quotes/hooks/useQuotesDebug.ts:14— useQuotesDebug.useQuotesDebug has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 3 of the 34 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 95, 121, 154, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TakeOrderReview.TakeOrderReview (cyclomatic 23) src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:56— TakeOrderReview.TakeOrderReview has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
TokenSelect.TokenSelect (cyclomatic 22) src/components/TokenSelect/TokenSelect.tsx:116— TokenSelect.TokenSelect has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
useSwapLogs.useSwapLogs (cyclomatic 21) src/features/transactions/hooks/useSwapLogs.ts:24— useSwapLogs.useSwapLogs has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 35, 109). 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.
MakeWidget.MakeWidget::renderScreens (cyclomatic 21) src/components/@widgets/MakeWidget/MakeWidget.tsx:583— MakeWidget.MakeWidget::renderScreens has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (MakeWidget.MakeWidget) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ApproveReview.ApproveReview (cyclomatic 20) src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:52— ApproveReview.ApproveReview has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 3 function items inside it that branch. 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.
Order.Order (cyclomatic 20) src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx:52— Order.Order has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
metadataHooks.useMetadata (cyclomatic 19) src/features/metadata/metadataHooks.ts:25— metadataHooks.useMetadata has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 47, 72, 94, …). 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.
WalletTransaction.WalletTransaction (cyclomatic 19) src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:42— WalletTransaction.WalletTransaction has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MakeOrderReview.MakeOrderReview (cyclomatic 18) src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:53— MakeOrderReview.MakeOrderReview has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
getHumanReadableNumber.getHumanReadableNumber (cyclomatic 18) src/helpers/getHumanReadableNumber.ts:7— getHumanReadableNumber.getHumanReadableNumber 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.
useShouldDepositNativeTokenAmount.useShouldDepositNativeTokenAmount (cyclomatic 17) src/hooks/useShouldDepositNativeTokenAmount.ts:17— useShouldDepositNativeTokenAmount.useShouldDepositNativeTokenAmount 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 31). 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.
MyLimitOrdersWidget.MyLimitOrdersWidget (cyclomatic 16) src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx:37— MyLimitOrdersWidget.MyLimitOrdersWidget has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Skipped test: should render a partial wallet address when provided src/components/WalletButton/WalletButton.spec.tsx:13— Skipped — switched off by it.skip
No assertions: should increment index by 3 after 3 second src/components/Timer/Timer.spec.tsx:8— 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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.
HackComment src/components/OrderSubmittedScreen/OrderSubmittedScreen.tsx:56— // Hacky hack to delay click to circomvent the useClickOutsideTransactionsTab hook — 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.
OtcOrderDetailWidget.OtcOrderDetailWidget (cognitive 63) src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:106— OtcOrderDetailWidget.OtcOrderDetailWidget has cognitive complexity 63 (threshold 15). Drivers by points: ternaries 24 (25 pts), boolean chains 22, if/else 16 (nesting depth added 1). Of this number, 33 points are the body's own statements and 30 belong to 7 function items inside it that branch. 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.
SwapWidget.SwapWidget (cognitive 61) src/components/@widgets/SwapWidget/SwapWidget.tsx:110— SwapWidget.SwapWidget has cognitive complexity 61 (threshold 15). Drivers by points: boolean chains 31, if/else 22 (23 pts), ternaries 5, error handling 1, match/switch 1 (nesting depth added 1). Of this number, 23 points are the body's own statements and 38 belong to 18 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LimitOrderDetailWidget.LimitOrderDetailWidget (cognitive 46) src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:97— LimitOrderDetailWidget.LimitOrderDetailWidget has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 22, if/else 17, ternaries 7. Of this number, 18 points are the body's own statements and 28 belong to 6 function items inside it that branch. 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.
MakeWidget.MakeWidget (cognitive 34) src/components/@widgets/MakeWidget/MakeWidget.tsx:118— MakeWidget.MakeWidget has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 41, ternaries 27 (33 pts), if/else 24 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This shape REPEATS in the file: one other method here (MakeWidget.MakeWidget::renderScreens) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
useQuotesDebug.useQuotesDebug (cognitive 30) src/features/quotes/hooks/useQuotesDebug.ts:14— useQuotesDebug.useQuotesDebug has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, if/else 14, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 154, 53, 59, …). 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.
quotesHooks.useQuotes (cognitive 30) src/features/quotes/quotesHooks.ts:47— quotesHooks.useQuotes has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 14, if/else 9, ternaries 7. Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 125, 197, 110, …). 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.
getHumanReadableNumber.getHumanReadableNumber (cognitive 29) src/helpers/getHumanReadableNumber.ts:7— getHumanReadableNumber.getHumanReadableNumber has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapInputs.SwapInputs (cognitive 26) src/components/SwapInputs/SwapInputs.tsx:50— SwapInputs.SwapInputs has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 14, boolean chains 12. Of this number, 22 points are the body's own statements and 4 belong to 4 function items inside it that branch. 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.
TakeOrderReview.TakeOrderReview (cognitive 20) src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:56— TakeOrderReview.TakeOrderReview has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 12, boolean chains 6, if/else 2. Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
MakeWidget.MakeWidget::renderScreens (cognitive 20) src/components/@widgets/MakeWidget/MakeWidget.tsx:583— MakeWidget.MakeWidget::renderScreens has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, ternaries 3 (6 pts), if/else 3 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (MakeWidget.MakeWidget) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Order.Order (cognitive 20) src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx:52— Order.Order has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 12 (14 pts), boolean chains 6 (nesting depth added 2). Of this number, 18 points are the body's own statements and 2 belong to 2 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.
stringToSignificantDecimals.stringToSignificantDecimals (cognitive 18) src/helpers/stringToSignificantDecimals.ts:5— stringToSignificantDecimals.stringToSignificantDecimals has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MakeOrderReview.MakeOrderReview (cognitive 17) src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:53— MakeOrderReview.MakeOrderReview has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9, boolean chains 6, if/else 2. Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
ApproveReview.ApproveReview (cognitive 16) src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:52— ApproveReview.ApproveReview has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4, ternaries 4. Of this number, 11 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AvailableOrdersWidget.AvailableOrdersWidget (cognitive 16) src/components/AvailableOrdersWidget/AvailableOrdersWidget.tsx:27— AvailableOrdersWidget.AvailableOrdersWidget has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, ternaries 4 (7 pts), boolean chains 2 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 3 function items inside it that branch (handleSortButtonClick, a function literal at line 51, a function literal at line 73). 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.
TransactionToast.TransactionToast (cognitive 16) src/components/Toasts/TransactionToast.tsx:59— TransactionToast.TransactionToast has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 2 (3 pts), boolean chains 2 (nesting depth added 5). 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 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.
End-of-life runtime: Node.js 18 .nvmrc:1— .nvmrc declares Node.js 18 as this project's version file, and Node.js 18, support ended 2025-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
No structured logging — No logging call was found in the 643 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 23 sibling directories (24 clone groups) src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:19— 24 duplicated blocks under src/components/ have copies in at least two of the sibling directories @reviewScreens, @widgets, ApprovalSubmittedScreen, AvailableOrdersWidget, ChainSelectionPopover, ChainSelector (+17 more sibling(s) not listed) — 12 of them are reported below, and 12 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 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 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 24 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 10 sibling directories (18 clone groups) src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:382— 18 duplicated blocks under src/components/@widgets/ have copies in at least two of the sibling directories ApprovalsWidget, CancelWidget, LimitOrderDetailWidget, MakeWidget, MyLimitOrdersWidget, MyOrdersWidget (+4 more sibling(s) not listed) — 8 of them are reported below, and 10 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 18 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 18 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 18 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 8 sibling directories (17 clone groups) src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41— 17 duplicated blocks under src/ have copies in at least two of the sibling directories components, contexts, entities, features, helpers, hooks (+2 more sibling(s) not listed) — 5 of them are reported below, and 12 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 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 9 sibling directories (9 clone groups) src/features/delegateRules/hooks/useSetRuleLogs.ts:30— 9 duplicated blocks under src/features/ have copies in at least two of the sibling directories balances, cancelLimit, delegateRules, makeOrder, metadata, myOtcOrders (+3 more sibling(s) not listed) — 4 of them are reported below, and 5 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 9 and which does not depend on how exactly each block's copies still match. 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.
R10 · Code Duplication· Duplicated block with local edits (182 matched lines × 2 locations) · ×1
Duplicated block with local edits (182 matched lines × 2 locations) src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:382— src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:382 · src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:370 — the two spans are one implementation copied and then locally edited — 757 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 (131 matched lines × 2 locations) · ×1
Duplicated block with local edits (131 matched lines × 2 locations) src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:47— src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:47 · src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:50 — the two spans are one implementation copied and then locally edited — 653 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 (109 matched lines × 2 locations) · ×1
Duplicated block with local edits (109 matched lines × 2 locations) src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:45— src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:45 · src/components/@reviewScreens/WrapReview/WrapReview.tsx:37 — the two spans are one implementation copied and then locally edited — 479 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 (69 lines × 2 locations) src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:19— src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:19 · src/features/transactions/hooks/useLatestUnsetRuleFromEvents.ts:18 — 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 (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx:68— src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx:68 · src/components/@widgets/MyOtcOrdersWidget/MyOtcOrdersWidget.tsx:76 — the two spans are one implementation copied and then locally edited — 297 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 (60 matched lines × 2 locations) · ×1
Duplicated block with local edits (60 matched lines × 2 locations) src/components/@widgets/MyLimitOrdersWidget/subcomponents/MyLimitOrdersList/MyLimitOrdersList.tsx:27— src/components/@widgets/MyLimitOrdersWidget/subcomponents/MyLimitOrdersList/MyLimitOrdersList.tsx:27 · src/components/@widgets/MyOtcOrdersWidget/subcomponents/MyOtcOrdersList/MyOtcOrdersList.tsx:30 — the two spans are one implementation copied and then locally edited — 315 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 (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) src/features/transactions/hooks/useLatestSwapErc20FromEvents.ts:14— src/features/transactions/hooks/useLatestSwapErc20FromEvents.ts:14 · src/features/transactions/hooks/useLatestSwapFromEvents.ts:14 — the two spans are one implementation copied and then locally edited — 294 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 (48 lines × 2 locations) src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:19— src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:19 · src/components/UnsetRuleScreen/UnsetRuleScreen.tsx:19 — 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 (46 lines × 2 locations) src/features/orders/ordersActions.ts:196— src/features/orders/ordersActions.ts:196 · src/features/orders/ordersActions.ts:244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (45 lines × 2 locations) src/components/DepositSubmittedScreen/DepositSubmittedScreen.tsx:21— src/components/DepositSubmittedScreen/DepositSubmittedScreen.tsx:21 · src/components/SubmittedCancellationScreen/SubmittedCancellationScreen.tsx:24 — 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.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) src/features/transactions/helpers/getOrdersFromSwapErc20Logs.ts:15— src/features/transactions/helpers/getOrdersFromSwapErc20Logs.ts:15 · src/features/transactions/helpers/getOrdersFromSwapLogs.ts:12 — the two spans are one implementation copied and then locally edited — 258 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 (35 matched lines × 2 locations) · ×1
Duplicated block with local edits (35 matched lines × 2 locations) src/features/delegateRules/hooks/useSetRuleLogs.ts:30— src/features/delegateRules/hooks/useSetRuleLogs.ts:30 · src/features/transactions/hooks/useSwapLogs.ts:24 — the two spans are one implementation copied and then locally edited — 210 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 (34 lines × 3 locations) src/components/ApprovalSubmittedScreen/ApprovalSubmittedScreen.tsx:37— src/components/ApprovalSubmittedScreen/ApprovalSubmittedScreen.tsx:37 · src/components/DepositSubmittedScreen/DepositSubmittedScreen.tsx:29 · src/components/SubmittedCancellationScreen/SubmittedCancellationScreen.tsx:32 — the 3 copies are spread across 3 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. 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 (26 lines × 3 locations) src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41— src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41 · src/hooks/useApprovalPending.ts:37 · src/hooks/useCancellationPending.ts:25 — the 3 copies are spread across 3 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 (26 lines × 2 locations) src/features/makeOrder/makeOrderActions.ts:180— src/features/makeOrder/makeOrderActions.ts:180 · src/features/makeOrder/makeOrderActions.ts:244 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 4 locations) src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:14— src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts:14 · src/features/transactions/hooks/useLatestDepositOrWithdrawFromEvents.ts:13 · src/features/transactions/hooks/useLatestSetRuleFromEvents.ts:13 · src/features/transactions/hooks/useLatestUnsetRuleFromEvents.ts:13 — the 4 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 4 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 (22 lines × 4 locations) src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41— src/components/@widgets/MyLimitOrdersWidget/hooks/useRuleUnsetPending.ts:41 · src/hooks/useApprovalPending.ts:37 · src/hooks/useCancellationPending.ts:25 · src/hooks/useDepositPending.ts:24 — the 4 copies are spread across 4 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 (21 matched lines × 2 locations) · ×1
Duplicated block with local edits (21 matched lines × 2 locations) src/entities/OrderERC20/OrderERC20Service.ts:22— src/entities/OrderERC20/OrderERC20Service.ts:22 · src/features/orders/ordersHelpers.ts:96 — the two spans are one implementation copied and then locally edited — 96 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 (21 lines × 2 locations) src/pages/LimitOrderDetail/LimitOrderDetail.tsx:71— src/pages/LimitOrderDetail/LimitOrderDetail.tsx:71 · src/pages/OtcOrderDetail/OtcOrderDetail.tsx:41 — 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.
R10 · Code Duplication· Duplicated block with local edits (20 matched lines × 2 locations) · ×1
Duplicated block with local edits (20 matched lines × 2 locations) src/components/ChainSelectionPopover/ChainSelectionPopover.styles.tsx:4— src/components/ChainSelectionPopover/ChainSelectionPopover.styles.tsx:4 · src/components/SettingsPopover/SettingsPopover.styles.tsx:11 — the two spans are one implementation copied and then locally edited — 146 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 (20 lines × 3 locations) src/features/transactions/hooks/useLatestCancelFromEvents.ts:48— src/features/transactions/hooks/useLatestCancelFromEvents.ts:48 · src/features/transactions/hooks/useLatestSwapErc20FromEvents.ts:64 · src/features/transactions/hooks/useLatestSwapFromEvents.ts:74 — the 3 copies are spread across 3 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 (19 lines × 2 locations) src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:64— src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:64 · src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:93 — 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 (19 matched lines × 2 locations) · ×1
Duplicated block with local edits (19 matched lines × 2 locations) src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.styles.tsx:1— src/pages/LimitOrderDetail/subcomponents/NotFound/NotFound.styles.tsx:1 · src/pages/OtcOrderDetail/subcomponents/InvalidOrder/InvalidOrder.styles.tsx:1 — the two spans are one implementation copied and then locally edited — 78 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 (18 lines × 3 locations) src/components/OrderSubmittedScreen/OrderSubmittedScreen.tsx:97— src/components/OrderSubmittedScreen/OrderSubmittedScreen.tsx:97 · src/components/SetRuleSubmittedScreen/SetRuleSubmittedScreen.tsx:51 · src/components/UnsetRuleScreen/UnsetRuleScreen.tsx:51 — the 3 copies are spread across 3 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 (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) src/features/cancelLimit/cancelLimitSlice.ts:20— src/features/cancelLimit/cancelLimitSlice.ts:20 · src/features/takeLimit/takeLimitSlice.ts:36 — the two spans are one implementation copied and then locally edited — 68 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 (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx:96— src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx:96 · src/components/AvailableOrdersWidget/subcomponents/AvailableOrdersList/AvailableOrdersList.tsx:71 — the two spans are one implementation copied and then locally edited — 78 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 (17 lines × 3 locations) src/components/Content/Introduction.tsx:4— src/components/Content/Introduction.tsx:4 · src/components/Content/Organization.tsx:4 · src/components/Content/Products.tsx:4 — 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.
Complex function MakeWidget (cyclomatic 38, cognitive 33) src/components/@widgets/MakeWidget/MakeWidget.tsx:118— MakeWidget has cyclomatic complexity 38 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 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 OtcOrderDetailWidget (cyclomatic 36, cognitive 33) src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:106— OtcOrderDetailWidget has cyclomatic complexity 36 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 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 SwapWidget (cyclomatic 33, cognitive 23) src/components/@widgets/SwapWidget/SwapWidget.tsx:110— SwapWidget has cyclomatic complexity 33 and cognitive complexity 23; 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 SwapInputs (cyclomatic 30, cognitive 22) src/components/SwapInputs/SwapInputs.tsx:50— SwapInputs has cyclomatic complexity 30 and cognitive complexity 22; 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 TokenSelect (cyclomatic 22, cognitive 14) src/components/TokenSelect/TokenSelect.tsx:116— TokenSelect has cyclomatic complexity 22 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 renderScreens (cyclomatic 21, cognitive 24) src/components/@widgets/MakeWidget/MakeWidget.tsx:583— renderScreens has cyclomatic complexity 21 and cognitive complexity 24; 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 21, cognitive 20) src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx:71— (anonymous) has cyclomatic complexity 21 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 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 LimitOrderDetailWidget (cyclomatic 21, cognitive 18) src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:97— LimitOrderDetailWidget has cyclomatic complexity 21 and cognitive complexity 18; 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 20, cognitive 21) src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx:52— (anonymous) has cyclomatic complexity 20 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 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 WalletTransaction (cyclomatic 19, cognitive 16) src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx:42— WalletTransaction has cyclomatic complexity 19 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 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 getHumanReadableNumber (cyclomatic 18, cognitive 29) src/helpers/getHumanReadableNumber.ts:7— getHumanReadableNumber has cyclomatic complexity 18 and cognitive complexity 29; 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 17, cognitive 12) src/hooks/useShouldDepositNativeTokenAmount.ts:31— (anonymous) has cyclomatic complexity 17 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 16, cognitive 15) src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx:67— (anonymous) has cyclomatic complexity 16 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 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 15, cognitive 12) src/features/quotes/quotesHooks.ts:47— (anonymous) has cyclomatic complexity 15 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 14, cognitive 13) src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:65— (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderScreens (cyclomatic 14, cognitive 13) src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:428— renderScreens has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 11) src/helpers/toMaxAllowedDecimalsNumberString.ts:9— (anonymous) has cyclomatic complexity 14 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 stringToSignificantDecimals (cyclomatic 13, cognitive 18) src/helpers/stringToSignificantDecimals.ts:5— stringToSignificantDecimals has cyclomatic complexity 13 and cognitive complexity 18; 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 ActionButtons (cyclomatic 13, cognitive 11) src/components/@widgets/OrderDetailWidget/subcomponents/ActionButtons/ActionButtons.tsx:42— ActionButtons has cyclomatic complexity 13 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 getTimeAgoTranslation (cyclomatic 12, cognitive 15) src/components/TransactionsTab/helpers/getTimeAgoTranslation.ts:7— getTimeAgoTranslation has cyclomatic complexity 12 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 ApprovalListItem (cyclomatic 12, cognitive 9) src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalListItem/ApprovalListItem.tsx:45— ApprovalListItem has cyclomatic complexity 12 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 (anonymous) (cyclomatic 12, cognitive 9) src/components/ApprovalNotice/helpers.ts:106— (anonymous) has cyclomatic complexity 12 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 findTokenFromAndTokenToAddress (cyclomatic 11, cognitive 12) src/components/@widgets/SwapWidget/helpers/findTokenFromAndTokenToAddress.ts:7— findTokenFromAndTokenToAddress has cyclomatic complexity 11 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 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 OrderStatusInfo (cyclomatic 11, cognitive 10) src/components/@widgets/OrderDetailWidget/subcomponents/OrderStatusInfo/OrderStatusInfo.tsx:21— OrderStatusInfo has cyclomatic complexity 11 and cognitive complexity 10; 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 renderScreens (cyclomatic 11, cognitive 9) src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:410— renderScreens has cyclomatic complexity 11 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 InfoSection (cyclomatic 11, cognitive 9) src/components/@widgets/SwapWidget/subcomponents/InfoSection/InfoSection.tsx:31— InfoSection has cyclomatic complexity 11 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 (anonymous) (cyclomatic 11, cognitive 9) src/hooks/useAllowance.ts:59— (anonymous) has cyclomatic complexity 11 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.
R3 · Large Files· src/components/@widgets/MakeWidget/MakeWidget.tsx · ×1
src/components/@widgets/MakeWidget/MakeWidget.tsx: 766 lines of code src/components/@widgets/MakeWidget/MakeWidget.tsx:1— src/components/@widgets/MakeWidget/MakeWidget.tsx has 766 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· src/components/@widgets/SwapWidget/SwapWidget.tsx · ×1
src/components/@widgets/SwapWidget/SwapWidget.tsx: 617 lines of code src/components/@widgets/SwapWidget/SwapWidget.tsx:1— src/components/@widgets/SwapWidget/SwapWidget.tsx has 617 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· src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx · ×1
src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx: 571 lines of code src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:1— src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx has 571 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· src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx · ×1
src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx: 551 lines of code src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx:1— src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx has 551 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· src/features/orders/ordersActions.ts · ×1
src/features/orders/ordersActions.ts: 453 lines of code src/features/orders/ordersActions.ts:1— src/features/orders/ordersActions.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step package.json:9— the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `lint` script (`eslint "./src/**/*.{ts,tsx}"`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
R6 · Tooling· This package's lint script runs in no CI job · ×1
This package's lint script runs in no CI job package.json:9— The root package declares the lint script `lint` (`eslint "./src/**/*.{ts,tsx}"`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `.` (or the workspace's task runner).
Dead file (~147 LoC) src/components/Toasts/TransactionToast.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~100 LoC) src/components/InformationModals/subcomponents/GuideButton/GuideButton.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/InformationModals/subcomponents/GuideButton/GuideButton.tsx) — 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 (~86 LoC) src/components/WalletButton/WalletButton.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~66 LoC) src/features/balances/balancesHelpers.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~50 LoC) src/features/delegateRules/hooks/useHistoricalDelegateRules.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~46 LoC) src/components/Toasts/ConfirmationToast.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~42 LoC) src/entities/BatchCall/BatchCallService.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~34 LoC) src/hooks/useStringToSignificantDecimals.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~28 LoC) src/components/InformationModals/subcomponents/GuideButton/GuideButton.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~27 LoC) src/components/TokenList/subcomponents/TokenDeleteButton/TokenDeleteButton.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/TokenList/subcomponents/TokenDeleteButton/TokenDeleteButton.tsx) — 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 (~25 LoC) src/components/@widgets/SwapWidget/hooks/useBestTradeOptionTransaction.ts— no import path from any entry point (3 application, 9 tooling, 17 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 (~19 LoC) src/components/TokenList/subcomponents/TokenDeleteButton/TokenDeleteButton.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~18 LoC) src/components/@widgets/MakeWidget/subcomponents/InputSection/InputSection.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/components/@widgets/MakeWidget/subcomponents/InputSection/InputSection.tsx) — 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 (~17 LoC) src/styled-components/Link/Link.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~13 LoC) src/components/@widgets/MyOrdersWidget/subcomponents/InfoSection/InfoSection.styles.tsx— no import path from any entry point (3 application, 9 tooling, 17 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 (~6 LoC) src/constants/Weth9.ts— no import path from any entry point (3 application, 9 tooling, 17 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 '@coinbase/wallet-sdk' package.json:19— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@web3-react/abstract-connector' package.json:36— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@web3-react/injected-connector' package.json:40— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@web3-react/store' package.json:42— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'classnames' package.json:49— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-beforeunload' package.json:65— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-blockies' package.json:66— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Third-party script without Subresource Integrity public/index.html:35— `https://www.googletagmanager.com/gtag/js?id=G-XSB2E7X42G` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup.
Swallowed exception (empty catch) src/helpers/switchToDefaultChain.ts:8— 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.
Orphaned file src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx: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 src/features/orders/ordersActions.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 src/features/balances/balancesApi.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 src/style/reset.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 src/features/orders/ordersHelpers.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 src/features/makeOrder/makeOrderActions.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 src/entities/SubmittedTransaction/SubmittedTransactionHelpers.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 src/components/TokenSelect/TokenSelect.styles.tsx: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 src/components/TokenSelect/TokenSelect.tsx: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 src/features/transactions/transactionsSlice.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 src/features/quotes/quotesHooks.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 src/components/TransactionsTab/TransactionsTab.tsx: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 src/components/@reviewScreens/TakeOrderReview/TakeOrderReview.tsx: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 src/components/@reviewScreens/MakeOrderReview/MakeOrderReview.tsx: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 src/components/TokenList/TokenList.tsx: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 src/components/@widgets/ApprovalsWidget/ApprovalsWidget.tsx: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 src/features/transactions/transactionsHelpers.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 src/components/SwapInputs/SwapInputs.tsx: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 src/features/balances/balancesSlice.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 src/components/@widgets/MyLimitOrdersWidget/MyLimitOrdersWidget.tsx: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 src/components/TransactionsTab/subcomponents/WalletTransaction/WalletTransaction.tsx: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 src/components/@widgets/MyOrdersWidget/subcomponents/Order/Order.tsx: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 src/components/@reviewScreens/ApproveReview/ApproveReview.tsx: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 src/features/quotes/quotesActions.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 src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.tsx: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.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:540— @babel/plugin-proposal-async-generator-functions 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:550— @babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-static-block REDACTED:558— @babel/plugin-proposal-class-static-block 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-static-block instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:578— @babel/plugin-proposal-dynamic-import 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:586— @babel/plugin-proposal-export-namespace-from 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-json-strings REDACTED:594— @babel/plugin-proposal-json-strings 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:602— @babel/plugin-proposal-logical-assignment-operators 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:610— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:618— @babel/plugin-proposal-numeric-separator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:626— @babel/plugin-proposal-object-rest-spread 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:637— @babel/plugin-proposal-optional-catch-binding 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:645— @babel/plugin-proposal-optional-chaining 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:654— @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:662— @babel/plugin-proposal-private-property-in-object 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-unicode-property-regex REDACTED:672— @babel/plugin-proposal-unicode-property-regex 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:2307— @humanwhocodes/config-array 0.11.8 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:2321— @humanwhocodes/object-schema 1.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @motionone/vue REDACTED:2742— @motionone/vue 10.16.4 is resolved in REDACTED and is marked deprecated by its publisher: "Motion One for Vue is deprecated. Use Oku Motion instead https://oku-ui.com/motion". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @react-hookz/deep-equal REDACTED:2919— @react-hookz/deep-equal 1.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "PACKAGE IS DEPRECATED AND WILL BE DETED SOON, USE @ver0/deep-equal INSTEAD". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @safe-global/safe-gateway-typescript-sdk REDACTED:3007— @safe-global/safe-gateway-typescript-sdk 3.21.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @walletconnect/ethereum-provider REDACTED:4156— @walletconnect/ethereum-provider 2.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Reliability and performance improvements. See: https://github.com/WalletConnect/walletconnect-monorepo/releases". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @walletconnect/modal REDACTED:4269— @walletconnect/modal 2.6.2 is resolved in REDACTED and is marked deprecated by its publisher: "Please follow the migration guide on https://docs.reown.com/appkit/upgrade/wcm". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @walletconnect/sign-client REDACTED:4303— @walletconnect/sign-client 2.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Reliability and performance improvements. See: https://github.com/WalletConnect/walletconnect-monorepo/releases". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @walletconnect/universal-provider REDACTED:4337— @walletconnect/universal-provider 2.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Reliability and performance improvements. See: https://github.com/WalletConnect/walletconnect-monorepo/releases". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: abab REDACTED:4618— abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Duplicated predicate src/features/delegateRules/hooks/useSetRuleLogs.ts:86— `!chainId || !account || !provider || !isNetworkSupported` appears character-identically in 9 files — src/features/delegateRules/hooks/useSetRuleLogs.ts, src/features/transactions/hooks/useLatestCancelFromEvents.ts, src/features/transactions/hooks/useLatestDelegateSwapFromEvents.ts, src/features/transactions/hooks/useLatestDepositOrWithdrawFromEvents.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 src/components/@widgets/MakeWidget/MakeWidget.tsx:676— `!isActive || isAllowancesOrBalancesFailed` appears character-identically in 2 files — src/components/@widgets/MakeWidget/MakeWidget.tsx, src/components/@widgets/SwapWidget/SwapWidget.tsx. 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 src/components/@reviewScreens/ApproveReview/ApproveReview.tsx:94— `!isLoading && hasEditButton && onEditButtonClick` appears character-identically in 2 files — src/components/@reviewScreens/ApproveReview/ApproveReview.tsx, src/components/@reviewScreens/WrapReview/WrapReview.tsx. 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 src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts:11— `!senderTokenDecimals || !signerTokenDecimals` appears character-identically in 2 files — src/components/@widgets/LimitOrderDetailWidget/helpers/index.ts, src/components/@widgets/LimitOrderDetailWidget/hooks/useAvailableSenderAndSignerAmount.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 src/components/@widgets/LimitOrderDetailWidget/hooks/useSessionDelegateSwapTransaction.ts:18— `!transactions.length || processingTransactionHash` appears character-identically in 3 files — src/components/@widgets/LimitOrderDetailWidget/hooks/useSessionDelegateSwapTransaction.ts, src/components/@widgets/LimitOrderDetailWidget/hooks/useSessionUnsetRuleTransaction.ts, src/components/@widgets/OtcOrderDetailWidget/hooks/useSessionOrderTransaction.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 src/components/ChainSelector/ChainSelector.tsx:33— `(containerRef.current && containerRef.current.contains(e.target)) || (popoverRef.current && popoverRef.current.contains(e.target))` appears character-identically in 2 files — src/components/ChainSelector/ChainSelector.tsx, src/components/SettingsButton/SettingsButton.tsx. 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 src/helpers/swap.ts:41— `SwapERC20.getAddress(chainId) || undefined` appears character-identically in 2 files — src/helpers/swap.ts, src/helpers/swapErc20.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 src/features/delegateRules/hooks/useSetRuleLogs.ts:88— `account === accountState && chainId === chainIdState` appears character-identically in 10 files — src/features/delegateRules/hooks/useSetRuleLogs.ts, src/features/transactions/hooks/useLatestApproveFromEvents.ts, src/features/transactions/hooks/useLatestCancelFromEvents.ts, src/features/transactions/hooks/useLatestDelegateSwapFromEvents.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 src/components/@widgets/MyLimitOrdersWidget/subcomponents/MyLimitOrdersList/MyLimitOrdersList.tsx:88— `allowances.swapERC20.status === "idle" && allowances.swap.status === "idle"` appears character-identically in 2 files — src/components/@widgets/MyLimitOrdersWidget/subcomponents/MyLimitOrdersList/MyLimitOrdersList.tsx, src/components/@widgets/MyOtcOrdersWidget/subcomponents/MyOtcOrdersList/MyOtcOrdersList.tsx. 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 src/entities/ExtendedPricing/ExtendedPricingHelpers.ts:89— `compareAddresses(pricing.baseToken, baseToken) && compareAddresses(pricing.quoteToken, quoteToken)` appears character-identically in 2 files — src/entities/ExtendedPricing/ExtendedPricingHelpers.ts, src/features/quotes/quotesApi.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 src/components/@widgets/MyOtcOrdersWidget/subcomponents/MyOtcOrdersList/helpers/index.ts:91— `isFullOrder(order) && order.signer.kind !== TokenKinds.ERC20` appears character-identically in 2 files — src/components/@widgets/MyOtcOrdersWidget/subcomponents/MyOtcOrdersList/helpers/index.ts, src/entities/OrderERC20/OrderERC20Helpers.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 src/components/@widgets/MakeWidget/MakeWidget.tsx:779— `ordersStatus === "signing" || !approvalTransaction` appears character-identically in 3 files — src/components/@widgets/MakeWidget/MakeWidget.tsx, src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx, src/components/@widgets/SwapWidget/SwapWidget.tsx. 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 src/components/@widgets/MakeWidget/MakeWidget.tsx:790— `ordersStatus === "signing" || !depositTransaction` appears character-identically in 2 files — src/components/@widgets/MakeWidget/MakeWidget.tsx, src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx. 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 src/features/transactions/helpers/getOrdersFromSwapErc20Logs.ts:25— `protocolFeeReceiverAddresses[chainId] || Pool.getAddress(chainId)` appears character-identically in 2 files — src/features/transactions/helpers/getOrdersFromSwapErc20Logs.ts, src/features/transactions/helpers/getOrdersFromSwapLogs.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 src/components/@widgets/CancelWidget/CancelWidget.tsx:111— `status === "signing" || !pendingCancelTranssaction` appears character-identically in 2 files — src/components/@widgets/CancelWidget/CancelWidget.tsx, src/components/@widgets/MyOtcOrdersWidget/MyOtcOrdersWidget.tsx. 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 src/components/OrderReviewToken/OrderReviewToken.tsx:31— `tokenKind === TokenKinds.ERC721 || tokenKind === TokenKinds.ERC1155` appears character-identically in 4 files — src/components/OrderReviewToken/OrderReviewToken.tsx, src/components/TokenSelect/TokenSelect.tsx, src/helpers/scrapeToken.ts, src/hooks/useAmountPlusFee.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.
Outdated (npm): @react-hookz/web package.json:23— @react-hookz/web is pinned at 14.2.2; registry.npmjs.org publishes 26.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @testing-library/react package.json:28— @testing-library/react is pinned at 11.2.7; registry.npmjs.org publishes 16.3.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/jest package.json:30— @types/jest is pinned at 26.0.24; registry.npmjs.org publishes 30.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/node package.json:31— @types/node is pinned at 12.20.33; registry.npmjs.org publishes 26.6.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): framer-motion package.json:56— framer-motion is pinned at 4.1.17; registry.npmjs.org publishes 14.14.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next package.json:59— i18next is pinned at 20.6.1; registry.npmjs.org publishes 27.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next-http-backend package.json:61— i18next-http-backend is pinned at 1.3.1; registry.npmjs.org publishes 4.0.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-i18next package.json:70— react-i18next is pinned at 11.12.0; registry.npmjs.org publishes 18.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): typescript package.json:81— typescript is pinned at 4.4.3; registry.npmjs.org publishes 7.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
redundant comment src/entities/ExtendedPricing/ExtendedPricingHelpers.ts:54— "If all pricings are errors, return the first error" repeats the code it sits on: 4 of its 5 words (pricings, errors, return, error) are already in `if (quoteAmounts.every((quoteAmount) => quoteAmount in PricingErrorType))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/features/balances/balancesApi.ts:137— "Get the BatchCall contract instance" repeats the code it sits on: 4 of its 5 words (get, batch, call, contract) are already in `const contract = BatchCall.getContract(provider, chainId);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/hooks/useWindowSize.ts:21— "Set window width/height to state" repeats the code it sits on: 4 of its 5 words (set, window, width, height) are already in `setWindowSize({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/hooks/useWindowSize.ts:27— "Add event listener" repeats the code it sits on: 3 of its 3 words (add, event, listener) are already in `window.addEventListener("resize", handleResize);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file src/components/@widgets/MakeWidget/MakeWidget.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/components/@widgets/SwapWidget/SwapWidget.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/components/@widgets/LimitOrderDetailWidget/LimitOrderDetailWidget.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
No ADRs found Procfile:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Procfile` makes this repository a deployable product (line 1).
Dormant codebase — 125 of 125 significant files have no living knowledge — the codebase as a whole is dormant, not 125 separate risks. Counted over 125 of the 644 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
Disabled test src/components/WalletButton/WalletButton.spec.tsx:13— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Thin README README.md:1— The root README is 106 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
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.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
README/code drift README.md:12— README.md names Node.js 16, but the repository declares engines `18.19.0`, pinned 18. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No SAST REDACTED:2— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation package.json:16— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
R7 · Dead Code· Unused export 'PairButtonWrapper' · ×1
Unused export 'PairButtonWrapper' src/components/@widgets/ApprovalsWidget/subcomponents/ApprovalsListSortButtons/ApprovalsListSortButtons.styles.tsx:12— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'StyledRateField' · ×1
Unused export 'StyledRateField' src/components/@widgets/MakeWidget/MakeWidget.styles.tsx:112— Nothing imports this binding — it is safe to review for removal.
Unused export 'Wrapper' src/components/@widgets/MakeWidget/subcomponents/ExpirySelector/ExpirySelector.styles.tsx:24— Nothing imports this binding — it is safe to review for removal.
Unused export 'Title' src/components/@widgets/MakeWidget/subcomponents/ExpirySelector/ExpirySelector.styles.tsx:32— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'TooltipContainer' · ×1
Unused export 'TooltipContainer' src/components/@widgets/MyOrdersWidget/subcomponents/MyOrdersList/MyOrdersList.styles.tsx:37— Nothing imports this binding — it is safe to review for removal.
Unused export 'StyledTitle' src/components/@widgets/OrderDetailWidget/subcomponents/OrderDetailWidgetHeader/OrderDetailWidgetHeader.styles.tsx:10— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'StyledInfoSectionHeading' · ×1
Unused export 'StyledInfoSectionHeading' src/components/@widgets/OrderDetailWidget/subcomponents/RecipientAndStatus/RecipientAndStatus.styles.tsx:19— Nothing imports this binding — it is safe to review for removal.
Unused export 'Recipient' src/components/@widgets/OrderDetailWidget/subcomponents/RecipientAndStatus/RecipientAndStatus.styles.tsx:26— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'WelcomeMessage' · ×1
Unused export 'WelcomeMessage' src/components/@widgets/SwapWidget/SwapWidget.styles.tsx:9— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'InfoSectionContainer' · ×1
Unused export 'InfoSectionContainer' src/components/AvailableOrdersWidget/AvailableOrdersWidget.styles.tsx:18— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'sortTokensByBalance' · ×1
Unused export 'sortTokensByBalance' src/components/TokenList/helpers/sort.ts:12— Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene· Test-only dependency '@testing-library/react' in production deps · ×1
Test-only dependency '@testing-library/react' in production deps package.json:28— Only test files import it (first: src/components/Timer/Timer.spec.tsx:1) — move it to devDependencies.
R8 · Dependency Hygiene· Test-only dependency '@testing-library/user-event' in production deps · ×1
Test-only dependency '@testing-library/user-event' in production deps package.json:29— Only test files import it (first: src/components/WalletButton/WalletButton.spec.tsx:2) — move it to devDependencies.
No app-layer HTTPS enforcement detected index.js:14— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−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/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) 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 (`!`) override strict null checking — ~2.4 `!` null assertions per 1k TypeScript source lines — 100 assertion(s) across the 41044 source line(s) of the 642 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: src/components/@widgets/SwapWidget/SwapWidget.tsx (22), src/components/@widgets/MakeWidget/MakeWidget.tsx (20), src/components/@widgets/OtcOrderDetailWidget/OtcOrderDetailWidget.tsx (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X7 · Silent fallback defaults· Pending state with no failure state · ×1
Pending state with no failure state src/pages/OtcOrderDetail/OtcOrderDetail.tsx:51— The view draws `<Page>` under `status === "idle" || ! activeOrder`, but `status` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Outdated (npm): @airswap/libraries — @airswap/libraries is pinned at 5.0.12; registry.npmjs.org publishes 5.0.15 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @coinbase/wallet-sdk — @coinbase/wallet-sdk is pinned at 3.7.2; registry.npmjs.org publishes 4.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @craco/craco — @craco/craco is pinned at 6.4.5; registry.npmjs.org publishes 7.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fontsource/dm-mono — @fontsource/dm-mono is pinned at 4.5.0; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @greypixel_/nicenumbers — @greypixel_/nicenumbers is pinned at 0.0.18; registry.npmjs.org publishes 0.0.20 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @reduxjs/toolkit — @reduxjs/toolkit is pinned at 1.5.1; registry.npmjs.org publishes 2.14.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @sentry/cli — @sentry/cli is pinned at 2.42.2; registry.npmjs.org publishes 3.8.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @sentry/react — @sentry/react is pinned at 9.4.0; registry.npmjs.org publishes 11.13.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @testing-library/jest-dom — @testing-library/jest-dom is pinned at 5.14.1; registry.npmjs.org publishes 7.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @testing-library/user-event — @testing-library/user-event is pinned at 13.5.0; registry.npmjs.org publishes 14.6.12 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/react — @types/react is pinned at 17.0.30; registry.npmjs.org publishes 19.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/react-dom — @types/react-dom is pinned at 17.0.9; registry.npmjs.org publishes 19.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/react-redux — @types/react-redux is pinned at 7.1.19; registry.npmjs.org publishes 7.1.35 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/styled-components — @types/styled-components is pinned at 5.1.15; registry.npmjs.org publishes 5.1.36 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): alchemy-sdk — alchemy-sdk is pinned at 3.5.6; registry.npmjs.org publishes 3.6.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): bignumber.js — bignumber.js is pinned at 9.0.1; registry.npmjs.org publishes 11.1.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): classnames — classnames is pinned at 2.3.1; registry.npmjs.org publishes 2.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): cors — cors is pinned at 2.8.5; registry.npmjs.org publishes 2.8.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): crypto-browserify — crypto-browserify is pinned at 3.12.0; registry.npmjs.org publishes 3.12.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): date-fns — date-fns is pinned at 2.28.0; registry.npmjs.org publishes 4.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): erc-20-abi — erc-20-abi is pinned at 1.0.0; registry.npmjs.org publishes 1.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ethers — ethers is pinned at 5.7.2; registry.npmjs.org publishes 6.17.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next-browser-languagedetector — i18next-browser-languagedetector is pinned at 6.1.2; registry.npmjs.org publishes 8.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react — react is pinned at 17.0.2; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-beforeunload — react-beforeunload is pinned at 2.5.2; registry.npmjs.org publishes 2.7.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names src/components/TokenList/TokenList.tsx:45— 2 of 16 documented parameters and 4 of 93 summaries in `airswap-web` only repeat the member or parameter name (e.g. "All active tokens." for `activeTokens`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
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.
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 01a1e64c-cc86-7027-8f55-be584f0f5c53 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 102 · Warnings: 366 · Recommendations: 238 · Info: 34 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 21:39 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.