Public report of FuelLabs/fuels-ts, published 26 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 26 October 2026, 15:01 UTC · Survey ID cd_65da5fad7731452c99b127d0bbf65aa5

FuelLabs/fuels-ts

Measured 26 October 2026, 14:40 UTC, at code version b3f37c9

Regression: 1 dimension fell since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 50out of 100 At risk Down 6 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Architecture 89 Adequate Code Health 79 Strong Maturity 62 Adequate Performance 60 Adequate Accessibility 54 Adequate Production Readiness 52 Adequate Security and Compliance 43 Weak

A medium codebase: 40,905 lines of product code in 26 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Security and Compliance, 43

Findings by how serious they are

233 critical 624 serious 220 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 14:40 UTC

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

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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

80of 80 dimensions measured by tools.
1053of 1077 findings point to an exact file and line, so you can open each one in the code. The other 24 concern the repository as a whole, such as missing documentation.
80dimensions across 7 lenses, read from 40,905 lines of product code in 26 projects.
Chapters

Executive summary

FuelLabs/fuels-ts is rated At risk because critical security findings are open. Its score is held back because 76 of the dependencies have a known vulnerability and it has passwords or keys in the code's history. It scores 50 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.

Security and Compliance, at 43, is the weakest lens and counts most in the score. The best first step is fixing the two packages published as malware, worth about 5 points. Replacing the 28 passwords or keys found in the code's history would lift Security and Compliance itself, also worth about 5. Raising Security and Compliance to 68 would lift the score to about 56.

Ninety-three known security holes in the packages the code depends on can be used by attackers. Forty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and twenty-eight passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Passing outside input through environment variables would fix the six pipeline steps that put outside input straight into a shell command, and limiting each secret to its own step would deal with the six secrets exposed to more of the pipeline than needed. The 34 form fields without a label need a label.

The product code is 40,905 lines, about €81,000 to rebuild.

Code Health 79 Strong Architecture 89 Adequate, capped by Boundary Type-Coupling Maturity 62 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 52 Adequate, capped by REDACTED Scanning, Dependency Hygiene and Outbound HTTP resilience Security and Compliance 43 Weak, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities and Malicious Dependencies Accessibility 54 Adequate Performance 60 Adequate

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

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

If Security and Compliance rose from 43 to 68, the lowest score rated Strong, the score would rise from 50 to about 56.

Code composition: what the lines of code are
Product code 47%Tests 53%
New since the last survey: 233 findings

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

  • Test Quality · Skipped test: should call onDeploy callback packages/fuels/src/cli/commands/deploy/index.test.ts
  • Test Quality · Skipped test: should ensure waitForResult always waits for the transaction to be processed packages/fuel-gauge/src/transaction-response.test.ts
  • Test Quality · Skipped test: should encode/decode just fine packages/fuel-gauge/src/abi/abi-coder.test.ts
  • REDACTED Scanning · REDACTED
  • Boundary Type-Coupling · Cross-context type BNInput (math → abi-coder) packages/abi-coder/src/encoding/coders/BigNumberCoder.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/encoding/coders/AbstractCoder.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/FunctionFragment.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/FunctionFragment.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/Interface.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/Interface.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts
  • Boundary Type-Coupling · Cross-context type AddressInput (address → account) packages/account/src/wallet/keystore-wallet.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/wallet/base-wallet-unlocked.ts
  • Boundary Type-Coupling · Cross-context type HashableMessage (hasher → account) packages/account/src/wallet/base-wallet-unlocked.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/utils.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/hdwallet/hdwallet.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallets.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallets.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallets.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallet.ts
  • Boundary Type-Coupling · Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/vaults/mnemonic-vault.ts
  • Boundary Type-Coupling · Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/vaults/mnemonic-vault.ts
  • Boundary Type-Coupling · Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/vaults/privatekey-vault.ts
  • Boundary Type-Coupling · Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/wallet-manager.ts
  • Boundary Type-Coupling · Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/wallet-manager.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-request/input.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-request/output.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/utils/gas.ts
  • Boundary Type-Coupling · Cross-context type BNInput (math → account) packages/account/src/providers/utils/gas.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/utils/gas.ts
  • Boundary Type-Coupling · Cross-context type InputType (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type InputType (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts
  • Boundary Type-Coupling · Cross-context type OutputType (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/types.ts
  • Boundary Type-Coupling · Cross-context type ReceiptType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/create-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/create-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type ContractIdLike (address → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type InputValue (abi-coder → account) packages/account/src/providers/transaction-request/script-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upgrade-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upgrade-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type UpgradePurposeTypeEnum (transactions → account) packages/account/src/providers/transaction-request/upgrade-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upgrade-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upload-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upload-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upload-transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/witness.ts
  • Boundary Type-Coupling · Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts
  • Boundary Type-Coupling · Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts
  • Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-request/transaction-request.ts

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

Fixed since the last survey: 86 findings

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

  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/account/src/providers/provider.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/account/src/utils/predicate-script-loader-instructions.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/fuels/src/cli/commands/deploy/deployPredicates.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/merkle/src/binary/types/node.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) scripts/changeset/get-full-changelog.mts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/abi-typegen/src/utils/assembleContracts.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/account/src/providers/provider.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/address/src/address.ts
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/program/src/functions/base-invocation-scope.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) packages/abi-coder/src/encoding/coders/RawSliceCoder.ts
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/account/src/account.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/account/src/utils/predicate-script-loader-instructions.ts
  • Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) packages/abi-coder/src/encoding/coders/EnumCoder.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/abi-typegen/src/abi/types/ArrayType.ts
  • Code Duplication · Duplicated block (10 lines × 10 locations) packages/abi-typegen/src/abi/types/ArrayType.ts
  • Code Duplication · Duplicated block (10 lines × 4 locations) packages/abi-typegen/src/abi/types/BoolType.ts
  • Code Duplication · Duplicated block (10 lines × 3 locations) packages/abi-typegen/src/abi/types/EvmAddressType.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/crypto/src/browser/bufferFromString.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/fuel-gauge/src/predicate/utils/predicate/fundAccount.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/program/src/response.ts
  • Code Duplication · Duplicated block (10 lines × 5 locations) packages/transactions/src/coders/input.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) scripts/changeset/get-full-changelog.mts
  • Code Duplication · Duplicated block (9 lines × 2 locations) internal/forc/lib/update.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/account/src/account.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/account/src/connectors/fuel-connector.ts
  • Code Duplication · Duplicated block (9 lines × 15 locations) packages/transactions/src/coders/input.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/transactions/src/coders/input.ts
  • Code Duplication · Duplicated block (9 lines × 3 locations) packages/transactions/src/coders/output.ts
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/abi-coder/src/encoding/coders/B256Coder.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/abi-coder/src/encoding/coders/StructCoder.ts
  • Code Duplication · Duplicated block (8 lines × 4 locations) packages/abi-typegen/src/abi/types/RawUntypedPtr.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/account/src/providers/transaction-response/transaction-response.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/contract/src/contract-factory.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/crypto/src/browser/aes-ctr.ts
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/fuels/src/cli/commands/deploy/deployContracts.ts
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/merkle/src/sparse/sparseMerkleTree.ts
  • Code Duplication · Duplicated block (8 lines × 6 locations) packages/transactions/src/coders/input.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/transactions/src/coders/input.ts
  • Code Duplication · Duplicated block (8 lines × 5 locations) packages/transactions/src/coders/transaction.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/versions/src/lib/semver.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/abi-coder/src/encoding/coders/BooleanCoder.ts
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) packages/abi-coder/src/encoding/coders/EnumCoder.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/abi-typegen/src/abi/types/BytesType.ts
  • Code Duplication · Duplicated block (7 lines × 5 locations) packages/abi-typegen/src/abi/types/RawUntypedPtr.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/account/src/account.ts
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) packages/account/src/providers/transaction-summary/get-transaction-summary.ts
  • Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) packages/account/src/account.ts
  • Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) packages/account/src/predicate/utils/getPredicateRoot.ts
  • Code Duplication · Duplicated block (5 lines × 9 locations) packages/transactions/src/coders/input.ts
  • Code Duplication · Duplicated block (5 lines × 2 locations) packages/transactions/src/coders/transaction.ts
  • Code Duplication · Duplicated block (5 lines × 2 locations) packages/transactions/src/coders/transaction.ts
  • Test Coverage · No test reaches this file scripts/changeset/get-latest-release.mts
  • Test Coverage · No test reaches this file internal/forc/lib/bin.js
  • Test Coverage · No test reaches this file internal/fuel-core/lib/bin.js
  • Test Coverage · No test reaches this file apps/demo-nodejs-esm/index.mjs
  • Test Coverage · No test reaches this file packages/abi-typegen/src/bin.ts
  • Test Coverage · No test reaches this file vitest.workspace.ts
  • Test Coverage · No test reaches this file internal/check-imports/src/index.ts
  • Test Coverage · No test reaches this file packages/abi-typegen/typegen.js
  • Test Coverage · No test reaches this file packages/create-fuels/create-fuels.js
  • Async & latency hygiene · Sync-over-async blocking REDACTED
  • Async & latency hygiene · Sync-over-async blocking packages/create-fuels/src/cli.ts
  • Async & latency hygiene · Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployContracts.ts
  • Async & latency hygiene · Sync-over-async blocking packages/fuels/test/utils/runCommands.ts
Rebuild cost: about €81,000 · Estimate
Cost to rebuild€27,000 to €140,000, for 451 to 1,430 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 40,905 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2).
Raises the score by about 5 points · Low effort · Malicious Dependencies
2
Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one.
Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 3 sites, not one: `packages/account/src/mnemonic/mnemonic.ts:123` (PBKDF2-SHA-512, 2,048 iterations), `packages/crypto/src/browser/aes-ctr.ts:21` (PBKDF2-SHA-256, 100,000 iterations), `packages/crypto/src/node/aes-ctr.ts:22` (PBKDF2-SHA-256, 100,000 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Raises the score by about 6 points · Medium effort · Web-Security Posture
3
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc.
Raises the score by about 3 points · Low effort · Platform End-of-Life

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 €81,000 to build again, about 0.6 person-years of work. Its weakest lens is Security and Compliance, at 43 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Malicious package finding(s) in Malicious Dependencies. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 2 Malicious Dependencies findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch @fuel-ts/abi-coder abi-coder @fuel-ts/crypto crypto @fuel-ts/abi-coder->@fuel-ts/crypto @fuel-ts/errors errors @fuel-ts/abi-coder->@fuel-ts/errors @fuel-ts/hasher hasher @fuel-ts/abi-coder->@fuel-ts/hasher @fuel-ts/math math @fuel-ts/abi-coder->@fuel-ts/math @fuel-ts/utils utils @fuel-ts/abi-coder->@fuel-ts/utils @fuel-ts/abi-typegen abi-typegen @fuel-ts/abi-typegen->@fuel-ts/errors @fuel-ts/abi-typegen->@fuel-ts/utils @fuel-ts/versions versions @fuel-ts/abi-typegen->@fuel-ts/versions @fuel-ts/account account @fuel-ts/account->@fuel-ts/abi-coder @fuel-ts/address address @fuel-ts/account->@fuel-ts/address @fuel-ts/account->@fuel-ts/crypto @fuel-ts/account->@fuel-ts/errors @fuel-ts/account->@fuel-ts/hasher @fuel-ts/account->@fuel-ts/math @fuel-ts/merkle merkle @fuel-ts/account->@fuel-ts/merkle @fuel-ts/transactions transactions @fuel-ts/account->@fuel-ts/transactions @fuel-ts/account->@fuel-ts/utils @fuel-ts/account->@fuel-ts/versions @fuel-ts/address->@fuel-ts/crypto @fuel-ts/address->@fuel-ts/errors @fuel-ts/address->@fuel-ts/utils @fuel-ts/contract contract @fuel-ts/contract->@fuel-ts/abi-coder @fuel-ts/contract->@fuel-ts/account @fuel-ts/contract->@fuel-ts/crypto @fuel-ts/contract->@fuel-ts/errors @fuel-ts/contract->@fuel-ts/hasher @fuel-ts/contract->@fuel-ts/math @fuel-ts/contract->@fuel-ts/merkle @fuel-ts/program program @fuel-ts/contract->@fuel-ts/program @fuel-ts/contract->@fuel-ts/transactions @fuel-ts/contract->@fuel-ts/utils @fuel-ts/crypto->@fuel-ts/errors @fuel-ts/crypto->@fuel-ts/utils @fuel-ts/errors->@fuel-ts/versions @fuel-ts/hasher->@fuel-ts/crypto @fuel-ts/hasher->@fuel-ts/utils @fuel-ts/logger logger @fuel-ts/logger->@fuel-ts/address @fuel-ts/logger->@fuel-ts/math @fuel-ts/math->@fuel-ts/errors @fuel-ts/merkle->@fuel-ts/hasher @fuel-ts/merkle->@fuel-ts/math @fuel-ts/program->@fuel-ts/abi-coder @fuel-ts/program->@fuel-ts/account @fuel-ts/program->@fuel-ts/address @fuel-ts/program->@fuel-ts/errors @fuel-ts/program->@fuel-ts/math @fuel-ts/program->@fuel-ts/transactions @fuel-ts/program->@fuel-ts/utils @fuel-ts/recipes recipes @fuel-ts/recipes->@fuel-ts/abi-coder @fuel-ts/recipes->@fuel-ts/abi-typegen @fuel-ts/recipes->@fuel-ts/account @fuel-ts/recipes->@fuel-ts/address @fuel-ts/recipes->@fuel-ts/contract @fuel-ts/recipes->@fuel-ts/program @fuel-ts/recipes->@fuel-ts/transactions @fuel-ts/recipes->@fuel-ts/utils @fuel-ts/script script @fuel-ts/script->@fuel-ts/abi-coder @fuel-ts/script->@fuel-ts/account @fuel-ts/script->@fuel-ts/errors @fuel-ts/script->@fuel-ts/math @fuel-ts/script->@fuel-ts/program @fuel-ts/script->@fuel-ts/transactions @fuel-ts/script->@fuel-ts/utils @fuel-ts/transactions->@fuel-ts/abi-coder @fuel-ts/transactions->@fuel-ts/address @fuel-ts/transactions->@fuel-ts/errors @fuel-ts/transactions->@fuel-ts/hasher @fuel-ts/transactions->@fuel-ts/math @fuel-ts/transactions->@fuel-ts/utils @fuel-ts/utils->@fuel-ts/errors @fuel-ts/utils->@fuel-ts/math @fuel-ts/utils->@fuel-ts/versions @internal/check-imports check-imports @internal/check-imports->@fuel-ts/abi-coder @internal/check-imports->@fuel-ts/abi-typegen @internal/check-imports->@fuel-ts/account @internal/check-imports->@fuel-ts/address @internal/check-imports->@fuel-ts/contract @internal/check-imports->@fuel-ts/crypto @internal/check-imports->@fuel-ts/errors @internal/check-imports->@fuel-ts/hasher @internal/check-imports->@fuel-ts/math @internal/check-imports->@fuel-ts/merkle @internal/check-imports->@fuel-ts/program @internal/check-imports->@fuel-ts/script @internal/check-imports->@fuel-ts/transactions @internal/check-imports->@fuel-ts/utils @internal/check-imports->@fuel-ts/versions fuels fuels @internal/check-imports->fuels create-fuels create-fuels create-fuels->@fuel-ts/errors create-fuels->@fuel-ts/versions fuels->@fuel-ts/abi-coder fuels->@fuel-ts/abi-typegen fuels->@fuel-ts/account fuels->@fuel-ts/address fuels->@fuel-ts/contract fuels->@fuel-ts/crypto fuels->@fuel-ts/errors fuels->@fuel-ts/hasher fuels->@fuel-ts/math fuels->@fuel-ts/program fuels->@fuel-ts/recipes fuels->@fuel-ts/script fuels->@fuel-ts/transactions fuels->@fuel-ts/utils fuels->@fuel-ts/versions __more__ +4 more projects

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.

280 modules, with 391 dependencies between them. 3 loops run through 6 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 abi-coder.src.encoding.coders.AbstractCoder2 abi-coder.src.types.JsonAbi3 abi-coder.src.types.JsonAbiNew4 account.src.providers.transaction-request.types5 math.src.bn6 math.src.types7 utils.src.utils.arrayify8 abi-coder.src.FunctionFragment9 abi-coder.src.encoding.coders.VecCoder10 abi-typegen.src.types.interfaces.IType11 account.src.connectors.fuel-connector12 account.src.providers.transaction-response.transaction-response13 address.src.address14 utils.src.utils.types15 abi-coder.src.Interface16 abi-coder.src.encoding.coders.StructCoder17 abi-typegen.src.abi.types.AType18 account.src.providers.transaction-request19 account.src.providers.transaction-summary.assemble-transaction-summary20 address.src.types21 abi-typegen.src.abi.types.ArrayType22 abi-typegen.src.abi.types.U8Type23 account.src.providers.provider24 account.src.providers.transaction-request.transaction-request25 account.src.providers.transaction-summary26 program.src.types27 account.src.providers.transaction-request.script-transaction-request28 account.src.providers.transaction-request.upgrade-transaction-request29 account.src.providers.utils30 account.src.account31 program.src.functions.base-invocation-scope32 account.src.predicate.predicate33 account.src.utils34 account.src.wallet.base-wallet-unlocked35 contract.src.contract-factory36 program.src.functions.invocation-scope37 script.src.script38 account.src.wallet.wallets39 program.src.contract40 account.src.wallet-manager.types
1 abi-coder.src.encoding.coders.AbstractCoder
2 abi-coder.src.types.JsonAbi
3 abi-coder.src.types.JsonAbiNew
4 account.src.providers.transaction-request.types
5 math.src.bn
6 math.src.types
7 utils.src.utils.arrayify
8 abi-coder.src.FunctionFragment211
9 abi-coder.src.encoding.coders.VecCoder1
10 abi-typegen.src.types.interfaces.IType1
11 account.src.connectors.fuel-connector2
12 account.src.providers.transaction-response.transaction-response111
13 address.src.address1
14 utils.src.utils.types1
15 abi-coder.src.Interface11211
16 abi-coder.src.encoding.coders.StructCoder11
17 abi-typegen.src.abi.types.AType11
18 account.src.providers.transaction-request411
19 account.src.providers.transaction-summary.assemble-transaction-summary121
20 address.src.types2
21 abi-typegen.src.abi.types.ArrayType11
22 abi-typegen.src.abi.types.U8Type11
23 account.src.providers.provider21111
24 account.src.providers.transaction-request.transaction-request121122
25 account.src.providers.transaction-summary2212
26 program.src.types111
27 account.src.providers.transaction-request.script-transaction-request111221111
28 account.src.providers.transaction-request.upgrade-transaction-request1111
29 account.src.providers.utils2511
30 account.src.account2111111211
31 program.src.functions.base-invocation-scope11111
32 account.src.predicate.predicate121111
33 account.src.utils112
34 account.src.wallet.base-wallet-unlocked11111
35 contract.src.contract-factory11111
36 program.src.functions.invocation-scope111
37 script.src.script11111
38 account.src.wallet.wallets3211
39 program.src.contract11111121
40 account.src.wallet-manager.types11
Uses a module listed above itPart of a loopThe module itself
1 abi-coder.src.encoding.coders.AbstractCoder2 abi-coder.src.types.JsonAbi3 abi-coder.src.types.JsonAbiNew4 account.src.providers.transaction-request.types5 math.src.bn6 math.src.types7 utils.src.utils.arrayify8 abi-coder.src.FunctionFragment9 abi-coder.src.encoding.coders.VecCoder10 abi-typegen.src.types.interfaces.IType11 account.src.connectors.fuel-connector12 account.src.providers.transaction-response.transaction-response13 address.src.address14 utils.src.utils.types15 abi-coder.src.Interface16 abi-coder.src.encoding.coders.StructCoder17 abi-typegen.src.abi.types.AType18 account.src.providers.transaction-request19 account.src.providers.transaction-summary.assemble-transaction-summary20 address.src.types21 abi-typegen.src.abi.types.ArrayType22 abi-typegen.src.abi.types.U8Type23 account.src.providers.provider24 account.src.providers.transaction-request.transaction-request25 account.src.providers.transaction-summary26 program.src.types27 account.src.providers.transaction-request.script-transaction-request28 account.src.providers.transaction-request.upgrade-transaction-request29 account.src.providers.utils30 account.src.account31 program.src.functions.base-invocation-scope32 account.src.predicate.predicate33 account.src.utils34 account.src.wallet.base-wallet-unlocked35 contract.src.contract-factory36 program.src.functions.invocation-scope37 script.src.script38 account.src.wallet.wallets39 program.src.contract40 account.src.wallet-manager.typesabi-coder.src.encoding.coders.AbstractCoder1abi-coder.src.types.JsonAbi2abi-coder.src.types.JsonAbiNew3account.src.providers.transaction-request.types4math.src.bn5math.src.types6utils.src.utils.arrayify7abi-coder.src.FunctionFragment8abi-coder.src.encoding.coders.VecCoder9abi-typegen.src.types.interfaces.IType10account.src.connectors.fuel-connector11account.src.providers.transaction-response.transaction-response12address.src.address13utils.src.utils.types14abi-coder.src.Interface15abi-coder.src.encoding.coders.StructCoder16abi-typegen.src.abi.types.AType17account.src.providers.transaction-request18account.src.providers.transaction-summary.assemble-transaction-summary19address.src.types20abi-typegen.src.abi.types.ArrayType21abi-typegen.src.abi.types.U8Type22account.src.providers.provider23account.src.providers.transaction-request.transaction-request24account.src.providers.transaction-summary25program.src.types26account.src.providers.transaction-request.script-transaction-request27account.src.providers.transaction-request.upgrade-transaction-request28account.src.providers.utils29account.src.account30program.src.functions.base-invocation-scope31account.src.predicate.predicate32account.src.utils33account.src.wallet.base-wallet-unlocked34contract.src.contract-factory35program.src.functions.invocation-scope36script.src.script37account.src.wallet.wallets38program.src.contract39account.src.wallet-manager.types4021111211111112111111411121211112111112112222121111112211111111251121111112111111112111111211111111111111111132111111112111+240 more modules (most-connected shown)

At a glance — Code Health · 79% · Strong ·

The Good
D1 · TypeScript Cyclomatic Complexity 9.1 D2 · TypeScript Cognitive Complexity 8.4 D3 · TypeScript God Classes 9.3 D17 · TypeScript Explicit Debt 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 9.8 R10 · React / TS Code Duplication 8.8 R2 · React / TS Cyclomatic Complexity 9.7 R3 · React / TS Large Files 9.1 R7 · React / TS Dead Code 7.9 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.3 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 9.7
The Bad
X2 · Repo Cancellation propagation 6.4

At a glance — Architecture · 89% · Adequate · gated by D23 ·

The Good
D5 · TypeScript Coupling 7.9 D6 · TypeScript Cohesion (LCOM4) 9.6 D26 · TypeScript Project Cohesion 9.2 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 9.8 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 R11 · React / TS Import Boundaries 9.7 R9 · React / TS Circular Imports 8.3
The Ugly
D23 · TypeScript Boundary Type-Coupling 2.4

At a glance — Maturity · 62% · Adequate · gated by D34, M2 ·

The Good
D15 · TypeScript Churn × Complexity Hotspots 10.0 D16 · TypeScript Bus Factor 10.0 D19 · TypeScript Documentation Quality 10.0 M1 · Repo Documentation (README) 8.2 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Ugly
D20 · TypeScript ADR Quality 0.0 D34 · TypeScript Knowledge Freshness 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 52% · Adequate · gated by D13, R8, P7 ·

The Good
D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 8.6 D12 · TypeScript Dependency Hygiene 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 8.7 R6 · React / TS Tooling 10.0
The Bad
P2 · Repo Observability 4.3
The Ugly
D13 · TypeScript REDACTED Scanning 0.0 P7 · Repo Outbound HTTP resilience 3.0 R8 · React / TS Dependency Hygiene 3.5

At a glance — Security · 43% · Weak · gated by D28, D29, D30, D43 ·

The Good
D37 · TypeScript Vulnerability-disclosure Policy 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D36 · TypeScript Supply-chain Provenance & Signing 5.0 D44 · TypeScript Platform End-of-Life 6.0 S1 · Repo Web-Security Posture 6.0
The Ugly
D28 · TypeScript Secrets (history) 0.0 D29 · TypeScript Static Analysis (SAST) 0.1 D30 · TypeScript Dependency Vulnerabilities 0.0 D43 · TypeScript Malicious Dependencies 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 3.5

At a glance — Accessibility · 54% · Adequate ·

The Good
AC1 · Repo Text alternatives 10.0 AC3 · Repo Page structure 6.6
The Bad
AC7 · Repo A11y enforcement 6.0
The Ugly
AC2 · Repo Forms & labels 4.0 AC6 · Repo Visual & motion safety 4.0

At a glance — Performance · 60% · Adequate ·

The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures139High / Critical
A05:2025 — Injection82High / Critical
A07:2025 — Authentication Failures31High / Critical
A08:2025 — Software or Data Integrity Failures2Medium

Roadmap

First, strengthen the web-security posture by updating key derivation parameters across all three identified sites to meet current guidance and ensure appropriate computational cost. Next, immediately resolve the two malicious dependencies and the 28 historical secrets to eliminate critical exposure risks. Then, address the 76 high-severity dependency vulnerabilities and update the end-of-life platform runtime to ensure long-term stability and security.

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

Do thisHelpsEffortDimension
Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2).+5.1 ptsLowMalicious Dependencies
Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 3 sites, not one: `packages/account/src/mnemonic/mnemonic.ts:123` (PBKDF2-SHA-512, 2,048 iterations), `packages/crypto/src/browser/aes-ctr.ts:21` (PBKDF2-SHA-256, 100,000 iterations), `packages/crypto/src/node/aes-ctr.ts:22` (PBKDF2-SHA-256, 100,000 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.+5.5 ptsMediumWeb-Security Posture
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc.+2.6 ptsLowPlatform End-of-Life
Resolve the 28 REDACTED finding(s) in Secrets (history) — start with REDACTED (10), REDACTED (5), REDACTED (4).+5.1 ptsMediumSecrets (history)
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.+2.4 ptsLowREDACTED Scanning
Resolve the 76 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (71), REDACTED (5).+4.0 ptsMediumDependency Vulnerabilities
Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 44 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.+1.3 ptsLowStatic Analysis (SAST)
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.+1.3 ptsLowStatic Analysis (SAST)

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.4SlopSecrets (history): REDACTED: REDACTED
REDACTED2.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopSecrets (history): REDACTED: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.0MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.0MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
packages/account/src/account.ts4.2MixedCognitive Complexity: Account.fund (cognitive 16)
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.6MixedSecrets (history): REDACTED: REDACTED
REDACTED4.6MixedSecrets (history): REDACTED: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.8MixedSecrets (history): REDACTED: REDACTED
packages/account/src/providers/provider.ts4.8MixedGod Classes: FileTooLong: providers/provider.ts
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 233

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

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

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

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 80 of 80 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 80 dimensions across the health lenses
D1D2D3D5D6D9D10D12D13D14D15D16D17D19D20D23D26D28D29D30D34D35D36D37D43D44AC1AC2AC3AC6AC7AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6P7PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a178a7-8c72-7855-8be0-ced10bf4a7ee.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in apps/create-fuels-counter-guide/ was NOT MEASURED: the dependency install for apps/create-fuels-counter-guide/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in templates/nextjs/ was NOT MEASURED: the dependency install for templates/nextjs/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in templates/vite/ was NOT MEASURED: the dependency install for templates/vite/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/docs/scripts/launcher-snippet.ts`, `apps/docs/src/guide/provider/snippets/functionality/get-message-proof-block-height.ts`, `apps/docs/src/guide/provider/snippets/functionality/get-message-proof-block-id.ts`, `apps/docs/src/guide/scripts/snippets/deploying-scripts.ts`, `apps/docs/src/guide/scripts/snippets/script-custom-transaction.ts`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
  • R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 16 further occurrence(s) are not listed individually; the score already reflects all 56.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust 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: 90 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity9.1 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was serialization.deserializeReceipt at 27.

serialization.deserializeReceipt (cyclomatic 27)packages/account/src/providers/utils/serialization.ts:246
getCoderV1.getCoder (cyclomatic 25)packages/abi-coder/src/encoding/strategies/getCoderV1.ts:60
handle-gql-error-message.mapGqlErrorMessage (cyclomatic 22)REDACTED:23

What to do

  1. Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with serialization.deserializeReceipt (cyclomatic 27), getCoderV1.getCoder (cyclomatic 25), handle-gql-error-message.mapGqlErrorMessage (cyclomatic 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity8.4 / 10Strong✓ Tool-verified

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

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

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

11 method(s) exceeded the cognitive complexity threshold of 15; the worst was handle-gql-error-message.mapGqlErrorMessage at 31.

handle-gql-error-message.mapGqlErrorMessage (cognitive 31)REDACTED:23
toUtf8String.getUtf8CodePoints (cognitive 28)packages/utils/src/utils/toUtf8String.ts:75
getAllDecodedLogs.getAllDecodedLogs (cognitive 20)packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:34
ContractFactory.deployAsBlobTx (cognitive 20)packages/contract/src/contract-factory.ts:266
BN.format (cognitive 19)packages/math/src/bn.ts:115

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

What to do

  1. Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with handle-gql-error-message.mapGqlErrorMessage (cognitive 31), toUtf8String.getUtf8CodePoints (cognitive 28), getAllDecodedLogs.getAllDecodedLogs (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.3 / 10Stronggated by 9 serious findings✓ Tool-verified

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

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

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

9 god class(es) detected.

TooManyMethods: Provider · ×4packages/account/src/providers/provider.ts:464
FileTooLong: providers/provider.ts · ×2packages/account/src/providers/provider.ts
FunctionTooLong: serialization.deserializeReceipt · ×2packages/account/src/providers/utils/serialization.ts:246
ClassTooLong: Accountpackages/account/src/account.ts:145

What to do

  1. Resolve the 4 TooManyMethods finding(s) in God Classes — start with provider.ts, transaction-request.ts, bn.ts. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 2 FileTooLong finding(s) in God Classes — start with provider.ts, account.ts. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 FunctionTooLong finding(s) in God Classes — start with serialization.ts, cli.ts. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D5 · Coupling7.9 / 10Strong✓ Tool-verified

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

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

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

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

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

Off the main sequence: @fuel-ts/versions · ×5
Unstable project @fuel-ts/recipes

What to do

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

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

D6 · Cohesion (LCOM4)9.6 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

2 of 54 classes have LCOM4 above 3.

Low cohesion: MockConnector (LCOM4 6) · ×2packages/account/test/fixtures/mocked-connector.ts:34

What to do

  1. Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with mocked-connector.ts, fuel.ts. — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

2193 test methods: 2179 unit, 6 integration, 0 BDD, 8 e2e. The JavaScript/TypeScript suite contributes 2193 `it`/`test` case(s) across 334 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality8.6 / 10Strong✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

12 skipped (9 with a documented reason), 197 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2193 tests.

No assertions: should throw an error when value is less than the minimum · ×197packages/utils/src/test-utils/expectToBeInRange.test.ts:11
Skipped test: should call onDeploy callback · ×3packages/fuels/src/cli/commands/deploy/index.test.ts:33
Fixed-sleep synchronisation: should wait for both preconfirmation and confirmation statusespackages/account/src/providers/provider.test.ts:2849
Mock-dominated test: should inform about newer versions · ×19packages/versions/src/cli.test.ts:87
Skipped (documented): (unnamed test) · ×9templates/vite/test/ui/ui.test.ts:18

What to do

  1. Resolve the 197 No assertions finding(s) in Test Quality — start with abi-coder.test.ts (21), provider.test.ts (17), revert-error.test.ts (16). — One of this dimension's main actionable groups (197 warning-level).
  2. Resolve the 3 Skipped test finding(s) in Test Quality — start with index.test.ts, transaction-response.test.ts, abi-coder.test.ts. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with provider.test.ts. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

2 secret(s) detected.

REDACTED

What to do

  1. Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

0 of 17 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

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

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

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

No source file's living knowledge is concentrated in a single author. Counted over 122 of the 517 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

D17 · Explicit Debt9.9 / 10Stronggated by 12 serious findings✓ Tool-verified

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

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

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

12 deducted task-comment markers across 40398 LoC (0.0/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.

TodoComment · ×12packages/script/src/script-invocation-scope.ts:26

What to do

  1. Resolve the 12 TodoComment finding(s) in Explicit Debt — start with scripts.ts (3), script-invocation-scope.ts, bn.ts. — One of this dimension's main actionable groups (12 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D23 · Boundary Type-Coupling2.4 / 10Critical✓ Tool-verified

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

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

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

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

162 domain type(s) cross context boundaries across 30 contexts.

Cross-context type BytesLike (utils → account) · ×45packages/account/src/signer/signer.ts:24
Cross-context type Input (transactions → account) · ×14packages/account/src/providers/transaction-request/input.ts:91
Cross-context type BigNumberish (math → account) · ×14packages/account/src/providers/transaction-request/script-transaction-request.ts:32
Cross-context type AddressInput (address → account) · ×13packages/account/src/wallet/keystore-wallet.ts:59
Cross-context type TransactionType (transactions → account) · ×9packages/account/src/providers/transaction-summary/operations.ts:65

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

What to do

  1. Resolve the 45 Cross-context type BytesLike (utils → account) finding(s) in Boundary Type-Coupling — start with signer.ts (7), mnemonic.ts (5), account.ts (5). — One of this dimension's main actionable groups (45 warning-level).
  2. Resolve the 14 Cross-context type Input (transactions → account) finding(s) in Boundary Type-Coupling — start with input.ts (12), gas.ts (2). — One of this dimension's main actionable groups (14 warning-level).
  3. Resolve the 14 Cross-context type BigNumberish (math → account) finding(s) in Boundary Type-Coupling — start with transaction-request.ts (4), account.ts (4), script-transaction-request.ts (2). — One of this dimension's main actionable groups (14 warning-level).
  4. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D26 · Project Cohesion9.2 / 10Exemplary✓ Tool-verified

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

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

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

1 of 26 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

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

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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

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

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

28 finding(s): 0 critical, 28 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 28 REDACTED finding(s) in Secrets (history) — start with REDACTED (10), REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (28 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

83 finding(s): 0 critical, 72 high, 11 medium, 0 low. 45 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 94 file(s) — `.github/ISSUE_TEMPLATE/2-feature.yaml`, `apps/demo-bun-fuels/src/bun.test.ts` (line 19, line 48, line 68, …), `apps/demo-fuels/src/index.test.ts` (line 19, line 43, line 61, …), `apps/demo-typegen/src/demo.test.ts` (line 18, line 37, line 68, …), `apps/docs/scripts/launcher-snippet.ts` (line 3), … (+89 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

125 finding(s): 16 critical, 77 high, 26 medium, 6 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 76 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (71), REDACTED (5). — One of this dimension's main actionable groups (76 issue-level).
  2. Resolve the 16 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED (4). — One of this dimension's main actionable groups (16 issue-level).
  3. Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

122 of 122 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/account/src/providers/provider.ts. Counted over 122 of the 517 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×119packages/program/src/functions/base-invocation-scope.ts:1
Most significant orphaned file · ×3packages/account/src/providers/provider.ts:1
Dormant codebase

What to do

  1. Resolve the 119 Orphaned file finding(s) in Knowledge Freshness — start with types.ts (4), cli.ts (4), input.ts (3). — One of this dimension's main actionable groups (119 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with provider.ts, account.ts, transaction.ts. — One of this dimension's main actionable groups (3 recommendation-level).
  3. 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.

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED

What to do

  1. Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

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

D44 · Platform End-of-Life6.0 / 10Adequate✓ Tool-verified

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

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

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

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

End-of-life runtime: Node.js 20.nvmrc:1

What to do

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

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.

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

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

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

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

  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×28) — apps/create-fuels-counter-guide/src/components/Contract.tsx:80, apps/create-fuels-counter-guide/src/components/Faucet.tsx:42, apps/create-fuels-counter-guide/src/components/Faucet.tsx:56, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×6) — apps/create-fuels-counter-guide/src/components/Predicate.tsx:199, apps/create-fuels-counter-guide/src/components/Script.tsx:78, templates/nextjs/src/components/Predicate.tsx:184, …

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.
AC3 · Page structure6.6 / 10Strong✓ Tool-verified

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

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

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

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — apps/demo-wallet-sdk-react/src/app/layout.tsx:24
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. — apps/demo-wallet-sdk-react/src/app/layout.tsx:24
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — apps/demo-wallet-sdk-react/src/app/layout.tsx:24

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.
AC6 · Visual & motion safety4.0 / 10Weak✓ Tool-verified

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.

  • `input` 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. (×3) — templates/vite/src/index.css:78, templates/nextjs/src/styles/globals.css:78, apps/create-fuels-counter-guide/src/index.css:78
  • `.card span` moves (`transition: transform 200ms`) 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. — apps/demo-nextjs/src/app/page.module.css:59

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.
AC7 · A11y enforcement6.0 / 10Adequate✓ Tool-verified

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

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

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

  • An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 47 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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.

  • A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×2) — packages/abi-coder/src/utils/transpile-abi.ts:5, packages/abi-typegen/src/utils/transpile-abi.ts:5
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — packages/fuel-gauge/src/abi/abi-coder.test.ts:1012, packages/fuel-gauge/src/transaction-response.test.ts:203, packages/fuels/src/cli/commands/deploy/index.test.ts:33

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.
M1 · Documentation (README)8.2 / 10Exemplary✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 9 of 38 project(s) that lack one — worth up to 0.5 pts.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

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

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • `run-s type:check-tests lint:check prettier:check type:check` (the `lint` script this step runs) invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:48

What to do

  • Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability4.3 / 10Adequate✓ Tool-verified

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

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

  • Only 1/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/demo-wallet-sdk-react`, `apps/docs/fuel-asm-example`, `internal/forc`, `internal/fuel-core`, `packages/abi-typegen` and 3 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Dependabot is configured but does not watch `npm`, `cargo` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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. — packages/fuels/src/cli/utils/getLatestFuelsVersion.ts:14

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.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • `existsSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:194
  • `mkdirSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:195
  • `writeFileSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — REDACTED:204, REDACTED:205, REDACTED:213, …
  • `existsSync` in `removeTempDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:253
  • `rmSync` in `removeTempDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:254
  • `existsSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/create-fuels/src/cli.ts:72
  • `readFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — packages/create-fuels/src/cli.ts:117, packages/create-fuels/src/cli.ts:124, packages/create-fuels/src/cli.ts:148, …
  • `writeFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — packages/create-fuels/src/cli.ts:119, packages/create-fuels/src/cli.ts:144, packages/create-fuels/src/cli.ts:152, …
  • `execSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/create-fuels/src/cli.ts:168, packages/create-fuels/src/cli.ts:172
  • `existsSync` in `deployContract` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/fuels/src/cli/commands/deploy/deployContracts.ts:39
  • `readFileSync` in `deployContract` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/fuels/src/cli/commands/deploy/deployContracts.ts:40, packages/fuels/src/cli/commands/deploy/deployContracts.ts:45, packages/fuels/src/cli/commands/deploy/deployContracts.ts:46
  • `readFileSync` in `deployPredicates` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/fuels/src/cli/commands/deploy/deployPredicates.ts:27, packages/fuels/src/cli/commands/deploy/deployPredicates.ts:28
  • `readFileSync` in `deployScripts` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/fuels/src/cli/commands/deploy/deployScripts.ts:28, packages/fuels/src/cli/commands/deploy/deployScripts.ts:29
  • `globSync` in `callback to flatMap` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/fuels/src/cli/commands/dev/index.ts:71, packages/fuels/src/cli/commands/dev/index.ts:72
  • `globSync` in `expandGlob` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/fuels/test/utils/runCommands.ts:143
  • `readFileSync` in `runInit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/fuels/test/utils/runCommands.ts:165
  • `writeFileSync` in `runInit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/fuels/test/utils/runCommands.ts:172

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety9.8 / 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.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • apps/create-fuels-counter-guide/ and templates/vite/ are near-verbatim copies of each other: 23 files are byte-identical under the same relative paths (~466 lines; the trees hold 43 and 49 files). That is one structural fact, not 23 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — apps/create-fuels-counter-guide/src/components/Wallet.tsx:1
  • 9 duplicated blocks under packages/ have copies in at least two of the sibling directories abi-coder, abi-typegen, account, contract, create-fuels, fuels (+2 more sibling(s) not listed) — 7 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — packages/abi-coder/src/types/JsonAbiNew.ts:5
  • packages/transactions/src/coders/input.ts:183 · packages/transactions/src/coders/output.ts:92 — the two spans are one implementation copied and then locally edited — 663 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. — packages/transactions/src/coders/input.ts:183
  • packages/abi-coder/src/types/JsonAbiNew.ts:5 · packages/abi-typegen/src/types/interfaces/JsonAbiNew.ts:5 — these 2 files are line-for-line copies of one another — 73 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/abi-coder/src/types/JsonAbiNew.ts:5
  • packages/abi-coder/src/utils/transpile-abi.ts:7 · packages/abi-typegen/src/utils/transpile-abi.ts:7 — these 2 files are line-for-line copies of one another — 71 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/abi-coder/src/utils/transpile-abi.ts:7
  • packages/merkle/src/binary/binaryMerkleTree.ts:30 · packages/merkle/src/sum/sumMerkleTree.ts:43 — the two spans are one implementation copied and then locally edited — 497 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. — packages/merkle/src/binary/binaryMerkleTree.ts:30
  • packages/abi-typegen/src/abi/types/EnumType.ts:23 · packages/abi-typegen/src/abi/types/StructType.ts:20 — the two spans are one implementation copied and then locally edited — 320 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. — packages/abi-typegen/src/abi/types/EnumType.ts:23
  • packages/abi-coder/src/types/JsonAbi.ts:10 · packages/abi-typegen/src/types/interfaces/JsonAbi.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/abi-coder/src/types/JsonAbi.ts:10
  • internal/forc/lib/install.js:20 · internal/fuel-core/lib/install.js:19 — the two spans are one implementation copied and then locally edited — 231 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. — internal/forc/lib/install.js:20
  • packages/crypto/src/browser/aes-ctr.ts:11 · packages/crypto/src/node/aes-ctr.ts:12 — the two spans are one implementation copied and then locally edited — 247 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. — packages/crypto/src/browser/aes-ctr.ts:11
  • packages/account/src/account.ts:780 · packages/account/src/account.ts:854 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/account/src/account.ts:780
  • packages/abi-typegen/src/utils/assemblePredicates.ts:15 · packages/abi-typegen/src/utils/assembleScripts.ts:15 — 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. — packages/abi-typegen/src/utils/assemblePredicates.ts:15
  • REDACTED:35 · internal/fuel-core/lib/shared.js:29 — the two spans are one implementation copied and then locally edited — 213 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. — REDACTED:35
  • packages/abi-coder/src/encoding/coders/B256Coder.ts:9 · packages/abi-coder/src/encoding/coders/B512Coder.ts:9 — 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. — packages/abi-coder/src/encoding/coders/B256Coder.ts:9
  • packages/abi-typegen/src/abi/types/ArrayType.ts:25 · packages/abi-typegen/src/abi/types/TupleType.ts:21 — 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. — packages/abi-typegen/src/abi/types/ArrayType.ts:25
  • packages/fuels/src/cli/commands/dev/index.ts:24 · packages/fuels/src/cli/commands/node/index.ts:13 — the two spans are one implementation copied and then locally edited — 175 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. — packages/fuels/src/cli/commands/dev/index.ts:24
  • packages/abi-coder/src/encoding/coders/StdStringCoder.ts:10 · packages/abi-coder/src/encoding/coders/StrSliceCoder.ts:10 — 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. — packages/abi-coder/src/encoding/coders/StdStringCoder.ts:10
  • packages/account/src/providers/utils/serialization.ts:534 · packages/account/src/providers/utils/serialization.ts:597 — 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. — packages/account/src/providers/utils/serialization.ts:534
  • packages/create-fuels/src/utils/logger.ts:3 · packages/fuels/src/cli/utils/logger.ts:3 — 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. — packages/create-fuels/src/utils/logger.ts:3
  • packages/transactions/src/coders/output.ts:27 · packages/transactions/src/coders/output.ts:123 · packages/transactions/src/coders/output.ts:171 — all 3 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. — packages/transactions/src/coders/output.ts:27
  • packages/abi-typegen/src/templates/predicate/main.ts:43 · packages/abi-typegen/src/templates/script/main.ts:37 — 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. — packages/abi-typegen/src/templates/predicate/main.ts:43
  • packages/abi-coder/src/encoding/coders/EnumCoder.ts:13 · packages/abi-coder/src/encoding/coders/StructCoder.ts:10 — the two spans are one implementation copied and then locally edited — 138 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. — packages/abi-coder/src/encoding/coders/EnumCoder.ts:13
  • packages/transactions/src/coders/input.ts:376 · packages/transactions/src/coders/output.ts:289 · packages/transactions/src/coders/transaction.ts:649 · packages/transactions/src/coders/upgrade-purpose.ts:56 — 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. — packages/transactions/src/coders/input.ts:376
  • packages/abi-typegen/src/templates/predicate/main.ts:13 · packages/abi-typegen/src/templates/script/main.ts:13 — 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. — packages/abi-typegen/src/templates/predicate/main.ts:13
  • packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:53 · packages/account/src/providers/transaction-response/getDecodedLogs.ts:45 — 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. — packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:53
  • packages/abi-typegen/src/utils/assembleContracts.ts:42 · packages/abi-typegen/src/utils/assemblePredicates.ts:33 · packages/abi-typegen/src/utils/assembleScripts.ts:33 — 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. — packages/abi-typegen/src/utils/assembleContracts.ts:42
  • REDACTED:34 · REDACTED:54 — 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. — REDACTED:34
  • packages/account/src/account.ts:625 · packages/account/src/account.ts:677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/account/src/account.ts:625
  • packages/account/src/predicate/predicate.ts:295 · packages/script/src/script.ts:100 — the two spans are one implementation copied and then locally edited — 91 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. — packages/account/src/predicate/predicate.ts:295
  • packages/account/src/providers/transaction-request/script-transaction-request.ts:207 · packages/account/src/providers/transaction-request/transaction-request.ts:607 — 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. — packages/account/src/providers/transaction-request/script-transaction-request.ts:207
  • packages/account/src/providers/transaction-request/transaction-request.ts:408 · packages/account/src/providers/transaction-request/transaction-request.ts:449 — 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. — packages/account/src/providers/transaction-request/transaction-request.ts:408
  • packages/merkle/src/sum/sumMerkleTree.ts:50 · packages/merkle/src/sum/sumMerkleTree.ts:96 — 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. — packages/merkle/src/sum/sumMerkleTree.ts:50
  • packages/abi-coder/src/encoding/coders/ByteCoder.ts:16 · packages/abi-coder/src/encoding/coders/StdStringCoder.ts:17 · packages/abi-coder/src/encoding/coders/StrSliceCoder.ts:17 — 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. — packages/abi-coder/src/encoding/coders/ByteCoder.ts:16
  • packages/account/src/providers/utils/serialization.ts:422 · packages/account/src/providers/utils/serialization.ts:440 — 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. — packages/account/src/providers/utils/serialization.ts:422
  • packages/crypto/src/browser/encryptJsonWalletData.ts:13 · packages/crypto/src/browser/encryptJsonWalletData.ts:40 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/crypto/src/browser/encryptJsonWalletData.ts:13
  • packages/transactions/src/coders/input.ts:109 · packages/transactions/src/coders/input.ts:326 — 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. — packages/transactions/src/coders/input.ts:109
  • packages/transactions/src/coders/policy.ts:124 · packages/transactions/src/coders/policy.ts:145 — 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. — packages/transactions/src/coders/policy.ts:124
  • packages/abi-coder/src/encoding/coders/NumberCoder.ts:53 · packages/abi-coder/src/encoding/coders/StringCoder.ts:16 — 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. — packages/abi-coder/src/encoding/coders/NumberCoder.ts:53
  • packages/account/src/account.ts:460 · packages/account/src/account.ts:515 — 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. — packages/account/src/account.ts:460
  • packages/account/src/connectors/fuel-connector.ts:133 · packages/account/src/connectors/fuel-connector.ts:293 — all 2 copies are in the same file, 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. — packages/account/src/connectors/fuel-connector.ts:133

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.
R11 · Import Boundaries9.7 / 10Exemplary✓ Tool-verified

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.

  • packages/account/scripts/generate-fuel-core-schema.ts:4 imports packages/account/src/test-utils/setup-test-provider-and-wallets.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/account/scripts/generate-fuel-core-schema.ts:4
  • packages/fuel-gauge/src/utils.ts:6 imports packages/fuel-gauge/test/fixtures/chain-config/state_transition_bytecode.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/fuel-gauge/src/utils.ts:6

What to do

  • Fix the listed violations: move the shared test helper into a source directory production code may depend on (2 rows).
R2 · Cyclomatic Complexity9.7 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • (anonymous) has cyclomatic complexity 27 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. — packages/account/src/providers/utils/serialization.ts:246
  • (anonymous) has cyclomatic complexity 25 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. — packages/abi-coder/src/encoding/strategies/getCoderV1.ts:63
  • (anonymous) has cyclomatic complexity 22 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:23
  • (anonymous) has cyclomatic complexity 17 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. — REDACTED:150
  • getUtf8CodePoints has cyclomatic complexity 15 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/utils/src/utils/toUtf8String.ts:75
  • runScaffoldCli has cyclomatic complexity 15 and cognitive complexity 19; 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. — packages/create-fuels/src/cli.ts:41
  • waitForStatusChange has cyclomatic complexity 14 and cognitive complexity 19; 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. — packages/account/src/providers/transaction-response/transaction-response.ts:440
  • format has cyclomatic complexity 14 and cognitive complexity 19; 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. — packages/math/src/bn.ts:115
  • (anonymous) has cyclomatic complexity 13 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. — packages/account/src/providers/utils/validate-pagination-args.ts:11
  • deleteWithSideNodes has cyclomatic complexity 12 and cognitive complexity 19; 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. — packages/merkle/src/sparse/sparseMerkleTree.ts:90
  • constructor 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. — packages/account/src/providers/transaction-request/transaction-request.ts:152
  • fromExtendedKey has cyclomatic complexity 11 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 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. — packages/account/src/hdwallet/hdwallet.ts:223
  • buildBlockExplorerUrl 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. — packages/account/src/providers/utils/block-explorer.ts:26
  • validate 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. — packages/account/src/test-utils/wallet-config.ts:141
  • extractInvocationResult 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. — packages/program/src/response.ts:65

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files9.1 / 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.

  • packages/account/src/providers/provider.ts has 2408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/providers/provider.ts:1
  • packages/account/src/account.ts has 1125 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/account.ts:1
  • packages/account/src/providers/transaction-request/transaction-request.ts has 685 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/providers/transaction-request/transaction-request.ts:1
  • packages/transactions/src/coders/transaction.ts has 608 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/transactions/src/coders/transaction.ts:1
  • packages/program/src/functions/base-invocation-scope.ts has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/program/src/functions/base-invocation-scope.ts:1
  • packages/account/src/providers/transaction-response/transaction-response.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/providers/transaction-response/transaction-response.ts:1
  • packages/account/src/providers/transaction-summary/operations.ts has 558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/providers/transaction-summary/operations.ts:1
  • packages/account/src/providers/utils/serialization.ts has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/providers/utils/serialization.ts:1
  • packages/account/src/connectors/fuel.ts has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/account/src/connectors/fuel.ts:1
  • packages/contract/src/contract-factory.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/contract/src/contract-factory.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage8.7 / 10Exemplary✓ 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) — scripts/changeset/get-full-changelog.mts:1, packages/fuel-gauge/scripts/latency-detection/helpers.ts:1, internal/check-imports/src/references.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code7.9 / 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.

  • 1 file(s) (~67 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — apps/create-fuels-counter-guide
  • 2 file(s) (~135 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — apps/demo-bun-fuels
  • 4 file(s) (~279 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: apps/demo-fuels/src/index.test.ts imports './sway-programs-api', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — apps/demo-fuels
  • Unreachable from the 93 application, 55 tooling and 395 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (93 application, 55 tooling, 395 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/merkle/src/sparse/types/sparseCompactMerkleSolidityProof.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/merkle/src/sparse/types/sparseMerkleSolidityNode.ts
  • no import path from any entry point (93 application, 55 tooling, 395 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 (×6) — packages/fuel-gauge/src/predicate/utils/predicate/fundPredicate.ts, packages/fuels/scripts/build-proxy-contract.ts, packages/merkle/src/sparse/types/sparseCompactMerkleBranch.ts, …
  • no import path from any entry point (93 application, 55 tooling, 395 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/merkle/src/sparse/types/sparseCompactMerkleBranch.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/merkle/src/sparse/types/sparseCompactMerkleSolidityProof.ts
  • Nothing imports this binding — it is safe to review for removal. (×27) — internal/check-imports/src/references.ts:77, internal/check-imports/src/references.ts:78, internal/check-imports/src/references.ts:79, …
  • Nothing ultimately consumes this binding: its only referrer is the re-export in packages/contract/src/loader/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/contract/src/loader/index.ts in the same commit, or the barrel will import a name that no longer exists. — packages/contract/src/loader/types.ts:3

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene3.5 / 10Weak✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — packages/fuel-gauge/scripts/latency-detection/main.ts:1
  • Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in apps/demo-typegen/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Every import is type-only — move it to devDependencies. — packages/abi-coder/src/encoding/coders/EnumCoder.ts:4

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports8.3 / 10Strong✓ 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.

  • packages/account/src/account.ts → packages/account/src/utils/consolidate-coins.ts → packages/account/src/account.ts — packages/account/src/account.ts:58

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

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. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, 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.

  • This code fixes PBKDF2-SHA-512 at 2,048 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. — packages/account/src/mnemonic/mnemonic.ts:123
  • This code fixes PBKDF2-SHA-256 at 100,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. (×2) — packages/crypto/src/browser/aes-ctr.ts:21, packages/crypto/src/node/aes-ctr.ts:22
  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — templates/vite/vercel.json:1
  • `server.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.) — packages/fuels/src/setup-launch-node-server.ts:100

What to do

  • Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 3 sites, not one: `packages/account/src/mnemonic/mnemonic.ts:123` (PBKDF2-SHA-512, 2,048 iterations), `packages/crypto/src/browser/aes-ctr.ts:21` (PBKDF2-SHA-256, 100,000 iterations), `packages/crypto/src/node/aes-ctr.ts:22` (PBKDF2-SHA-256, 100,000 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
  • 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`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • `normalizeJSON` is exported, takes a document from its caller (line 41) and hands it to `normalize`, which calls itself at line 18 (`normalize`) with a piece of `object` (and at line 27) — and nowhere in `normalize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `normalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/account/src/providers/utils/json.ts:18

What to do

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

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

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

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

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

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

X2 · Cancellation propagation6.4 / 10Adequate✓ Tool-verified

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 2/5 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `teardown` 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 })`. — vitest.global-browser-setup.ts:10
  • `getVersionsToDeprecate` 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 })`. — scripts/release-deprecate.ts:32
  • `getLatestFuelsVersion` 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 })`. — packages/fuels/src/cli/utils/getLatestFuelsVersion.ts:3

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

X3 · Exception handling7.3 / 10Strong✓ Tool-verified

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. — packages/account/src/providers/provider.ts:2560

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

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

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.

  • 55/56 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~0.4 `!` null assertions per 1k TypeScript source lines — 17 assertion(s) across the 46138 source line(s) of the 680 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: packages/program/src/contract.ts (4), apps/docs/src/guide/utilities/snippets/using-assets.ts (2), packages/contract/src/contract-factory.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

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

Reference — by lens

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

LensScoreRatingImpact
Code Health79%StrongStrongest area.
Architecture89%Adequate — gated by D23Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity62%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness52%Adequate — gated by D13, R8, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security43%Weak — gated by D28, D29, D30, D43Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility54%AdequateAcceptable, with room to improve.
Performance60%AdequateAcceptable, with room to improve.
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.

  • P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 48 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; 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: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — 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.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, 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 measured — JavaScript/TypeScript suite did not run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust, TypeScript not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .mts, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (REDACTED, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.mts, .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.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 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)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • 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
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 233 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×76
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 51 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 22 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×33
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Contract.tsx:80 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Faucet.tsx:42 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Faucet.tsx:56 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Predicate.tsx:156 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Predicate.tsx:173 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Predicate.tsx:193 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Predicate.tsx:199 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Script.tsx:78 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Script.tsx:92 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Wallet.tsx:34 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label apps/create-fuels-counter-guide/src/components/Wallet.tsx:50 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Contract.tsx:64 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Faucet.tsx:45 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Faucet.tsx:59 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Predicate.tsx:133 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Predicate.tsx:150 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Predicate.tsx:174 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Predicate.tsx:184 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label templates/nextjs/src/components/Script.tsx:82 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label templates/nextjs/src/components/Script.tsx:95 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Wallet.tsx:33 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/nextjs/src/components/Wallet.tsx:49 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/vite/src/components/Contract.tsx:64 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/vite/src/components/Faucet.tsx:45 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label templates/vite/src/components/Faucet.tsx:59 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • + 8 more in this group — see findings.md.
D28 · Secrets (history) · REDACTED · ×28
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 3 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×1
  • <select> without a programmatic label apps/demo-wallet-sdk-react/src/app/page.tsx:36 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang apps/demo-wallet-sdk-react/src/app/layout.tsx:24 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> apps/demo-wallet-sdk-react/src/app/layout.tsx:24 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'dotenv' · ×1
  • Unlisted import 'dotenv' packages/fuel-gauge/scripts/latency-detection/main.ts:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (2 files) · ×1
  • Import cycle (2 files) packages/account/src/account.ts:58 — packages/account/src/account.ts → packages/account/src/utils/consolidate-coins.ts → packages/account/src/account.ts
Serious — 624 finding(s)
D10 · Test Quality · No assertions · ×197
  • No assertions: should throw an error when value is less than the minimum packages/utils/src/test-utils/expectToBeInRange.test.ts:11 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throw an error when value is greater than the maximum packages/utils/src/test-utils/expectToBeInRange.test.ts:26 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return true when value is equal to the minimum packages/utils/src/test-utils/expectToBeInRange.test.ts:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return true when value is equal to the maximum packages/utils/src/test-utils/expectToBeInRange.test.ts:49 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should return true when value is within the range packages/utils/src/test-utils/expectToBeInRange.test.ts:57 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: will throw encoding a coin with larger than max predicate length packages/transactions/src/coders/input.test.ts:77 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throw an error when a duplicated policy is found packages/transactions/src/coders/policy.test.ts:203 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: throws if invalid length of gql scalar packages/transactions/src/coders/tx-pointer.test.ts:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throw if script has no configurable to be set packages/script/src/script.test.ts:117 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throw when setting configurable with wrong name packages/script/src/script.test.ts:135 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throws expected error when using unsafe numbers packages/math/src/bn.test.ts:560 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: the /close-server endpoint closes the server packages/fuels/src/setup-launch-node-server.test.ts:80 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: returns a valid fuel-core node url on request packages/fuels/src/setup-launch-node-server.test.ts:87 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: the /cleanup endpoint kills the node packages/fuels/src/setup-launch-node-server.test.ts:96 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: kills all nodes when the server is shut down packages/fuels/src/setup-launch-node-server.test.ts:106 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: launchTestNode launches and kills node packages/fuels/src/setup-launch-node-server.test.ts:118 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: throws error when failed to connect to node packages/fuels/src/cli/commands/deploy/createWallet.test.ts:46 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should not display undecoded logs in the error message packages/fuel-gauge/src/advanced-logging.test.ts:538 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should validate OutputChange collision packages/fuel-gauge/src/assemble-tx.test.ts:261 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should validate OutputChange collision, multiple changeOutputAccount for same assetId packages/fuel-gauge/src/assemble-tx.test.ts:289 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throws if calls createTransactionRequest is called when provider is not set packages/fuel-gauge/src/contract-factory.test.ts:242 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should not deploy large contracts via create packages/fuel-gauge/src/contract-factory.test.ts:257 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should not deploy large contracts via blobs [invalid chunk size multiplier] packages/fuel-gauge/src/contract-factory.test.ts:354 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should not deploy large contract with invalid balance packages/fuel-gauge/src/contract-factory.test.ts:464 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should throw when trying to transfer a zero or negative amount to a contract packages/fuel-gauge/src/contract.test.ts:1074 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 172 more in this group — see findings.md.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → account) · ×45
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:24 — BytesLike (context utils) is exposed in account's public surface via Signer.constructor — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:54 — BytesLike (context utils) is exposed in account's public surface via Signer.sign — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:72 — BytesLike (context utils) is exposed in account's public surface via Signer.addPoint — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:86 — BytesLike (context utils) is exposed in account's public surface via Signer.recoverPublicKey — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:110 — BytesLike (context utils) is exposed in account's public surface via Signer.recoverAddress — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:120 — BytesLike (context utils) is exposed in account's public surface via Signer.generatePrivateKey — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/signer/signer.ts:130 — BytesLike (context utils) is exposed in account's public surface via Signer.extendPublicKey — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/wallet/base-wallet-unlocked.ts:41 — BytesLike (context utils) is exposed in account's public surface via BaseWalletUnlocked.constructor — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/utils.ts:66 — BytesLike (context utils) is exposed in account's public surface via utils.mnemonicWordsToEntropy — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts:78 — BytesLike (context utils) is exposed in account's public surface via Mnemonic.entropyToMnemonic — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts:101 — BytesLike (context utils) is exposed in account's public surface via Mnemonic.entropyToMnemonic — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts:117 — BytesLike (context utils) is exposed in account's public surface via Mnemonic.mnemonicToSeed — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts:131 — BytesLike (context utils) is exposed in account's public surface via Mnemonic.mnemonicToMasterKeys — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/mnemonic/mnemonic.ts:243 — BytesLike (context utils) is exposed in account's public surface via Mnemonic.generate — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/hdwallet/hdwallet.ts:73 — BytesLike (context utils) is exposed in account's public surface via HDWallet.chainCode — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallets.ts:19 — BytesLike (context utils) is exposed in account's public surface via GenerateOptions.entropy — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallets.ts:33 — BytesLike (context utils) is exposed in account's public surface via WalletLocked.unlock — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallets.ts:89 — BytesLike (context utils) is exposed in account's public surface via WalletUnlocked.fromMnemonic — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/wallet/wallet.ts:30 — BytesLike (context utils) is exposed in account's public surface via Wallet.fromPrivateKey — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/create-transaction-request.ts:26 — BytesLike (context utils) is exposed in account's public surface via CreateTransactionRequestLike.salt — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/create-transaction-request.ts:108 — BytesLike (context utils) is exposed in account's public surface via CreateTransactionRequest.addContractCreatedOutput — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:34 — BytesLike (context utils) is exposed in account's public surface via ScriptTransactionRequestLike.script — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:36 — BytesLike (context utils) is exposed in account's public surface via ScriptTransactionRequestLike.scriptData — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:191 — BytesLike (context utils) is exposed in account's public surface via ScriptTransactionRequest.addVariableOutput — couples the contexts.
  • Cross-context type BytesLike (utils → account) packages/account/src/providers/transaction-request/upgrade-transaction-request.ts:84 — BytesLike (context utils) is exposed in account's public surface via UpgradeTransactionRequest.addConsensusParametersUpgradePurpose — couples the contexts.
  • + 20 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file scripts/changeset/get-full-changelog.mts: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 packages/fuel-gauge/scripts/latency-detection/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.
  • No test reaches this file internal/check-imports/src/references.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 scripts/changeset/update-changelog.mts: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 scripts/release-deprecate.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 packages/fuel-gauge/scripts/latency-detection/predicate-signature-validation.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 REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file internal/fuel-core/lib/shared.js: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 internal/fuel-core/lib/install.js: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 packages/recipes/scripts/build-recipes.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 internal/forc/lib/install.js: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 apps/demo-wallet-sdk-react/src/app/page.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 scripts/changeset/changeset-version-with-docs.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 internal/tsup/src/index.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 scripts/changeset/changeset-next.mts: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 packages/fuel-gauge/scripts/latency-detection/missing-4x-variable-output-call.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 scripts/lint-package-jsons.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 scripts/lint-md-links.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 scripts/postbuild.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 internal/check-imports/src/imports.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 packages/fuel-gauge/scripts/latency-detection/types.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/merkle/src/sparse/types/sparseMerkleSolidityNode.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 scripts/tests-coverage-merge.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 apps/demo-wallet-sdk-react/src/app/layout.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 packages/fuel-gauge/src/predicate/utils/predicate/fundPredicate.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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×32
  • Sync-over-async blocking REDACTED:194 — `existsSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:195 — `mkdirSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:204 — `writeFileSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:205 — `writeFileSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:213 — `writeFileSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:214 — `writeFileSync` in `callback to Promise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:253 — `existsSync` in `removeTempDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:254 — `rmSync` in `removeTempDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:72 — `existsSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:117 — `readFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:119 — `writeFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:124 — `readFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:144 — `writeFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:148 — `readFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:152 — `writeFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:158 — `readFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:160 — `writeFileSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:168 — `execSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-fuels/src/cli.ts:172 — `execSync` in `runScaffoldCli` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployContracts.ts:39 — `existsSync` in `deployContract` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployContracts.ts:40 — `readFileSync` in `deployContract` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployContracts.ts:45 — `readFileSync` in `deployContract` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployContracts.ts:46 — `readFileSync` in `deployContract` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployPredicates.ts:27 — `readFileSync` in `deployPredicates` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/fuels/src/cli/commands/deploy/deployPredicates.ts:28 — `readFileSync` in `deployPredicates` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 7 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×25
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D23 · Boundary Type-Coupling · Cross-context type Input (transactions → account) · ×14
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-request/input.ts:91 — Input (context transactions) is exposed in account's public surface via input.inputify — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/utils/gas.ts:81 — Input (context transactions) is exposed in account's public surface via IGetMinGasParams.inputs — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/utils/gas.ts:40 — Input (context transactions) is exposed in account's public surface via gas.gasUsedByInputs — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:7 — Input (context transactions) is exposed in account's public surface via input.getInputsByTypes — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:12 — Input (context transactions) is exposed in account's public surface via input.getInputsByType — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:17 — Input (context transactions) is exposed in account's public surface via input.getInputsCoin — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:22 — Input (context transactions) is exposed in account's public surface via input.getInputsMessage — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:27 — Input (context transactions) is exposed in account's public surface via input.getInputsCoinAndMessage — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:32 — Input (context transactions) is exposed in account's public surface via input.isInputCoin — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:37 — Input (context transactions) is exposed in account's public surface via input.getInputsContract — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:48 — Input (context transactions) is exposed in account's public surface via input.aggregateInputsAmountsByAssetAndOwner — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:84 — Input (context transactions) is exposed in account's public surface via input.getInputFromAssetId — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:103 — Input (context transactions) is exposed in account's public surface via input.getInputContractFromIndex — couples the contexts.
  • Cross-context type Input (transactions → account) packages/account/src/providers/transaction-summary/input.ts:127 — Input (context transactions) is exposed in account's public surface via input.getInputAccountAddress — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BigNumberish (math → account) · ×14
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:32 — BigNumberish (context math) is exposed in account's public surface via ScriptTransactionRequestLike.gasLimit — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:191 — BigNumberish (context math) is exposed in account's public surface via ScriptTransactionRequest.addVariableOutput — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts:76 — BigNumberish (context math) is exposed in account's public surface via BaseTransactionRequestLike.tip — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts:84 — BigNumberish (context math) is exposed in account's public surface via BaseTransactionRequestLike.maxFee — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts:86 — BigNumberish (context math) is exposed in account's public surface via BaseTransactionRequestLike.witnessLimit — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/transaction-request/transaction-request.ts:523 — BigNumberish (context math) is exposed in account's public surface via BaseTransactionRequest.addCoinOutput — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/account.ts:447 — BigNumberish (context math) is exposed in account's public surface via Account.createTransfer — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/account.ts:488 — BigNumberish (context math) is exposed in account's public surface via Account.transfer — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/account.ts:574 — BigNumberish (context math) is exposed in account's public surface via Account.transferToContract — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/account.ts:653 — BigNumberish (context math) is exposed in account's public surface via Account.withdrawToBaseLayer — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/assemble-tx-helpers.ts:56 — BigNumberish (context math) is exposed in account's public surface via assemble-tx-helpers.setAndValidateGasAndFeeForAssembledTx — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/provider.ts:2011 — BigNumberish (context math) is exposed in account's public surface via Provider.getBlock — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/providers/provider.ts:2094 — BigNumberish (context math) is exposed in account's public surface via Provider.getBlockWithTransactions — couples the contexts.
  • Cross-context type BigNumberish (math → account) packages/account/src/test-utils/wallet-config.ts:33 — BigNumberish (context math) is exposed in account's public surface via WalletsConfigOptions.amountPerCoin — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type AddressInput (address → account) · ×13
  • Cross-context type AddressInput (address → account) packages/account/src/wallet/keystore-wallet.ts:59 — AddressInput (context address) is exposed in account's public surface via keystore-wallet.encryptKeystoreWallet — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/vaults/mnemonic-vault.ts:73 — AddressInput (context address) is exposed in account's public surface via MnemonicVault.exportAccount — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/vaults/mnemonic-vault.ts:91 — AddressInput (context address) is exposed in account's public surface via MnemonicVault.getWallet — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/vaults/privatekey-vault.ts:57 — AddressInput (context address) is exposed in account's public surface via PrivateKeyVault.exportAccount — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/wallet-manager.ts:115 — AddressInput (context address) is exposed in account's public surface via WalletManager.getWallet — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/wallet-manager/wallet-manager.ts:128 — AddressInput (context address) is exposed in account's public surface via WalletManager.exportPrivateKey — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/providers/transaction-request/transaction-request.ts:306 — AddressInput (context address) is exposed in account's public surface via BaseTransactionRequest.updateWitnessByOwner — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/account.ts:168 — AddressInput (context address) is exposed in account's public surface via Account.constructor — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/account.ts:653 — AddressInput (context address) is exposed in account's public surface via Account.withdrawToBaseLayer — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/providers/provider.ts:1890 — AddressInput (context address) is exposed in account's public surface via Provider.getCoins — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/providers/provider.ts:1929 — AddressInput (context address) is exposed in account's public surface via Provider.getResourcesToSpend — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/providers/provider.ts:2259 — AddressInput (context address) is exposed in account's public surface via Provider.getBalance — couples the contexts.
  • Cross-context type AddressInput (address → account) packages/account/src/providers/provider.ts:2322 — AddressInput (context address) is exposed in account's public surface via Provider.getMessages — couples the contexts.
D17 · Explicit Debt · TodoComment · ×12
  • TodoComment packages/script/src/script-invocation-scope.ts:26 — // TODO: Remove this error since it is already handled on Provider class — 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 packages/script/src/scripts.ts:18 — // TODO: Don't use hardcoded scripts: https://github.com/FuelLabs/fuels-ts/issues/281
  • TodoComment packages/account/src/providers/transaction-request/scripts.ts:13 — // TODO: Don't use hardcoded scripts: https://github.com/FuelLabs/fuels-ts/issues/281
  • TodoComment packages/account/src/providers/transaction-request/scripts.ts:29 — // TODO: Don't use hardcoded scripts: https://github.com/FuelLabs/fuels-ts/issues/281
  • TodoComment packages/math/src/bn.ts:128 — // TODO: This really should throw an error because you can't have a precision less than the minPrecision but this would be a breaking change — 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 packages/fuels/src/cli/templates/index.ts:4 — // TODO: once abi-typegen implements a way to generate all types of sway — 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 packages/fuels/src/cli/commands/deploy/index.test.ts:32 — // TODO: Fix this test — 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 packages/create-fuels/src/cli.ts:130 — // TODO: remove once upgraded to `graphql-request@v7` — 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 packages/account/test/fuel-wallet-connector.test.ts:915 — // TODO: re-enable this test after rollout of fuel-core 0.44.1 — 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 packages/account/src/consolidate-coins.test.ts:759 — // TODO: re-enable this test after rollout of fuel-core 0.44.1 — 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 packages/account/src/hdwallet/hdwallet.ts:81 — // TODO: set some asserts here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment internal/check-imports/src/references.ts:29 — // TODO: Add `launchNode` and `launchNodeAndGetWallets` here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D23 · Boundary Type-Coupling · Cross-context type TransactionType (transactions → account) · ×9
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:65 — TransactionType (context transactions) is exposed in account's public surface via operations.getTransactionTypeName — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:88 — TransactionType (context transactions) is exposed in account's public surface via operations.isType — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:95 — TransactionType (context transactions) is exposed in account's public surface via operations.isTypeMint — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:100 — TransactionType (context transactions) is exposed in account's public surface via operations.isTypeCreate — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:105 — TransactionType (context transactions) is exposed in account's public surface via operations.isTypeScript — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:110 — TransactionType (context transactions) is exposed in account's public surface via operations.isTypeUpgrade — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:115 — TransactionType (context transactions) is exposed in account's public surface via operations.isTypeUpload — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:120 — TransactionType (context transactions) is exposed in account's public surface via operations.isTypeBlob — couples the contexts.
  • Cross-context type TransactionType (transactions → account) packages/account/src/providers/transaction-request/transaction-request.ts:122 — TransactionType (context transactions) is exposed in account's public surface via BaseTransactionRequest.type — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Output (transactions → account) · ×8
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-request/output.ts:55 — Output (context transactions) is exposed in account's public surface via output.outputify — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts:12 — Output (context transactions) is exposed in account's public surface via output.getOutputsByType — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts:17 — Output (context transactions) is exposed in account's public surface via output.getOutputsContractCreated — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts:22 — Output (context transactions) is exposed in account's public surface via output.getOutputsCoin — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts:27 — Output (context transactions) is exposed in account's public surface via output.getOutputsChange — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts:32 — Output (context transactions) is exposed in account's public surface via output.getOutputsContract — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/output.ts:37 — Output (context transactions) is exposed in account's public surface via output.getOutputsVariable — couples the contexts.
  • Cross-context type Output (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:556 — Output (context transactions) is exposed in account's public surface via operations.getPayProducerOperations — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Operation (utils → account) · ×8
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/types.ts:255 — Operation (context utils) is exposed in account's public surface via PreConfirmationTransactionSummary.operations — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:207 — Operation (context utils) is exposed in account's public surface via operations.addOperation — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:230 — Operation (context utils) is exposed in account's public surface via operations.getWithdrawFromFuelOperations — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:386 — Operation (context utils) is exposed in account's public surface via operations.getContractCallOperations — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:475 — Operation (context utils) is exposed in account's public surface via operations.getTransferOperations — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:556 — Operation (context utils) is exposed in account's public surface via operations.getPayProducerOperations — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:584 — Operation (context utils) is exposed in account's public surface via operations.getContractCreatedOperations — couples the contexts.
  • Cross-context type Operation (utils → account) packages/account/src/providers/transaction-summary/operations.ts:608 — Operation (context utils) is exposed in account's public surface via operations.getOperations — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → crypto) · ×6
  • Cross-context type BytesLike (utils → crypto) packages/crypto/src/types.ts:31 — BytesLike (context utils) is exposed in crypto's public surface via CryptoApi.computeHmac — couples the contexts.
  • Cross-context type BytesLike (utils → crypto) packages/crypto/src/types.ts:33 — BytesLike (context utils) is exposed in crypto's public surface via CryptoApi.pbkdf2 — couples the contexts.
  • Cross-context type BytesLike (utils → crypto) packages/crypto/src/types.ts:40 — BytesLike (context utils) is exposed in crypto's public surface via CryptoApi.ripemd160 — couples the contexts.
  • Cross-context type BytesLike (utils → crypto) packages/crypto/src/browser/pbkdf2.ts:9 — BytesLike (context utils) is exposed in crypto's public surface via pbkdf2.pbkdf2 — couples the contexts.
  • Cross-context type BytesLike (utils → crypto) packages/crypto/src/shared/ripemd160.ts:5 — BytesLike (context utils) is exposed in crypto's public surface via ripemd160.ripemd160 — couples the contexts.
  • Cross-context type BytesLike (utils → crypto) packages/crypto/src/node/pbkdf2.ts:5 — BytesLike (context utils) is exposed in crypto's public surface via pbkdf2.pbkdf2 — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → abi-coder) · ×5
  • Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/encoding/coders/AbstractCoder.ts:11 — BytesLike (context utils) is exposed in abi-coder's public surface via InputValue.InputValue — couples the contexts.
  • Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/FunctionFragment.ts:78 — BytesLike (context utils) is exposed in abi-coder's public surface via FunctionFragment.decodeArguments — couples the contexts.
  • Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/FunctionFragment.ts:121 — BytesLike (context utils) is exposed in abi-coder's public surface via FunctionFragment.decodeOutput — couples the contexts.
  • Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/Interface.ts:56 — BytesLike (context utils) is exposed in abi-coder's public surface via Interface.decodeFunctionResult — couples the contexts.
  • Cross-context type BytesLike (utils → abi-coder) packages/abi-coder/src/Interface.ts:63 — BytesLike (context utils) is exposed in abi-coder's public surface via Interface.decodeLog — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → contract) · ×5
  • Cross-context type BytesLike (utils → contract) packages/contract/src/util.ts:13 — BytesLike (context utils) is exposed in contract's public surface via util.getContractRoot — couples the contexts.
  • Cross-context type BytesLike (utils → contract) packages/contract/src/util.ts:44 — BytesLike (context utils) is exposed in contract's public surface via util.getContractId — couples the contexts.
  • Cross-context type BytesLike (utils → contract) packages/contract/src/contract-factory.ts:61 — BytesLike (context utils) is exposed in contract's public surface via ContractFactory.bytecode — couples the contexts.
  • Cross-context type BytesLike (utils → contract) packages/contract/src/contract-factory.ts:74 — BytesLike (context utils) is exposed in contract's public surface via ContractFactory.constructor — couples the contexts.
  • Cross-context type BytesLike (utils → contract) packages/contract/src/contract-factory.ts:129 — BytesLike (context utils) is exposed in contract's public surface via ContractFactory.createTransactionRequest — couples the contexts.
D5 · Coupling · Off the main sequence · ×5
  • Off the main sequence: @fuel-ts/versions — @fuel-ts/versions: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: @fuel-ts/errors — @fuel-ts/errors: abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
  • Off the main sequence: @fuel-ts/hasher — @fuel-ts/hasher: abstractness 0.00, instability 0.22, distance 0.78 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: @fuel-ts/crypto — @fuel-ts/crypto: abstractness 0.05, instability 0.22, distance 0.73 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: @fuel-ts/utils — @fuel-ts/utils: abstractness 0.09, instability 0.19, distance 0.73 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
D23 · Boundary Type-Coupling · Cross-context type AddressLike (address → account) · ×4
  • Cross-context type AddressLike (address → account) packages/account/src/providers/transaction-request/transaction-request.ts:383 — AddressLike (context address) is exposed in account's public surface via BaseTransactionRequest.getCoinInputWitnessIndexByOwner — couples the contexts.
  • Cross-context type AddressLike (address → account) packages/account/src/providers/transaction-request/transaction-request.ts:523 — AddressLike (context address) is exposed in account's public surface via BaseTransactionRequest.addCoinOutput — couples the contexts.
  • Cross-context type AddressLike (address → account) packages/account/src/providers/transaction-request/transaction-request.ts:540 — AddressLike (context address) is exposed in account's public surface via BaseTransactionRequest.addCoinOutputs — couples the contexts.
  • Cross-context type AddressLike (address → account) packages/account/src/providers/transaction-request/transaction-request.ts:559 — AddressLike (context address) is exposed in account's public surface via BaseTransactionRequest.addChangeOutput — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · TooManyMethods · ×4
  • TooManyMethods: Provider packages/account/src/providers/provider.ts:464 — TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BaseTransactionRequest packages/account/src/providers/transaction-request/transaction-request.ts:120 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BN packages/math/src/bn.ts:44 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Account packages/account/src/account.ts:145 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×4
  • Duplicated block (16 lines × 2 locations) packages/account/src/account.ts:625 — packages/account/src/account.ts:625 · packages/account/src/account.ts:677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2 locations) packages/account/src/providers/transaction-request/script-transaction-request.ts:207 — packages/account/src/providers/transaction-request/script-transaction-request.ts:207 · packages/account/src/providers/transaction-request/transaction-request.ts:607 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (16 lines × 2 locations) packages/account/src/providers/transaction-request/transaction-request.ts:408 — packages/account/src/providers/transaction-request/transaction-request.ts:408 · packages/account/src/providers/transaction-request/transaction-request.ts:449 — 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 (16 lines × 2 locations) packages/merkle/src/sum/sumMerkleTree.ts:50 — packages/merkle/src/sum/sumMerkleTree.ts:50 · packages/merkle/src/sum/sumMerkleTree.ts:96 — 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×3
  • Focus outline removed in CSS without a :focus replacement templates/vite/src/index.css:78 — `input` 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 templates/nextjs/src/styles/globals.css:78 — `input` 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 apps/create-fuels-counter-guide/src/index.css:78 — `input` 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.
D10 · Test Quality · Skipped test · ×3
  • Skipped test: should call onDeploy callback packages/fuels/src/cli/commands/deploy/index.test.ts:33 — Skipped — switched off by test.skip
  • Skipped test: should ensure waitForResult always waits for the transaction to be processed packages/fuel-gauge/src/transaction-response.test.ts:203 — Skipped — switched off by it.skip
  • Skipped test: should encode/decode just fine packages/fuel-gauge/src/abi/abi-coder.test.ts:1012 — Skipped — switched off by it.skip
D23 · Boundary Type-Coupling · Cross-context type HashableMessage (hasher → account) · ×3
  • Cross-context type HashableMessage (hasher → account) packages/account/src/wallet/base-wallet-unlocked.ts:71 — HashableMessage (context hasher) is exposed in account's public surface via BaseWalletUnlocked.signMessage — couples the contexts.
  • Cross-context type HashableMessage (hasher → account) packages/account/src/connectors/fuel-connector.ts:180 — HashableMessage (context hasher) is exposed in account's public surface via FuelConnector.signMessage — couples the contexts.
  • Cross-context type HashableMessage (hasher → account) packages/account/src/account.ts:1071 — HashableMessage (context hasher) is exposed in account's public surface via Account.signMessage — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BigNumberish (math → fuel-gauge) · ×3
  • Cross-context type BigNumberish (math → fuel-gauge) packages/fuel-gauge/src/predicate/utils/predicate/assertBalances.ts:4 — BigNumberish (context math) is exposed in fuel-gauge's public surface via assertBalances.assertBalances — couples the contexts.
  • Cross-context type BigNumberish (math → fuel-gauge) packages/fuel-gauge/src/predicate/utils/predicate/fundAccount.ts:4 — BigNumberish (context math) is exposed in fuel-gauge's public surface via fundAccount.fundAccount — couples the contexts.
  • Cross-context type BigNumberish (math → fuel-gauge) packages/fuel-gauge/src/predicate/utils/predicate/fundPredicate.ts:4 — BigNumberish (context math) is exposed in fuel-gauge's public surface via fundPredicate.fundPredicate — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type TransactionResultReceipt (account → program) · ×3
  • Cross-context type TransactionResultReceipt (account → program) packages/program/src/utils.ts:46 — TransactionResultReceipt (context account) is exposed in program's public surface via utils.getResultLogs — couples the contexts.
  • Cross-context type TransactionResultReceipt (account → program) packages/program/src/utils.ts:59 — TransactionResultReceipt (context account) is exposed in program's public surface via utils.getAllResultLogs — couples the contexts.
  • Cross-context type TransactionResultReceipt (account → program) packages/program/src/response.ts:65 — TransactionResultReceipt (context account) is exposed in program's public surface via response.extractInvocationResult — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → transactions) · ×3
  • Cross-context type BytesLike (utils → transactions) packages/transactions/src/coders/byte-array.ts:25 — BytesLike (context utils) is exposed in transactions's public surface via ByteArrayCoder.encode — couples the contexts.
  • Cross-context type BytesLike (utils → transactions) packages/transactions/src/coders/input.ts:266 — BytesLike (context utils) is exposed in transactions's public surface via InputMessageCoder.encodeData — couples the contexts.
  • Cross-context type BytesLike (utils → transactions) packages/transactions/src/coders/input.ts:294 — BytesLike (context utils) is exposed in transactions's public surface via InputMessageCoder.decodeData — couples the contexts.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×3
  • Duplicated block (24 lines × 2 locations) packages/abi-coder/src/encoding/coders/StdStringCoder.ts:10 — packages/abi-coder/src/encoding/coders/StdStringCoder.ts:10 · packages/abi-coder/src/encoding/coders/StrSliceCoder.ts:10 — 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 (24 lines × 2 locations) packages/account/src/providers/utils/serialization.ts:534 — packages/account/src/providers/utils/serialization.ts:534 · packages/account/src/providers/utils/serialization.ts:597 — 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 (24 lines × 2 locations) packages/create-fuels/src/utils/logger.ts:3 — packages/create-fuels/src/utils/logger.ts:3 · packages/fuels/src/cli/utils/logger.ts:3 — 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 (13 lines × 2 locations) · ×3
  • Duplicated block (13 lines × 2 locations) packages/abi-coder/src/encoding/coders/NumberCoder.ts:53 — packages/abi-coder/src/encoding/coders/NumberCoder.ts:53 · packages/abi-coder/src/encoding/coders/StringCoder.ts:16 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) packages/account/src/account.ts:460 — packages/account/src/account.ts:460 · packages/account/src/account.ts:515 — 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 (13 lines × 2 locations) packages/account/src/connectors/fuel-connector.ts:133 — packages/account/src/connectors/fuel-connector.ts:133 · packages/account/src/connectors/fuel-connector.ts:293 — all 2 copies are in the same file, 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.
S1 · Web-Security Posture · Password key derivation is priced too cheaply · ×3
  • Password key derivation is priced too cheaply packages/account/src/mnemonic/mnemonic.ts:123 — This code fixes PBKDF2-SHA-512 at 2,048 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
  • Password key derivation is priced too cheaply packages/crypto/src/browser/aes-ctr.ts:21 — This code fixes PBKDF2-SHA-256 at 100,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
  • Password key derivation is priced too cheaply packages/crypto/src/node/aes-ctr.ts:22 — This code fixes PBKDF2-SHA-256 at 100,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
X2 · Cancellation propagation · Async function without AbortSignal · ×3
  • Async function without AbortSignal: teardown vitest.global-browser-setup.ts:10 — `teardown` 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: getVersionsToDeprecate scripts/release-deprecate.ts:32 — `getVersionsToDeprecate` 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: getLatestFuelsVersion packages/fuels/src/cli/utils/getLatestFuelsVersion.ts:3 — `getLatestFuelsVersion` 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 })`.
D23 · Boundary Type-Coupling · Cross-context type InputType (transactions → account) · ×2
  • Cross-context type InputType (transactions → account) packages/account/src/providers/transaction-summary/input.ts:7 — InputType (context transactions) is exposed in account's public surface via input.getInputsByTypes — couples the contexts.
  • Cross-context type InputType (transactions → account) packages/account/src/providers/transaction-summary/input.ts:12 — InputType (context transactions) is exposed in account's public surface via input.getInputsByType — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → hasher) · ×2
  • Cross-context type BytesLike (utils → hasher) packages/hasher/src/hasher.ts:26 — BytesLike (context utils) is exposed in hasher's public surface via hasher.sha256 — couples the contexts.
  • Cross-context type BytesLike (utils → hasher) packages/hasher/src/hasher.ts:36 — BytesLike (context utils) is exposed in hasher's public surface via hasher.hash — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → program) · ×2
  • Cross-context type BytesLike (utils → program) packages/program/src/script-request.ts:220 — BytesLike (context utils) is exposed in program's public surface via ScriptRequest.constructor — couples the contexts.
  • Cross-context type BytesLike (utils → program) packages/program/src/contract.ts:118 — BytesLike (context utils) is exposed in program's public surface via Contract.getBalance — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: providers/provider.ts packages/account/src/providers/provider.ts — FileTooLong — 1495 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 995 over it, 2.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/account.ts packages/account/src/account.ts — FileTooLong — 699 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: Account (145-1313). The bar is 500 significant lines; this is 199 over it, 1.40× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D3 · God Classes · FunctionTooLong · ×2
  • FunctionTooLong: serialization.deserializeReceipt packages/account/src/providers/utils/serialization.ts:246 — FunctionTooLong — deserializeReceipt runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: cli.runScaffoldCli packages/create-fuels/src/cli.ts:41 — FunctionTooLong — runScaffoldCli 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.
D43 · Malicious Dependencies · Malicious package · ×2
  • REDACTED
  • REDACTED
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: MockConnector (LCOM4 6) packages/account/test/fixtures/mocked-connector.ts:34 — MockConnector's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Fuel (LCOM4 5) packages/account/src/connectors/fuel.ts:78 — Fuel's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) packages/abi-typegen/src/templates/predicate/main.ts:13 — packages/abi-typegen/src/templates/predicate/main.ts:13 · packages/abi-typegen/src/templates/script/main.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (19 lines × 2 locations) packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:53 — packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:53 · packages/account/src/providers/transaction-response/getDecodedLogs.ts:45 — 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 (15 lines × 2 locations) · ×2
  • Duplicated block (15 lines × 2 locations) packages/account/src/providers/utils/serialization.ts:422 — packages/account/src/providers/utils/serialization.ts:422 · packages/account/src/providers/utils/serialization.ts:440 — 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 (15 lines × 2 locations) packages/crypto/src/browser/encryptJsonWalletData.ts:13 — packages/crypto/src/browser/encryptJsonWalletData.ts:13 · packages/crypto/src/browser/encryptJsonWalletData.ts:40 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×2
  • Duplicated block (14 lines × 2 locations) packages/transactions/src/coders/input.ts:109 — packages/transactions/src/coders/input.ts:109 · packages/transactions/src/coders/input.ts:326 — 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 (14 lines × 2 locations) packages/transactions/src/coders/policy.ts:124 — packages/transactions/src/coders/policy.ts:124 · packages/transactions/src/coders/policy.ts:145 — 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.
R11 · Import Boundaries · Boundary violation [package · ×2
  • Boundary violation [package:test-suite-dependency] packages/account/scripts/generate-fuel-core-schema.ts:4 — packages/account/scripts/generate-fuel-core-schema.ts:4 imports packages/account/src/test-utils/setup-test-provider-and-wallets.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/fuel-gauge/src/utils.ts:6 — packages/fuel-gauge/src/utils.ts:6 imports packages/fuel-gauge/test/fixtures/chain-config/state_transition_bytecode.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
R8 · Dependency Hygiene · Unused dependency '@internal/forc' · ×2
  • Unused dependency '@internal/forc' — Declared in apps/demo-typegen/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Unused dependency '@internal/forc' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark apps/demo-wallet-sdk-react/src/app/layout.tsx:24 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×1
  • Animation without a prefers-reduced-motion guard apps/demo-nextjs/src/app/page.module.css:59 — `.card span` moves (`transition: transform 200ms`) 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.
D1 · Cyclomatic Complexity · serialization.deserializeReceipt (cyclomatic 27) · ×1
  • serialization.deserializeReceipt (cyclomatic 27) packages/account/src/providers/utils/serialization.ts:246 — serialization.deserializeReceipt has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · getCoderV1.getCoder (cyclomatic 25) · ×1
  • getCoderV1.getCoder (cyclomatic 25) packages/abi-coder/src/encoding/strategies/getCoderV1.ts:60 — getCoderV1.getCoder has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · handle-gql-error-message.mapGqlErrorMessage (cyclomatic 22) · ×1
  • handle-gql-error-message.mapGqlErrorMessage (cyclomatic 22) REDACTED:23 — handle-gql-error-message.mapGqlErrorMessage has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality · Fixed-sleep synchronisation · ×1
  • Fixed-sleep synchronisation: should wait for both preconfirmation and confirmation statuses packages/account/src/providers/provider.test.ts:2849 — This test starts work it did not wait for (`readEventSpy`, still running when the sleep starts) and then orders itself against it with `sleep(2500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D2 · Cognitive Complexity · handle-gql-error-message.mapGqlErrorMessage (cognitive 31) · ×1
  • handle-gql-error-message.mapGqlErrorMessage (cognitive 31) REDACTED:23 — handle-gql-error-message.mapGqlErrorMessage has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 6 (12 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · toUtf8String.getUtf8CodePoints (cognitive 28) · ×1
  • toUtf8String.getUtf8CodePoints (cognitive 28) packages/utils/src/utils/toUtf8String.ts:75 — toUtf8String.getUtf8CodePoints has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getAllDecodedLogs.getAllDecodedLogs (cognitive 20) · ×1
  • getAllDecodedLogs.getAllDecodedLogs (cognitive 20) packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:34 — getAllDecodedLogs.getAllDecodedLogs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (6 pts), boolean chains 5, error handling 1 (3 pts) (nesting depth added 8). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 53, 44). 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.
D2 · Cognitive Complexity · ContractFactory.deployAsBlobTx (cognitive 20) · ×1
  • ContractFactory.deployAsBlobTx (cognitive 20) packages/contract/src/contract-factory.ts:266 — ContractFactory.deployAsBlobTx has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 1 (3 pts), boolean chains 2, loops 2 (nesting depth added 9). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (waitForResult). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · BN.format (cognitive 19) · ×1
  • BN.format (cognitive 19) packages/math/src/bn.ts:115 — BN.format has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, ternaries 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SparseMerkleTree.deleteWithSideNodes (cognitive 19) · ×1
  • SparseMerkleTree.deleteWithSideNodes (cognitive 19) packages/merkle/src/sparse/sparseMerkleTree.ts:90 — SparseMerkleTree.deleteWithSideNodes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SparseMerkleTree.updateWithSideNodes (cognitive 19) · ×1
  • SparseMerkleTree.updateWithSideNodes (cognitive 19) packages/merkle/src/sparse/sparseMerkleTree.ts:165 — SparseMerkleTree.updateWithSideNodes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TransactionResponse.waitForStatusChange (cognitive 18) · ×1
  • TransactionResponse.waitForStatusChange (cognitive 18) packages/account/src/providers/transaction-response/transaction-response.ts:440 — TransactionResponse.waitForStatusChange has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getDecodedLogs.getDecodedLogs (cognitive 17) · ×1
  • getDecodedLogs.getDecodedLogs (cognitive 17) packages/account/src/providers/transaction-response/getDecodedLogs.ts:31 — getDecodedLogs.getDecodedLogs has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 2 (6 pts), boolean chains 4, if/else 3 (4 pts), error handling 1 (3 pts) (nesting depth added 7). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 45, 39). 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.
D2 · Cognitive Complexity · Account.fund (cognitive 16) · ×1
  • Account.fund (cognitive 16) packages/account/src/account.ts:297 — Account.fund has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · cli.runScaffoldCli (cognitive 16) · ×1
  • cli.runScaffoldCli (cognitive 16) packages/create-fuels/src/cli.ts:41 — cli.runScaffoldCli has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (4 pts), ternaries 2 (4 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.
D23 · Boundary Type-Coupling · Cross-context type BNInput (math → abi-coder) · ×1
  • Cross-context type BNInput (math → abi-coder) packages/abi-coder/src/encoding/coders/BigNumberCoder.ts:20 — BNInput (context math) is exposed in abi-coder's public surface via BigNumberCoder.encode — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BNInput (math → account) · ×1
  • Cross-context type BNInput (math → account) packages/account/src/providers/utils/gas.ts:29 — BNInput (context math) is exposed in account's public surface via gas.resolveGasDependentCosts — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type OutputType (transactions → account) · ×1
  • Cross-context type OutputType (transactions → account) packages/account/src/providers/transaction-summary/output.ts:12 — OutputType (context transactions) is exposed in account's public surface via output.getOutputsByType — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type ReceiptType (transactions → account) · ×1
  • Cross-context type ReceiptType (transactions → account) packages/account/src/providers/transaction-summary/operations.ts:52 — ReceiptType (context transactions) is exposed in account's public surface via operations.getReceiptsByType — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type ContractIdLike (address → account) · ×1
  • Cross-context type ContractIdLike (address → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:235 — ContractIdLike (context address) is exposed in account's public surface via ScriptTransactionRequest.addContractInputAndOutput — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type InputValue (abi-coder → account) · ×1
  • Cross-context type InputValue (abi-coder → account) packages/account/src/providers/transaction-request/script-transaction-request.ts:275 — InputValue (context abi-coder) is exposed in account's public surface via ScriptTransactionRequest.setData — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type UpgradePurposeTypeEnum (transactions → account) · ×1
  • Cross-context type UpgradePurposeTypeEnum (transactions → account) packages/account/src/providers/transaction-request/upgrade-transaction-request.ts:116 — UpgradePurposeTypeEnum (context transactions) is exposed in account's public surface via UpgradeTransactionRequest.addUpgradePurpose — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Operation (utils → fuel-gauge) · ×1
  • Cross-context type Operation (utils → fuel-gauge) packages/fuel-gauge/scripts/latency-detection/helpers.ts:144 — Operation (context utils) is exposed in fuel-gauge's public surface via helpers.runOperations — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type AddressInput (address → program) · ×1
  • Cross-context type AddressInput (address → program) packages/program/src/contract.ts:48 — AddressInput (context address) is exposed in program's public surface via Contract.constructor — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type AddressInput (address → recipes) · ×1
  • Cross-context type AddressInput (address → recipes) packages/recipes/src/types/Src14OwnedProxy.ts:46 — AddressInput (context address) is exposed in recipes's public surface via AddressOutput.AddressOutput — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type InputValue (abi-coder → script) · ×1
  • Cross-context type InputValue (abi-coder → script) packages/script/src/script.ts:51 — InputValue (context abi-coder) is exposed in script's public surface via Script.script — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BytesLike (utils → script) · ×1
  • Cross-context type BytesLike (utils → script) packages/script/src/script.ts:70 — BytesLike (context utils) is exposed in script's public surface via Script.constructor — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type BNInput (math → utils) · ×1
  • Cross-context type BNInput (math → utils) packages/utils/src/test-utils/vitest.matchers.ts:12 — BNInput (context math) is exposed in utils's public surface via ExpectStatic.toEqualBn — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: Account packages/account/src/account.ts:145 — ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 186 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: Node.js 20 .nvmrc:1 — .nvmrc declares Node.js 20 as this project's version file, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-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.
D5 · Coupling · Unstable project @fuel-ts/recipes · ×1
  • Unstable project @fuel-ts/recipes — @fuel-ts/recipes has instability 0.89 with 1 dependents.
P1 · CI/CD gates · CI formatting step cannot fail · ×1
  • CI formatting step cannot fail REDACTED:48 — `run-s type:check-tests lint:check prettier:check type:check` (the `lint` script this step runs) invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted.
P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×1
  • Workspace package's tests never run by CI REDACTED:1 — `packages/utils` is a workspace package with 79 test(s) in 19 file(s) (e.g. `packages/utils/src/index.test.ts`, `packages/utils/src/test-util.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience packages/fuels/src/cli/utils/getLatestFuelsVersion.ts:14 — `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.
R10 · Code Duplication · Forked directory tree (23 identical files, ~466 lines × 2 trees) · ×1
  • Forked directory tree (23 identical files, ~466 lines × 2 trees) apps/create-fuels-counter-guide/src/components/Wallet.tsx:1 — apps/create-fuels-counter-guide/ and templates/vite/ are near-verbatim copies of each other: 23 files are byte-identical under the same relative paths (~466 lines; the trees hold 43 and 49 files). That is one structural fact, not 23 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (9 clone groups) packages/abi-coder/src/types/JsonAbiNew.ts:5 — 9 duplicated blocks under packages/ have copies in at least two of the sibling directories abi-coder, abi-typegen, account, contract, create-fuels, fuels (+2 more sibling(s) not listed) — 7 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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 (88 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (88 matched lines × 2 locations) packages/transactions/src/coders/input.ts:183 — packages/transactions/src/coders/input.ts:183 · packages/transactions/src/coders/output.ts:92 — the two spans are one implementation copied and then locally edited — 663 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 · Wholesale file copy (73 identical lines × 2 files) · ×1
  • Wholesale file copy (73 identical lines × 2 files) packages/abi-coder/src/types/JsonAbiNew.ts:5 — packages/abi-coder/src/types/JsonAbiNew.ts:5 · packages/abi-typegen/src/types/interfaces/JsonAbiNew.ts:5 — these 2 files are line-for-line copies of one another — 73 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (71 identical lines × 2 files) · ×1
  • Wholesale file copy (71 identical lines × 2 files) packages/abi-coder/src/utils/transpile-abi.ts:7 — packages/abi-coder/src/utils/transpile-abi.ts:7 · packages/abi-typegen/src/utils/transpile-abi.ts:7 — these 2 files are line-for-line copies of one another — 71 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (59 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (59 matched lines × 2 locations) packages/merkle/src/binary/binaryMerkleTree.ts:30 — packages/merkle/src/binary/binaryMerkleTree.ts:30 · packages/merkle/src/sum/sumMerkleTree.ts:43 — the two spans are one implementation copied and then locally edited — 497 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 (52 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (52 matched lines × 2 locations) packages/abi-typegen/src/abi/types/EnumType.ts:23 — packages/abi-typegen/src/abi/types/EnumType.ts:23 · packages/abi-typegen/src/abi/types/StructType.ts:20 — the two spans are one implementation copied and then locally edited — 320 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 (40 lines × 2 locations) · ×1
  • Duplicated block (40 lines × 2 locations) packages/abi-coder/src/types/JsonAbi.ts:10 — packages/abi-coder/src/types/JsonAbi.ts:10 · packages/abi-typegen/src/types/interfaces/JsonAbi.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) internal/forc/lib/install.js:20 — internal/forc/lib/install.js:20 · internal/fuel-core/lib/install.js:19 — the two spans are one implementation copied and then locally edited — 231 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 (34 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (34 matched lines × 2 locations) packages/crypto/src/browser/aes-ctr.ts:11 — packages/crypto/src/browser/aes-ctr.ts:11 · packages/crypto/src/node/aes-ctr.ts:12 — the two spans are one implementation copied and then locally edited — 247 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 (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) packages/account/src/account.ts:780 — packages/account/src/account.ts:780 · packages/account/src/account.ts:854 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) packages/abi-typegen/src/utils/assemblePredicates.ts:15 — packages/abi-typegen/src/utils/assemblePredicates.ts:15 · packages/abi-typegen/src/utils/assembleScripts.ts:15 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) REDACTED:35 — REDACTED:35 · internal/fuel-core/lib/shared.js:29 — the two spans are one implementation copied and then locally edited — 213 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 (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) packages/abi-coder/src/encoding/coders/B256Coder.ts:9 — packages/abi-coder/src/encoding/coders/B256Coder.ts:9 · packages/abi-coder/src/encoding/coders/B512Coder.ts:9 — 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 (26 lines × 2 locations) · ×1
  • Duplicated block (26 lines × 2 locations) packages/abi-typegen/src/abi/types/ArrayType.ts:25 — packages/abi-typegen/src/abi/types/ArrayType.ts:25 · packages/abi-typegen/src/abi/types/TupleType.ts:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (26 matched lines × 2 locations) packages/fuels/src/cli/commands/dev/index.ts:24 — packages/fuels/src/cli/commands/dev/index.ts:24 · packages/fuels/src/cli/commands/node/index.ts:13 — the two spans are one implementation copied and then locally edited — 175 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 (23 lines × 3 locations) · ×1
  • Duplicated block (23 lines × 3 locations) packages/transactions/src/coders/output.ts:27 — packages/transactions/src/coders/output.ts:27 · packages/transactions/src/coders/output.ts:123 · packages/transactions/src/coders/output.ts:171 — all 3 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 (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) packages/abi-typegen/src/templates/predicate/main.ts:43 — packages/abi-typegen/src/templates/predicate/main.ts:43 · packages/abi-typegen/src/templates/script/main.ts:37 — 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 (20 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (20 matched lines × 2 locations) packages/abi-coder/src/encoding/coders/EnumCoder.ts:13 — packages/abi-coder/src/encoding/coders/EnumCoder.ts:13 · packages/abi-coder/src/encoding/coders/StructCoder.ts:10 — the two spans are one implementation copied and then locally edited — 138 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 (20 lines × 4 locations) · ×1
  • Duplicated block (20 lines × 4 locations) packages/transactions/src/coders/input.ts:376 — packages/transactions/src/coders/input.ts:376 · packages/transactions/src/coders/output.ts:289 · packages/transactions/src/coders/transaction.ts:649 · packages/transactions/src/coders/upgrade-purpose.ts:56 — 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 (18 lines × 3 locations) · ×1
  • Duplicated block (18 lines × 3 locations) packages/abi-typegen/src/utils/assembleContracts.ts:42 — packages/abi-typegen/src/utils/assembleContracts.ts:42 · packages/abi-typegen/src/utils/assemblePredicates.ts:33 · packages/abi-typegen/src/utils/assembleScripts.ts:33 — 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 (17 lines × 2 locations) · ×1
  • Duplicated block (17 lines × 2 locations) REDACTED:34 — REDACTED:34 · REDACTED:54 — 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 (16 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (16 matched lines × 2 locations) packages/account/src/predicate/predicate.ts:295 — packages/account/src/predicate/predicate.ts:295 · packages/script/src/script.ts:100 — the two spans are one implementation copied and then locally edited — 91 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 (15 lines × 3 locations) · ×1
  • Duplicated block (15 lines × 3 locations) packages/abi-coder/src/encoding/coders/ByteCoder.ts:16 — packages/abi-coder/src/encoding/coders/ByteCoder.ts:16 · packages/abi-coder/src/encoding/coders/StdStringCoder.ts:17 · packages/abi-coder/src/encoding/coders/StrSliceCoder.ts:17 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 27, cognitive 15) · ×1
  • Complex function (anonymous) (cyclomatic 27, cognitive 15) packages/account/src/providers/utils/serialization.ts:246 — (anonymous) has cyclomatic complexity 27 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 25, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 25, cognitive 13) packages/abi-coder/src/encoding/strategies/getCoderV1.ts:63 — (anonymous) has cyclomatic complexity 25 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 31) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 31) REDACTED:23 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 18) REDACTED:150 — (anonymous) has cyclomatic complexity 17 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.
R2 · Cyclomatic Complexity · Complex function getUtf8CodePoints (cyclomatic 15, cognitive 28) · ×1
  • Complex function getUtf8CodePoints (cyclomatic 15, cognitive 28) packages/utils/src/utils/toUtf8String.ts:75 — getUtf8CodePoints has cyclomatic complexity 15 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runScaffoldCli (cyclomatic 15, cognitive 19) · ×1
  • Complex function runScaffoldCli (cyclomatic 15, cognitive 19) packages/create-fuels/src/cli.ts:41 — runScaffoldCli has cyclomatic complexity 15 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity · Complex function waitForStatusChange (cyclomatic 14, cognitive 19) · ×1
  • Complex function waitForStatusChange (cyclomatic 14, cognitive 19) packages/account/src/providers/transaction-response/transaction-response.ts:440 — waitForStatusChange has cyclomatic complexity 14 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity · Complex function format (cyclomatic 14, cognitive 19) · ×1
  • Complex function format (cyclomatic 14, cognitive 19) packages/math/src/bn.ts:115 — format has cyclomatic complexity 14 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 10) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 10) packages/account/src/providers/utils/validate-pagination-args.ts:11 — (anonymous) has cyclomatic complexity 13 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.
R2 · Cyclomatic Complexity · Complex function deleteWithSideNodes (cyclomatic 12, cognitive 19) · ×1
  • Complex function deleteWithSideNodes (cyclomatic 12, cognitive 19) packages/merkle/src/sparse/sparseMerkleTree.ts:90 — deleteWithSideNodes has cyclomatic complexity 12 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity · Complex function constructor (cyclomatic 12, cognitive 11) · ×1
  • Complex function constructor (cyclomatic 12, cognitive 11) packages/account/src/providers/transaction-request/transaction-request.ts:152 — constructor 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.
R2 · Cyclomatic Complexity · Complex function fromExtendedKey (cyclomatic 11, cognitive 11) · ×1
  • Complex function fromExtendedKey (cyclomatic 11, cognitive 11) packages/account/src/hdwallet/hdwallet.ts:223 — fromExtendedKey has cyclomatic complexity 11 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 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.
R2 · Cyclomatic Complexity · Complex function buildBlockExplorerUrl (cyclomatic 11, cognitive 10) · ×1
  • Complex function buildBlockExplorerUrl (cyclomatic 11, cognitive 10) packages/account/src/providers/utils/block-explorer.ts:26 — buildBlockExplorerUrl 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.
R2 · Cyclomatic Complexity · Complex function validate (cyclomatic 11, cognitive 10) · ×1
  • Complex function validate (cyclomatic 11, cognitive 10) packages/account/src/test-utils/wallet-config.ts:141 — validate 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.
R2 · Cyclomatic Complexity · Complex function extractInvocationResult (cyclomatic 11, cognitive 10) · ×1
  • Complex function extractInvocationResult (cyclomatic 11, cognitive 10) packages/program/src/response.ts:65 — extractInvocationResult 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.
R3 · Large Files · packages/account/src/providers/provider.ts · ×1
  • packages/account/src/providers/provider.ts: 2408 lines of code packages/account/src/providers/provider.ts:1 — packages/account/src/providers/provider.ts has 2408 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 · packages/account/src/account.ts · ×1
  • packages/account/src/account.ts: 1125 lines of code packages/account/src/account.ts:1 — packages/account/src/account.ts has 1125 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 · packages/account/src/providers/transaction-request/transaction-request.ts · ×1
  • packages/account/src/providers/transaction-request/transaction-request.ts: 685 lines of code packages/account/src/providers/transaction-request/transaction-request.ts:1 — packages/account/src/providers/transaction-request/transaction-request.ts has 685 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 · packages/transactions/src/coders/transaction.ts · ×1
  • packages/transactions/src/coders/transaction.ts: 608 lines of code packages/transactions/src/coders/transaction.ts:1 — packages/transactions/src/coders/transaction.ts has 608 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 · packages/program/src/functions/base-invocation-scope.ts · ×1
  • packages/program/src/functions/base-invocation-scope.ts: 596 lines of code packages/program/src/functions/base-invocation-scope.ts:1 — packages/program/src/functions/base-invocation-scope.ts has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/account/src/providers/transaction-response/transaction-response.ts · ×1
  • packages/account/src/providers/transaction-response/transaction-response.ts: 566 lines of code packages/account/src/providers/transaction-response/transaction-response.ts:1 — packages/account/src/providers/transaction-response/transaction-response.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/account/src/providers/transaction-summary/operations.ts · ×1
  • packages/account/src/providers/transaction-summary/operations.ts: 558 lines of code packages/account/src/providers/transaction-summary/operations.ts:1 — packages/account/src/providers/transaction-summary/operations.ts has 558 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 · packages/account/src/providers/utils/serialization.ts · ×1
  • packages/account/src/providers/utils/serialization.ts: 552 lines of code packages/account/src/providers/utils/serialization.ts:1 — packages/account/src/providers/utils/serialization.ts has 552 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 · packages/account/src/connectors/fuel.ts · ×1
  • packages/account/src/connectors/fuel.ts: 460 lines of code packages/account/src/connectors/fuel.ts:1 — packages/account/src/connectors/fuel.ts has 460 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 · packages/contract/src/contract-factory.ts · ×1
  • packages/contract/src/contract-factory.ts: 434 lines of code packages/contract/src/contract-factory.ts:1 — packages/contract/src/contract-factory.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~37 LoC) · ×1
  • Dead file (~37 LoC) packages/merkle/src/sparse/types/sparseMerkleSolidityNode.ts — no import path from any entry point (93 application, 55 tooling, 395 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/merkle/src/sparse/types/sparseCompactMerkleSolidityProof.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~30 LoC) · ×1
  • Dead file (~30 LoC) packages/fuel-gauge/src/predicate/utils/predicate/fundPredicate.ts — no import path from any entry point (93 application, 55 tooling, 395 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
R7 · Dead Code · Dead file (~25 LoC) · ×1
  • Dead file (~25 LoC) packages/merkle/src/sparse/types/sparseCompactMerkleSolidityProof.ts — no import path from any entry point (93 application, 55 tooling, 395 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/merkle/src/sparse/types/sparseCompactMerkleBranch.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~20 LoC) · ×1
  • Dead file (~20 LoC) packages/fuels/scripts/build-proxy-contract.ts — no import path from any entry point (93 application, 55 tooling, 395 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
R7 · Dead Code · Dead file (~15 LoC) · ×1
  • Dead file (~15 LoC) packages/merkle/src/sparse/types/sparseCompactMerkleBranch.ts — no import path from any entry point (93 application, 55 tooling, 395 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
R7 · Dead Code · Dead file (~13 LoC) · ×1
  • Dead file (~13 LoC) packages/merkle/src/binary/types/branch.ts — no import path from any entry point (93 application, 55 tooling, 395 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
R7 · Dead Code · Dead file (~6 LoC) · ×1
  • Dead file (~6 LoC) vitest.workspace.ts — no import path from any entry point (93 application, 55 tooling, 395 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
R7 · Dead Code · Dead file (~1 LoC) · ×1
  • Dead file (~1 LoC) packages/merkle/src/sum/index.ts — no import path from any entry point (93 application, 55 tooling, 395 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
R8 · Dependency Hygiene · Unused dependency '@changesets/cli' · ×1
  • Unused dependency '@changesets/cli' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap packages/account/src/providers/utils/json.ts:18 — `normalizeJSON` is exported, takes a document from its caller (line 41) and hands it to `normalize`, which calls itself at line 18 (`normalize`) with a piece of `object` (and at line 27) — and nowhere in `normalize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `normalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) packages/account/src/providers/provider.ts:2560 — 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.
Minor — 211 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×119
  • Orphaned file packages/program/src/functions/base-invocation-scope.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 packages/account/src/providers/transaction-request/transaction-request.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 packages/account/src/providers/transaction-response/transaction-response.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 packages/account/src/providers/transaction-summary/operations.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 packages/contract/src/contract-factory.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 packages/account/src/providers/utils/serialization.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 packages/account/src/connectors/fuel.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 packages/account/src/connectors/fuel-connector.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 packages/account/src/predicate/predicate.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 packages/transactions/src/coders/input.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/math/src/bn.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 packages/program/src/script-request.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 packages/account/src/wallet-manager/wallet-manager.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 packages/account/src/providers/transaction-request/script-transaction-request.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 packages/account/src/hdwallet/hdwallet.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 packages/account/src/utils/predicate-script-loader-instructions.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 packages/transactions/src/coders/output.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 packages/merkle/src/sparse/sparseMerkleTree.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 packages/program/src/contract-call-script.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 packages/account/src/mnemonic/mnemonic.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 packages/program/src/response.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 packages/transactions/src/receipt.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 packages/account/src/providers/utils/extract-tx-error.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 packages/account/src/providers/utils/gas.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.
  • + 94 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×19
  • Mock-dominated test: should inform about newer versions packages/versions/src/cli.test.ts:87 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should inform about exact versions packages/versions/src/cli.test.ts:110 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should warn about older versions packages/versions/src/cli.test.ts:133 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should warn about fuelup exception packages/versions/src/cli.test.ts:156 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 7 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should warn the user when binaries are outdated packages/utils/src/cli-utils/tryFindBinaries.test.ts:124 — This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should run `dev` command packages/fuels/test/features/dev.test.ts:64 — This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should load the user config from the path packages/fuels/src/cli/commands/withBinaryPaths.test.ts:49 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should debug any errors that occur while loading the user config packages/fuels/src/cli/commands/withBinaryPaths.test.ts:76 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should restart everything when config file changes packages/fuels/src/cli/commands/dev/index.test.ts:114 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should restart everything and handle errors packages/fuels/src/cli/commands/dev/index.test.ts:145 — This test sets up 4 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ensures gas price and predicates are estimated on the same request packages/fuel-gauge/src/fee.test.ts:524 — This test sets up 3 test doubles (for example `vi.spyOn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ensures gas price is estimated alone when no predicates are present packages/fuel-gauge/src/fee.test.ts:546 — This test sets up 3 test doubles (for example `vi.spyOn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ensures predicates are estimated alone when gas price is present packages/fuel-gauge/src/fee.test.ts:569 — This test sets up 3 test doubles (for example `vi.spyOn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should install fuelup successfully packages/create-fuels/src/lib/installFuelUp.test.ts:54 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should display a message of installation to the user packages/create-fuels/src/lib/tryInstallFuelUp.test.ts:53 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should use custom storage packages/account/test/fuel-wallet-connector.browser.test.ts:68 — This test sets up 3 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should execute fund just as fine packages/account/src/account.test.ts:242 — This test sets up 3 test doubles (for example `vi .spyOn`) against 2 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: Test WalletManager events packages/account/src/wallet-manager/wallet-manager.test.ts:293 — This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: calling cleanup on externally killed node does not throw packages/account/src/test-utils/launchNode.test.ts:244 — This test sets up 4 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
X10 · Duplicated predicate · Duplicated predicate · ×15
  • Duplicated predicate packages/abi-coder/src/encoding/coders/StructCoder.ts:55 — `!this.#hasNestedOption && data.length < this.encodedLength` appears character-identically in 2 files — packages/abi-coder/src/encoding/coders/StructCoder.ts, packages/abi-coder/src/encoding/coders/TupleCoder.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 packages/abi-coder/src/encoding/coders/ArrayCoder.ts:41 — `(!this.#hasNestedOption && data.length < this.encodedLength) || data.length > MAX_BYTES` appears character-identically in 2 files — packages/abi-coder/src/encoding/coders/ArrayCoder.ts, packages/abi-coder/src/encoding/coders/VecCoder.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 packages/contract/src/contract-factory.ts:102 — `accountOrProvider && 'provider' in accountOrProvider` appears character-identically in 2 files — packages/contract/src/contract-factory.ts, packages/program/src/contract.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 apps/create-fuels-counter-guide/src/components/LocalFaucet.tsx:28 — `addressToFund || wallet.address.toB256()` appears character-identically in 3 files — apps/create-fuels-counter-guide/src/components/LocalFaucet.tsx, templates/nextjs/src/components/LocalFaucet.tsx, templates/vite/src/components/LocalFaucet.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 apps/create-fuels-counter-guide/src/components/Button.tsx:17 — `color === "secondary" && "btn-secondary"` appears character-identically in 3 files — apps/create-fuels-counter-guide/src/components/Button.tsx, templates/nextjs/src/components/Button.tsx, templates/vite/src/components/Button.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 apps/create-fuels-counter-guide/src/components/Faucet.tsx:20 — `connectedWalletAddress && !initialAddressLoaded && !addressToFund` appears character-identically in 3 files — apps/create-fuels-counter-guide/src/components/Faucet.tsx, templates/nextjs/src/components/Faucet.tsx, templates/vite/src/components/Faucet.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 packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:56 — `isLogFromMainAbi || externalAbis[receipt.id]` appears character-identically in 2 files — packages/account/src/providers/transaction-response/getAllDecodedLogs.ts, packages/account/src/providers/transaction-response/getDecodedLogs.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 packages/create-fuels/src/utils/logger.ts:10 — `params.isDebugEnabled && loggingConfig.isLoggingEnabled` appears character-identically in 2 files — packages/create-fuels/src/utils/logger.ts, packages/fuels/src/cli/utils/logger.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 REDACTED:45 — `process.arch !== 'arm64' && process.arch !== 'x64'` appears character-identically in 2 files — REDACTED, internal/fuel-core/lib/shared.js. 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 apps/create-fuels-counter-guide/src/lib.tsx:6 — `process.env.VITE_DAPP_ENVIRONMENT || environments.LOCAL` appears character-identically in 3 files — apps/create-fuels-counter-guide/src/lib.tsx, templates/nextjs/src/lib.tsx, templates/vite/src/lib.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 REDACTED:38 — `process.platform !== 'darwin' && process.platform !== 'linux'` appears character-identically in 2 files — REDACTED, internal/fuel-core/lib/shared.js. 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 packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:44 — `r.type === ReceiptType.Call && r.id === ZeroBytes32` appears character-identically in 2 files — packages/account/src/providers/transaction-response/getAllDecodedLogs.ts, packages/account/src/providers/transaction-response/getDecodedLogs.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 packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:55 — `receipt.id === ZeroBytes32 || mainContract === receipt.id` appears character-identically in 2 files — packages/account/src/providers/transaction-response/getAllDecodedLogs.ts, packages/account/src/providers/transaction-response/getDecodedLogs.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 packages/account/src/providers/transaction-response/getAllDecodedLogs.ts:54 — `receipt.type === ReceiptType.LogData || receipt.type === ReceiptType.Log` appears character-identically in 2 files — packages/account/src/providers/transaction-response/getAllDecodedLogs.ts, packages/account/src/providers/transaction-response/getDecodedLogs.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 apps/docs/src/guide/transactions/snippets/pre-confirmation/contract-call.ts:28 — `resolved.output.type === OutputType.Change && resolved.output.assetId === baseAssetId` appears character-identically in 2 files — apps/docs/src/guide/transactions/snippets/pre-confirmation/contract-call.ts, apps/docs/src/guide/transactions/snippets/pre-confirmation/send-transaction.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.
D30 · Dependency Vulnerabilities · Low CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file packages/account/src/providers/provider.ts: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 packages/account/src/account.ts: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 packages/transactions/src/coders/transaction.ts: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.
IC1 · Incompleteness & stubs · Disabled test · ×3
  • Disabled test packages/fuel-gauge/src/abi/abi-coder.test.ts:1012 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/fuel-gauge/src/transaction-response.test.ts:203 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/fuels/src/cli/commands/deploy/index.test.ts:33 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
IC1 · Incompleteness & stubs · Blanket warning suppression · ×2
  • Blanket warning suppression packages/abi-coder/src/utils/transpile-abi.ts:5 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression packages/abi-typegen/src/utils/transpile-abi.ts:5 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 47 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 26 project(s) overshoot their size bounds, lowering Project Cohesion to 9.2/10. The most over is `packages/account` (16670 LoC, 180 module-visible types across 24 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 122 of 122 significant files have no living knowledge — the codebase as a whole is dormant, not 122 separate risks. Counted over 122 of the 517 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/demo-wallet-sdk-react`, `apps/docs/fuel-asm-example`, `internal/forc`, `internal/fuel-core`, `packages/abi-typegen` and 3 more.
R7 · Dead Code · Unused export 'x' · ×1
  • Unused export 'x' internal/check-imports/src/references.ts:77 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'y' · ×1
  • Unused export 'y' internal/check-imports/src/references.ts:78 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'z' · ×1
  • Unused export 'z' internal/check-imports/src/references.ts:79 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'MAX_INPUTS' · ×1
  • Unused export 'MAX_INPUTS' packages/abi-coder/src/utils/constants.ts:43 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'INPUT_MESSAGE_FIXED_SIZE' · ×1
  • Unused export 'INPUT_MESSAGE_FIXED_SIZE' packages/abi-coder/src/utils/constants.ts:86 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'chunkByLength' · ×1
  • Unused export 'chunkByLength' packages/abi-coder/src/utils/utilities.ts:25 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ContractChunk' · ×1
  • Unused export 'ContractChunk' packages/contract/src/loader/types.ts:3 — Nothing ultimately consumes this binding: its only referrer is the re-export in packages/contract/src/loader/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/contract/src/loader/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'U8_MAX_ENCODED' · ×1
  • Unused export 'U8_MAX_ENCODED' packages/fuel-gauge/src/abi/constants.ts:5 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U8_MIN_ENCODED' · ×1
  • Unused export 'U8_MIN_ENCODED' packages/fuel-gauge/src/abi/constants.ts:6 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U16_MAX_ENCODED' · ×1
  • Unused export 'U16_MAX_ENCODED' packages/fuel-gauge/src/abi/constants.ts:9 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U16_MIN_ENCODED' · ×1
  • Unused export 'U16_MIN_ENCODED' packages/fuel-gauge/src/abi/constants.ts:10 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U32_MAX_ENCODED' · ×1
  • Unused export 'U32_MAX_ENCODED' packages/fuel-gauge/src/abi/constants.ts:13 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U32_MIN_ENCODED' · ×1
  • Unused export 'U32_MIN_ENCODED' packages/fuel-gauge/src/abi/constants.ts:14 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U64_MAX_ENCODED' · ×1
  • Unused export 'U64_MAX_ENCODED' packages/fuel-gauge/src/abi/constants.ts:17 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U64_MIN_ENCODED' · ×1
  • Unused export 'U64_MIN_ENCODED' packages/fuel-gauge/src/abi/constants.ts:18 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U256_MAX_ENCODED' · ×1
  • Unused export 'U256_MAX_ENCODED' packages/fuel-gauge/src/abi/constants.ts:21 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'U256_MIN_ENCODED' · ×1
  • Unused export 'U256_MIN_ENCODED' packages/fuel-gauge/src/abi/constants.ts:22 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ENUM_FIRST_INDEX' · ×1
  • Unused export 'ENUM_FIRST_INDEX' packages/fuel-gauge/src/abi/constants.ts:25 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ENUM_SECOND_INDEX' · ×1
  • Unused export 'ENUM_SECOND_INDEX' packages/fuel-gauge/src/abi/constants.ts:26 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ENUM_THIRD_INDEX' · ×1
  • Unused export 'ENUM_THIRD_INDEX' packages/fuel-gauge/src/abi/constants.ts:27 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'STRING_MIN_DECODED' · ×1
  • Unused export 'STRING_MIN_DECODED' packages/fuel-gauge/src/abi/constants.ts:29 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'STRING_MIN_ENCODED' · ×1
  • Unused export 'STRING_MIN_ENCODED' packages/fuel-gauge/src/abi/constants.ts:30 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'STRING_MAX_DECODED' · ×1
  • Unused export 'STRING_MAX_DECODED' packages/fuel-gauge/src/abi/constants.ts:31 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'STRING_MAX_ENCODED' · ×1
  • Unused export 'STRING_MAX_ENCODED' packages/fuel-gauge/src/abi/constants.ts:32 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'B256_DECODED' · ×1
  • Unused export 'B256_DECODED' packages/fuel-gauge/src/abi/constants.ts:36 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'B256_ENCODED' · ×1
  • Unused export 'B256_ENCODED' packages/fuel-gauge/src/abi/constants.ts:37 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'B256_ZERO_DECODED' · ×1
  • Unused export 'B256_ZERO_DECODED' packages/fuel-gauge/src/abi/constants.ts:41 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'B256_ZERO_ENCODED' · ×1
  • Unused export 'B256_ZERO_ENCODED' packages/fuel-gauge/src/abi/constants.ts:43 — Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene · Type-only dependency 'type-fest' in production deps · ×1
  • Type-only dependency 'type-fest' in production deps packages/abi-coder/src/encoding/coders/EnumCoder.ts:4 — Every import is type-only — move it to devDependencies.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected templates/vite/vercel.json:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected packages/fuels/src/setup-launch-node-server.ts:100 — `server.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 2/5 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 55/56 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~0.4 `!` null assertions per 1k TypeScript source lines — 17 assertion(s) across the 46138 source line(s) of the 680 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: packages/program/src/contract.ts (4), apps/docs/src/guide/utilities/snippets/using-assets.ts (2), packages/contract/src/contract-factory.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex packages/account/src/providers/provider.ts:529 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Minor — 9 finding(s)
D10 · Test Quality · Skipped (documented) · ×9
  • Skipped (documented): (unnamed test) templates/vite/test/ui/ui.test.ts:18 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) templates/nextjs/test/ui/ui.test.ts:18 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) playwright-tests/create-fuels.test.ts:18 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): times out test if url is live packages/utils/src/test-utils/wait-until-unreachable.test.ts:30 — Skipped with a documented reason — a deferral, not lazy debt: declared test.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): should encode/decode just fine packages/fuel-gauge/src/abi/abi-coder.test.ts:1092 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): should encode/decode just fine packages/fuel-gauge/src/abi/abi-coder.test.ts:1228 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): should encode/decode just fine packages/fuel-gauge/src/abi/abi-coder.test.ts:1274 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): should start consolidation process packages/account/test/fuel-wallet-connector.test.ts:916 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) apps/create-fuels-counter-guide/test/ui/ui.test.ts:18 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bb684584b30348fe830a57f632f9c0c4/history.json --exit-code 0 --source .32artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bb684584b30348fe830a57f632f9c0c4/tree.json --exit-code 0 --source .18artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude apps/create-fuels-counter-guide/src --exclude packages/abi-typegen/test/fixtures/templates --exclude packages/account/src/assets/utils --exclude packages/fuels/test/fixtures/project --exclude packages/recipes/src/types --exclude templates/nextjs/src --exclude templates/nextjs/test/integration --exclude templates/vite/src --exclude templates/vite/test/integration .83artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update125artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (REDACTED, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `apps/docs/scripts/launcher-snippet.ts`, `apps/docs/src/guide/provider/snippets/functionality/get-message-proof-block-height.ts`, `apps/docs/src/guide/provider/snippets/functionality/get-message-proof-block-id.ts`, `apps/docs/src/guide/scripts/snippets/deploying-scripts.ts`, `apps/docs/src/guide/scripts/snippets/script-custom-transaction.ts`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update2artifacts/raw/trivy-fs.json

Run 01a178a7-8c72-7855-8be0-ced10bf4a7ee · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 233 · Warnings: 624 · Recommendations: 211 · Info: 9 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 14:40 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.

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