Executive summary
FuelLabs/fuels-rs falls short of our standard for a preview release because we found no recorded design decisions and no architecture document or diagram, and 78 files are no longer known to anyone active in the project. It scores 62 out of 100 and is rated Adequate, and 39 of its 40 critical findings are security problems in the build pipeline.
Maturity, at 49, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Having someone learn and document the 78 files no active contributor knows comes next, worth about 9 points. Raising Maturity to 62 would lift the score to about 68.
Thirty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five pipeline steps run downloads nobody checks, and four secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 24,324 lines, about €44,000 to rebuild.
If Maturity rose from 49 to 62, the lowest score rated Strong, the score would rise from 62 to about 68.
New since the last survey: 34 findings
- Code Duplication · Edited copy of a member (42 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) packages/fuels-macros/src/derive/parameterize.rs
- Code Duplication · Edited copy of a member (27 corresponding lines) packages/fuels-accounts/src/provider/cache.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) packages/fuels-programs/src/calls/call_handler.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) packages/fuels-code-gen/src/program_bindings/custom_types/enums.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) packages/fuels-programs/src/calls/call_handler.rs
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) packages/fuels-macros/src/derive/parameterize.rs
- Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) packages/fuels-accounts/src/provider.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (30 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) packages/fuels-accounts/src/signers/kms/aws.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) packages/fuels-core/src/types/param_types/from_type_application.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) packages/fuels-programs/src/calls/call_handler.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) packages/fuels-accounts/src/provider.rs
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) packages/fuels-macros/src/abigen/parsing.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) packages/fuels-programs/src/assembly/script_and_predicate_loader.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) packages/fuels-programs/src/calls/call_handler.rs
- Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) packages/fuels-accounts/src/provider.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) packages/fuels-accounts/src/signers/kms/aws.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) packages/fuels-accounts/src/signers/kms/aws.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) packages/fuels-core/src/codec.rs
- Code Duplication · Duplicated block (11–12 lines × 2) packages/fuels-programs/src/calls/call_handler.rs
- Code Duplication · Duplicated block (9 lines × 2) packages/fuels-macros/src/derive/parameterize.rs
Fixed since the last survey: 2 findings
- Cognitive Complexity · change_log::domain::changelog::generate_changelog (cognitive 23) scripts/change-log/src/domain/changelog.rs
- Code Duplication · Duplicated block (11–12 lines × 2) packages/fuels-programs/src/calls/call_handler.rs
Rebuild cost: about €44,000 · Estimate
| Cost to rebuild | €15,000 to €73,000, for 242 to 767 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 24,324 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 fuels_code_gen.program_bindings.utils | 2 fuels_core.types.param_types.param_type | 3 fuels_core.types.wrappers.coin_type_id | 4 fuels_core.types.wrappers.input | 5 fuels_core.types.wrappers.message | 6 fuels_core.utils.sealed | 7 fuels_programs.calls.utils.sealed | 8 fuels_core.codec.abi_decoder | 9 fuels_core.traits.parameterize | 10 fuels_core.traits.signer | 11 fuels_core.types.errors | 12 fuels_core.types.token | 13 fuels_core.types.transaction_builders | 14 fuels_accounts.signers.fake | 15 fuels_accounts.signers.kms.aws | 16 fuels_accounts.signers.kms.google | 17 fuels_core.codec.logs | 18 fuels_core.traits.tokenizable | 19 fuels_core.types.transaction_builders.blob | 20 fuels_programs.calls.traits.response_parser | 21 fuels_core.types.core.bits | 22 fuels_core.types.core.bytes | 23 fuels_core.types.core.raw_slice | 24 fuels_core.types.core.sized_ascii_string | 25 fuels_core.types.core.u256 | 26 fuels_core.types.tx_status | 27 fuels_core.types.wrappers.transaction | 28 fuels_accounts.account | 29 fuels_accounts.provider.retryable_client | 30 fuels_core.codec.abi_encoder.bounded_encoder | 31 fuels_programs.calls.receipt_parser | 32 fuels_programs.calls.traits.transaction_tuner | 33 fuels_programs.calls.utils | 34 fuels_programs.contract.regular | 35 fuels_accounts.provider | 36 fuels_programs.calls.contract_call | 37 fuels_programs.calls.script_call | 38 fuels_accounts.accounts_utils | 39 fuels_accounts.predicate | 40 fuels_programs.calls.call_handler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 fuels_code_gen.program_bindings.utils | ||||||||||||||||||||||||||||||||||||||||
| 2 fuels_core.types.param_types.param_type | ||||||||||||||||||||||||||||||||||||||||
| 3 fuels_core.types.wrappers.coin_type_id | ||||||||||||||||||||||||||||||||||||||||
| 4 fuels_core.types.wrappers.input | ||||||||||||||||||||||||||||||||||||||||
| 5 fuels_core.types.wrappers.message | ||||||||||||||||||||||||||||||||||||||||
| 6 fuels_core.utils.sealed | ||||||||||||||||||||||||||||||||||||||||
| 7 fuels_programs.calls.utils.sealed | ||||||||||||||||||||||||||||||||||||||||
| 8 fuels_core.codec.abi_decoder | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 fuels_core.traits.parameterize | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 fuels_core.traits.signer | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 fuels_core.types.errors | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 fuels_core.types.token | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 fuels_core.types.transaction_builders | 6 | 1 | 6 | 5 | ||||||||||||||||||||||||||||||||||||
| 14 fuels_accounts.signers.fake | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 fuels_accounts.signers.kms.aws | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 fuels_accounts.signers.kms.google | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 fuels_core.codec.logs | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 fuels_core.traits.tokenizable | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 fuels_core.types.transaction_builders.blob | 1 | 1 | 4 | 2 | ||||||||||||||||||||||||||||||||||||
| 20 fuels_programs.calls.traits.response_parser | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 fuels_core.types.core.bits | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 fuels_core.types.core.bytes | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 fuels_core.types.core.raw_slice | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 fuels_core.types.core.sized_ascii_string | 2 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 fuels_core.types.core.u256 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 fuels_core.types.tx_status | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 fuels_core.types.wrappers.transaction | 1 | 7 | 8 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 fuels_accounts.account | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 fuels_accounts.provider.retryable_client | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 fuels_core.codec.abi_encoder.bounded_encoder | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 fuels_programs.calls.receipt_parser | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 fuels_programs.calls.traits.transaction_tuner | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 fuels_programs.calls.utils | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 fuels_programs.contract.regular | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 fuels_accounts.provider | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 fuels_programs.calls.contract_call | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 37 fuels_programs.calls.script_call | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 fuels_accounts.accounts_utils | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 fuels_accounts.predicate | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 fuels_programs.calls.call_handler | 1 | 1 | 1 | 2 | 1 | 1 | 1 |
8→2 fuels_core.codec.abi_decoder uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_core.codec.abi_decoder uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.codec.abi_decoder.ABIDecoder→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.codec.abi_decoder uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.codec.abi_decoder, while a change to fuels_core.codec.abi_decoder can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.codec.abi_decoder uses a module listed above it, which is the healthy direction.
9→2 fuels_core.traits.parameterize uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_core.traits.parameterize uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.traits.parameterize.Parameterize→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.traits.parameterize uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.traits.parameterize, while a change to fuels_core.traits.parameterize can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.traits.parameterize uses a module listed above it, which is the healthy direction.
10→5 fuels_core.traits.signer uses fuels_core.types.wrappers.message✕
- Connections
- 1 pair of types, where a type in fuels_core.traits.signer uses a type in fuels_core.types.wrappers.message.
- The types involved
fuels_core.traits.signer.Signer→fuels_core.types.wrappers.message.Message
- Direction
- fuels_core.traits.signer uses fuels_core.types.wrappers.message, so a change to fuels_core.types.wrappers.message can break fuels_core.traits.signer, while a change to fuels_core.traits.signer can't break fuels_core.types.wrappers.message.
- Position
- Below the diagonal: fuels_core.traits.signer uses a module listed above it, which is the healthy direction.
11→6 fuels_core.types.errors uses fuels_core.utils.sealed✕
- Connections
- 1 pair of types, where a type in fuels_core.types.errors uses a type in fuels_core.utils.sealed.
- The types involved
fuels_core.types.errors.Context→fuels_core.utils.sealed.Sealed
- Direction
- fuels_core.types.errors uses fuels_core.utils.sealed, so a change to fuels_core.utils.sealed can break fuels_core.types.errors, while a change to fuels_core.types.errors can't break fuels_core.utils.sealed.
- Position
- Below the diagonal: fuels_core.types.errors uses a module listed above it, which is the healthy direction.
12→18 fuels_core.types.token uses fuels_core.traits.tokenizable part of a loop✕
- Connections
- 1 pair of types, where a type in fuels_core.types.token uses a type in fuels_core.traits.tokenizable.
- The types involved
fuels_core.types.token.Token→fuels_core.traits.tokenizable.Tokenizable
- Direction
- fuels_core.types.token uses fuels_core.traits.tokenizable, so a change to fuels_core.traits.tokenizable can break fuels_core.types.token, while a change to fuels_core.types.token can't break fuels_core.traits.tokenizable.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 fuels_core.types.transaction_builders uses fuels_core.types.wrappers.input✕
- Connections
- 6 pairs of types, where a type in fuels_core.types.transaction_builders uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_core.types.transaction_builders.CreateTransactionBuilder→fuels_core.types.wrappers.input.Inputfuels_core.types.transaction_builders.ScriptTransactionBuilder→fuels_core.types.wrappers.input.Inputfuels_core.types.transaction_builders.TransactionBuilder→fuels_core.types.wrappers.input.Inputfuels_core.types.transaction_builders.UpgradeTransactionBuilder→fuels_core.types.wrappers.input.Inputfuels_core.types.transaction_builders.UploadTransactionBuilder→fuels_core.types.wrappers.input.Inputfuels_core.types.transaction_builders.transaction_builders$module→fuels_core.types.wrappers.input.Input
- Direction
- fuels_core.types.transaction_builders uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_core.types.transaction_builders, while a change to fuels_core.types.transaction_builders can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_core.types.transaction_builders uses a module listed above it, which is the healthy direction.
13→5 fuels_core.types.transaction_builders uses fuels_core.types.wrappers.message✕
- Connections
- 1 pair of types, where a type in fuels_core.types.transaction_builders uses a type in fuels_core.types.wrappers.message.
- The types involved
fuels_core.types.transaction_builders.transaction_builders$module→fuels_core.types.wrappers.message.Message
- Direction
- fuels_core.types.transaction_builders uses fuels_core.types.wrappers.message, so a change to fuels_core.types.wrappers.message can break fuels_core.types.transaction_builders, while a change to fuels_core.types.transaction_builders can't break fuels_core.types.wrappers.message.
- Position
- Below the diagonal: fuels_core.types.transaction_builders uses a module listed above it, which is the healthy direction.
13→6 fuels_core.types.transaction_builders uses fuels_core.utils.sealed✕
- Connections
- 6 pairs of types, where a type in fuels_core.types.transaction_builders uses a type in fuels_core.utils.sealed.
- The types involved
fuels_core.types.transaction_builders.BuildableTransaction→fuels_core.utils.sealed.Sealedfuels_core.types.transaction_builders.CreateTransactionBuilder→fuels_core.utils.sealed.Sealedfuels_core.types.transaction_builders.ScriptTransactionBuilder→fuels_core.utils.sealed.Sealedfuels_core.types.transaction_builders.TransactionBuilder→fuels_core.utils.sealed.Sealedfuels_core.types.transaction_builders.UpgradeTransactionBuilder→fuels_core.utils.sealed.Sealedfuels_core.types.transaction_builders.UploadTransactionBuilder→fuels_core.utils.sealed.Sealed
- Direction
- fuels_core.types.transaction_builders uses fuels_core.utils.sealed, so a change to fuels_core.utils.sealed can break fuels_core.types.transaction_builders, while a change to fuels_core.types.transaction_builders can't break fuels_core.utils.sealed.
- Position
- Below the diagonal: fuels_core.types.transaction_builders uses a module listed above it, which is the healthy direction.
13→27 fuels_core.types.transaction_builders uses fuels_core.types.wrappers.transaction part of a loop✕
- Connections
- 5 pairs of types, where a type in fuels_core.types.transaction_builders uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_core.types.transaction_builders.CreateTransactionBuilder→fuels_core.types.wrappers.transaction.TxPoliciesfuels_core.types.transaction_builders.ScriptTransactionBuilder→fuels_core.types.wrappers.transaction.TxPoliciesfuels_core.types.transaction_builders.TransactionBuilder→fuels_core.types.wrappers.transaction.TxPoliciesfuels_core.types.transaction_builders.UpgradeTransactionBuilder→fuels_core.types.wrappers.transaction.TxPoliciesfuels_core.types.transaction_builders.UploadTransactionBuilder→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_core.types.transaction_builders uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_core.types.transaction_builders, while a change to fuels_core.types.transaction_builders can't break fuels_core.types.wrappers.transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→5 fuels_accounts.signers.fake uses fuels_core.types.wrappers.message✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.fake uses a type in fuels_core.types.wrappers.message.
- The types involved
fuels_accounts.signers.fake.FakeSigner→fuels_core.types.wrappers.message.Message
- Direction
- fuels_accounts.signers.fake uses fuels_core.types.wrappers.message, so a change to fuels_core.types.wrappers.message can break fuels_accounts.signers.fake, while a change to fuels_accounts.signers.fake can't break fuels_core.types.wrappers.message.
- Position
- Below the diagonal: fuels_accounts.signers.fake uses a module listed above it, which is the healthy direction.
14→10 fuels_accounts.signers.fake uses fuels_core.traits.signer✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.fake uses a type in fuels_core.traits.signer.
- The types involved
fuels_accounts.signers.fake.FakeSigner→fuels_core.traits.signer.Signer
- Direction
- fuels_accounts.signers.fake uses fuels_core.traits.signer, so a change to fuels_core.traits.signer can break fuels_accounts.signers.fake, while a change to fuels_accounts.signers.fake can't break fuels_core.traits.signer.
- Position
- Below the diagonal: fuels_accounts.signers.fake uses a module listed above it, which is the healthy direction.
15→5 fuels_accounts.signers.kms.aws uses fuels_core.types.wrappers.message✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.kms.aws uses a type in fuels_core.types.wrappers.message.
- The types involved
fuels_accounts.signers.kms.aws.AwsKmsSigner→fuels_core.types.wrappers.message.Message
- Direction
- fuels_accounts.signers.kms.aws uses fuels_core.types.wrappers.message, so a change to fuels_core.types.wrappers.message can break fuels_accounts.signers.kms.aws, while a change to fuels_accounts.signers.kms.aws can't break fuels_core.types.wrappers.message.
- Position
- Below the diagonal: fuels_accounts.signers.kms.aws uses a module listed above it, which is the healthy direction.
15→10 fuels_accounts.signers.kms.aws uses fuels_core.traits.signer✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.kms.aws uses a type in fuels_core.traits.signer.
- The types involved
fuels_accounts.signers.kms.aws.AwsKmsSigner→fuels_core.traits.signer.Signer
- Direction
- fuels_accounts.signers.kms.aws uses fuels_core.traits.signer, so a change to fuels_core.traits.signer can break fuels_accounts.signers.kms.aws, while a change to fuels_accounts.signers.kms.aws can't break fuels_core.traits.signer.
- Position
- Below the diagonal: fuels_accounts.signers.kms.aws uses a module listed above it, which is the healthy direction.
15→11 fuels_accounts.signers.kms.aws uses fuels_core.types.errors✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.kms.aws uses a type in fuels_core.types.errors.
- The types involved
fuels_accounts.signers.kms.aws.aws$module→fuels_core.types.errors.Error
- Direction
- fuels_accounts.signers.kms.aws uses fuels_core.types.errors, so a change to fuels_core.types.errors can break fuels_accounts.signers.kms.aws, while a change to fuels_accounts.signers.kms.aws can't break fuels_core.types.errors.
- Position
- Below the diagonal: fuels_accounts.signers.kms.aws uses a module listed above it, which is the healthy direction.
16→5 fuels_accounts.signers.kms.google uses fuels_core.types.wrappers.message✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.kms.google uses a type in fuels_core.types.wrappers.message.
- The types involved
fuels_accounts.signers.kms.google.GoogleKmsSigner→fuels_core.types.wrappers.message.Message
- Direction
- fuels_accounts.signers.kms.google uses fuels_core.types.wrappers.message, so a change to fuels_core.types.wrappers.message can break fuels_accounts.signers.kms.google, while a change to fuels_accounts.signers.kms.google can't break fuels_core.types.wrappers.message.
- Position
- Below the diagonal: fuels_accounts.signers.kms.google uses a module listed above it, which is the healthy direction.
16→10 fuels_accounts.signers.kms.google uses fuels_core.traits.signer✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.kms.google uses a type in fuels_core.traits.signer.
- The types involved
fuels_accounts.signers.kms.google.GoogleKmsSigner→fuels_core.traits.signer.Signer
- Direction
- fuels_accounts.signers.kms.google uses fuels_core.traits.signer, so a change to fuels_core.traits.signer can break fuels_accounts.signers.kms.google, while a change to fuels_accounts.signers.kms.google can't break fuels_core.traits.signer.
- Position
- Below the diagonal: fuels_accounts.signers.kms.google uses a module listed above it, which is the healthy direction.
16→11 fuels_accounts.signers.kms.google uses fuels_core.types.errors✕
- Connections
- 1 pair of types, where a type in fuels_accounts.signers.kms.google uses a type in fuels_core.types.errors.
- The types involved
fuels_accounts.signers.kms.google.google$module→fuels_core.types.errors.Error
- Direction
- fuels_accounts.signers.kms.google uses fuels_core.types.errors, so a change to fuels_core.types.errors can break fuels_accounts.signers.kms.google, while a change to fuels_accounts.signers.kms.google can't break fuels_core.types.errors.
- Position
- Below the diagonal: fuels_accounts.signers.kms.google uses a module listed above it, which is the healthy direction.
17→8 fuels_core.codec.logs uses fuels_core.codec.abi_decoder✕
- Connections
- 3 pairs of types, where a type in fuels_core.codec.logs uses a type in fuels_core.codec.abi_decoder.
- The types involved
fuels_core.codec.logs.ExtractLogIdLazy→fuels_core.codec.abi_decoder.DecoderConfigfuels_core.codec.logs.LogDecoder→fuels_core.codec.abi_decoder.DecoderConfigfuels_core.codec.logs.LogFormatter→fuels_core.codec.abi_decoder.DecoderConfig
- Direction
- fuels_core.codec.logs uses fuels_core.codec.abi_decoder, so a change to fuels_core.codec.abi_decoder can break fuels_core.codec.logs, while a change to fuels_core.codec.logs can't break fuels_core.codec.abi_decoder.
- Position
- Below the diagonal: fuels_core.codec.logs uses a module listed above it, which is the healthy direction.
17→11 fuels_core.codec.logs uses fuels_core.types.errors✕
- Connections
- 1 pair of types, where a type in fuels_core.codec.logs uses a type in fuels_core.types.errors.
- The types involved
fuels_core.codec.logs.LogResult→fuels_core.types.errors.Error
- Direction
- fuels_core.codec.logs uses fuels_core.types.errors, so a change to fuels_core.types.errors can break fuels_core.codec.logs, while a change to fuels_core.codec.logs can't break fuels_core.types.errors.
- Position
- Below the diagonal: fuels_core.codec.logs uses a module listed above it, which is the healthy direction.
18→12 fuels_core.traits.tokenizable uses fuels_core.types.token✕
- Connections
- 1 pair of types, where a type in fuels_core.traits.tokenizable uses a type in fuels_core.types.token.
- The types involved
fuels_core.traits.tokenizable.Tokenizable→fuels_core.types.token.Token
- Direction
- fuels_core.traits.tokenizable uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.traits.tokenizable, while a change to fuels_core.traits.tokenizable can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.traits.tokenizable uses a module listed above it, which is the healthy direction.
19→4 fuels_core.types.transaction_builders.blob uses fuels_core.types.wrappers.input✕
- Connections
- 1 pair of types, where a type in fuels_core.types.transaction_builders.blob uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.types.wrappers.input.Input
- Direction
- fuels_core.types.transaction_builders.blob uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_core.types.transaction_builders.blob, while a change to fuels_core.types.transaction_builders.blob can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_core.types.transaction_builders.blob uses a module listed above it, which is the healthy direction.
19→6 fuels_core.types.transaction_builders.blob uses fuels_core.utils.sealed✕
- Connections
- 1 pair of types, where a type in fuels_core.types.transaction_builders.blob uses a type in fuels_core.utils.sealed.
- The types involved
fuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.utils.sealed.Sealed
- Direction
- fuels_core.types.transaction_builders.blob uses fuels_core.utils.sealed, so a change to fuels_core.utils.sealed can break fuels_core.types.transaction_builders.blob, while a change to fuels_core.types.transaction_builders.blob can't break fuels_core.utils.sealed.
- Position
- Below the diagonal: fuels_core.types.transaction_builders.blob uses a module listed above it, which is the healthy direction.
19→13 fuels_core.types.transaction_builders.blob uses fuels_core.types.transaction_builders✕
- Connections
- 4 pairs of types, where a type in fuels_core.types.transaction_builders.blob uses a type in fuels_core.types.transaction_builders.
- The types involved
fuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.types.transaction_builders.BuildableTransactionfuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.types.transaction_builders.Strategyfuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.types.transaction_builders.TransactionBuilderfuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.types.transaction_builders.UnresolvedWitnessIndexes
- Direction
- fuels_core.types.transaction_builders.blob uses fuels_core.types.transaction_builders, so a change to fuels_core.types.transaction_builders can break fuels_core.types.transaction_builders.blob, while a change to fuels_core.types.transaction_builders.blob can't break fuels_core.types.transaction_builders.
- Position
- Below the diagonal: fuels_core.types.transaction_builders.blob uses a module listed above it, which is the healthy direction.
19→27 fuels_core.types.transaction_builders.blob uses fuels_core.types.wrappers.transaction part of a loop✕
- Connections
- 2 pairs of types, where a type in fuels_core.types.transaction_builders.blob uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_core.types.transaction_builders.blob.Blob→fuels_core.types.wrappers.transaction.BlobTransactionfuels_core.types.transaction_builders.blob.BlobTransactionBuilder→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_core.types.transaction_builders.blob uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_core.types.transaction_builders.blob, while a change to fuels_core.types.transaction_builders.blob can't break fuels_core.types.wrappers.transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 fuels_programs.calls.traits.response_parser uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.traits.response_parser uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_programs.calls.traits.response_parser.ResponseParser→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_programs.calls.traits.response_parser uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_programs.calls.traits.response_parser, while a change to fuels_programs.calls.traits.response_parser can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_programs.calls.traits.response_parser uses a module listed above it, which is the healthy direction.
20→7 fuels_programs.calls.traits.response_parser uses fuels_programs.calls.utils.sealed✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.traits.response_parser uses a type in fuels_programs.calls.utils.sealed.
- The types involved
fuels_programs.calls.traits.response_parser.ResponseParser→fuels_programs.calls.utils.sealed.Sealed
- Direction
- fuels_programs.calls.traits.response_parser uses fuels_programs.calls.utils.sealed, so a change to fuels_programs.calls.utils.sealed can break fuels_programs.calls.traits.response_parser, while a change to fuels_programs.calls.traits.response_parser can't break fuels_programs.calls.utils.sealed.
- Position
- Below the diagonal: fuels_programs.calls.traits.response_parser uses a module listed above it, which is the healthy direction.
20→8 fuels_programs.calls.traits.response_parser uses fuels_core.codec.abi_decoder✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.traits.response_parser uses a type in fuels_core.codec.abi_decoder.
- The types involved
fuels_programs.calls.traits.response_parser.ResponseParser→fuels_core.codec.abi_decoder.DecoderConfig
- Direction
- fuels_programs.calls.traits.response_parser uses fuels_core.codec.abi_decoder, so a change to fuels_core.codec.abi_decoder can break fuels_programs.calls.traits.response_parser, while a change to fuels_programs.calls.traits.response_parser can't break fuels_core.codec.abi_decoder.
- Position
- Below the diagonal: fuels_programs.calls.traits.response_parser uses a module listed above it, which is the healthy direction.
21→2 fuels_core.types.core.bits uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bits uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.types.core.bits.Bits256→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.types.core.bits uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.types.core.bits, while a change to fuels_core.types.core.bits can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.types.core.bits uses a module listed above it, which is the healthy direction.
21→9 fuels_core.types.core.bits uses fuels_core.traits.parameterize✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bits uses a type in fuels_core.traits.parameterize.
- The types involved
fuels_core.types.core.bits.Bits256→fuels_core.traits.parameterize.Parameterize
- Direction
- fuels_core.types.core.bits uses fuels_core.traits.parameterize, so a change to fuels_core.traits.parameterize can break fuels_core.types.core.bits, while a change to fuels_core.types.core.bits can't break fuels_core.traits.parameterize.
- Position
- Below the diagonal: fuels_core.types.core.bits uses a module listed above it, which is the healthy direction.
21→12 fuels_core.types.core.bits uses fuels_core.types.token✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bits uses a type in fuels_core.types.token.
- The types involved
fuels_core.types.core.bits.Bits256→fuels_core.types.token.Token
- Direction
- fuels_core.types.core.bits uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.types.core.bits, while a change to fuels_core.types.core.bits can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.types.core.bits uses a module listed above it, which is the healthy direction.
21→18 fuels_core.types.core.bits uses fuels_core.traits.tokenizable✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bits uses a type in fuels_core.traits.tokenizable.
- The types involved
fuels_core.types.core.bits.Bits256→fuels_core.traits.tokenizable.Tokenizable
- Direction
- fuels_core.types.core.bits uses fuels_core.traits.tokenizable, so a change to fuels_core.traits.tokenizable can break fuels_core.types.core.bits, while a change to fuels_core.types.core.bits can't break fuels_core.traits.tokenizable.
- Position
- Below the diagonal: fuels_core.types.core.bits uses a module listed above it, which is the healthy direction.
22→2 fuels_core.types.core.bytes uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bytes uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.types.core.bytes.Bytes→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.types.core.bytes uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.types.core.bytes, while a change to fuels_core.types.core.bytes can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.types.core.bytes uses a module listed above it, which is the healthy direction.
22→9 fuels_core.types.core.bytes uses fuels_core.traits.parameterize✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bytes uses a type in fuels_core.traits.parameterize.
- The types involved
fuels_core.types.core.bytes.Bytes→fuels_core.traits.parameterize.Parameterize
- Direction
- fuels_core.types.core.bytes uses fuels_core.traits.parameterize, so a change to fuels_core.traits.parameterize can break fuels_core.types.core.bytes, while a change to fuels_core.types.core.bytes can't break fuels_core.traits.parameterize.
- Position
- Below the diagonal: fuels_core.types.core.bytes uses a module listed above it, which is the healthy direction.
22→12 fuels_core.types.core.bytes uses fuels_core.types.token✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bytes uses a type in fuels_core.types.token.
- The types involved
fuels_core.types.core.bytes.Bytes→fuels_core.types.token.Token
- Direction
- fuels_core.types.core.bytes uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.types.core.bytes, while a change to fuels_core.types.core.bytes can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.types.core.bytes uses a module listed above it, which is the healthy direction.
22→18 fuels_core.types.core.bytes uses fuels_core.traits.tokenizable✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.bytes uses a type in fuels_core.traits.tokenizable.
- The types involved
fuels_core.types.core.bytes.Bytes→fuels_core.traits.tokenizable.Tokenizable
- Direction
- fuels_core.types.core.bytes uses fuels_core.traits.tokenizable, so a change to fuels_core.traits.tokenizable can break fuels_core.types.core.bytes, while a change to fuels_core.types.core.bytes can't break fuels_core.traits.tokenizable.
- Position
- Below the diagonal: fuels_core.types.core.bytes uses a module listed above it, which is the healthy direction.
23→2 fuels_core.types.core.raw_slice uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.raw_slice uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.types.core.raw_slice.RawSlice→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.types.core.raw_slice uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.types.core.raw_slice, while a change to fuels_core.types.core.raw_slice can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.types.core.raw_slice uses a module listed above it, which is the healthy direction.
23→9 fuels_core.types.core.raw_slice uses fuels_core.traits.parameterize✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.raw_slice uses a type in fuels_core.traits.parameterize.
- The types involved
fuels_core.types.core.raw_slice.RawSlice→fuels_core.traits.parameterize.Parameterize
- Direction
- fuels_core.types.core.raw_slice uses fuels_core.traits.parameterize, so a change to fuels_core.traits.parameterize can break fuels_core.types.core.raw_slice, while a change to fuels_core.types.core.raw_slice can't break fuels_core.traits.parameterize.
- Position
- Below the diagonal: fuels_core.types.core.raw_slice uses a module listed above it, which is the healthy direction.
23→12 fuels_core.types.core.raw_slice uses fuels_core.types.token✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.raw_slice uses a type in fuels_core.types.token.
- The types involved
fuels_core.types.core.raw_slice.RawSlice→fuels_core.types.token.Token
- Direction
- fuels_core.types.core.raw_slice uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.types.core.raw_slice, while a change to fuels_core.types.core.raw_slice can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.types.core.raw_slice uses a module listed above it, which is the healthy direction.
23→18 fuels_core.types.core.raw_slice uses fuels_core.traits.tokenizable✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.raw_slice uses a type in fuels_core.traits.tokenizable.
- The types involved
fuels_core.types.core.raw_slice.RawSlice→fuels_core.traits.tokenizable.Tokenizable
- Direction
- fuels_core.types.core.raw_slice uses fuels_core.traits.tokenizable, so a change to fuels_core.traits.tokenizable can break fuels_core.types.core.raw_slice, while a change to fuels_core.types.core.raw_slice can't break fuels_core.traits.tokenizable.
- Position
- Below the diagonal: fuels_core.types.core.raw_slice uses a module listed above it, which is the healthy direction.
24→2 fuels_core.types.core.sized_ascii_string uses fuels_core.types.param_types.param_type✕
- Connections
- 2 pairs of types, where a type in fuels_core.types.core.sized_ascii_string uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.types.core.sized_ascii_string.AsciiString→fuels_core.types.param_types.param_type.ParamTypefuels_core.types.core.sized_ascii_string.SizedAsciiString→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.types.core.sized_ascii_string uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.types.core.sized_ascii_string, while a change to fuels_core.types.core.sized_ascii_string can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.types.core.sized_ascii_string uses a module listed above it, which is the healthy direction.
24→9 fuels_core.types.core.sized_ascii_string uses fuels_core.traits.parameterize✕
- Connections
- 2 pairs of types, where a type in fuels_core.types.core.sized_ascii_string uses a type in fuels_core.traits.parameterize.
- The types involved
fuels_core.types.core.sized_ascii_string.AsciiString→fuels_core.traits.parameterize.Parameterizefuels_core.types.core.sized_ascii_string.SizedAsciiString→fuels_core.traits.parameterize.Parameterize
- Direction
- fuels_core.types.core.sized_ascii_string uses fuels_core.traits.parameterize, so a change to fuels_core.traits.parameterize can break fuels_core.types.core.sized_ascii_string, while a change to fuels_core.types.core.sized_ascii_string can't break fuels_core.traits.parameterize.
- Position
- Below the diagonal: fuels_core.types.core.sized_ascii_string uses a module listed above it, which is the healthy direction.
24→12 fuels_core.types.core.sized_ascii_string uses fuels_core.types.token✕
- Connections
- 2 pairs of types, where a type in fuels_core.types.core.sized_ascii_string uses a type in fuels_core.types.token.
- The types involved
fuels_core.types.core.sized_ascii_string.AsciiString→fuels_core.types.token.Tokenfuels_core.types.core.sized_ascii_string.SizedAsciiString→fuels_core.types.token.Token
- Direction
- fuels_core.types.core.sized_ascii_string uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.types.core.sized_ascii_string, while a change to fuels_core.types.core.sized_ascii_string can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.types.core.sized_ascii_string uses a module listed above it, which is the healthy direction.
24→18 fuels_core.types.core.sized_ascii_string uses fuels_core.traits.tokenizable✕
- Connections
- 2 pairs of types, where a type in fuels_core.types.core.sized_ascii_string uses a type in fuels_core.traits.tokenizable.
- The types involved
fuels_core.types.core.sized_ascii_string.AsciiString→fuels_core.traits.tokenizable.Tokenizablefuels_core.types.core.sized_ascii_string.SizedAsciiString→fuels_core.traits.tokenizable.Tokenizable
- Direction
- fuels_core.types.core.sized_ascii_string uses fuels_core.traits.tokenizable, so a change to fuels_core.traits.tokenizable can break fuels_core.types.core.sized_ascii_string, while a change to fuels_core.types.core.sized_ascii_string can't break fuels_core.traits.tokenizable.
- Position
- Below the diagonal: fuels_core.types.core.sized_ascii_string uses a module listed above it, which is the healthy direction.
25→2 fuels_core.types.core.u256 uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.u256 uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_core.types.core.u256.U256→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_core.types.core.u256 uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_core.types.core.u256, while a change to fuels_core.types.core.u256 can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_core.types.core.u256 uses a module listed above it, which is the healthy direction.
25→9 fuels_core.types.core.u256 uses fuels_core.traits.parameterize✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.u256 uses a type in fuels_core.traits.parameterize.
- The types involved
fuels_core.types.core.u256.U256→fuels_core.traits.parameterize.Parameterize
- Direction
- fuels_core.types.core.u256 uses fuels_core.traits.parameterize, so a change to fuels_core.traits.parameterize can break fuels_core.types.core.u256, while a change to fuels_core.types.core.u256 can't break fuels_core.traits.parameterize.
- Position
- Below the diagonal: fuels_core.types.core.u256 uses a module listed above it, which is the healthy direction.
25→12 fuels_core.types.core.u256 uses fuels_core.types.token✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.u256 uses a type in fuels_core.types.token.
- The types involved
fuels_core.types.core.u256.U256→fuels_core.types.token.Token
- Direction
- fuels_core.types.core.u256 uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.types.core.u256, while a change to fuels_core.types.core.u256 can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.types.core.u256 uses a module listed above it, which is the healthy direction.
25→18 fuels_core.types.core.u256 uses fuels_core.traits.tokenizable✕
- Connections
- 1 pair of types, where a type in fuels_core.types.core.u256 uses a type in fuels_core.traits.tokenizable.
- The types involved
fuels_core.types.core.u256.U256→fuels_core.traits.tokenizable.Tokenizable
- Direction
- fuels_core.types.core.u256 uses fuels_core.traits.tokenizable, so a change to fuels_core.traits.tokenizable can break fuels_core.types.core.u256, while a change to fuels_core.types.core.u256 can't break fuels_core.traits.tokenizable.
- Position
- Below the diagonal: fuels_core.types.core.u256 uses a module listed above it, which is the healthy direction.
26→11 fuels_core.types.tx_status uses fuels_core.types.errors✕
- Connections
- 1 pair of types, where a type in fuels_core.types.tx_status uses a type in fuels_core.types.errors.
- The types involved
fuels_core.types.tx_status.TxStatus→fuels_core.types.errors.Error
- Direction
- fuels_core.types.tx_status uses fuels_core.types.errors, so a change to fuels_core.types.errors can break fuels_core.types.tx_status, while a change to fuels_core.types.tx_status can't break fuels_core.types.errors.
- Position
- Below the diagonal: fuels_core.types.tx_status uses a module listed above it, which is the healthy direction.
26→17 fuels_core.types.tx_status uses fuels_core.codec.logs✕
- Connections
- 1 pair of types, where a type in fuels_core.types.tx_status uses a type in fuels_core.codec.logs.
- The types involved
fuels_core.types.tx_status.TxStatus→fuels_core.codec.logs.LogDecoder
- Direction
- fuels_core.types.tx_status uses fuels_core.codec.logs, so a change to fuels_core.codec.logs can break fuels_core.types.tx_status, while a change to fuels_core.types.tx_status can't break fuels_core.codec.logs.
- Position
- Below the diagonal: fuels_core.types.tx_status uses a module listed above it, which is the healthy direction.
27→3 fuels_core.types.wrappers.transaction uses fuels_core.types.wrappers.coin_type_id✕
- Connections
- 1 pair of types, where a type in fuels_core.types.wrappers.transaction uses a type in fuels_core.types.wrappers.coin_type_id.
- The types involved
fuels_core.types.wrappers.transaction.transaction$module→fuels_core.types.wrappers.coin_type_id.CoinTypeId
- Direction
- fuels_core.types.wrappers.transaction uses fuels_core.types.wrappers.coin_type_id, so a change to fuels_core.types.wrappers.coin_type_id can break fuels_core.types.wrappers.transaction, while a change to fuels_core.types.wrappers.transaction can't break fuels_core.types.wrappers.coin_type_id.
- Position
- Below the diagonal: fuels_core.types.wrappers.transaction uses a module listed above it, which is the healthy direction.
27→4 fuels_core.types.wrappers.transaction uses fuels_core.types.wrappers.input✕
- Connections
- 7 pairs of types, where a type in fuels_core.types.wrappers.transaction uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_core.types.wrappers.transaction.BlobTransaction→fuels_core.types.wrappers.input.Inputfuels_core.types.wrappers.transaction.CreateTransaction→fuels_core.types.wrappers.input.Inputfuels_core.types.wrappers.transaction.ScriptTransaction→fuels_core.types.wrappers.input.Inputfuels_core.types.wrappers.transaction.Transaction→fuels_core.types.wrappers.input.Inputfuels_core.types.wrappers.transaction.UpgradeTransaction→fuels_core.types.wrappers.input.Inputfuels_core.types.wrappers.transaction.UploadTransaction→fuels_core.types.wrappers.input.Inputfuels_core.types.wrappers.transaction.transaction$module→fuels_core.types.wrappers.input.Input
- Direction
- fuels_core.types.wrappers.transaction uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_core.types.wrappers.transaction, while a change to fuels_core.types.wrappers.transaction can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_core.types.wrappers.transaction uses a module listed above it, which is the healthy direction.
27→6 fuels_core.types.wrappers.transaction uses fuels_core.utils.sealed✕
- Connections
- 8 pairs of types, where a type in fuels_core.types.wrappers.transaction uses a type in fuels_core.utils.sealed.
- The types involved
fuels_core.types.wrappers.transaction.BlobTransaction→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.CreateTransaction→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.EstimablePredicates→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.ScriptTransaction→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.Transaction→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.UpgradeTransaction→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.UploadTransaction→fuels_core.utils.sealed.Sealedfuels_core.types.wrappers.transaction.ValidatablePredicates→fuels_core.utils.sealed.Sealed
- Direction
- fuels_core.types.wrappers.transaction uses fuels_core.utils.sealed, so a change to fuels_core.utils.sealed can break fuels_core.types.wrappers.transaction, while a change to fuels_core.types.wrappers.transaction can't break fuels_core.utils.sealed.
- Position
- Below the diagonal: fuels_core.types.wrappers.transaction uses a module listed above it, which is the healthy direction.
27→19 fuels_core.types.wrappers.transaction uses fuels_core.types.transaction_builders.blob✕
- Connections
- 1 pair of types, where a type in fuels_core.types.wrappers.transaction uses a type in fuels_core.types.transaction_builders.blob.
- The types involved
fuels_core.types.wrappers.transaction.BlobTransaction→fuels_core.types.transaction_builders.blob.Blob
- Direction
- fuels_core.types.wrappers.transaction uses fuels_core.types.transaction_builders.blob, so a change to fuels_core.types.transaction_builders.blob can break fuels_core.types.wrappers.transaction, while a change to fuels_core.types.wrappers.transaction can't break fuels_core.types.transaction_builders.blob.
- Position
- Below the diagonal: fuels_core.types.wrappers.transaction uses a module listed above it, which is the healthy direction.
28→3 fuels_accounts.account uses fuels_core.types.wrappers.coin_type_id✕
- Connections
- 1 pair of types, where a type in fuels_accounts.account uses a type in fuels_core.types.wrappers.coin_type_id.
- The types involved
fuels_accounts.account.ViewOnlyAccount→fuels_core.types.wrappers.coin_type_id.CoinTypeId
- Direction
- fuels_accounts.account uses fuels_core.types.wrappers.coin_type_id, so a change to fuels_core.types.wrappers.coin_type_id can break fuels_accounts.account, while a change to fuels_accounts.account can't break fuels_core.types.wrappers.coin_type_id.
- Position
- Below the diagonal: fuels_accounts.account uses a module listed above it, which is the healthy direction.
28→26 fuels_accounts.account uses fuels_core.types.tx_status✕
- Connections
- 1 pair of types, where a type in fuels_accounts.account uses a type in fuels_core.types.tx_status.
- The types involved
fuels_accounts.account.WithdrawToBaseResponse→fuels_core.types.tx_status.Success
- Direction
- fuels_accounts.account uses fuels_core.types.tx_status, so a change to fuels_core.types.tx_status can break fuels_accounts.account, while a change to fuels_accounts.account can't break fuels_core.types.tx_status.
- Position
- Below the diagonal: fuels_accounts.account uses a module listed above it, which is the healthy direction.
28→27 fuels_accounts.account uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_accounts.account uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_accounts.account.Account→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_accounts.account uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_accounts.account, while a change to fuels_accounts.account can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_accounts.account uses a module listed above it, which is the healthy direction.
29→27 fuels_accounts.provider.retryable_client uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_accounts.provider.retryable_client uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_accounts.provider.retryable_client.RetryableClient→fuels_core.types.wrappers.transaction.Transaction
- Direction
- fuels_accounts.provider.retryable_client uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_accounts.provider.retryable_client, while a change to fuels_accounts.provider.retryable_client can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_accounts.provider.retryable_client uses a module listed above it, which is the healthy direction.
30→12 fuels_core.codec.abi_encoder.bounded_encoder uses fuels_core.types.token✕
- Connections
- 2 pairs of types, where a type in fuels_core.codec.abi_encoder.bounded_encoder uses a type in fuels_core.types.token.
- The types involved
fuels_core.codec.abi_encoder.bounded_encoder.BoundedEncoder→fuels_core.types.token.StaticStringTokenfuels_core.codec.abi_encoder.bounded_encoder.BoundedEncoder→fuels_core.types.token.Token
- Direction
- fuels_core.codec.abi_encoder.bounded_encoder uses fuels_core.types.token, so a change to fuels_core.types.token can break fuels_core.codec.abi_encoder.bounded_encoder, while a change to fuels_core.codec.abi_encoder.bounded_encoder can't break fuels_core.types.token.
- Position
- Below the diagonal: fuels_core.codec.abi_encoder.bounded_encoder uses a module listed above it, which is the healthy direction.
30→25 fuels_core.codec.abi_encoder.bounded_encoder uses fuels_core.types.core.u256✕
- Connections
- 1 pair of types, where a type in fuels_core.codec.abi_encoder.bounded_encoder uses a type in fuels_core.types.core.u256.
- The types involved
fuels_core.codec.abi_encoder.bounded_encoder.BoundedEncoder→fuels_core.types.core.u256.U256
- Direction
- fuels_core.codec.abi_encoder.bounded_encoder uses fuels_core.types.core.u256, so a change to fuels_core.types.core.u256 can break fuels_core.codec.abi_encoder.bounded_encoder, while a change to fuels_core.codec.abi_encoder.bounded_encoder can't break fuels_core.types.core.u256.
- Position
- Below the diagonal: fuels_core.codec.abi_encoder.bounded_encoder uses a module listed above it, which is the healthy direction.
31→2 fuels_programs.calls.receipt_parser uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.receipt_parser uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_programs.calls.receipt_parser.ReceiptParser→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_programs.calls.receipt_parser uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_programs.calls.receipt_parser, while a change to fuels_programs.calls.receipt_parser can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_programs.calls.receipt_parser uses a module listed above it, which is the healthy direction.
31→8 fuels_programs.calls.receipt_parser uses fuels_core.codec.abi_decoder✕
- Connections
- 2 pairs of types, where a type in fuels_programs.calls.receipt_parser uses a type in fuels_core.codec.abi_decoder.
- The types involved
fuels_programs.calls.receipt_parser.ReceiptParser→fuels_core.codec.abi_decoder.ABIDecoderfuels_programs.calls.receipt_parser.ReceiptParser→fuels_core.codec.abi_decoder.DecoderConfig
- Direction
- fuels_programs.calls.receipt_parser uses fuels_core.codec.abi_decoder, so a change to fuels_core.codec.abi_decoder can break fuels_programs.calls.receipt_parser, while a change to fuels_programs.calls.receipt_parser can't break fuels_core.codec.abi_decoder.
- Position
- Below the diagonal: fuels_programs.calls.receipt_parser uses a module listed above it, which is the healthy direction.
31→11 fuels_programs.calls.receipt_parser uses fuels_core.types.errors✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.receipt_parser uses a type in fuels_core.types.errors.
- The types involved
fuels_programs.calls.receipt_parser.ReceiptParser→fuels_core.types.errors.Error
- Direction
- fuels_programs.calls.receipt_parser uses fuels_core.types.errors, so a change to fuels_core.types.errors can break fuels_programs.calls.receipt_parser, while a change to fuels_programs.calls.receipt_parser can't break fuels_core.types.errors.
- Position
- Below the diagonal: fuels_programs.calls.receipt_parser uses a module listed above it, which is the healthy direction.
31→22 fuels_programs.calls.receipt_parser uses fuels_core.types.core.bytes✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.receipt_parser uses a type in fuels_core.types.core.bytes.
- The types involved
fuels_programs.calls.receipt_parser.ReceiptParser→fuels_core.types.core.bytes.Bytes
- Direction
- fuels_programs.calls.receipt_parser uses fuels_core.types.core.bytes, so a change to fuels_core.types.core.bytes can break fuels_programs.calls.receipt_parser, while a change to fuels_programs.calls.receipt_parser can't break fuels_core.types.core.bytes.
- Position
- Below the diagonal: fuels_programs.calls.receipt_parser uses a module listed above it, which is the healthy direction.
32→4 fuels_programs.calls.traits.transaction_tuner uses fuels_core.types.wrappers.input✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.traits.transaction_tuner uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_programs.calls.traits.transaction_tuner.TransactionTuner→fuels_core.types.wrappers.input.Input
- Direction
- fuels_programs.calls.traits.transaction_tuner uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_programs.calls.traits.transaction_tuner, while a change to fuels_programs.calls.traits.transaction_tuner can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_programs.calls.traits.transaction_tuner uses a module listed above it, which is the healthy direction.
32→7 fuels_programs.calls.traits.transaction_tuner uses fuels_programs.calls.utils.sealed✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.traits.transaction_tuner uses a type in fuels_programs.calls.utils.sealed.
- The types involved
fuels_programs.calls.traits.transaction_tuner.TransactionTuner→fuels_programs.calls.utils.sealed.Sealed
- Direction
- fuels_programs.calls.traits.transaction_tuner uses fuels_programs.calls.utils.sealed, so a change to fuels_programs.calls.utils.sealed can break fuels_programs.calls.traits.transaction_tuner, while a change to fuels_programs.calls.traits.transaction_tuner can't break fuels_programs.calls.utils.sealed.
- Position
- Below the diagonal: fuels_programs.calls.traits.transaction_tuner uses a module listed above it, which is the healthy direction.
32→13 fuels_programs.calls.traits.transaction_tuner uses fuels_core.types.transaction_builders✕
- Connections
- 2 pairs of types, where a type in fuels_programs.calls.traits.transaction_tuner uses a type in fuels_core.types.transaction_builders.
- The types involved
fuels_programs.calls.traits.transaction_tuner.TransactionTuner→fuels_core.types.transaction_builders.ScriptTransactionBuilderfuels_programs.calls.traits.transaction_tuner.TransactionTuner→fuels_core.types.transaction_builders.VariableOutputPolicy
- Direction
- fuels_programs.calls.traits.transaction_tuner uses fuels_core.types.transaction_builders, so a change to fuels_core.types.transaction_builders can break fuels_programs.calls.traits.transaction_tuner, while a change to fuels_programs.calls.traits.transaction_tuner can't break fuels_core.types.transaction_builders.
- Position
- Below the diagonal: fuels_programs.calls.traits.transaction_tuner uses a module listed above it, which is the healthy direction.
32→27 fuels_programs.calls.traits.transaction_tuner uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.traits.transaction_tuner uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_programs.calls.traits.transaction_tuner.TransactionTuner→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_programs.calls.traits.transaction_tuner uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_programs.calls.traits.transaction_tuner, while a change to fuels_programs.calls.traits.transaction_tuner can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_programs.calls.traits.transaction_tuner uses a module listed above it, which is the healthy direction.
33→4 fuels_programs.calls.utils uses fuels_core.types.wrappers.input✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.utils uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_programs.calls.utils.utils$module→fuels_core.types.wrappers.input.Input
- Direction
- fuels_programs.calls.utils uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_programs.calls.utils, while a change to fuels_programs.calls.utils can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_programs.calls.utils uses a module listed above it, which is the healthy direction.
33→13 fuels_programs.calls.utils uses fuels_core.types.transaction_builders✕
- Connections
- 2 pairs of types, where a type in fuels_programs.calls.utils uses a type in fuels_core.types.transaction_builders.
- The types involved
fuels_programs.calls.utils.utils$module→fuels_core.types.transaction_builders.ScriptTransactionBuilderfuels_programs.calls.utils.utils$module→fuels_core.types.transaction_builders.VariableOutputPolicy
- Direction
- fuels_programs.calls.utils uses fuels_core.types.transaction_builders, so a change to fuels_core.types.transaction_builders can break fuels_programs.calls.utils, while a change to fuels_programs.calls.utils can't break fuels_core.types.transaction_builders.
- Position
- Below the diagonal: fuels_programs.calls.utils uses a module listed above it, which is the healthy direction.
33→27 fuels_programs.calls.utils uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.utils uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_programs.calls.utils.utils$module→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_programs.calls.utils uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_programs.calls.utils, while a change to fuels_programs.calls.utils can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_programs.calls.utils uses a module listed above it, which is the healthy direction.
34→26 fuels_programs.contract.regular uses fuels_core.types.tx_status✕
- Connections
- 1 pair of types, where a type in fuels_programs.contract.regular uses a type in fuels_core.types.tx_status.
- The types involved
fuels_programs.contract.regular.DeployResponse→fuels_core.types.tx_status.Success
- Direction
- fuels_programs.contract.regular uses fuels_core.types.tx_status, so a change to fuels_core.types.tx_status can break fuels_programs.contract.regular, while a change to fuels_programs.contract.regular can't break fuels_core.types.tx_status.
- Position
- Below the diagonal: fuels_programs.contract.regular uses a module listed above it, which is the healthy direction.
35→27 fuels_accounts.provider uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_accounts.provider uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_accounts.provider.Provider→fuels_core.types.wrappers.transaction.Transactions
- Direction
- fuels_accounts.provider uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_accounts.provider, while a change to fuels_accounts.provider can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_accounts.provider uses a module listed above it, which is the healthy direction.
35→29 fuels_accounts.provider uses fuels_accounts.provider.retryable_client✕
- Connections
- 1 pair of types, where a type in fuels_accounts.provider uses a type in fuels_accounts.provider.retryable_client.
- The types involved
fuels_accounts.provider.Provider→fuels_accounts.provider.retryable_client.RetryableClient
- Direction
- fuels_accounts.provider uses fuels_accounts.provider.retryable_client, so a change to fuels_accounts.provider.retryable_client can break fuels_accounts.provider, while a change to fuels_accounts.provider can't break fuels_accounts.provider.retryable_client.
- Position
- Below the diagonal: fuels_accounts.provider uses a module listed above it, which is the healthy direction.
36→2 fuels_programs.calls.contract_call uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_programs.calls.contract_call uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→4 fuels_programs.calls.contract_call uses fuels_core.types.wrappers.input✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_core.types.wrappers.input.Input
- Direction
- fuels_programs.calls.contract_call uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→7 fuels_programs.calls.contract_call uses fuels_programs.calls.utils.sealed✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_programs.calls.utils.sealed.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_programs.calls.utils.sealed.Sealed
- Direction
- fuels_programs.calls.contract_call uses fuels_programs.calls.utils.sealed, so a change to fuels_programs.calls.utils.sealed can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_programs.calls.utils.sealed.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→8 fuels_programs.calls.contract_call uses fuels_core.codec.abi_decoder✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_core.codec.abi_decoder.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_core.codec.abi_decoder.DecoderConfig
- Direction
- fuels_programs.calls.contract_call uses fuels_core.codec.abi_decoder, so a change to fuels_core.codec.abi_decoder can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_core.codec.abi_decoder.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→13 fuels_programs.calls.contract_call uses fuels_core.types.transaction_builders✕
- Connections
- 2 pairs of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_core.types.transaction_builders.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_core.types.transaction_builders.ScriptTransactionBuilderfuels_programs.calls.contract_call.ContractCall→fuels_core.types.transaction_builders.VariableOutputPolicy
- Direction
- fuels_programs.calls.contract_call uses fuels_core.types.transaction_builders, so a change to fuels_core.types.transaction_builders can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_core.types.transaction_builders.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→20 fuels_programs.calls.contract_call uses fuels_programs.calls.traits.response_parser✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_programs.calls.traits.response_parser.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_programs.calls.traits.response_parser.ResponseParser
- Direction
- fuels_programs.calls.contract_call uses fuels_programs.calls.traits.response_parser, so a change to fuels_programs.calls.traits.response_parser can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_programs.calls.traits.response_parser.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→27 fuels_programs.calls.contract_call uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_programs.calls.contract_call uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
36→32 fuels_programs.calls.contract_call uses fuels_programs.calls.traits.transaction_tuner✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.contract_call uses a type in fuels_programs.calls.traits.transaction_tuner.
- The types involved
fuels_programs.calls.contract_call.ContractCall→fuels_programs.calls.traits.transaction_tuner.TransactionTuner
- Direction
- fuels_programs.calls.contract_call uses fuels_programs.calls.traits.transaction_tuner, so a change to fuels_programs.calls.traits.transaction_tuner can break fuels_programs.calls.contract_call, while a change to fuels_programs.calls.contract_call can't break fuels_programs.calls.traits.transaction_tuner.
- Position
- Below the diagonal: fuels_programs.calls.contract_call uses a module listed above it, which is the healthy direction.
37→2 fuels_programs.calls.script_call uses fuels_core.types.param_types.param_type✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_core.types.param_types.param_type.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_core.types.param_types.param_type.ParamType
- Direction
- fuels_programs.calls.script_call uses fuels_core.types.param_types.param_type, so a change to fuels_core.types.param_types.param_type can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_core.types.param_types.param_type.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→4 fuels_programs.calls.script_call uses fuels_core.types.wrappers.input✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_core.types.wrappers.input.Input
- Direction
- fuels_programs.calls.script_call uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→7 fuels_programs.calls.script_call uses fuels_programs.calls.utils.sealed✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_programs.calls.utils.sealed.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_programs.calls.utils.sealed.Sealed
- Direction
- fuels_programs.calls.script_call uses fuels_programs.calls.utils.sealed, so a change to fuels_programs.calls.utils.sealed can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_programs.calls.utils.sealed.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→8 fuels_programs.calls.script_call uses fuels_core.codec.abi_decoder✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_core.codec.abi_decoder.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_core.codec.abi_decoder.DecoderConfig
- Direction
- fuels_programs.calls.script_call uses fuels_core.codec.abi_decoder, so a change to fuels_core.codec.abi_decoder can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_core.codec.abi_decoder.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→13 fuels_programs.calls.script_call uses fuels_core.types.transaction_builders✕
- Connections
- 2 pairs of types, where a type in fuels_programs.calls.script_call uses a type in fuels_core.types.transaction_builders.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_core.types.transaction_builders.ScriptTransactionBuilderfuels_programs.calls.script_call.ScriptCall→fuels_core.types.transaction_builders.VariableOutputPolicy
- Direction
- fuels_programs.calls.script_call uses fuels_core.types.transaction_builders, so a change to fuels_core.types.transaction_builders can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_core.types.transaction_builders.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→20 fuels_programs.calls.script_call uses fuels_programs.calls.traits.response_parser✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_programs.calls.traits.response_parser.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_programs.calls.traits.response_parser.ResponseParser
- Direction
- fuels_programs.calls.script_call uses fuels_programs.calls.traits.response_parser, so a change to fuels_programs.calls.traits.response_parser can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_programs.calls.traits.response_parser.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→27 fuels_programs.calls.script_call uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_programs.calls.script_call uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
37→32 fuels_programs.calls.script_call uses fuels_programs.calls.traits.transaction_tuner✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.script_call uses a type in fuels_programs.calls.traits.transaction_tuner.
- The types involved
fuels_programs.calls.script_call.ScriptCall→fuels_programs.calls.traits.transaction_tuner.TransactionTuner
- Direction
- fuels_programs.calls.script_call uses fuels_programs.calls.traits.transaction_tuner, so a change to fuels_programs.calls.traits.transaction_tuner can break fuels_programs.calls.script_call, while a change to fuels_programs.calls.script_call can't break fuels_programs.calls.traits.transaction_tuner.
- Position
- Below the diagonal: fuels_programs.calls.script_call uses a module listed above it, which is the healthy direction.
38→3 fuels_accounts.accounts_utils uses fuels_core.types.wrappers.coin_type_id✕
- Connections
- 1 pair of types, where a type in fuels_accounts.accounts_utils uses a type in fuels_core.types.wrappers.coin_type_id.
- The types involved
fuels_accounts.accounts_utils.accounts_utils$module→fuels_core.types.wrappers.coin_type_id.CoinTypeId
- Direction
- fuels_accounts.accounts_utils uses fuels_core.types.wrappers.coin_type_id, so a change to fuels_core.types.wrappers.coin_type_id can break fuels_accounts.accounts_utils, while a change to fuels_accounts.accounts_utils can't break fuels_core.types.wrappers.coin_type_id.
- Position
- Below the diagonal: fuels_accounts.accounts_utils uses a module listed above it, which is the healthy direction.
38→11 fuels_accounts.accounts_utils uses fuels_core.types.errors✕
- Connections
- 1 pair of types, where a type in fuels_accounts.accounts_utils uses a type in fuels_core.types.errors.
- The types involved
fuels_accounts.accounts_utils.accounts_utils$module→fuels_core.types.errors.Error
- Direction
- fuels_accounts.accounts_utils uses fuels_core.types.errors, so a change to fuels_core.types.errors can break fuels_accounts.accounts_utils, while a change to fuels_accounts.accounts_utils can't break fuels_core.types.errors.
- Position
- Below the diagonal: fuels_accounts.accounts_utils uses a module listed above it, which is the healthy direction.
38→35 fuels_accounts.accounts_utils uses fuels_accounts.provider✕
- Connections
- 1 pair of types, where a type in fuels_accounts.accounts_utils uses a type in fuels_accounts.provider.
- The types involved
fuels_accounts.accounts_utils.accounts_utils$module→fuels_accounts.provider.Provider
- Direction
- fuels_accounts.accounts_utils uses fuels_accounts.provider, so a change to fuels_accounts.provider can break fuels_accounts.accounts_utils, while a change to fuels_accounts.accounts_utils can't break fuels_accounts.provider.
- Position
- Below the diagonal: fuels_accounts.accounts_utils uses a module listed above it, which is the healthy direction.
39→3 fuels_accounts.predicate uses fuels_core.types.wrappers.coin_type_id✕
- Connections
- 1 pair of types, where a type in fuels_accounts.predicate uses a type in fuels_core.types.wrappers.coin_type_id.
- The types involved
fuels_accounts.predicate.Predicate→fuels_core.types.wrappers.coin_type_id.CoinTypeId
- Direction
- fuels_accounts.predicate uses fuels_core.types.wrappers.coin_type_id, so a change to fuels_core.types.wrappers.coin_type_id can break fuels_accounts.predicate, while a change to fuels_accounts.predicate can't break fuels_core.types.wrappers.coin_type_id.
- Position
- Below the diagonal: fuels_accounts.predicate uses a module listed above it, which is the healthy direction.
39→28 fuels_accounts.predicate uses fuels_accounts.account✕
- Connections
- 2 pairs of types, where a type in fuels_accounts.predicate uses a type in fuels_accounts.account.
- The types involved
fuels_accounts.predicate.Predicate→fuels_accounts.account.Accountfuels_accounts.predicate.Predicate→fuels_accounts.account.ViewOnlyAccount
- Direction
- fuels_accounts.predicate uses fuels_accounts.account, so a change to fuels_accounts.account can break fuels_accounts.predicate, while a change to fuels_accounts.predicate can't break fuels_accounts.account.
- Position
- Below the diagonal: fuels_accounts.predicate uses a module listed above it, which is the healthy direction.
39→35 fuels_accounts.predicate uses fuels_accounts.provider✕
- Connections
- 1 pair of types, where a type in fuels_accounts.predicate uses a type in fuels_accounts.provider.
- The types involved
fuels_accounts.predicate.Predicate→fuels_accounts.provider.Provider
- Direction
- fuels_accounts.predicate uses fuels_accounts.provider, so a change to fuels_accounts.provider can break fuels_accounts.predicate, while a change to fuels_accounts.predicate can't break fuels_accounts.provider.
- Position
- Below the diagonal: fuels_accounts.predicate uses a module listed above it, which is the healthy direction.
40→4 fuels_programs.calls.call_handler uses fuels_core.types.wrappers.input✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_core.types.wrappers.input.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_core.types.wrappers.input.Input
- Direction
- fuels_programs.calls.call_handler uses fuels_core.types.wrappers.input, so a change to fuels_core.types.wrappers.input can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_core.types.wrappers.input.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
40→8 fuels_programs.calls.call_handler uses fuels_core.codec.abi_decoder✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_core.codec.abi_decoder.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_core.codec.abi_decoder.DecoderConfig
- Direction
- fuels_programs.calls.call_handler uses fuels_core.codec.abi_decoder, so a change to fuels_core.codec.abi_decoder can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_core.codec.abi_decoder.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
40→13 fuels_programs.calls.call_handler uses fuels_core.types.transaction_builders✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_core.types.transaction_builders.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_core.types.transaction_builders.VariableOutputPolicy
- Direction
- fuels_programs.calls.call_handler uses fuels_core.types.transaction_builders, so a change to fuels_core.types.transaction_builders can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_core.types.transaction_builders.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
40→17 fuels_programs.calls.call_handler uses fuels_core.codec.logs✕
- Connections
- 2 pairs of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_core.codec.logs.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_core.codec.logs.LogDecoderfuels_programs.calls.call_handler.ContractDependency→fuels_core.codec.logs.LogDecoder
- Direction
- fuels_programs.calls.call_handler uses fuels_core.codec.logs, so a change to fuels_core.codec.logs can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_core.codec.logs.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
40→26 fuels_programs.calls.call_handler uses fuels_core.types.tx_status✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_core.types.tx_status.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_core.types.tx_status.TxStatus
- Direction
- fuels_programs.calls.call_handler uses fuels_core.types.tx_status, so a change to fuels_core.types.tx_status can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_core.types.tx_status.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
40→27 fuels_programs.calls.call_handler uses fuels_core.types.wrappers.transaction✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_core.types.wrappers.transaction.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_core.types.wrappers.transaction.TxPolicies
- Direction
- fuels_programs.calls.call_handler uses fuels_core.types.wrappers.transaction, so a change to fuels_core.types.wrappers.transaction can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_core.types.wrappers.transaction.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
40→36 fuels_programs.calls.call_handler uses fuels_programs.calls.contract_call✕
- Connections
- 1 pair of types, where a type in fuels_programs.calls.call_handler uses a type in fuels_programs.calls.contract_call.
- The types involved
fuels_programs.calls.call_handler.CallHandler→fuels_programs.calls.contract_call.CallParameters
- Direction
- fuels_programs.calls.call_handler uses fuels_programs.calls.contract_call, so a change to fuels_programs.calls.contract_call can break fuels_programs.calls.call_handler, while a change to fuels_programs.calls.call_handler can't break fuels_programs.calls.contract_call.
- Position
- Below the diagonal: fuels_programs.calls.call_handler uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Top priorities: 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; Resolve the 78 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (5), utils.rs (4), tokenizable.rs (2); Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +9.6 pts | Medium | Architecture documentation |
| Resolve the 78 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (5), utils.rs (4), tokenizable.rs (2). | +9.4 pts | Medium | Knowledge Freshness |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). | +1.4 pts | Low | Static Analysis (SAST) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.3 pts | Medium | Release Hygiene |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/fuels-code-gen/src/program_bindings/resolved_type.rs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: resolved_type.rs ↔ function_selector.rs |
| packages/fuels-core/src/types/transaction_builders.rs | 7.0 | Near-clean | God Classes: FileTooLong: types/transaction_builders.rs |
| packages/fuels-accounts/src/provider.rs | 7.0 | Near-clean | God Classes: TooManyMethods: Provider |
| packages/fuels-programs/src/calls/call_handler.rs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| packages/fuels-macros/src/derive/parameterize.rs | 7.2 | Near-clean | Code Duplication: Edited copy of a member (22 corresponding lines) |
| e2e/tests/providers.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| packages/fuels-accounts/src/signers/kms/aws.rs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| packages/fuels-code-gen/src/program_bindings/custom_types/enums.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (16 corresponding lines) |
| packages/fuels-programs/src/assembly/script_and_predicate_loader.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (12 corresponding lines) |
| packages/fuels-code-gen/src/program_bindings/custom_types.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| e2e/tests/types_scripts.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| packages/fuels-accounts/src/provider/retryable_client.rs | 8.5 | Near-clean | God Classes: TooManyMethods: RetryableClient |
| packages/fuels-accounts/src/provider/cache.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (27 corresponding lines) |
| packages/fuels-core/src/types/param_types/from_type_application.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (16 corresponding lines) |
| packages/fuels-macros/src/abigen/parsing.rs | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 14+ corresponding lines) |
| packages/fuels-core/src/codec.rs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| packages/fuels-core/src/codec/abi_decoder/bounded_decoder.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 36 dimensions across the health lenses
- 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, 186 of 197 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 80 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares Cargo manifests but commits no Cargo.lock, so its dependency graph was closed from the manifests over the crates.io index, and part of it could not be read: no published release of bollard-stubs satisfies `=1.47.1-rc.27.3.1`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, 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.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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 Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being fuels_core::codec::abi_decoder::decode_as_debug_str::decode_as_debug_str at 21 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: packages/fuels-core/src/codec/abi_decoder/decode_as_debug_str.rs (fuels_core::codec::abi_decoder::decode_as_debug_str::decode_as_debug_str at 21), packages/fuels-core/src/codec/abi_decoder/bounded_decoder.rs (BoundedDecoder::decode_param at 19), packages/fuels-core/src/codec/abi_encoder/bounded_encoder.rs (BoundedEncoder::encode_token at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with transaction_builders.rs, provider.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with provider.rs, retryable_client.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with provider.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
13 duplicated block group(s) detected. 4.0 % of the production lines (972 of 24,324) are in a reported copy. A further 34 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 47 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 11 Edited copy of a member (1 corresponding lines) finding(s) in Code Duplication — start with transaction_builders.rs (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with transaction_builders.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with call_handler.rs, aws.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
11 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 9 of the 11 (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).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 53 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with resolved_type.rs. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
1 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 84 of the 163 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
4 deducted task-comment markers across 24324 LoC (0.0/KLoC) → score 10.0. 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.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with providers.rs (2), custom_types.rs, types_scripts.rs. — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 85 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 11 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
41 finding(s): 0 critical, 39 high, 2 medium, 0 low. 30 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 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.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 29 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (29 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
81 of 84 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/fuels-core/src/types/transaction_builders.rs. Counted over 84 of the 163 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 78 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (5), utils.rs (4), tokenizable.rs (2). — One of this dimension's main actionable groups (78 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with transaction_builders.rs, from_type_application.rs, provider.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: supported_fuel_core_version.rs↔service.rs 64%; predicate.rs↔wallet.rs 64%; function_selector.rs↔types.rs 56%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with resolved_type.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with supported_fuel_core_version.rs, predicate.rs, function_selector.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 49% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Strong | Solid. |
| Security | 64% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 1 markup document under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~14688 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D14 License Compliance — Crate licences not graded — the lock-less Cargo graph could not be read in full
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3486 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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 — Rust suite
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 17 value object(s); a Domain/Aggregates/ValueObjects layer; a Rust domain-layer crate (a .../domain/ clean-architecture layer); a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 85 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 129 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 2% of this repository's production lines — rust (24,324 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 2% of this repository's production lines — rust (24,324 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. 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 — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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)
Critical — 40 finding(s)
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: resolved_type.rs ↔ function_selector.rs packages/fuels-code-gen/src/program_bindings/resolved_type.rs:1
Serious — 67 finding(s)
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:370
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:218
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:346
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:440
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:330
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:204
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:191
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:410
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:424
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:363
- Edited copy of a member (1 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:315
- TodoComment packages/fuels-code-gen/src/program_bindings/custom_types.rs:123
- TodoComment e2e/tests/providers.rs:964
- TodoComment e2e/tests/providers.rs:1251
- TodoComment e2e/tests/types_scripts.rs:356
- Change coupling: supported_fuel_core_version.rs ↔ service.rs packages/fuels-accounts/src/provider/supported_fuel_core_version.rs:1
- Change coupling: predicate.rs ↔ wallet.rs packages/fuels-accounts/src/predicate.rs:1
- Change coupling: function_selector.rs ↔ types.rs packages/fuels-core/src/codec/function_selector.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: types/transaction_builders.rs packages/fuels-core/src/types/transaction_builders.rs
- FileTooLong: src/provider.rs packages/fuels-accounts/src/provider.rs
- TooManyMethods: Provider packages/fuels-accounts/src/provider.rs:123
- TooManyMethods: RetryableClient packages/fuels-accounts/src/provider/retryable_client.rs:44
- Members sharing a duplicated core (4 members, 50+ identical tokens) packages/fuels-core/src/types/transaction_builders.rs:1004
- Members sharing a duplicated core (4 members, 50+ identical tokens) packages/fuels-core/src/types/transaction_builders.rs:1025
- Edited copy of a member (19 corresponding lines) packages/fuels-programs/src/calls/call_handler.rs:573
- Edited copy of a member (19 corresponding lines) packages/fuels-accounts/src/signers/kms/aws.rs:124
- Edited copy of a member (16 corresponding lines) packages/fuels-code-gen/src/program_bindings/custom_types/enums.rs:24
- Edited copy of a member (16 corresponding lines) packages/fuels-core/src/types/param_types/from_type_application.rs:219
- Edited copy of a member (12 corresponding lines) packages/fuels-programs/src/assembly/script_and_predicate_loader.rs:289
- Edited copy of a member (12 corresponding lines) packages/fuels-accounts/src/signers/kms/aws.rs:34
- Duplicated block (12 lines × 2) packages/fuels-core/src/types/transaction_builders.rs:741
- Duplicated block (12 lines × 2) scripts/change-log/src/adapters/octocrab.rs:146
- Duplicated block (10 lines × 2) packages/fuels-core/src/codec/abi_decoder/bounded_decoder.rs:23
- Duplicated block (10 lines × 2) packages/fuels-programs/src/assembly/script_and_predicate_loader.rs:291
- ClassTooLong: Provider packages/fuels-accounts/src/provider.rs:123
- REDACTED
- Edited copy of a member (42 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:716
- Edited copy of a member (22 corresponding lines) packages/fuels-macros/src/derive/parameterize.rs:45
- Edited copy of a member (27 corresponding lines) packages/fuels-accounts/src/provider/cache.rs:102
- Edited copies of one member (3 members, 19+ corresponding lines) packages/fuels-programs/src/calls/call_handler.rs:231
- Edited copies of one member (3 members, 17+ corresponding lines) packages/fuels-macros/src/derive/parameterize.rs:10
- Edited copies of one member (3 members, 27+ corresponding lines) packages/fuels-accounts/src/provider.rs:487
- Edited copies of one member (4 members, 17+ corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:544
- Edited copy of a member (30 corresponding lines) packages/fuels-core/src/types/transaction_builders.rs:918
- Edited copy of a member (15 corresponding lines) packages/fuels-programs/src/calls/call_handler.rs:267
- Edited copy of a member (13 corresponding lines) packages/fuels-accounts/src/provider.rs:413
- Edited copies of one member (3 members, 14+ corresponding lines) packages/fuels-macros/src/abigen/parsing.rs:50
- Edited copy of a member (9 corresponding lines) packages/fuels-programs/src/calls/call_handler.rs:213
- Edited copies of one member (3 members, 10+ corresponding lines) packages/fuels-accounts/src/provider.rs:715
- Edited copy of a member (8 corresponding lines) packages/fuels-accounts/src/signers/kms/aws.rs:82
- Edited copy of a member (5 corresponding lines) packages/fuels-core/src/codec.rs:25
- Duplicated block (24 lines × 4) packages/fuels-core/src/types/transaction_builders.rs:1036
- Duplicated block (18 lines × 2) packages/fuels-accounts/src/provider.rs:497
- Duplicated block (16 lines × 2) packages/fuels-core/src/types/transaction_builders.rs:717
- Duplicated block (15 lines × 3) packages/fuels-programs/src/calls/call_handler.rs:232
- Duplicated block (12–14 lines × 2) packages/fuels-code-gen/src/program_bindings/custom_types/enums.rs:83
- Duplicated block (12–13 lines × 4) packages/fuels-core/src/types/transaction_builders.rs:1005
- Duplicated block (11–12 lines × 2) packages/fuels-programs/src/calls/call_handler.rs:201
- Duplicated block (9 lines × 2) packages/fuels-macros/src/derive/parameterize.rs:49
- Duplicated block (7 lines × 3) packages/fuels-macros/src/derive/parameterize.rs:11
- Off the main sequence: fuels-code-gen
- Low cohesion: TypeResolver (LCOM4 7) packages/fuels-code-gen/src/program_bindings/resolved_type.rs:98
Minor — 89 finding(s)
- Orphaned file packages/fuels-code-gen/src/program_bindings/resolved_type.rs:1
- Orphaned file packages/fuels-core/src/codec/abi_decoder.rs:1
- Orphaned file packages/fuels-code-gen/src/program_bindings/custom_types.rs:1
- Orphaned file packages/fuels-programs/src/calls/call_handler.rs:1
- Orphaned file packages/fuels-core/src/types/wrappers/transaction.rs:1
- Orphaned file packages/fuels-programs/src/calls/utils.rs:1
- Orphaned file packages/fuels-core/src/traits/tokenizable.rs:1
- Orphaned file wasm-tests/src/lib.rs:1
- Orphaned file packages/fuels-accounts/src/account.rs:1
- Orphaned file packages/fuels-core/src/codec/abi_encoder.rs:1
- Orphaned file packages/fuels-code-gen/src/program_bindings/abigen/bindings/contract.rs:1
- Orphaned file packages/fuels-programs/src/assembly/script_and_predicate_loader.rs:1
- Orphaned file packages/fuels-programs/src/executable.rs:1
- Orphaned file packages/fuels-programs/src/debug.rs:1
- Orphaned file packages/fuels-accounts/src/provider/cache.rs:1
- Orphaned file packages/fuels-programs/src/assembly/contract_call.rs:1
- Orphaned file packages/fuels-test-helpers/src/lib.rs:1
- Orphaned file packages/fuels-programs/src/contract.rs:1
- Orphaned file packages/fuels-accounts/src/provider/retry_util.rs:1
- Orphaned file packages/fuels-code-gen/src/program_bindings/generated_code.rs:1
- Orphaned file packages/fuels-core/src/types/tx_status.rs:1
- Orphaned file packages/fuels-core/src/codec/abi_decoder/decode_as_debug_str.rs:1
- Orphaned file packages/fuels-code-gen/src/program_bindings/abigen/bindings/script.rs:1
- Orphaned file packages/fuels-core/src/types/core/sized_ascii_string.rs:1
- Orphaned file packages/fuels-test-helpers/src/accounts.rs:1
- Most significant orphaned file packages/fuels-core/src/types/transaction_builders.rs:1
- Most significant orphaned file packages/fuels-core/src/types/param_types/from_type_application.rs:1
- Most significant orphaned file packages/fuels-accounts/src/provider.rs:1
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
Minor — 1 finding(s)
- Outdated: tai64
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-60fc1bd1431745b2bf8cfbff6062b74f/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-60fc1bd1431745b2bf8cfbff6062b74f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-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 . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, 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. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |