Public report of aws-amplify/amplify-flutter, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 22:10 UTC · Survey ID cd_bf2eea030b874fbdb9103c465fd59bf2

aws-amplify/amplify-flutter

Measured 17 November 2026, 22:09 UTC, at code version f418245

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).

Knowledge freshness is not measured: Freshness signal contradicted by repo activity.

CAI score 30.6out of 100 At risk Down 16.6 since the last survey

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

A large codebase: 180,319 lines of product code in 82 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Event Sourcing, 10.0

Findings by how serious they are

326 critical 1477 serious 155 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 22:09 UTC

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

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

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

77of 77 dimensions measured by tools.
1940of 1958 findings point to an exact file and line, so you can open each one in the code. The other 18 concern the repository as a whole, such as missing documentation.
77dimensions across 9 lenses, read from 180,319 lines of product code in 82 projects.
Chapters

Executive summary

aws-amplify/amplify-flutter is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because it has recorded events that can be changed afterwards. It scores 30.6 out of 100, which the At risk rating leaves unchanged.

Event Sourcing, at 10.0, is the weakest lens and counts most in the score. The best first step is making the events unchangeable, worth about 17.2 points. Raising Event Sourcing to 70 would lift the score to about 47.2.

246 secrets can leak from the build pipeline. Thirty-four known security holes in the packages the code depends on can be used by attackers. Limiting each secret to its own step and updating the vulnerable packages would close both risks. Passing outside input through environment variables would fix the 25 pipeline steps that put outside input straight into a shell command, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first. Making recorded events unchangeable would take care of the 11 recorded events that can be changed afterwards.

The product code is 180,319 lines, about €220,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Event Sourcing 10.0 · counts for 45%Code Health 38.4 · counts for 25%Production Readiness 41.3 · counts for 14%Performance 60.0 · counts for 8%Security and Compliance 62.1 · counts for 4%Event-Driven 80.0 · counts for 2%Maturity 81.1 · counts for 1%Architecture 86.5 · counts for 1%Domain Modelling 100.0 · counts for 0%

If Event Sourcing rose from 10.0 to 70, the lowest score rated Strong, the score would rise from 30.6 to about 47.2.

Code composition: what the lines of code are
Product code 70%Tests 30%
New since the last survey: 227 findings

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

  • Cyclomatic Complexity · GlobalConstraintsUpdater.update (cyclomatic 17) packages/aft/lib/src/constraints_updater.dart
  • Cognitive Complexity · GlobalConstraintsUpdater.update (cognitive 46) packages/aft/lib/src/constraints_updater.dart
  • Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStoreError.swift
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift
  • Code Duplication · Edited copy of a member (93 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart
  • Code Duplication · Edited copy of a member (72 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_device_password_verifier_worker.dart
  • Code Duplication · Edited copy of a member (47 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart
  • Code Duplication · Edited copy of a member (39 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift
  • Code Duplication · Edited copy of a member (35 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart
  • Code Duplication · Edited copy of a member (26 corresponding lines) packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart
  • Code Duplication · Edited copy of a member (54 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt
  • Code Duplication · Edited copy of a member (35 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift
  • Code Duplication · Edited copy of a member (35 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart
  • Code Duplication · Edited copy of a member (37 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt
  • Code Duplication · Edited copy of a member (31 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedCustomType.kt
  • Code Duplication · Edited copy of a member (45 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart
  • Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift
  • Code Duplication · Edited copies of one member (6 members, 23+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift
  • Code Duplication · Edited copy of a member (45 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart
  • Code Duplication · Edited copy of a member (33 corresponding lines) packages/kinesis/amplify_firehose_dart/lib/src/impl/firehose_sender.dart
  • Code Duplication · Edited copy of a member (37 corresponding lines) packages/storage/amplify_storage_s3_dart/lib/src/amplify_storage_s3_dart_impl.dart
  • Code Duplication · Edited copy of a member (26 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreError.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart
  • Code Duplication · Edited copy of a member (26 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift
  • Code Duplication · Edited copy of a member (28 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart
  • Code Duplication · Edited copy of a member (30 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/amplify_datastore/lib/src/method_channel_datastore.dart
  • Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart
  • Code Duplication · Edited copy of a member (23 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart
  • Code Duplication · Edited copy of a member (19 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift
  • Code Duplication · Edited copy of a member (25 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart
  • Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift
  • Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) packages/smithy/smithy_aws/lib/src/protocol/aws_query_protocol.dart
  • Code Duplication · Edited copy of a member (24 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/smithy/smithy_codegen/lib/src/generator/visitors/library_visitor.dart
  • Code Duplication · Edited copy of a member (13 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Error/AuthError.swift
  • Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift
  • Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/inherited_auth_bloc.dart
  • Code Duplication · Edited copy of a member (22 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyInProcessReportingOperation.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) packages/smithy/smithy_codegen/lib/src/generator/visitors/symbol_visitor.dart
  • Code Duplication · Edited copy of a member (17 corresponding lines) packages/amplify_datastore/lib/src/method_channel_datastore.dart
  • Code Duplication · Edited copy of a member (32 corresponding lines) packages/aft/lib/src/commands/publish_command.dart
  • Code Duplication · Edited copy of a member (13 corresponding lines) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart
  • Code Duplication · Edited copies of one member (5 members, 19+ corresponding lines) packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/smithy/smithy/lib/src/protocol/json_serializer.dart
  • Code Duplication · Edited copy of a member (13 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/QueryPredicate+GraphQL.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Request/GraphQLOperationRequest.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStore.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) packages/amplify_core/lib/src/types/models/auth_rule.dart
  • Code Duplication · Edited copy of a member (19 corresponding lines) packages/amplify_core/lib/src/types/models/model_field_definition.dart
  • Code Duplication · Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) packages/amplify_core/lib/src/types/models/model_field_definition.dart
  • Code Duplication · Edited copy of a member (22 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Operation/AmplifyOperation+APIPublishers.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) packages/auth/amplify_auth_cognito/darwin/amplify_auth_cognito/Sources/amplify_auth_cognito/AmplifyAuthCognitoPlugin.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) packages/aft/lib/src/commands/bootstrap_command.dart
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) packages/amplify_native_legacy_wrapper/darwin/amplify_native_legacy_wrapper/Sources/amplify_native_legacy_wrapper/AmplifyNativeLegacyWrapperPlugin.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift
  • Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart
  • Code Duplication · Edited copy of a member (11 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/AWSModelReconciliationQueue.swift
  • Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart
  • Code Duplication · Edited copy of a member (17 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/authenticator_state.dart
  • Code Duplication · Edited copy of a member (19 corresponding lines) packages/aws_common/lib/src/io/aws_file_platform_html.dart
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/SortedList.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/AuthRule.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) packages/amplify_core/lib/src/types/analytics/analytics/custom_properties.dart
  • Code Duplication · Edited copy of a member (11 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift
  • Code Duplication · Edited copies of one member (8 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift
  • Code Duplication · Edited copies of one member (6 members, 11+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyInProcessReportingOperation.swift
  • Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/amplify_datastore/lib/amplify_datastore.dart
  • Code Duplication · Edited copy of a member (17 corresponding lines) packages/smithy/smithy/lib/src/ast/traits/aws/protocols/rest_json_1_trait.dart
  • Code Duplication · Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/ErrorUtil.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/inherited_config.dart
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/secure_storage/amplify_secure_storage_dart/lib/src/platforms/amplify_secure_storage_web.dart
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/Internal/HubCategory+CategoryConfigurable.swift

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

Fixed since the last survey: 129 findings

These 129 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · _ConstraintsUpdateCommand.run (cyclomatic 20) packages/aft/lib/src/commands/constraints_command.dart
  • Cognitive Complexity · _ConstraintsUpdateCommand.run (cognitive 50) packages/aft/lib/src/commands/constraints_command.dart
  • Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_worker.worker.js.dart
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStoreError.swift
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift
  • Code Duplication · Duplicated block (30 lines × 7) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_worker.worker.js.dart
  • Code Duplication · Duplicated block (20 lines × 2) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart
  • Code Duplication · Duplicated block (16 lines × 24) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart
  • Code Duplication · Duplicated block (16 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart
  • Code Duplication · Duplicated block (12 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart
  • Code Duplication · Duplicated block (11 lines × 2) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart
  • Code Duplication · Duplicated block (10 lines × 4) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart
  • Code Duplication · Duplicated block (9 lines × 4) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart
  • Code Duplication · Duplicated block (9 lines × 2) packages/amplify_core/lib/src/types/models/model_field.dart
  • Code Duplication · Duplicated block (7 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_device_info_collector.js.dart
  • Code Duplication · Duplicated block (7 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart
  • Code Duplication · Duplicated block (27 lines × 2) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt
  • Code Duplication · Duplicated block (18 lines × 2) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt
  • Code Duplication · Duplicated block (19 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift
  • Code Duplication · Duplicated block (17 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift
  • Code Duplication · Duplicated block (11–12 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift
  • Code Duplication · Duplicated block (10–11 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreHubEventStreamHandler.swift
  • Code Duplication · Duplicated block (10 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift
  • Code Duplication · Duplicated block (10 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreHubEventStreamHandler.swift
  • Code Duplication · Duplicated block (10 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift
  • Code Duplication · Duplicated block (5 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/SelectionSet.swift
  • Code Duplication · Duplicated block (20 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLMutation.swift
  • Code Duplication · Duplicated block (13 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadDataRequest.swift
  • Code Duplication · Duplicated block (14 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadFileRequest.swift
  • Code Duplication · Duplicated block (7 lines × 2) canaries/ios/Runner/AppDelegate.swift
  • Code Duplication · Duplicated block (6 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift
  • Code Duplication · Duplicated block (5 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthChangePasswordRequest.swift
  • Code Duplication · Duplicated block (11 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift
  • Churn × Complexity Hotspots · Repeated repair: packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/auth-user-extensions/delete-user-lambda.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/auth-user-extensions/auth-user-extensions.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/storage/main/amplify/storage/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/auth-user-extensions/user-graphql.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/analytics-extensions/pinpoint.ts
  • Test Coverage · No test reaches this file infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts
  • Test Coverage · No test reaches this file infra/lib/auth/custom-authorizer-user-pools/stack.api-handler.ts
  • Test Coverage · No test reaches this file canaries/amplify/backend/function/canaries741cf74ePreSignup/src/index.js
  • Test Coverage · No test reaches this file infra/lib/auth/stack.pre-sign-up.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/no-unauth-identities/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/kinesis/main/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts
  • Test Coverage · No test reaches this file infra/lib/auth/stack.custom-email-sender.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/main/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/no-unauth-access/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/lambda-triggers/pre-sign-up.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/email-sign-in/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-optional-sms/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-required-sms/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/phone-sign-in/amplify/backend.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/username-login-mfa/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/expiration.ts
  • Test Coverage · No test reaches this file infra/lib/auth/stack.custom-sms-sender.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-optional-email-sms/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-optional-email-totp/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-required-email-sms/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-required-email-totp/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-optional-email/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-required-email/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/main/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/no-unauth-access/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/no-unauth-identities/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/api/api-multi-auth/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/storage/dots-in-name/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/storage/main/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts
  • Test Coverage · No test reaches this file infra/lib/auth/custom-auth-without-srp/verify-auth-challenge.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/storage/dots-in-name/amplify/storage/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/api/api-multi-auth/amplify/functions/rest-api/handler.ts
  • Test Coverage · No test reaches this file infra/lib/auth/custom-auth-with-srp/create-auth-challenge.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/kinesis/firehose/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/kinesis/main/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/email-sign-in/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-optional-sms/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/mfa-required-sms/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/auth/phone-sign-in/amplify/auth/resource.ts
  • Test Coverage · No test reaches this file infra/lib/auth/custom-authorizer-user-pools/stack.auto-confirm.ts
  • Test Coverage · No test reaches this file infra-gen2/infra-common/src/index.ts
  • Test Coverage · No test reaches this file canaries/amplify/backend/function/canaries741cf74ePreSignup/src/custom.js
  • Test Coverage · No test reaches this file infra-gen2/backends/api/api-multi-auth/amplify/functions/rest-api/resource.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/main/amplify/auth/pre-sign-up-handler.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/no-unauth-access/amplify/auth/pre-sign-up-handler.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/analytics/no-unauth-identities/amplify/auth/pre-sign-up-handler.ts
  • Test Coverage · No test reaches this file infra-gen2/backends/api/api-multi-auth/amplify/auth/pre-sign-up-handler.ts
Rebuild cost: about €220,000 · Estimate
Cost to rebuild€73,000 to €370,000, for 1,218 to 3,864 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 31. 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.
SizeLarge: 180,319 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 11 finding(s) in Immutable events.
Raises the score by about 17.2 points · Medium effort · Immutable events
2
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 2.2 points · Medium effort · Dead Code
3
Act on each finding's own remediation rather than one rule: the move depends on what recurs.
Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Raises the score by about 2.1 points · Medium effort · Code Duplication

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €220,000 to build again, about 1.5 person-years of work. Its weakest lens is Event Sourcing, at 10.0 (Critical). Event Sourcing is about whether the stored history the system is built on can be trusted. Because the weakest lens counts most in the score, work on Event Sourcing also moves the score most.
Based on: the rebuild estimate · the Event Sourcing grade · how much each lens counts
What to do: Start with the Event Sourcing actions in Top priorities.
If you do one thing first · First action
Resolve the 11 finding(s) in Immutable events. Of all the actions in this report, it raises the score most for the work it takes: about 17.2 points for medium effort, because it clears the 11 Immutable events findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 10% on every change. The history of the code shows how much it changes: about 6,734 lines over the last 90 days, which is about 27,310 lines a year. At that pace, the extra work comes to an estimated 3.1 to 18.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch actions (npm) actions (npm) actions (pub) actions (pub) aft aft aws_common aws_common aft->aws_common smithy smithy aft->smithy smithy_codegen smithy_codegen aft->smithy_codegen amplified_todo amplified_todo amplify_analytics_pinpoint (Gradle) amplify_analytics_pinpoint (Gradle) amplify_analytics_pinpoint (pub) amplify_analytics_pinpoint (pub) amplify_analytics_pinpoint_dart amplify_analytics_pinpoint_dart amplify_api amplify_api amplify_api_dart amplify_api_dart amplify_auth_cognito (Gradle) amplify_auth_cognito (Gradle) amplify_auth_cognito (SwiftPM) amplify_auth_cognito (SwiftPM) amplify_auth_cognito (pub) amplify_auth_cognito (pub) amplify_auth_cognito_dart amplify_auth_cognito_dart amplify_authenticator amplify_authenticator amplify_push_notifications (SwiftPM) amplify_push_notifications (SwiftPM) amplify_push_notifications_objc amplify_push_notifications_objc amplify_push_notifications (SwiftPM)->amplify_push_notifications_objc goldens (pub) goldens (pub) goldens (pub)->aws_common goldens (pub)->smithy __more__ +62 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

105 modules, with 59 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 com.amazonaws.amplify.amplify_auth_cognito3 com.amazonaws.amplify.amplify_datastore.pigeons4 com.amazonaws.amplify.amplify_native_legacy_wrapper.pigeons5 com.amazonaws.amplify.amplify_push_notifications6 com.amazonaws.amplify.amplify_secure_storage.pigeons7 infra-gen2.infra-common.src.lambda-triggers.create-user8 infra-gen2.infra-common.src.lambda-triggers.delete-user9 infra-gen2.infra-common.src.lambda-triggers.enable-sms-mfa10 infra.lib.common11 SmithyVersion12 com.amazonaws.amplify.amplify_auth_cognito.HostedUiException13 com.amazonaws.amplify.amplify_auth_cognito.LegacyCredentialStoreData14 com.amazonaws.amplify.amplify_auth_cognito.LegacyDeviceDetailsSecret15 com.amazonaws.amplify.amplify_auth_cognito.NativeAuthBridge16 com.amazonaws.amplify.amplify_auth_cognito.NativeUserContextData17 com.amazonaws.amplify.amplify_datastore18 com.amazonaws.amplify.amplify_datastore.pigeons.LegacyCredentialStoreData19 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAWSCredentials20 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAmplifyBridge21 com.amazonaws.amplify.amplify_datastore.pigeons.NativeApiBridge22 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthBridge23 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthSession24 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthUser25 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLRequest26 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLResponse27 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLSubscriptionResponse28 com.amazonaws.amplify.amplify_datastore.pigeons.NativeUserPoolTokens29 infra-gen2.infra-common.src.lambda-triggers30 infra.lib.auth31 packages~amplify_native_legacy_wrapper~darwin~amplify_native_legacy_wrapper~amplify_native_legacy_wrapper32 repository.src33 com.amazonaws.amplify.amplify_datastore.AmplifyDataStorePlugin34 com.amazonaws.amplify.amplify_datastore.FlutterModelProvider35 packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore36 packages~auth~amplify_auth_cognito~darwin~amplify_auth_cognito~amplify_auth_cognito37 packages~notifications~push~amplify_push_notifications~darwin~amplify_push_notifications~amplify_push_notifications38 packages~secure_storage~amplify_secure_storage~ios~amplify_secure_storage~amplify_secure_storage39 packages~secure_storage~amplify_secure_storage~macos~amplify_secure_storage~amplify_secure_storage40 repository
1 (global)
2 com.amazonaws.amplify.amplify_auth_cognito
3 com.amazonaws.amplify.amplify_datastore.pigeons
4 com.amazonaws.amplify.amplify_native_legacy_wrapper.pigeons
5 com.amazonaws.amplify.amplify_push_notifications
6 com.amazonaws.amplify.amplify_secure_storage.pigeons
7 infra-gen2.infra-common.src.lambda-triggers.create-user
8 infra-gen2.infra-common.src.lambda-triggers.delete-user
9 infra-gen2.infra-common.src.lambda-triggers.enable-sms-mfa
10 infra.lib.common
11 SmithyVersion2
12 com.amazonaws.amplify.amplify_auth_cognito.HostedUiException4
13 com.amazonaws.amplify.amplify_auth_cognito.LegacyCredentialStoreData1
14 com.amazonaws.amplify.amplify_auth_cognito.LegacyDeviceDetailsSecret1
15 com.amazonaws.amplify.amplify_auth_cognito.NativeAuthBridge1
16 com.amazonaws.amplify.amplify_auth_cognito.NativeUserContextData1
17 com.amazonaws.amplify.amplify_datastore8
18 com.amazonaws.amplify.amplify_datastore.pigeons.LegacyCredentialStoreData1
19 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAWSCredentials1
20 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAmplifyBridge1
21 com.amazonaws.amplify.amplify_datastore.pigeons.NativeApiBridge1
22 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthBridge1
23 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthSession1
24 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthUser1
25 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLRequest1
26 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLResponse1
27 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLSubscriptionResponse1
28 com.amazonaws.amplify.amplify_datastore.pigeons.NativeUserPoolTokens1
29 infra-gen2.infra-common.src.lambda-triggers222
30 infra.lib.auth222
31 packages~amplify_native_legacy_wrapper~darwin~amplify_native_legacy_wrapper~amplify_native_legacy_wrapper1
32 repository.src10
33 com.amazonaws.amplify.amplify_datastore.AmplifyDataStorePlugin11
34 com.amazonaws.amplify.amplify_datastore.FlutterModelProvider1
35 packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore307
36 packages~auth~amplify_auth_cognito~darwin~amplify_auth_cognito~amplify_auth_cognito119
37 packages~notifications~push~amplify_push_notifications~darwin~amplify_push_notifications~amplify_push_notifications12
38 packages~secure_storage~amplify_secure_storage~ios~amplify_secure_storage~amplify_secure_storage43
39 packages~secure_storage~amplify_secure_storage~macos~amplify_secure_storage~amplify_secure_storage43
40 repository211
Uses a module listed above itPart of a loopThe module itself
1 (global)2 com.amazonaws.amplify.amplify_auth_cognito3 com.amazonaws.amplify.amplify_datastore.pigeons4 com.amazonaws.amplify.amplify_native_legacy_wrapper.pigeons5 com.amazonaws.amplify.amplify_push_notifications6 com.amazonaws.amplify.amplify_secure_storage.pigeons7 infra-gen2.infra-common.src.lambda-triggers.create-user8 infra-gen2.infra-common.src.lambda-triggers.delete-user9 infra-gen2.infra-common.src.lambda-triggers.enable-sms-mfa10 infra.lib.common11 SmithyVersion12 com.amazonaws.amplify.amplify_auth_cognito.HostedUiException13 com.amazonaws.amplify.amplify_auth_cognito.LegacyCredentialStoreData14 com.amazonaws.amplify.amplify_auth_cognito.LegacyDeviceDetailsSecret15 com.amazonaws.amplify.amplify_auth_cognito.NativeAuthBridge16 com.amazonaws.amplify.amplify_auth_cognito.NativeUserContextData17 com.amazonaws.amplify.amplify_datastore18 com.amazonaws.amplify.amplify_datastore.pigeons.LegacyCredentialStoreData19 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAWSCredentials20 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAmplifyBridge21 com.amazonaws.amplify.amplify_datastore.pigeons.NativeApiBridge22 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthBridge23 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthSession24 com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthUser25 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLRequest26 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLResponse27 com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLSubscriptionResponse28 com.amazonaws.amplify.amplify_datastore.pigeons.NativeUserPoolTokens29 infra-gen2.infra-common.src.lambda-triggers30 infra.lib.auth31 packages~amplify_native_legacy_wrapper~darwin~amplify_native_legacy_wrapper~amplify_native_legacy_wrapper32 repository.src33 com.amazonaws.amplify.amplify_datastore.AmplifyDataStorePlugin34 com.amazonaws.amplify.amplify_datastore.FlutterModelProvider35 packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore36 packages~auth~amplify_auth_cognito~darwin~amplify_auth_cognito~amplify_auth_cognito37 packages~notifications~push~amplify_push_notifications~darwin~amplify_push_notifications~amplify_push_notifications38 packages~secure_storage~amplify_secure_storage~ios~amplify_secure_storage~amplify_secure_storage39 packages~secure_storage~amplify_secure_storage~macos~amplify_secure_storage~amplify_secure_storage40 repository(global)1com.amazonaws.amplify.amplify_auth_cognito2com.amazonaws.amplify.amplify_datastore.pigeons3com.amazonaws.amplify.amplify_native_legacy_wrapper.pigeons4com.amazonaws.amplify.amplify_push_notifications5com.amazonaws.amplify.amplify_secure_storage.pigeons6infra-gen2.infra-common.src.lambda-triggers.create-user7infra-gen2.infra-common.src.lambda-triggers.delete-user8infra-gen2.infra-common.src.lambda-triggers.enable-sms-mfa9infra.lib.common10SmithyVersion11com.amazonaws.amplify.amplify_auth_cognito.HostedUiException12com.amazonaws.amplify.amplify_auth_cognito.LegacyCredentialStoreData13com.amazonaws.amplify.amplify_auth_cognito.LegacyDeviceDetailsSecret14com.amazonaws.amplify.amplify_auth_cognito.NativeAuthBridge15com.amazonaws.amplify.amplify_auth_cognito.NativeUserContextData16com.amazonaws.amplify.amplify_datastore17com.amazonaws.amplify.amplify_datastore.pigeons.LegacyCredentialStoreData18com.amazonaws.amplify.amplify_datastore.pigeons.NativeAWSCredentials19com.amazonaws.amplify.amplify_datastore.pigeons.NativeAmplifyBridge20com.amazonaws.amplify.amplify_datastore.pigeons.NativeApiBridge21com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthBridge22com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthSession23com.amazonaws.amplify.amplify_datastore.pigeons.NativeAuthUser24com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLRequest25com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLResponse26com.amazonaws.amplify.amplify_datastore.pigeons.NativeGraphQLSubscriptionResponse27com.amazonaws.amplify.amplify_datastore.pigeons.NativeUserPoolTokens28infra-gen2.infra-common.src.lambda-triggers29infra.lib.auth30packages~amplify_native_legacy_wrapper~darwin~amplify_native_legacy_wrapper~amplify_native_legacy_wrapper31repository.src32com.amazonaws.amplify.amplify_datastore.AmplifyDataStorePlugin33com.amazonaws.amplify.amplify_datastore.FlutterModelProvider34packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore35packages~auth~amplify_auth_cognito~darwin~amplify_auth_cognito~amplify_auth_cognito36packages~notifications~push~amplify_push_notifications~darwin~amplify_push_notifications~amplify_push_notifications37packages~secure_storage~amplify_secure_storage~ios~amplify_secure_storage~amplify_secure_storage38packages~secure_storage~amplify_secure_storage~macos~amplify_secure_storage~amplify_secure_storage39repository40241111811111111111222222110111307119124343211+65 more modules (most-connected shown)

At a glance — Code Health · 38.4 · Weak · gated by R10, R7 ·

At a glance — Architecture · 86.5 · Strong ·

At a glance — Maturity · 81.1 · Strong ·

At a glance — Readiness · 41.3 · Weak · gated by R4, P3, P7 ·

At a glance — Security · 62.1 · Adequate · gated by D29, D36 ·

At a glance — Domain Modelling · 100.0 · Exemplary ·

At a glance — Event-Driven · 80.0 · Strong ·

At a glance — Event Sourcing · 10.0 · Critical · gated by ES2 ·

At a glance — Performance · 60.0 · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection281High / Critical
A03:2025 — Software Supply Chain Failures69High / Critical
A02:2025 — Security Misconfiguration4Medium

Roadmap

Top priorities: Resolve the 11 finding(s) in Immutable events; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.

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

Do thisHelpsEffortDimension
Resolve the 11 finding(s) in Immutable events.+17.2 ptsMediumImmutable events
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+2.2 ptsMediumDead Code
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.+2.1 ptsMediumCode Duplication
Add tests that import the unreached modules (directly or through their public entry).+1.9 ptsMediumTest Coverage
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.+1.1 ptsMediumCancellation propagation
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.+1.1 ptsMediumAsync & latency hygiene
Prune the dead entries from your analyzer's `exclude:` list — each one names a path that is not in the repository, so the list no longer describes what is actually being skipped.+0.9 ptsMediumSecurity & performance tooling
Bound every outbound call: `.timeout(const Duration(seconds: 10))` on the request future for `package:http` and `dart:io`'s `HttpClient` (neither has a default), `receiveTimeout` on dio's `BaseOptions`, and a `RetryClient` (package:http/retry.dart) or `package:retry` around dependencies that fail.+0.9 ptsMediumOutbound HTTP resilience

File quality

Per-file score 0–10 — a quality signature. Of 1109 files carrying findings, judged against the Production bar: 0% slop · 23% mixed · 77% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 326

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 1477

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 155

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 13

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 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 77 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D19D20D21D24D26D28D29D30D31D35D36D43D44AX10AX3AX4AX6AX8AX9DM2DM5DM6ED4ES2GD1IC1M1M2M3M4P1P10P2P3P4P6P7P8PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X16X17X18X2X21X23X25X27X28X3X4X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1eb8e-be3f-7bb8-a588-64239f38a810.

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

Run transparency — what happened this run

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

  • D10 Test 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. The 1 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 624 test source file(s) (.dart, .kt, .swift) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — 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 reliability not scored — the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in infra/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
  • D12 Dependency Hygiene — 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 — 46 Maven/Gradle manifest(s) were read, stating a version for 46 dependency(ies) and leaving 11 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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 — 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 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.
  • D32 Data Compliance (PII/GDPR) — 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. `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+CreateTable.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/AWSIncomingEventReconciliationQueue.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/IncomingAsyncSubscriptionEventPublisher.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStore.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Operation/RetryableGraphQLOperation.swift`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 57 commits in the last 90 days, yet 626 of 655 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
  • AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RemoteSyncEngine+Resolver.swift, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. An image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository. (rule: registry). The renderer reported: docker build failed (exit 1) — 1 | >>> FROM public.ecr.aws/ubuntu/ubuntu:latest 2 | 3 | ## REDACTED for local development of Amplify Flutter packages on Linux -------------------- ERROR: failed to solve: public.ecr.aws/ubuntu/ubuntu:latest: failed to resolve source metadata for public.ecr.aws/ubuntu/ubuntu:latest: failed to do request: Head "https://public.ecr.aws/v2/ubuntu/ubuntu/manifests/latest": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 1 | >>> FROM public.ecr.aws/ubuntu/ubuntu:latest 2 | 3 | ## REDACTED for local development of Amplify Flutter packages on Linux -------------------- ERROR: failed to solve: public.ecr.aws/ubuntu/ubuntu:latest: failed to resolve source metadata for public.ecr.aws/ubuntu/ubuntu:latest: failed to do request: Head "https://public.ecr.aws/v2/ubuntu/ubuntu/manifests/latest": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
  • C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 59 further occurrence(s) are not listed individually; the score already reflects all 99.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
  • X1 Async correctness — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X12 Unreachable branch — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X13 Undrained process stream — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X16 Unfloored truncation loop — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X17 Uncapped recursion over a caller-supplied document — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern correctness — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X2 Cancellation propagation — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X21 Side-effecting pattern guard — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X23 Unguarded diagnostic materialisation — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X25 Inert configuration knob — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X26 Unsynchronised callback handoff — 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.
  • X27 Collection changed while being enumerated — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

Repo exclusion declarations: 37 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • 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.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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 Complexity6.7 / 10Adequate✓ Tool-verified

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

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

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

43 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ModelSchema.compare at 52. A further 23 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 DialCodeResolver.resolve at 247 — they are counted neither in the figure above nor in this dimension's score. 15 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart (DialCodeResolver.resolve at 247), packages/authenticator/amplify_authenticator/lib/src/l10n/input_resolver.dart (InputResolver.title at 24), packages/smithy/smithy_codegen/lib/src/jmespath/visitor.dart (JmesVisitor.visit at 24), packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/Amplify+Reset.swift (Amplify.reset at 22), packages/authenticator/amplify_authenticator/lib/src/screens/authenticator_screen.dart (AuthenticatorScreen.builder at 21), and 10 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

ModelSchema.compare (cyclomatic 52)packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/Model+Compare.swift:30
GenerateWorkflowsCommand.generateForPackage (cyclomatic 36)packages/aft/lib/src/commands/generate/generate_workflows_command.dart:270
QueryPredicateBuilder.fromSerializedMap (cyclomatic 34)packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/QueryPredicateBuilder.swift:8
QueryPredicateBuilder.fromSerializedMap (cyclomatic 33)packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/query/QueryPredicateBuilder.kt:26
ModelSchema.comparator (cyclomatic 33)packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/Model+Sort.swift:86

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

What to do

  1. Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ModelSchema.compare (cyclomatic 52), GenerateWorkflowsCommand.generateForPackage (cyclomatic 36), QueryPredicateBuilder.fromSerializedMap (cyclomatic 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity6.0 / 10Adequate✓ Tool-verified

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

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

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

73 method(s) exceeded the cognitive complexity threshold of 15; the worst was ModelSchema.compare at 97.

DataStoreHubEventStreamHandler.sendPayload (cognitive 32) · ×2packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/DataStoreHubEventStreamHandler.kt:82
ModelSchema.compare (cognitive 97)packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/Model+Compare.swift:30
WorkerBeeImpl.spawn (cognitive 63)packages/worker_bee/worker_bee/lib/src/js/impl.dart:160
GenerateWorkflowsCommand.generateForPackage (cognitive 55)packages/aft/lib/src/commands/generate/generate_workflows_command.dart:270
StructureXmlSerializerGenerator._builtXmlConstructor (cognitive 52)packages/smithy/smithy_codegen/lib/src/generator/serialization/structure_xml_serializer_generator.dart:109

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with ModelSchema.compare (cognitive 97), WorkerBeeImpl.spawn (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes9.1 / 10Stronggated by 50 serious findings✓ Tool-verified

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

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

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

50 god class(es) detected.

FileTooLong: l10n/dial_code_resolver.dart · ×15packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart
MethodTooLong: DialCodeResolver.resolve · ×13packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart:1491
TooManyMethods: DialCodeResolver · ×11packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart:258
ClassTooLong: DialCodeResolver · ×11packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart:258

What to do

  1. Resolve the 15 FileTooLong finding(s) in God Classes — start with dial_code_resolver.dart, sign_in_state_machine.dart, auth_plugin_impl.dart. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 13 MethodTooLong finding(s) in God Classes — start with dial_code_resolver.dart, stack.ts, generate_workflows_command.dart. — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 11 TooManyMethods finding(s) in God Classes — start with dial_code_resolver.dart, authenticator_state.dart, types.dart. — One of this dimension's main actionable groups (11 warning-level).

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

D4 · Code Duplication7.9 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

126 duplicated block group(s) detected. 5.3 % of the production lines (9,480 of 180,319) are in a reported copy. A further 196 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 38 of the 322 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.

Duplicated block (8 lines × 2) · ×13packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:359
Edited copy of a member (10 corresponding lines) · ×12packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/SortedList.swift:79
Edited copy of a member (5 corresponding lines) · ×11packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelField+Association.swift:111
Edited copy of a member (7 corresponding lines) · ×10packages/secure_storage/amplify_secure_storage_dart/lib/src/amplify_secure_storage_dart.dart:129
Edited copy of a member (16 corresponding lines) · ×9packages/amplify_datastore/lib/src/method_channel_datastore.dart:173

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

What to do

  1. Resolve the 13 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with GraphQLRequest+Model.swift (2), AnalyticsError.swift (2), api_plugin_impl.dart. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 12 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with Geo+Error.swift (3), SortedList.swift, AmplifyInProcessReportingOperation.swift. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 11 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with AWSDataStorePlugin+DataStoreBaseBehavior.swift (3), ModelField+Association.swift, AmplifyAsyncSequence.swift. — One of this dimension's main actionable groups (11 warning-level).

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

D5 · Coupling9.8 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

82 production modules (Gradle+npm+SwiftPM+pub+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 3 module(s) off the main sequence, with abstractness counted on 55 of the 82 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: smithy_codegen · ×2
Off the main sequence: aws_common

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).

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

D6 · Cohesion (LCOM4)4.2 / 10Weak✓ Tool-verified

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

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

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

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

644 of 1326 classes have LCOM4 above 3.

Low cohesion: MockCognitoIdentityProviderClient (LCOM4 24) · ×644packages/auth/amplify_auth_cognito_test/lib/common/mock_clients.dart:26

What to do

  1. Resolve the 644 Low cohesion finding(s) in Cohesion (LCOM4) — start with endpoint_operation.dart (12), endpoint_with_host_label_operation.dart (12), greeting_with_errors_operation.dart (12). — One of this dimension's main actionable groups (644 warning-level).

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

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests. Measured on the JavaScript/TypeScript suite only — at least 624 test source file(s) (.dart, .kt, .swift) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 111 resolved pub package(s) use a banned license. Licences were read from pub.dev's analysis of each package's licence file. ★ This repository commits no pubspec.lock (Dart's guidance for a package), so the graph was closed here: the 33 package(s) its pubspec declares under dependencies, and transitively every package their published pubspecs declare, each at the newest release its constraint admits — the release a fresh `pub get` picks wherever constraints agree; where two disagree the first to reach the package was taken. dev_dependencies are not part of it. The packages the `flutter`, `flutter_web_plugins` SDK itself pins are the toolchain's and were not reached. pub.dev analyses only recent releases, so for 1 package(s) locked at an older version the licence read is that of the package's latest analysed release, not of the locked one. ★ COVERAGE OF THIS VERDICT: it grades this repository's pub package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

Top hotspots: packages/aft/lib/src/commands/generate/generate_workflows_command.dart (2×36=72)

Hotspot: packages/aft/lib/src/commands/generate/generate_workflows_command.dartpackages/aft/lib/src/commands/generate/generate_workflows_command.dart:270

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with generate_workflows_command.dart. — One of this dimension's main actionable groups (1 warning-level).

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

D16 · Bus Factor9.7 / 10Exemplary✓ Tool-verified

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

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

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

16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/aft/lib/src/commands/publish_command.dart. Counted over 654 of the 2277 production source files in this repository: 1622 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.8 / 10Stronggated by 146 serious findings✓ Tool-verified

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

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

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

146 deducted task-comment markers across 180319 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×135packages/worker_bee/worker_bee_builder/lib/src/worker_generator.dart:58
FixmeComment · ×11templates/flutter-package/__brick__/example/lib/main.dart:13

What to do

  1. Resolve the 135 TodoComment finding(s) in Explicit Debt — start with web_socket_bloc.dart (11), queries_display_widgets.dart (3), download_file_test.dart (3). — One of this dimension's main actionable groups (135 warning-level).
  2. Resolve the 11 FixmeComment finding(s) in Explicit Debt — start with main.dart (8), DataStorePluginUnitTests.swift (2), authenticator_with_controllers.dart. — One of this dimension's main actionable groups (11 warning-level).

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

D19 · Documentation Quality6.1 / 10Adequate✓ Tool-verified

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

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

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

1 of 2 documentation facets pass in full; short on: F2 example. 68 document(s) read across 91 unit(s).

Documentation: no build, run or usage example · ×32actions/README.md:1

What to do

  1. Resolve the 32 Documentation finding(s) in Documentation Quality — start with README.md (32). — One of this dimension's main actionable groups (32 recommendation-level).

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

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

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundpackages/worker_bee/e2e_flutter_test/macos/Runner.xcodeproj/project.pbxproj:1

What to do

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

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

D21 · Naming Consistency9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

11 naming inconsistencies among 1619 declarations measured against a convention their peers follow.

`getIDToken` spells `ID` where 707 names in the project spell it `Id`actions/lib/src/node/actions/core.dart:88
`_subscriptionByID` spells `ID` where 24 names in the project spell it `Id`packages/api/amplify_api/example/lib/graphql_api_view.dart:31
`AmplifyAPI` spells `API` where 21 names in the project spell it `Api`packages/api/amplify_api/lib/src/api_plugin_impl.dart:9
`AmplifyAPIDart` spells `API` where 21 names in the project spell it `Api`packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:26
`setupURI` spells `URI` where 1059 names in the project spell it `Uri`packages/authenticator/amplify_authenticator/lib/src/state/auth_state.dart:141

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

✓ On the Gold path — maintain.

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

D24 · Comment Value0.0 / 10Critical✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

10 of 87 judged comments only repeat the code they sit on (11.5 %). 9 comment(s) in another language or script were not judged.

redundant comment · ×10infra-gen2/backends/api/api-multi-auth/amplify/backend.ts:29
doc comments repeat the namesinfra/lib/auth/stack.ts:127

What to do

  1. Resolve the 10 redundant comment finding(s) in Comment Value — start with backend.ts (4), stack.ts (4), custom-sender-lambda.ts (2). — One of this dimension's main actionable groups (10 recommendation-level).

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

D26 · Project Cohesion8.5 / 10Strong✓ Tool-verified

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

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

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

6 of 80 build units (Gradle, SwiftPM, Xcode, npm, pub) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×6packages/amplify_datastore/darwin/amplify_datastore/Package.swift:1

What to do

  1. Resolve the 6 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with pubspec.yaml (5), Package.swift. — One of this dimension's main actionable groups (6 recommendation-level).

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

281 finding(s): 0 critical, 278 high, 2 medium, 1 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 6 file(s) — `build-support/codecov.sh` (lines 89–155), `packages/smithy/goldens/gradlew` (line 72, line 173), `REDACTED`, `REDACTED`, `templates/dart-package/__brick__/example/pubspec.yaml`, … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 18 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 245 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (245 issue-level).
  2. Resolve the 25 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (25 issue-level).
  3. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).

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

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

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

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

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

57 finding(s): 3 critical, 31 high, 20 medium, 3 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 30 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (18), REDACTED (11), REDACTED. — One of this dimension's main actionable groups (30 issue-level).
  2. Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

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

REDACTED

✓ On the Gold path — maintain.

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

D35 · Change Coupling10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: SwiftAmplifyDataStorePlugin.swift↔amplify_datastore.dart 61%; auth.dart↔amplify_auth_category.dart 60%

Change coupling: SwiftAmplifyDataStorePlugin.swift ↔ amplify_datastore.dart · ×2packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:1

What to do

  1. Resolve the 2 Change coupling finding(s) in Change Coupling — start with SwiftAmplifyDataStorePlugin.swift, auth.dart. — One of this dimension's main actionable groups (2 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition8.7 / 10Strong✓ Tool-verified

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

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

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

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `E2EMessage` declares 17 abstract methods: `bigInt`, `bool_`, `builtList`, `builtListMultimap`, `builtMap`, `builtSet`, `builtSetMultimap`, `dateTime`, `double_`, `duration`, `int_`, `int64`, `jsonObject`, `num_`, `regExp`, `string`, `uri`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/worker_bee/e2e/lib/e2e_message.dart:21
  • `JsonProtocolServerBase` declares 16 abstract methods: `datetimeOffsets`, `emptyOperation`, `endpointOperation`, `endpointWithHostLabelOperation`, `fractionalSeconds`, `greetingWithErrors`, `hostWithPathOperation`, `jsonEnums`, `jsonIntEnums`, `jsonUnions`, `kitchenSinkOperation`, `nullOperation`, `operationWithOptionalInputOutput`, `putAndGetInlineDocuments`, `putWithContentEncoding`, `simpleScalarProperties`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/awsJson1_1/lib/src/json_protocol/json_protocol_server.dart:34, packages/smithy/goldens/lib2/awsJson1_1/lib/src/json_protocol/json_protocol_server.dart:34
  • `KitchenSink` declares 26 abstract methods: `blob`, `boolean`, `double_`, `emptyStruct`, `float`, `httpdateTimestamp`, `integer`, `iso8601Timestamp`, `jsonValue`, `listOfLists`, `listOfMapsOfStrings`, `listOfStrings`, `listOfStructs`, `long`, `mapOfListsOfStrings`, `mapOfMaps`, `mapOfStrings`, `mapOfStructs`, `recursiveList`, `recursiveMap`, `recursiveStruct`, `simpleStruct`, `string`, `structWithJsonName`, `timestamp`, `unixTimestamp`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/awsJson1_1/lib/src/json_protocol/model/kitchen_sink.dart:21, packages/smithy/goldens/lib2/awsJson1_1/lib/src/json_protocol/model/kitchen_sink.dart:21
  • `AppLocalizations` declares 19 abstract methods: `signIn`, `signUp`, `confirm`, `submit`, `changePassword`, `sendCode`, `lostCode`, `noAccount`, `haveAccount`, `forgotPassword`, `confirmResetPassword`, `verify`, `skip`, `signOut`, `backTo`, `signInWith`, `us`, `selectDialCode`, `confirmSignInCustomAuth`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations.dart:13
  • `AllQueryStringTypesInput` declares 21 abstract methods: `queryString`, `queryStringList`, `queryStringSet`, `queryByte`, `queryShort`, `queryInteger`, `queryIntegerList`, `queryIntegerSet`, `queryLong`, `queryFloat`, `queryDouble`, `queryDoubleList`, `queryBoolean`, `queryBooleanList`, `queryTimestamp`, `queryTimestampList`, `queryEnum`, `queryEnumList`, `queryIntegerEnum`, `queryIntegerEnumList`, `queryParamsMapOfStringList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restJson1/lib/src/rest_json_protocol/model/all_query_string_types_input.dart:17, packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_protocol/model/all_query_string_types_input.dart:18
  • `InputAndOutputWithHeadersIo` declares 18 abstract methods: `headerString`, `headerByte`, `headerShort`, `headerInteger`, `headerLong`, `headerFloat`, `headerDouble`, `headerTrueBool`, `headerFalseBool`, `headerStringList`, `headerStringSet`, `headerIntegerList`, `headerBooleanList`, `headerTimestampList`, `headerEnum`, `headerEnumList`, `headerIntegerEnum`, `headerIntegerEnumList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restJson1/lib/src/rest_json_protocol/model/input_and_output_with_headers_io.dart:17, packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_protocol/model/input_and_output_with_headers_io.dart:18
  • `RestJsonProtocolServerBase` declares 94 abstract methods: `allQueryStringTypes`, `constantAndVariableQueryString`, `constantQueryString`, `datetimeOffsets`, `documentType`, `documentTypeAsPayload`, `emptyInputAndEmptyOutput`, `endpointOperation`, `endpointWithHostLabelOperation`, `fractionalSeconds`, `greetingWithErrors`, `hostWithPathOperation`, `httpChecksumRequired`, `httpEnumPayload`, `httpPayloadTraits`, `httpPayloadTraitsWithMediaType`, `httpPayloadWithStructure`, `httpPrefixHeaders`, `httpPrefixHeadersInResponse`, `httpRequestWithFloatLabels`, `httpRequestWithGreedyLabelInPath`, `httpRequestWithLabels`, `httpRequestWithLabelsAndTimestampFormat`, `httpRequestWithRegexLiteral`, `httpResponseCode`, `httpStringPayload`, `ignoreQueryParamsInResponse`, `inputAndOutputWithHeaders`, `jsonBlobs`, `jsonEnums`, `jsonIntEnums`, `jsonLists`, `jsonMaps`, `jsonTimestamps`, `jsonUnions`, `malformedAcceptWithBody`, `malformedAcceptWithGenericString`, `malformedAcceptWithPayload`, `malformedBlob`, `malformedBoolean`, and 54 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restJson1/lib/src/rest_json_protocol/rest_json_protocol_server.dart:116, packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_protocol/rest_json_protocol_server.dart:116
  • `MalformedUniqueItemsInput` declares 16 abstract methods: `blobList`, `booleanList`, `stringList`, `byteList`, `shortList`, `integerList`, `longList`, `timestampList`, `dateTimeList`, `httpDateList`, `enumList`, `intEnumList`, `listList`, `structureList`, `structureListWithNoKey`, `unionList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restJson1/lib/src/rest_json_validation_protocol/model/malformed_unique_items_input.dart:21, packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_validation_protocol/model/malformed_unique_items_input.dart:22
  • `AllQueryStringTypesInput` declares 21 abstract methods: `queryString`, `queryStringList`, `queryStringSet`, `queryByte`, `queryShort`, `queryInteger`, `queryIntegerList`, `queryIntegerSet`, `queryLong`, `queryFloat`, `queryDouble`, `queryDoubleList`, `queryBoolean`, `queryBooleanList`, `queryTimestamp`, `queryTimestampList`, `queryEnum`, `queryEnumList`, `queryIntegerEnum`, `queryIntegerEnumList`, `queryParamsMapOfStrings`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restXml/lib/src/rest_xml_protocol/model/all_query_string_types_input.dart:17, packages/smithy/goldens/lib2/restXml/lib/src/rest_xml_protocol/model/all_query_string_types_input.dart:18
  • `InputAndOutputWithHeadersIo` declares 16 abstract methods: `headerString`, `headerByte`, `headerShort`, `headerInteger`, `headerLong`, `headerFloat`, `headerDouble`, `headerTrueBool`, `headerFalseBool`, `headerStringList`, `headerStringSet`, `headerIntegerList`, `headerBooleanList`, `headerTimestampList`, `headerEnum`, `headerEnumList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restXml/lib/src/rest_xml_protocol/model/input_and_output_with_headers_io.dart:17, packages/smithy/goldens/lib2/restXml/lib/src/rest_xml_protocol/model/input_and_output_with_headers_io.dart:17
  • `RestXmlProtocolServerBase` declares 57 abstract methods: `allQueryStringTypes`, `bodyWithXmlName`, `constantAndVariableQueryString`, `constantQueryString`, `datetimeOffsets`, `emptyInputAndEmptyOutput`, `endpointOperation`, `endpointWithHostLabelHeaderOperation`, `endpointWithHostLabelOperation`, `flattenedXmlMap`, `flattenedXmlMapWithXmlName`, `flattenedXmlMapWithXmlNamespace`, `fractionalSeconds`, `greetingWithErrors`, `httpPayloadTraits`, `httpPayloadTraitsWithMediaType`, `httpPayloadWithMemberXmlName`, `httpPayloadWithStructure`, `httpPayloadWithXmlName`, `httpPayloadWithXmlNamespace`, `httpPayloadWithXmlNamespaceAndPrefix`, `httpPrefixHeaders`, `httpRequestWithFloatLabels`, `httpRequestWithGreedyLabelInPath`, `httpRequestWithLabels`, `httpRequestWithLabelsAndTimestampFormat`, `httpResponseCode`, `ignoreQueryParamsInResponse`, `inputAndOutputWithHeaders`, `nestedXmlMaps`, `noInputAndNoOutput`, `noInputAndOutput`, `nullAndEmptyHeadersClient`, `nullAndEmptyHeadersServer`, `omitsNullSerializesEmptyString`, `putWithContentEncoding`, `queryIdempotencyTokenAutoFill`, `queryParamsAsStringListMap`, `queryPrecedence`, `recursiveShapes`, and 17 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — packages/smithy/goldens/lib/restXml/lib/src/rest_xml_protocol/rest_xml_protocol_server.dart:74, packages/smithy/goldens/lib2/restXml/lib/src/rest_xml_protocol/rest_xml_protocol_server.dart:74
  • `AuthenticatorButtonLocalizations` declares 18 abstract methods: `signIn`, `signUp`, `confirm`, `continueLabel`, `submit`, `changePassword`, `sendCode`, `lostCode`, `noAccount`, `haveAccount`, `forgotPassword`, `confirmResetPassword`, `verify`, `skip`, `copyKey`, `signOut`, `backTo`, `signInWith`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations.dart:12
  • `AuthenticatorCountryLocalizations` declares 246 abstract methods: `selectDialCode`, `noDialCodeSearchResults`, `af`, `ax`, `al`, `dz`, `as1`, `ad`, `ao`, `ai`, `aq`, `ag`, `ar`, `am`, `aw`, `au`, `at`, `az`, `bs`, `bh`, `bd`, `bb`, `by`, `be`, `bz`, `bj`, `bm`, `bt`, `bo`, `bq`, `ba`, `bw`, `br`, `io`, `bn`, `bg`, `bf`, `bi`, `kh`, `cm`, and 206 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/authenticator/amplify_authenticator/lib/src/l10n/generated/country_localizations.dart:12
  • `AuthenticatorInputLocalizations` declares 37 abstract methods: `username`, `password`, `newPassword`, `email`, `phoneNumber`, `verificationCode`, `address`, `birthdate`, `familyName`, `middleName`, `gender`, `genders`, `givenName`, `name`, `nickname`, `or`, `preferredUsername`, `warnEmpty`, `warnInvalidFormat`, `promptFill`, `promptRefill`, `confirmAttribute`, `usernameRequirements`, `passwordRequirementsPreamble`, `passwordRequirementsCharacterType`, `passwordRequirementsAtLeast`, `passwordsDoNotMatch`, `rememberDevice`, `usernameType`, `optional`, `customChallenge`, `selectSms`, `selectTotp`, `selectEmail`, `totpCodePrompt`, `showPassword`, `hidePassword`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/authenticator/amplify_authenticator/lib/src/l10n/generated/input_localizations.dart:12
  • `AuthService` declares 18 abstract methods: `signIn`, `signInWithProvider`, `signOut`, `signUp`, `confirmSignUp`, `currentUser`, `isValidSession`, `isLoggedIn`, `resetPassword`, `confirmResetPassword`, `confirmSignIn`, `resendSignUpCode`, `getAttributeVerificationStatus`, `sendUserAttributeVerificationCode`, `confirmUserAttribute`, `waitForConfiguration`, `rememberDevice`, `hubEvents`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/authenticator/amplify_authenticator/lib/src/services/amplify_auth_service.dart:11
  • `DefaultValuesInput` declares 18 abstract methods: `requiredDefaultInt`, `optionalDefaultInt`, `nullifiedDefaultInt`, `requiredDefaultString`, `optionalDefaultString`, `nullifiedDefaultString`, `requiredDefaultEnum`, `optionalDefaultEnum`, `nullifiedDefaultEnum`, `requiredDefaultList`, `optionalDefaultList`, `nullifiedDefaultList`, `requiredDefaultMap`, `optionalDefaultMap`, `nullifiedDefaultMap`, `requiredDefaultBool`, `optionalDefaultBool`, `nullifiedDefaultBool`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/smithy/goldens/lib2/custom/lib/src/custom/model/default_values_input.dart:15
  • `DefaultValuesOutput` declares 18 abstract methods: `requiredDefaultInt`, `optionalDefaultInt`, `nullifiedDefaultInt`, `requiredDefaultString`, `optionalDefaultString`, `nullifiedDefaultString`, `requiredDefaultEnum`, `optionalDefaultEnum`, `nullifiedDefaultEnum`, `requiredDefaultList`, `optionalDefaultList`, `nullifiedDefaultList`, `requiredDefaultMap`, `optionalDefaultMap`, `nullifiedDefaultMap`, `requiredDefaultBool`, `optionalDefaultBool`, `nullifiedDefaultBool`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/smithy/goldens/lib2/custom/lib/src/custom/model/default_values_output.dart:15
  • `ShapeVisitor` declares 30 abstract methods: `blobShape`, `booleanShape`, `primitiveBooleanShape`, `listShape`, `setShape`, `mapShape`, `byteShape`, `primitiveByteShape`, `shortShape`, `integerShape`, `longShape`, `floatShape`, `primitiveShortShape`, `primitiveIntegerShape`, `primitiveLongShape`, `primitiveFloatShape`, `documentShape`, `doubleShape`, `primitiveDoubleShape`, `bigIntegerShape`, `bigDecimalShape`, `operationShape`, `resourceShape`, `serviceShape`, `stringShape`, `enumShape`, `structureShape`, `unionShape`, `memberShape`, `timestampShape`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/smithy/smithy/lib/src/ast/shapes/shape_visitor.dart:6
  • `CopyObjectRequest` declares 41 abstract methods: `acl`, `bucket`, `cacheControl`, `checksumAlgorithm`, `contentDisposition`, `contentEncoding`, `contentLanguage`, `contentType`, `copySource`, `copySourceIfMatch`, `copySourceIfModifiedSince`, `copySourceIfNoneMatch`, `copySourceIfUnmodifiedSince`, `expires`, `grantFullControl`, `grantRead`, `grantReadAcp`, `grantWriteAcp`, `key`, `metadata`, `metadataDirective`, `taggingDirective`, `serverSideEncryption`, `storageClass`, `websiteRedirectLocation`, `sseCustomerAlgorithm`, `sseCustomerKey`, `sseCustomerKeyMd5`, `ssekmsKeyId`, `ssekmsEncryptionContext`, `bucketKeyEnabled`, `copySourceSseCustomerAlgorithm`, `copySourceSseCustomerKey`, `copySourceSseCustomerKeyMd5`, `requestPayer`, `tagging`, `objectLockMode`, `objectLockRetainUntilDate`, `objectLockLegalHoldStatus`, `expectedBucketOwner`, and 1 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/copy_object_request.dart:24
  • `CreateMultipartUploadRequest` declares 30 abstract methods: `acl`, `bucket`, `cacheControl`, `contentDisposition`, `contentEncoding`, `contentLanguage`, `contentType`, `expires`, `grantFullControl`, `grantRead`, `grantReadAcp`, `grantWriteAcp`, `key`, `metadata`, `serverSideEncryption`, `storageClass`, `websiteRedirectLocation`, `sseCustomerAlgorithm`, `sseCustomerKey`, `sseCustomerKeyMd5`, `ssekmsKeyId`, `ssekmsEncryptionContext`, `bucketKeyEnabled`, `requestPayer`, `tagging`, `objectLockMode`, `objectLockRetainUntilDate`, `objectLockLegalHoldStatus`, `expectedBucketOwner`, `checksumAlgorithm`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/create_multipart_upload_request.dart:22
  • `GetObjectOutput` declares 36 abstract methods: `body`, `deleteMarker`, `acceptRanges`, `expiration`, `restore`, `lastModified`, `contentLength`, `eTag`, `checksumCrc32`, `checksumCrc32C`, `checksumSha1`, `checksumSha256`, `missingMeta`, `versionId`, `cacheControl`, `contentDisposition`, `contentEncoding`, `contentLanguage`, `contentRange`, `contentType`, `expires`, `websiteRedirectLocation`, `serverSideEncryption`, `metadata`, `sseCustomerAlgorithm`, `sseCustomerKeyMd5`, `ssekmsKeyId`, `bucketKeyEnabled`, `storageClass`, `requestCharged`, `replicationStatus`, `partsCount`, `tagCount`, `objectLockMode`, `objectLockRetainUntilDate`, `objectLockLegalHoldStatus`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/get_object_output.dart:23
  • `GetObjectRequest` declares 21 abstract methods: `bucket`, `ifMatch`, `ifModifiedSince`, `ifNoneMatch`, `ifUnmodifiedSince`, `key`, `range`, `responseCacheControl`, `responseContentDisposition`, `responseContentEncoding`, `responseContentLanguage`, `responseContentType`, `responseExpires`, `versionId`, `sseCustomerAlgorithm`, `sseCustomerKey`, `sseCustomerKeyMd5`, `requestPayer`, `partNumber`, `expectedBucketOwner`, `checksumMode`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/get_object_request.dart:16
  • `HeadObjectOutput` declares 34 abstract methods: `deleteMarker`, `acceptRanges`, `expiration`, `restore`, `archiveStatus`, `lastModified`, `contentLength`, `checksumCrc32`, `checksumCrc32C`, `checksumSha1`, `checksumSha256`, `eTag`, `missingMeta`, `versionId`, `cacheControl`, `contentDisposition`, `contentEncoding`, `contentLanguage`, `contentType`, `expires`, `websiteRedirectLocation`, `serverSideEncryption`, `metadata`, `sseCustomerAlgorithm`, `sseCustomerKeyMd5`, `ssekmsKeyId`, `bucketKeyEnabled`, `storageClass`, `requestCharged`, `replicationStatus`, `partsCount`, `objectLockMode`, `objectLockRetainUntilDate`, `objectLockLegalHoldStatus`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/head_object_output.dart:23
  • `PutObjectRequest` declares 37 abstract methods: `acl`, `body`, `bucket`, `cacheControl`, `contentDisposition`, `contentEncoding`, `contentLanguage`, `contentLength`, `contentMd5`, `contentType`, `checksumAlgorithm`, `checksumCrc32`, `checksumCrc32C`, `checksumSha1`, `checksumSha256`, `expires`, `grantFullControl`, `grantRead`, `grantReadAcp`, `grantWriteAcp`, `key`, `metadata`, `serverSideEncryption`, `storageClass`, `websiteRedirectLocation`, `sseCustomerAlgorithm`, `sseCustomerKey`, `sseCustomerKeyMd5`, `ssekmsKeyId`, `ssekmsEncryptionContext`, `bucketKeyEnabled`, `requestPayer`, `tagging`, `objectLockMode`, `objectLockRetainUntilDate`, `objectLockLegalHoldStatus`, `expectedBucketOwner`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/put_object_request.dart:24
  • `UploadPartCopyRequest` declares 19 abstract methods: `bucket`, `copySource`, `copySourceIfMatch`, `copySourceIfModifiedSince`, `copySourceIfNoneMatch`, `copySourceIfUnmodifiedSince`, `copySourceRange`, `key`, `partNumber`, `uploadId`, `sseCustomerAlgorithm`, `sseCustomerKey`, `sseCustomerKeyMd5`, `copySourceSseCustomerAlgorithm`, `copySourceSseCustomerKey`, `copySourceSseCustomerKeyMd5`, `requestPayer`, `expectedBucketOwner`, `expectedSourceBucketOwner`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/upload_part_copy_request.dart:15
  • `UploadPartRequest` declares 17 abstract methods: `body`, `bucket`, `contentLength`, `contentMd5`, `checksumAlgorithm`, `checksumCrc32`, `checksumCrc32C`, `checksumSha1`, `checksumSha256`, `key`, `partNumber`, `uploadId`, `sseCustomerAlgorithm`, `sseCustomerKey`, `sseCustomerKeyMd5`, `requestPayer`, `expectedBucketOwner`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/model/upload_part_request.dart:18

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation7.5 / 10Strong✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

  • `aft` (production) references the test project `pub_server`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

What to do

  • Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

  • `CascadeDeleteOperation.queryAndDeleteTransaction` is a read-named query yet it performs a durable write on the read path (a persist to a store/client). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:167

What to do

  • Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
DM2 · Strongly-typed ids10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain identifiers are strongly typed (an extension-type / value-class wrapper) rather than raw primitives — consistency once an idiom exists.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether an entity protects its own invariants — a class whose identity is derived from its fields (value equality) but whose fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain entity fused to a persistence ORM (drift/floor/isar/objectbox/hive) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

ED4 · Outbox / dual-write8.0 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

  • `EndpointInfoStoreManager._retrieveEndpointId` performs two independent DURABLE writes — `_endpointStore` (a durable store) and `_store` (a second durable store) — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox). — packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_info_store_manager.dart:65

What to do

  • Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ES2 · Immutable events1.0 / 10Critical✓ Tool-verified

Other · Event Sourcing — Whether domain events stay immutable (a `struct` with `let` fields) rather than carrying mutable state.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

  • `FlutterModelSyncedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelSyncedEvent.swift:6
  • `FlutterNetworkStatusEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterNetworkStatusEvent.swift:6
  • `FlutterOutboxMutationEnqueuedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift:6
  • `FlutterOutboxMutationProcessedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationProcessedEvent.swift:7
  • `FlutterOutboxStatusEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxStatusEvent.swift:6
  • `FlutterReadyEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterReadyEvent.swift:6
  • `FlutterSubscriptionsEstablishedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSubscriptionsEstablishedEvent.swift:6
  • `FlutterSyncQueriesReadyEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncQueriesReadyEvent.swift:6
  • `FlutterSyncQueriesStartedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncQueriesStartedEvent.swift:6
  • `FlutterSyncReceivedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncReceivedEvent.swift:6
  • `BasicAnalyticsEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Event/BasicAnalyticsEvent.swift:11
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Dart: methods whose whole body still throws UnimplementedError or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • `_promptUserPreference` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface. — packages/amplify_core/doc/lib/auth.dart:251
  • `_promptUserFirstFactorPreference` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface. — packages/amplify_core/doc/lib/auth.dart:272

What to do

  • Finish or delete the methods that still throw UnimplementedError, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs8.5 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Dart: methods that only throw UnimplementedError or a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `_promptUserPreference` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface. — packages/amplify_core/doc/lib/auth.dart:251
  • `_promptUserFirstFactorPreference` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface. — packages/amplify_core/doc/lib/auth.dart:272
  • `canRun`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — actions/lib/src/node/process_manager.dart:152
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×7) — packages/amplify_datastore/example/integration_test/query_test/query_predicate_test/boolean_query_predicate_test.dart:128, packages/amplify_datastore/example/integration_test/query_test/sort_order_test.dart:76, packages/smithy/smithy_codegen/test/aws/endpoints_test.dart:67, …
  • `registerWith` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/secure_storage/amplify_secure_storage_dart/lib/src/amplify_secure_storage_dart.dart:67
  • `resourceShape`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — packages/smithy/smithy_codegen/lib/src/generator/visitors/symbol_visitor.dart:104
  • `// ignore_for_file: type=lint` switches every lint off for the whole file — hidden debt. Ignore the specific lint on the specific line, with a justification, instead. (×2) — packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/database_io.drift.dart:2, packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:2

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
  • Clear the softer debt: re-enable or delete tests marked `skip:`, decide whether each empty method or UnsupportedError is deliberate (and say so in a comment), and replace `// ignore_for_file: type=lint` with targeted, justified ignores.
M1 · Documentation (README)9.1 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

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

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

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

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

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

P10 · Library API & versioning9.7 / 10Exemplary✓ Tool-verified

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

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

  • 52 public types in `repository.src` are marked as implementation by their own namespace, folder or name: `AmplifyClassImpl` (packages/amplify/amplify_flutter/lib/src/amplify_impl.dart:11, name ends in `Impl`), `AmplifyHybridImpl` (packages/amplify/amplify_flutter/lib/src/hybrid_impl.dart:7, name ends in `Impl`), `AmplifyHubImpl` (packages/amplify_core/lib/src/hub/amplify_hub_impl.dart:11, name ends in `Impl`), `AnalyticsClient` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/analytics_client.dart:14, `impl`), `AWSPinpointUserProfile` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/aws_pinpoint_user_profile.dart:6, `impl`), `EndpointClient` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_client.dart:13, `impl`), `EndpointGlobalFieldsManager` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_global_fields_manager.dart:12, `impl`), `EndpointInfoStoreManager` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_info_store_manager.dart:12, `impl`), and 44 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — packages/amplify/amplify_flutter/lib/src/amplify_impl.dart:11
  • 52 public types in `packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore` are marked as implementation by their own namespace, folder or name: `Embeddable` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Embedded.swift:20, `Internal`), `ModelDateFormatting` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+DateFormatting.swift:14, `Internal`), `JSONDecoder` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+DateFormatting.swift:37, `Internal`), `JSONEncoder` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+DateFormatting.swift:49, `Internal`), `EnumPersistable` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+Enum.swift:25, `Internal`), `ModelListDecoderRegistry` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/ModelListDecoder.swift:17, `Internal`), `ModelListDecoder` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/ModelListDecoder.swift:38, `Internal`), `ModelListMarker` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/ModelListProvider.swift:16, `Internal`), and 44 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Embedded.swift:20

What to do

  • Hide `repository.src` (`AmplifyClassImpl`, `AmplifyHybridImpl`, `AmplifyHubImpl`, `AnalyticsClient`, `AWSPinpointUserProfile`, `EndpointClient`, `EndpointGlobalFieldsManager`, `EndpointInfoStoreManager`, and 44 more) (Dart: a `_` name, or keep it under `lib/src/` unexported; Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`; Swift: leave it `internal` (the default) instead of `public`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore` (`Embeddable`, `ModelDateFormatting`, `JSONDecoder`, `JSONEncoder`, `EnumPersistable`, `ModelListDecoderRegistry`, `ModelListDecoder`, `ModelListMarker`, and 44 more) (Dart: a `_` name, or keep it under `lib/src/` unexported; Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`; Swift: leave it `internal` (the default) instead of `public`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability5.5 / 10Adequate✓ Tool-verified

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

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

  • Only 27/55 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `actions`, `canaries`, `canaries/ios`, `packages/amplify/amplify_flutter/example`, `packages/amplify_connect_client/amplify_connect_client/example` and 23 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • `packages/aft/analysis_options.yaml` excludes `external/` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do. — packages/aft/analysis_options.yaml:1
  • `packages/api/amplify_api/analysis_options.yaml` excludes `lib/src/native_api_plugin.dart` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do. — packages/api/amplify_api/analysis_options.yaml:1
  • `packages/auth/amplify_auth_cognito/analysis_options.yaml` excludes `lib/src/native_auth_plugin.dart` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do. — packages/auth/amplify_auth_cognito/analysis_options.yaml:1
  • `packages/example_common/analysis_options.yaml` excludes `lib/amplifyconfiguration.dart` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do. — packages/example_common/analysis_options.yaml:1
  • No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 115 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/actions.yaml:11
  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:4

What to do

  • Prune the dead entries from your analyzer's `exclude:` list — each one names a path that is not in the repository, so the list no longer describes what is actually being skipped.
  • Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `pip`, `gitsubmodule` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — .github/workflows/publish-tag.yaml:160

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `http.Client(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — packages/auth/amplify_auth_cognito_dart/lib/src/state/cognito_state_machine.dart:37

What to do

  • Bound every outbound call: `.timeout(const Duration(seconds: 10))` on the request future for `package:http` and `dart:io`'s `HttpClient` (neither has a default), `receiveTimeout` on dio's `BaseOptions`, and a `RetryClient` (package:http/retry.dart) or `package:retry` around dependencies that fail.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/Task+Seconds.swift:11
  • `canResolveVersion` is async and calls writeAsStringSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/amplify_command.dart:183
  • `_run` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/constraints_command.dart:62
  • `run` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. (×2) — packages/aft/lib/src/commands/constraints_command.dart:126, packages/aft/lib/src/commands/save_repo_state_command.dart:33
  • `run` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/create_command.dart:35
  • `updateModels` is async and calls listSync, readAsStringSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/generate/generate_goldens_command.dart:80
  • `_transform` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/generate/generate_goldens_command.dart:175
  • `_generateFor` is async and calls deleteSync, createSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/generate/generate_goldens_command.dart:208
  • `run` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/get_release_notes_command.dart:307
  • `prePublish` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/publish_command.dart:117
  • `_runNewPackageBootstrap` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/publish_command.dart:523
  • `_createBootstrapPackage` is async and calls deleteSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/publish_command.dart:566
  • `run` is async and calls createSync, writeAsStringSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — packages/aft/lib/src/commands/run_command.dart:43

What to do

  • Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
  • Dart: await the async dart:io API (readAsString, writeAsString, Process.run, Future.delayed) instead of the *Sync variant or sleep(), or move heavy synchronous work to another isolate with Isolate.run.
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

R10 · Code Duplication0.2 / 10Critical✓ Tool-verified

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

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

  • 8 of the duplicated blocks reported below have copies in at least two of the sibling directories infra, infra-gen2 under the repository root. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:17
  • 6 duplicated blocks under infra/lib/auth/ have copies in at least two of the sibling directories custom-auth-with-srp, custom-auth-without-srp, custom-authorizer-iam, custom-authorizer-user-pools — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts:9
  • REDACTED:17 · REDACTED:5 — these 2 files are line-for-line copies of one another — 86 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:17
  • infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:28 · infra/lib/auth/custom-sender.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:28
  • infra-gen2/infra-common/src/lambda-triggers/enable-sms-mfa.ts:26 · infra/lib/auth/stack.enable-sms-mfa.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/lambda-triggers/enable-sms-mfa.ts:26
  • infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts:9 · infra/lib/auth/custom-authorizer-user-pools/stack.api-handler.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts:9
  • infra-gen2/backends/storage/dots-in-name/amplify/backend.ts:5 · infra-gen2/backends/storage/main/amplify/backend.ts:4 — the two spans are one implementation copied and then locally edited — 105 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — infra-gen2/backends/storage/dots-in-name/amplify/backend.ts:5
  • infra-gen2/infra-common/src/lambda-triggers/delete-user.ts:26 · infra/lib/auth/stack.delete-user.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/lambda-triggers/delete-user.ts:26
  • infra/lib/auth/stack.ts:316 · infra/lib/auth/stack.ts:340 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra/lib/auth/stack.ts:316
  • infra-gen2/infra-common/src/auth-user-extensions/create-user-lambda.ts:11 · infra-gen2/infra-common/src/auth-user-extensions/delete-user-lambda.ts:11 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — infra-gen2/infra-common/src/auth-user-extensions/create-user-lambda.ts:11
  • infra-gen2/backends/auth/mfa-optional-email-sms/amplify/backend.ts:8 · infra-gen2/backends/auth/mfa-optional-email-totp/amplify/backend.ts:8 · infra-gen2/backends/auth/mfa-optional-email/amplify/backend.ts:8 · infra-gen2/backends/auth/mfa-required-email-sms/amplify/backend.ts:8 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — infra-gen2/backends/auth/mfa-optional-email-sms/amplify/backend.ts:8
  • infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:7 · infra/lib/auth/stack.custom-email-sender.ts:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:7
  • infra/lib/auth/stack.ts:269 · infra/lib/auth/stack.ts:288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — infra/lib/auth/stack.ts:269
  • infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts:12 · infra/lib/auth/stack.custom-sms-sender.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts:12
  • infra-gen2/infra-common/src/lambda-triggers/pre-sign-up.ts:5 · infra/lib/auth/stack.pre-sign-up.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/lambda-triggers/pre-sign-up.ts:5
  • infra-gen2/backends/storage/dots-in-name/amplify/storage/resource.ts:5 · infra-gen2/backends/storage/main/amplify/storage/resource.ts:6 · infra-gen2/backends/storage/main/amplify/storage/resource.ts:23 — the 3 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — infra-gen2/backends/storage/dots-in-name/amplify/storage/resource.ts:5
  • infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:10 · infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:10
  • infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts:8 · infra/lib/auth/custom-auth-without-srp/verify-auth-challenge.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts:8
  • REDACTED:141 · infra/lib/auth/stack.delete-device.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:141
  • infra-gen2/backends/auth/email-sign-in/amplify/backend.ts:4 · infra-gen2/backends/auth/mfa-optional-email-sms/amplify/backend.ts:4 · infra-gen2/backends/auth/mfa-optional-email-totp/amplify/backend.ts:4 · infra-gen2/backends/auth/mfa-optional-email/amplify/backend.ts:4 · +7 more site(s) not listed — the 11 copies are spread across 11 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — infra-gen2/backends/auth/email-sign-in/amplify/backend.ts:4
  • infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:6 · infra/lib/auth/custom-auth-without-srp/define-auth-challenge.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:6
  • infra-gen2/backends/analytics/main/amplify/backend.ts:11 · infra-gen2/backends/analytics/no-unauth-identities/amplify/backend.ts:14 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — infra-gen2/backends/analytics/main/amplify/backend.ts:11
  • infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:19 · infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:27 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:19
  • infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:10 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:114 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:138 — all 3 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:10
  • infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:74 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:88 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:74
  • infra-gen2/infra-common/src/expiration.ts:15 · infra/lib/common.ts:22 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra-gen2/infra-common/src/expiration.ts:15
  • infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:97 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:106 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:97
  • infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:4 · infra/lib/auth/custom-auth-without-srp/create-auth-challenge.ts:9 · infra/lib/auth/custom-auth-without-srp/define-auth-challenge.ts:9 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:4
  • infra/lib/auth/custom-auth-with-srp/create-auth-challenge.ts:6 · infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts:6 · infra/lib/auth/custom-auth-without-srp/verify-auth-challenge.ts:6 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — infra/lib/auth/custom-auth-with-srp/create-auth-challenge.ts:6

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity9.0 / 10Exemplary✓ Tool-verified

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

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

  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — REDACTED:49, REDACTED:37
R3 · Large Files9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • infra/lib/auth/stack.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — infra/lib/auth/stack.ts:1
  • infra/lib/common.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — infra/lib/common.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.1 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — infra/lib/auth/stack.ts:1, infra/lib/stack.ts:1, infra/lib/github/github.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness9.9 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

R7 · Dead Code0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 2 file(s) (~220 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
  • 2 file(s) (~39 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. (×4) — infra-gen2/backends/auth/email-sign-in/amplify, infra-gen2/backends/auth/mfa-optional-sms/amplify, infra-gen2/backends/auth/mfa-required-sms/amplify, …
  • 2 file(s) (~64 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. (×4) — infra-gen2/backends/auth/mfa-optional-email-sms/amplify, infra-gen2/backends/auth/mfa-optional-email-totp/amplify, infra-gen2/backends/auth/mfa-required-email-sms/amplify, …
  • 2 file(s) (~63 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. (×2) — infra-gen2/backends/auth/mfa-optional-email/amplify, infra-gen2/backends/auth/mfa-required-email/amplify
  • 2 file(s) (~66 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — infra-gen2/backends/auth/username-login-mfa/amplify
  • 1 file(s) (~61 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/amplify_core/test/config/amplify_outputs_mapping/app
  • Unreachable from the 18 application, 2 tooling and 3 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (infra/lib/auth/custom-authorizer-iam/stack.ts, infra/lib/auth/custom-authorizer-user-pools/stack.ts, infra/lib/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — infra/lib/auth/stack.ts
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×18) — infra/lib/stack.ts, REDACTED, REDACTED, …
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra/lib/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — infra/lib/github/github.ts
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra-gen2/backends/api/api-multi-auth/amplify/backend.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra/lib/auth/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — infra/lib/auth/custom-authorizer-iam/stack.ts, infra/lib/auth/custom-authorizer-user-pools/stack.ts
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts, infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (infra/lib/auth/stack.custom-email-sender.ts, infra/lib/auth/stack.custom-sms-sender.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — infra/lib/auth/custom-sender.ts
  • no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra-gen2/backends/storage/main/amplify/backend.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — infra-gen2/backends/storage/main/amplify/storage/resource.ts

What to do

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

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

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

  • Declared in infra/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — infra/package.json:34
  • Declared in infra-gen2/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — infra-gen2/package.json:27, infra-gen2/package.json:17

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's Dart source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS certificate validation — facts about code that hold whether or not it serves anything itself. The TLS protocol version is not read: `dart:io` leaves the protocol floor to the platform's TLS library and has no switch that admits an obsolete version. This repository serves HTTP itself (packages/smithy/smithy_codegen/pubspec.yaml:31 — depends on `shelf`), so its Dart source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Dart spelling appears in production source, not proven on every route.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • This repository runs an HTTP server that is not bound to the loopback interface alone — or binds it at an address its source does not spell out — and nothing in its Dart source secures the transport: no `HttpServer.bindSecure` or `securityContext:`, no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: packages/smithy/smithy_codegen/pubspec.yaml:31 — depends on `shelf`.
  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: packages/smithy/smithy_codegen/pubspec.yaml:31 — depends on `shelf`.

What to do

  • Secure the server's transport: serve TLS itself (`HttpServer.bindSecure(…, context)`, or `shelf_io.serve(…, securityContext: context)`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only. A server only this device needs to reach should bind `InternetAddress.loopbackIPv4` instead.
  • Set security response headers on what the server sends — `response.headers.set('X-Content-Type-Options', 'nosniff')` in a `dart:io` handler, or a shelf middleware that adds `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy to every `Response`.
X1 · Async correctness7.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×4) — tool/bump_version.dart:40, tool/bump_version.dart:65, packages/amplify_datastore/lib/amplify_datastore.dart:405, …

What to do

  • `async` callback passed to `forEach`
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X17 · Uncapped recursion over a caller-supplied document2.0 / 10Critical✓ Tool-verified

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

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

  • `afterSerialize` is public, takes a document from its caller (line 21) and hands it to `_nest`, which calls itself at line 164 (`_nest`) with a piece of `value` (and at line 169) — and nowhere in `_nest` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `_nest` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/smithy/smithy/lib/src/serialization/xml/smithy_xml_plugin.dart:164
  • `beforeDeserialize` is public, takes a document from its caller (line 178) and hands it to `_deserialize`, which calls itself at line 207 (`_deserialize`) with a piece of `node` (and at line 209, line 225) — and nowhere in `_deserialize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `_deserialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/smithy/smithy/lib/src/serialization/xml/smithy_xml_plugin.dart:207
  • `deserializeNestedModel` is public and takes `serializedModelData: Map<String, Any ?>` from its caller, and it calls itself at line 691 with a piece of `serializedModelData` — the function is not `tailrec`, so every call is a real frame — and nowhere in `deserializeNestedModel` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `deserializeNestedModel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`. — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:691
  • `PackageSelector.fromJson` is public and takes `Object ? json` from its caller, and it calls itself at line 73 (`PackageSelector.fromJson`) with a piece of `json` (and at line 85, line 86, line 93, line 99) — and nowhere in `PackageSelector.fromJson` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `PackageSelector.fromJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/aft/lib/src/config/package_selector.dart:73

What to do

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

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

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

  • `StateMachineBloc` carries a disposal duty — it declares its own release — and it creates `_infoMessageController` itself (line 105, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_infoMessageController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_infoMessageController.close();` in `dispose()` before `super.dispose()`. — packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:105

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `decryptAndBroadcastCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:36, infra/lib/auth/custom-sender.ts:34

What to do

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

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

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

X23 · Unguarded diagnostic materialisation7.7 / 10Strong✓ Tool-verified

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

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

  • `verbose` at line 63 is called with an argument built by `commandPaths.map((path) => '…' path)` (line 67), whose cost grows with the collection it walks. Dart evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLoggable` test, no `kDebugMode` or debug flag, no `assert`, no closure the logger calls only when the level is on. — packages/aft/lib/src/commands/run_command.dart:63

What to do

  • In Dart, put the construction behind the logger's own check (`if (log.isLoggable(Level.FINE))` for package:logging, `if (kDebugMode)` for a line only a debug build needs), or hand the logger a closure it calls only when the record is written (`log.fine(() => 'rows: ${rows.map((r) => r.id).join(', ')}')`; package:logger's `logger.d(() => …)` likewise). Interpolating the value into the message is not the fix: Dart builds the string, and every `map`, `join` or `jsonEncode` inside it, before the call is entered.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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

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

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

X3 · Exception handling6.6 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — packages/smithy/smithy_aws/lib/src/protocol/aws_query_protocol.dart:98, packages/smithy/smithy_aws/lib/src/protocol/ec2_query.dart:37, packages/smithy/smithy_aws/lib/src/protocol/rest_xml.dart:83, …
  • `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×12) — packages/smithy/smithy_aws/lib/src/http/interceptors/s3/check_error_on_success.dart:40, packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:273, packages/authenticator/amplify_authenticator/lib/src/models/authenticator_exception.dart:106, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — packages/auth/amplify_auth_cognito/android/src/main/kotlin/com/amazonaws/amplify/amplify_auth_cognito/LegacyKeyProvider.kt:96
  • `catch (ex: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — packages/auth/amplify_auth_cognito/android/src/main/kotlin/com/amazonaws/amplify/amplify_auth_cognito/LegacyKeyValueStore.kt:146
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RemoteSyncEngine+AuthModeStrategyDelegate.swift:23, packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/Model+Compare.swift:139, packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine+SyncRequirement.swift:87, …

What to do

  • Swallowed exception (caught, then discarded)
X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

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

Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 45/47 of this repository's Dart packages (a `pubspec.yaml` with product Dart beneath it) declare a language version of 2.12 or above in `environment: sdk:`, which is what turns sound null safety on. A pubspec with no SDK constraint, or a lower bound below 2.12, runs its code unsound: every type admits null, and a null reaching a method call throws `NoSuchMethodError` with nothing in the analyzer having said so.

What to do

  • Raise every package's `environment: sdk:` lower bound to 2.12 or above (`^3.0.0` today) and migrate with `dart migrate` on an SDK that still has it, so `String` and `String?` mean different things. Then replace assertions rather than adding to them: each `!` is a run-time null check the analyzer could not prove — promote the value with a null check or an early return, use `?.` / `??` where absence is legitimate, make the field non-nullable and `late final` only where initialisation is truly guaranteed, or change the API so the null cannot arrive.

Reference — by lens

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

LensScoreRatingImpact
Code Health38.4Weak — gated by R10, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture86.5StrongSolid.
Maturity81.1StrongSolid.
Readiness41.3Weak — gated by R4, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security62.1Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100.0ExemplaryStrongest area.
Event-Driven80.0StrongSolid.
Event Sourcing10.0Critical — gated by ES2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60.0AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — 1 | >>> FROM public.ecr.aws/ubuntu/ubuntu:latest 2 | 3 | ## REDACTED for local development of Amplify Flutter packages on Linux -------------------- ERROR: failed to solve: public.ecr.aws/ubuntu/ubuntu:latest: failed to resolve source metadata for public.ecr.aws/ubuntu/ubuntu:latest: failed to do request: Head "https://public.ecr.aws/v2/ubuntu/ubuntu/manifests/latest": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D11 Test Reliability — No tests discovered
  • D12 Dependency Hygiene — Not scored — 46 Maven/Gradle manifest(s) were read, stating a version for 46 dependency(ies) and leaving 11 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • 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.
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript, Swift 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"]`.
  • 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 (.dart), 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.
  • D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in infra/ ran and not one test passed (FAIL test/common.test.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
  • DM1 Aggregate boundaries — not scored for Dart: aggregate-vs-value-object classification cannot be told apart in source (every class-holding-class reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — reported as guidance rather than measured
  • DM3 Integration-event coupling — not scored for Dart: a cross-package domain leak cannot be told apart in source from a legitimate shared-kernel package, and most repositories ship a single package — reported as guidance rather than measured
  • DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
  • DM7 Repository granularity — not scored for Dart: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • 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 classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, 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.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — X26 reached only 28% of this repository's production lines — dart (124,936 lines), typescript (4,986 lines), cpp (531 lines), javascript (526 lines), c (210 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • 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.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 326 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 220 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×30
  • 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
  • + 5 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
ES2 · Immutable events · Mutable domain event · ×11
  • Mutable domain event: FlutterModelSyncedEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelSyncedEvent.swift:6 — `FlutterModelSyncedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterNetworkStatusEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterNetworkStatusEvent.swift:6 — `FlutterNetworkStatusEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterOutboxMutationEnqueuedEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift:6 — `FlutterOutboxMutationEnqueuedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterOutboxMutationProcessedEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationProcessedEvent.swift:7 — `FlutterOutboxMutationProcessedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterOutboxStatusEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxStatusEvent.swift:6 — `FlutterOutboxStatusEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterReadyEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterReadyEvent.swift:6 — `FlutterReadyEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterSubscriptionsEstablishedEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSubscriptionsEstablishedEvent.swift:6 — `FlutterSubscriptionsEstablishedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterSyncQueriesReadyEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncQueriesReadyEvent.swift:6 — `FlutterSyncQueriesReadyEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterSyncQueriesStartedEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncQueriesStartedEvent.swift:6 — `FlutterSyncQueriesStartedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: FlutterSyncReceivedEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncReceivedEvent.swift:6 — `FlutterSyncReceivedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
  • Mutable domain event: BasicAnalyticsEvent packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Event/BasicAnalyticsEvent.swift:11 — `BasicAnalyticsEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AX8 · Test isolation · Production project references a test project · ×1
  • Production project references a test project: aft → pub_server — `aft` (production) references the test project `pub_server`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
AX9 · CQS / query purity · Query writes persistent state on the read path · ×1
  • Query writes persistent state on the read path: CascadeDeleteOperation.queryAndDeleteTransaction packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:167 — `CascadeDeleteOperation.queryAndDeleteTransaction` is a read-named query yet it performs a durable write on the read path (a persist to a store/client). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
ED4 · Outbox / dual-write · Dual write (no outbox) · ×1
  • Dual write (no outbox): EndpointInfoStoreManager._retrieveEndpointId packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_info_store_manager.dart:65 — `EndpointInfoStoreManager._retrieveEndpointId` performs two independent DURABLE writes — `_endpointStore` (a durable store) and `_store` (a second durable store) — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox).
Serious — 1477 finding(s)
D6 · Cohesion (LCOM4) · Low cohesion · ×644
  • Low cohesion: MockCognitoIdentityProviderClient (LCOM4 24) packages/auth/amplify_auth_cognito_test/lib/common/mock_clients.dart:26 — MockCognitoIdentityProviderClient's methods fall into 24 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 24 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AmplifyAuthCognitoDart (LCOM4 15) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:57 — AmplifyAuthCognitoDart's methods fall into 15 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 15 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AmplifyStorageS3Dart (LCOM4 12) packages/storage/amplify_storage_s3_dart/lib/src/amplify_storage_s3_dart_impl.dart:28 — AmplifyStorageS3Dart's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: GetRestApisOperation (LCOM4 11) packages/smithy/goldens/lib/restJson1/lib/src/api_gateway/operation/get_rest_apis_operation.dart:22 — GetRestApisOperation's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DataStorePluginInterface (LCOM4 11) packages/amplify_core/lib/src/plugin/amplify_datastore_plugin_interface.dart:11 — DataStorePluginInterface's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: GetRestApisOperation (LCOM4 11) packages/smithy/goldens/lib2/restJson1/lib/src/api_gateway/operation/get_rest_apis_operation.dart:22 — GetRestApisOperation's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ListObjectsV2Operation (LCOM4 10) packages/smithy/goldens/lib/restXml/lib/src/s3/operation/list_objects_v2_operation.dart:18 — ListObjectsV2Operation's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: APIPluginInterface (LCOM4 10) packages/amplify_core/lib/src/plugin/amplify_api_plugin_interface.dart:7 — APIPluginInterface's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ListObjectsV2Operation (LCOM4 10) packages/smithy/goldens/lib2/restXml/lib/src/s3/operation/list_objects_v2_operation.dart:18 — ListObjectsV2Operation's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ListObjectsV2Operation (LCOM4 10) packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/operation/list_objects_v2_operation.dart:18 — ListObjectsV2Operation's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ListPartsOperation (LCOM4 10) packages/storage/amplify_storage_s3_dart/lib/src/sdk/src/s3/operation/list_parts_operation.dart:19 — ListPartsOperation's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ASFDeviceInfoPlatform (LCOM4 9) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_device_info_collector.js.dart:16 — ASFDeviceInfoPlatform's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ASFDeviceInfoMacOS (LCOM4 9) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_device_info_collector.macos.dart:18 — ASFDeviceInfoMacOS's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: StructureXmlSerializerGenerator (LCOM4 9) packages/smithy/smithy_codegen/lib/src/generator/serialization/structure_xml_serializer_generator.dart:12 — StructureXmlSerializerGenerator's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EmptyInputAndEmptyOutputOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/empty_input_and_empty_output_operation.dart:16 — EmptyInputAndEmptyOutputOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EndpointOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/endpoint_operation.dart:14 — EndpointOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: EndpointWithHostLabelOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/endpoint_with_host_label_operation.dart:15 — EndpointWithHostLabelOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: GreetingWithErrorsOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/greeting_with_errors_operation.dart:19 — GreetingWithErrorsOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: HostWithPathOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/host_with_path_operation.dart:14 — HostWithPathOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: JsonUnionsOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/json_unions_operation.dart:16 — JsonUnionsOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NoInputAndNoOutputOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/no_input_and_no_output_operation.dart:14 — NoInputAndNoOutputOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NoInputAndOutputOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/no_input_and_output_operation.dart:15 — NoInputAndOutputOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: PutWithContentEncodingOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/put_with_content_encoding_operation.dart:15 — PutWithContentEncodingOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SimpleScalarPropertiesOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_0/lib/src/json_rpc_10/operation/simple_scalar_properties_operation.dart:16 — SimpleScalarPropertiesOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DatetimeOffsetsOperation (LCOM4 8) packages/smithy/goldens/lib/awsJson1_1/lib/src/json_protocol/operation/datetime_offsets_operation.dart:16 — DatetimeOffsetsOperation's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • + 619 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×135
  • TodoComment packages/worker_bee/worker_bee_builder/lib/src/worker_generator.dart:58 — // TODO(Jordan-Nelson): remove use of `withNullability` when min dart version is 3.4 or higher — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/test/pub_server/lib/src/launcher.dart:174 — // TODO(dnys1): Consolidate with `aft` logic. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/test/amplify_integration_test/lib/src/integration_test_utils/auth_cognito/integration_test_auth_utils.dart:247 — // TODO(dnys1): Cognito cannot always delete a user by `cognitoUsername`. Why? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/storage_s3_service_impl.dart:95 — // TODO(HuiSF): re-enable signPayload when the signer supports hashing on — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:572 — // TODO(HuiSF): verify if s3Client sdk throws different exception type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3_dart/example/web/main.dart:6 — // TODO(HuiSF): Add example Web App — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3/example/lib/main.dart:307 — // TODO(Jordan-Nelson): use `WidgetStateProperty` when min flutter sdk is 3.22.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/authenticator/amplify_authenticator/lib/src/widgets/social/social_button.dart:178 — // TODO(Jordan-Nelson): use `WidgetStateProperty` when min flutter sdk is 3.22.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/authenticator/amplify_authenticator/lib/src/widgets/social/social_button.dart:188 — // TODO(Jordan-Nelson): use `WidgetStateProperty` when min flutter sdk is 3.22.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/amplify_datastore/example/lib/widgets/queries_display_widgets.dart:28 — // TODO(Jordan-Nelson): use `WidgetStateProperty` when min flutter sdk is 3.22.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/amplify_datastore/example/lib/widgets/queries_display_widgets.dart:48 — // TODO(Jordan-Nelson): use `WidgetStateProperty` when min flutter sdk is 3.22.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/amplify_datastore/example/lib/widgets/queries_display_widgets.dart:68 — // TODO(Jordan-Nelson): use `WidgetStateProperty` when min flutter sdk is 3.22.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3/example/integration_test/download_data_test.dart:232 — // TODO(Jordan-Nelson): resolve issue and re-enable test — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3/example/integration_test/download_file_test.dart:301 — // TODO(Jordan-Nelson): resolve issue and re-enable test — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3/example/integration_test/download_file_test.dart:236 — // TODO(Jordan-Nelson): Determine why these are failing on web — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/storage/amplify_storage_s3/example/integration_test/download_file_test.dart:306 — // TODO(Jordan-Nelson): Determine why these are failing on web — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy_codegen/lib/src/generate.dart:147 — // TODO(dnys1): Remove when fixed by Cognito — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy_codegen/lib/src/util/shape_ext.dart:268 — // TODO(dnys1): Once service client interface is finalized. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy_codegen/lib/src/generator/shape_overrides.dart:65 — // TODO(dnys1): After `SmithySerializer` is no longer required. Make this required? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart:679 — // TODO(dnys1): Find a way to make these non-null. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy_aws/test/http/aws_retryer_test.dart:136 — // TODO(dnys1): Try to get fake_async to work properly to avoid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy_aws/lib/src/http/interceptors/with_sdk_request.dart:20 — // TODO(dnys1): Add ttl when config is complete — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy/lib/src/serialization/stream_serializer.dart:44 — // TODO(dnys1): https://github.com/dart-lang/sdk/issues/49851
  • TodoComment packages/smithy/smithy/lib/src/serialization/json/big_int_serializer.dart:6 — // TODO(dnys1): Remove when doing so wouldn't crash DDC — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/smithy/smithy/lib/src/serialization/json/int64_serializer.dart:9 — // TODO(dnys1): Remove when doing so wouldn't crash DDC — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 110 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file infra/lib/auth/stack.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/stack.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/github/github.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/custom-authorizer-iam/stack.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/auth-user-extensions/custom-sender-lambda.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/custom-authorizer-user-pools/stack.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/analytics-extensions/data.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/backends/api/api-multi-auth/amplify/backend.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/custom-sender.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/config-creator.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/backends/storage/main/amplify/backend.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/lambda-triggers/kinesis-consumer.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/backends/kinesis/firehose/amplify/backend.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/custom-auth-without-srp/define-auth-challenge.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/lambda-triggers/enable-sms-mfa.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/stack.delete-device.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/stack.enable-sms-mfa.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/lambda-triggers/delete-user.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra/lib/auth/stack.delete-user.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/auth-user-extensions/enable-sms-mfa-lambda.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file infra-gen2/infra-common/src/analytics-extensions/kinesis.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×25
  • Swallowed exception (caught, then discarded) packages/smithy/smithy_aws/lib/src/protocol/aws_query_protocol.dart:98 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/smithy/smithy_aws/lib/src/protocol/ec2_query.dart:37 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/smithy/smithy_aws/lib/src/protocol/rest_xml.dart:83 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/smithy/smithy_aws/lib/src/http/interceptors/s3/check_error_on_success.dart:40 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:273 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/authenticator/amplify_authenticator/lib/src/models/authenticator_exception.dart:106 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:1046 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/auth/amplify_auth_cognito_dart/lib/src/jwt/src/keyset.dart:34 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:172 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_device_info_collector.linux.dart:108 — `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/auth/amplify_auth_cognito/android/src/main/kotlin/com/amazonaws/amplify/amplify_auth_cognito/LegacyKeyValueStore.kt:146 — `catch (ex: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/event_client/queued_item_store/index_db/indexed_db_adapter.dart:149 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RemoteSyncEngine+AuthModeStrategyDelegate.swift:23 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/Model+Compare.swift:139 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine+SyncRequirement.swift:87 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine+SyncRequirement.swift:95 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Core/DataStoreListDecoder.swift:42 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_core/lib/src/types/exception/auth/auth_exception.dart:39 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_core/lib/src/types/exception/analytics/analytics_exception.dart:35 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/amplify_core/lib/src/state_machine/state_machine.dart:110 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/aft/lib/src/config/config.dart:479 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/aft/lib/src/commands/generate/generate_goldens_command.dart:102 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) actions/lib/src/node/fs.dart:56 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) actions/lib/src/node/actions/tool_cache.dart:25 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) actions/lib/src/android/avd_manager.dart:116 — `on Object` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D30 · Dependency Vulnerabilities · Medium CVE · ×20
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×15
  • FileTooLong: l10n/dial_code_resolver.dart packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart — FileTooLong — 1241 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: DialCodeResolver (258-1988). The bar is 500 significant lines; this is 741 over it, 2.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: machines/sign_in_state_machine.dart packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart — FileTooLong — 950 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: SignInStateMachine (43-1423). The bar is 500 significant lines; this is 450 over it, 1.90× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/auth_plugin_impl.dart packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart — FileTooLong — 803 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: AmplifyAuthCognitoDart (60-1172). The bar is 500 significant lines; this is 303 over it, 1.61× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: form_fields/confirm_sign_in_form_field.dart packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart — FileTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 222 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: form_fields/sign_up_form_field.dart packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart — FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 206 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: generator/structure_generator.dart packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart — FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: StructureGenerator (17-973). The bar is 500 significant lines; this is 195 over it, 1.39× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: amplify_datastore/AmplifyDataStorePlugin.kt packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt — FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: AmplifyDataStorePlugin (80-983). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: amplify_datastore/SwiftAmplifyDataStorePlugin.swift packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift — FileTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: SwiftAmplifyDataStorePlugin (8-884). The bar is 500 significant lines; this is 143 over it, 1.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: sdk/sdk_bridge.dart packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart — FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: WrappedCognitoIdentityProviderClient (178-779). The bar is 500 significant lines; this is 138 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: generate/generate_workflows_command.dart packages/aft/lib/src/commands/generate/generate_workflows_command.dart — FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: GenerateWorkflowsCommand (12-822). The bar is 500 significant lines; this is 113 over it, 1.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Models/Language.swift packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Models/Language.swift — FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 107 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: generator/operation_generator.dart packages/smithy/smithy_codegen/lib/src/generator/operation_generator.dart — FileTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: OperationGenerator (15-750). The bar is 500 significant lines; this is 60 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: task/s3_upload_task.dart packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart — FileTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: S3UploadTask (67-820). The bar is 500 significant lines; this is 60 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: database/tables.drift.dart packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart — FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: commands/publish_command.dart packages/aft/lib/src/commands/publish_command.dart — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×14
  • Sync-over-async blocking packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/Task+Seconds.swift:11 — `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/amplify_command.dart:183 — `canResolveVersion` is async and calls writeAsStringSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/constraints_command.dart:62 — `_run` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/constraints_command.dart:126 — `run` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/create_command.dart:35 — `run` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/generate/generate_goldens_command.dart:80 — `updateModels` is async and calls listSync, readAsStringSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/generate/generate_goldens_command.dart:175 — `_transform` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/generate/generate_goldens_command.dart:208 — `_generateFor` is async and calls deleteSync, createSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/get_release_notes_command.dart:307 — `run` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/publish_command.dart:117 — `prePublish` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/publish_command.dart:523 — `_runNewPackageBootstrap` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/publish_command.dart:566 — `_createBootstrapPackage` is async and calls deleteSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/run_command.dart:43 — `run` is async and calls createSync, writeAsStringSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
  • Sync-over-async blocking packages/aft/lib/src/commands/save_repo_state_command.dart:33 — `run` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
D3 · God Classes · MethodTooLong · ×13
  • MethodTooLong: DialCodeResolver.resolve packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart:1491 — MethodTooLong — resolve runs 495 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 395 over it, 4.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AuthIntegrationTestStackEnvironment.constructor infra/lib/auth/stack.ts:202 — MethodTooLong — constructor runs 349 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 249 over it, 3.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GenerateWorkflowsCommand.generateForPackage packages/aft/lib/src/commands/generate/generate_workflows_command.dart:270 — MethodTooLong — generateForPackage runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OperationGenerator._httpOverrides packages/smithy/smithy_codegen/lib/src/generator/operation_generator.dart:350 — MethodTooLong — _httpOverrides runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AWSHttpClientImpl._sendH2 packages/aws_common/lib/src/http/aws_http_client_io.dart:222 — MethodTooLong — _sendH2 runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ServiceServerGenerator._serviceMethodBody packages/smithy/smithy_codegen/lib/src/generator/service_server_generator.dart:111 — MethodTooLong — _serviceMethodBody runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: StructureGenerator._outputBuilder packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart:728 — MethodTooLong — _outputBuilder runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WorkerBeeImpl.spawn packages/worker_bee/worker_bee/lib/src/js/impl.dart:160 — MethodTooLong — spawn runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: QueryPredicateBuilder.fromSerializedMap packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/QueryPredicateBuilder.swift:8 — MethodTooLong — fromSerializedMap runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UnionGenerator._variantClasses packages/smithy/smithy_codegen/lib/src/generator/union_generator.dart:174 — MethodTooLong — _variantClasses runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DataStoreHubEventStreamHandler.sendPayload packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/DataStoreHubEventStreamHandler.kt:82 — MethodTooLong — sendPayload runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GenerateSdkCommand._generateForPackage packages/aft/lib/src/commands/generate/generate_sdk_command.dart:126 — MethodTooLong — _generateForPackage runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Companion.fromSerializedMap packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/query/QueryPredicateBuilder.kt:26 — MethodTooLong — fromSerializedMap runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×13
  • Duplicated block (8 lines × 2) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:359 — packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:359-366 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:373-380 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:359` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 2) packages/storage/amplify_storage_s3_dart/lib/src/model/s3_download_data_operation.dart:31 — packages/storage/amplify_storage_s3_dart/lib/src/model/s3_download_data_operation.dart:31-38 | packages/storage/amplify_storage_s3_dart/lib/src/model/s3_upload_file_operation.dart:31-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_ios_cognito_keys.dart:208 — packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_ios_cognito_keys.dart:208-215 | packages/auth/amplify_auth_cognito_dart/lib/src/credentials/cognito_keys.dart:209-216 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_context_data_provider.dart:66 — packages/auth/amplify_auth_cognito_dart/lib/src/asf/asf_context_data_provider.dart:66-73 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:115-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:620 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:620-627 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:898-905 — before extracting anything, compare `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart` and `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) packages/smithy/smithy/lib/src/serialization/query/query_bool_serializer.dart:12 — packages/smithy/smithy/lib/src/serialization/query/query_bool_serializer.dart:12-19 | packages/smithy/smithy/lib/src/serialization/xml/xml_bool_serializer.dart:24-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) packages/aft/lib/src/config/serializers.dart:74 — packages/aft/lib/src/config/serializers.dart:74-81 | packages/smithy/smithy/lib/src/ast/shapes/shape_id.dart:89-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart:20 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart:20-27 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_setup_selection_form_field.dart:23-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:200 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:200-207 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:213-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:200` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:281 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:281-288 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:313-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:361 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:361-368 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:377-384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:361` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Error/AnalyticsError.swift:20 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Error/AnalyticsError.swift:20-27 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/LoggingError.swift:14-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Error/AnalyticsError.swift:30 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Error/AnalyticsError.swift:30-37 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/LoggingError.swift:23-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×12
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/SortedList.swift:79 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/SortedList.swift:79-91 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/SortedList.swift:94-103 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyInProcessReportingOperation.swift:113 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyInProcessReportingOperation.swift:113-122 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyOperation.swift:165-174 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:71 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:71-82 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/ConfigurationError.swift:66-75 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/ErrorUtil.swift:23 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/ErrorUtil.swift:23-35 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterDataStoreErrorHandler.swift:20-29 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/secure_storage/amplify_secure_storage_dart/lib/src/platforms/amplify_secure_storage_web.dart:119 — packages/secure_storage/amplify_secure_storage_dart/lib/src/platforms/amplify_secure_storage_web.dart:119-128 | packages/secure_storage/amplify_secure_storage_dart/lib/src/platforms/amplify_secure_storage_web.dart:142-151 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:43 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:43-54 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/ConfigurationError.swift:42-51 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:57 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:57-68 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/ConfigurationError.swift:54-63 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:153 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:153-162 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:188-197 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_up_form_field.dart:128 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_up_form_field.dart:128-137 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_in_form_field.dart:127-136 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:272 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:272-282 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngineAdapter.swift:78-87 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/amplify_core/lib/src/config/analytics/analytics_config.dart:36 — packages/amplify_core/lib/src/config/analytics/analytics_config.dart:36-47 | packages/amplify_core/lib/src/config/storage/storage_config.dart:35-44 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:51 — packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:51-60 | packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:62-71 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D17 · Explicit Debt · FixmeComment · ×11
  • FixmeComment templates/flutter-package/__brick__/example/lib/main.dart:13 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/storage/amplify_storage_s3/example/lib/main.dart:51 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/kinesis/amplify_kinesis/example/lib/main.dart:74 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/authenticator/amplify_authenticator/example/lib/authenticator_with_controllers.dart:57 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/authenticator/amplify_authenticator/example/lib/main.dart:39 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/auth/amplify_auth_cognito/example/lib/main.dart:83 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/api/amplify_api/example/lib/main.dart:39 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/analytics/amplify_analytics_pinpoint/example/lib/main.dart:42 — // FIXME: In your app, make sure to remove this line and set up — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/api/amplify_api/example/lib/main.dart:50 — // FIXME: In your app, make sure to run `amplify codegen models` to generate — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/amplify_datastore/example/ios/unit_tests/DataStorePluginUnitTests.swift:75 — // Fixme, manually testing results in int — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/amplify_datastore/example/ios/unit_tests/DataStorePluginUnitTests.swift:206 — // Fixme, manually testing results in int — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D3 · God Classes · TooManyMethods · ×11
  • TooManyMethods: DialCodeResolver packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart:258 — TooManyMethods — 248 methods. The bar is 30 methods; this is 218 over it, 8.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AuthenticatorState packages/authenticator/amplify_authenticator/lib/src/state/authenticator_state.dart:15 — TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: _Smithy packages/smithy/smithy_codegen/lib/src/generator/types.dart:484 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AWSDataStorePlugin packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin.swift:17 — TooManyMethods — 58 methods, declared across 3 files: AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift (43), AWSDataStorePluginInternal/AWSDataStorePlugin.swift (12), AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreSubscribeBehavior.swift (3). The bar is 30 methods; this is 28 over it, 1.93× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SignInStateMachine packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:38 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: NativeAuthPluginWrapper packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/NativeAuthPluginWrapper.kt:64 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AmplifyAuthCognitoDart packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:57 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: WebSocketBloc packages/api/amplify_api_dart/lib/src/graphql/web_socket/blocs/web_socket_bloc.dart:23 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SQLiteStorageEngineAdapter packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:14 — TooManyMethods — 34 methods, declared across 3 files: SQLite/StorageEngineAdapter+SQLite.swift (28), SQLite/StorageEngineMigrationAdapter+SQLite.swift (4), SQLite/StorageEngineAdapter+UntypedModel.swift (2). The bar is 30 methods; this is 4 over it, 1.13× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RemoteSyncEngine packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RemoteSyncEngine.swift:12 — TooManyMethods — 32 methods, declared across 4 files: Sync/RemoteSyncEngine.swift (21), Sync/RemoteSyncEngine+IncomingEventReconciliationQueueEvent.swift (5), Sync/RemoteSyncEngine+Retryable.swift (5), Sync/RemoteSyncEngine+AuthModeStrategyDelegate.swift (1). The bar is 30 methods; this is 2 over it, 1.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DefaultVisitor packages/smithy/smithy_codegen/lib/src/generator/visitors/default_visitor.dart:6 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. Most of these members implement src.ShapeVisitor (30 of 31 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
D3 · God Classes · ClassTooLong · ×11
  • ClassTooLong: DialCodeResolver packages/authenticator/amplify_authenticator/lib/src/l10n/dial_code_resolver.dart:258 — ClassTooLong — 991 significant lines (blank, comment-only and punctuation-only lines excluded), 248 methods. The bar is 400 significant lines; this is 591 over it, 2.48× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SignInStateMachine packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:38 — ClassTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 516 over it, 2.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AmplifyAuthCognitoDart packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:57 — ClassTooLong — 750 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 350 over it, 1.88× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: StructureGenerator packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart:16 — ClassTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 284 over it, 1.71× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SwiftAmplifyDataStorePlugin packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:8 — ClassTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 240 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AmplifyDataStorePlugin packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:80 — ClassTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 204 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: GenerateWorkflowsCommand packages/aft/lib/src/commands/generate/generate_workflows_command.dart:10 — ClassTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 201 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: OperationGenerator packages/smithy/smithy_codegen/lib/src/generator/operation_generator.dart:15 — ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 150 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: S3UploadTask packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:47 — ClassTooLong — 496 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 96 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: WrappedCognitoIdentityProviderClient packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:174 — ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 29 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: StorageS3Service packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/storage_s3_service_impl.dart:30 — ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 25 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×11
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelField+Association.swift:111 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelField+Association.swift:111-115 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelField+Association.swift:121-125 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyAsyncSequence.swift:20 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyAsyncSequence.swift:20-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyAsyncThrowingSequence.swift:20-24 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:109 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:109-115 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:21-25 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:126 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:126-132 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:27-31 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/Statement+Model.swift:22 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/Statement+Model.swift:22-27 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+Codable.swift:50-54 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:227 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:227-233 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:45-49 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubCategory+ClientBehavior.swift:21 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubCategory+ClientBehavior.swift:21-25 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/DefaultPlugins/AWSHubPlugin/AWSHubPlugin.swift:52-57 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/secure_storage/amplify_secure_storage/lib/src/amplify_secure_storage.vm.dart:110 — packages/secure_storage/amplify_secure_storage/lib/src/amplify_secure_storage.vm.dart:110-114 | packages/secure_storage/amplify_secure_storage_dart/lib/src/platforms/amplify_secure_storage_web.dart:49-53 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:503 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:503-507 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:392-398 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthSignInRequest.swift:22 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthSignInRequest.swift:22-26 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthSignUpRequest.swift:22-26 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthConfirmResetPasswordRequest.swift:25 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthConfirmResetPasswordRequest.swift:25-33 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Request/AuthConfirmSignUpRequest.swift:22-26 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×10
  • Edited copy of a member (7 corresponding lines) packages/secure_storage/amplify_secure_storage_dart/lib/src/amplify_secure_storage_dart.dart:129 — packages/secure_storage/amplify_secure_storage_dart/lib/src/amplify_secure_storage_dart.dart:129-135 | packages/secure_storage/amplify_secure_storage_dart/lib/src/amplify_secure_storage_dart.dart:148-154 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Decorator/ModelIdDecorator.swift:32 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Decorator/ModelIdDecorator.swift:32-38 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Decorator/ModelIdDecorator.swift:40-46 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterDataStoreRequestUtils.swift:41 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterDataStoreRequestUtils.swift:41-48 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:638-644 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:128 — packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:128-135 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/hosted_ui_state_machine.dart:43-49 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/screens/authenticator_screen.dart:216 — packages/authenticator/amplify_authenticator/lib/src/screens/authenticator_screen.dart:216-222 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/phone_number_field.dart:118-126 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/inherited_config.dart:57 — packages/authenticator/amplify_authenticator/lib/src/state/inherited_config.dart:57-63 | packages/authenticator/amplify_authenticator/lib/src/widgets/social/social_button.dart:117-123 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedCustomType.kt:19 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedCustomType.kt:19-25 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedModel.kt:24-31 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubError.swift:31 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubError.swift:31-37 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/LoggingError.swift:32-38 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:878 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:878-884 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/verify_user_form_field.dart:129-138 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/RemoteSyncReconciler.swift:26 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/RemoteSyncReconciler.swift:26-32 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Subscribe/MutationEvent+MutationType.swift:19-28 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×9
  • Edited copy of a member (16 corresponding lines) packages/amplify_datastore/lib/src/method_channel_datastore.dart:173 — packages/amplify_datastore/lib/src/method_channel_datastore.dart:173-188 | packages/amplify_datastore/lib/src/method_channel_datastore.dart:190-205 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:219 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:219-234 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:284-302 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/smithy/smithy_codegen/lib/src/generator/visitors/library_visitor.dart:207 — packages/smithy/smithy_codegen/lib/src/generator/visitors/library_visitor.dart:207-226 | packages/smithy/smithy_codegen/lib/src/generator/visitors/library_visitor.dart:228-243 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/smithy/smithy/lib/src/protocol/json_serializer.dart:23 — packages/smithy/smithy/lib/src/protocol/json_serializer.dart:23-42 | packages/smithy/smithy/lib/src/protocol/xml_serializer.dart:16-31 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/QueryPredicate+GraphQL.swift:22 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/QueryPredicate+GraphQL.swift:22-37 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/QueryPredicate+GraphQL.swift:39-56 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStore.swift:197 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStore.swift:197-212 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStore.swift:214-230 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration.swift:74 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration.swift:74-90 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration.swift:92-107 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/api/amplify_api/example/lib/widgets/get_by_id.dart:34 — packages/api/amplify_api/example/lib/widgets/get_by_id.dart:34-49 | packages/api/amplify_api/example/lib/widgets/get_by_id.dart:52-67 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:53 — packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:53-68 | packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart:53-68 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×9
  • Duplicated block (12 lines × 2) packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:37 — packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:37-48 | packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:125-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:222 — packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:222-233 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:284-295 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:411 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:411-422 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:436-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:411` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:465 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:465-476 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:488-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:465` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) packages/kinesis/amplify_firehose_dart/lib/src/impl/firehose_sender.dart:25 — packages/kinesis/amplify_firehose_dart/lib/src/impl/firehose_sender.dart:25-38 | packages/kinesis/amplify_kinesis_dart/lib/src/impl/kinesis_sender.dart:23-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `packages/kinesis/amplify_firehose_dart/lib/src/impl/firehose_sender.dart:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (12 lines × 2) packages/smithy/smithy/lib/src/protocol/json_serializer.dart:44 — packages/smithy/smithy/lib/src/protocol/json_serializer.dart:44-55 | packages/smithy/smithy/lib/src/protocol/xml_serializer.dart:33-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy/lib/src/protocol/json_serializer.dart:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:535 — packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:535-546 | packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:648-659 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:535` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) packages/amplify_core/lib/src/types/storage/upload_data_options.dart:30 — packages/amplify_core/lib/src/types/storage/upload_data_options.dart:30-41 | packages/amplify_core/lib/src/types/storage/upload_file_options.dart:30-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/DataStoreError+Plugin.swift:26 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/DataStoreError+Plugin.swift:26-37 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/DataStoreError+Plugin.swift:40-51 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/DataStoreError+Plugin.swift:26` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×9
  • Duplicated block (7 lines × 2) packages/amplify_core/lib/src/types/exception/amplify_exception.dart:81 — packages/amplify_core/lib/src/types/exception/amplify_exception.dart:81-87 | packages/amplify_core/lib/src/types/exception/error/amplify_error.dart:27-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:629 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:629-635 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:907-913 — before extracting anything, compare `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart` and `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart:51 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart:51-57 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_setup_selection_form_field.dart:49-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/hub/FlutterOutboxMutationEnqueuedEvent.kt:14 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/hub/FlutterOutboxMutationEnqueuedEvent.kt:14-20 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/hub/FlutterOutboxMutationProcessedEvent.kt:14-20 — before extracting anything, compare `packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/hub/FlutterOutboxMutationEnqueuedEvent.kt` and `packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/hub/FlutterOutboxMutationProcessedEvent.kt` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:172 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:172-178 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:194-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:172` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelField.swift:17 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelField.swift:17-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelSchema.swift:16-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) canaries/ios/Runner/AppDelegate.swift:6 — canaries/ios/Runner/AppDelegate.swift:6-12 | packages/worker_bee/e2e_flutter_test/ios/Runner/AppDelegate.swift:9-15 — before extracting anything, compare `canaries/ios/Runner/AppDelegate.swift` and `packages/worker_bee/e2e_flutter_test/ios/Runner/AppDelegate.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift:31 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift:31-37 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationProcessedEvent.swift:32-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyConfiguration.swift:186 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyConfiguration.swift:186-192 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyOutputsData.swift:356-362 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×8
  • Edited copy of a member (15 corresponding lines) packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:449 — packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:449-463 | packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:624-646 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:352 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:352-368 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:370-384 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Request/GraphQLOperationRequest.swift:35 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Request/GraphQLOperationRequest.swift:35-51 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Request/GraphQLRequest.swift:38-52 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:298 — packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:298-317 | packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:483-497 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:295 — packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:295-309 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:311-325 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/AuthRule.swift:53 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/AuthRule.swift:53-69 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:139-153 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/amplify_datastore/lib/amplify_datastore.dart:240 — packages/amplify_datastore/lib/amplify_datastore.dart:240-254 | packages/amplify_datastore/lib/src/method_channel_datastore.dart:275-291 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:266 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:266-280 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:282-296 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×8
  • Edited copy of a member (9 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:89 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:89-97 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:156-164 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/smithy/smithy/lib/src/http/interceptors/checksum.dart:22 — packages/smithy/smithy/lib/src/http/interceptors/checksum.dart:22-30 | packages/smithy/smithy_aws/lib/src/http/interceptors/with_checksum.dart:89-99 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:101 — packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:101-109 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:111-119 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Lazy/LazyReference.swift:66 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Lazy/LazyReference.swift:66-74 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Lazy/List+Model.swift:75-83 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations_en.dart:77 — packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations_en.dart:77-87 | packages/authenticator/amplify_authenticator/lib/src/l10n/generated/input_localizations_en.dart:45-53 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/smithy/smithy_codegen/lib/src/generator/enum_generator.dart:32 — packages/smithy/smithy_codegen/lib/src/generator/enum_generator.dart:32-40 | packages/smithy/smithy_codegen/lib/src/generator/union_generator.dart:25-33 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/smithy/smithy/lib/src/serialization/xml/xml_bool_serializer.dart:14 — packages/smithy/smithy/lib/src/serialization/xml/xml_bool_serializer.dart:14-22 | packages/smithy/smithy_test/lib/src/http/serializers.dart:64-72 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) packages/example_common/lib/src/components/flex_component.dart:28 — packages/example_common/lib/src/components/flex_component.dart:28-38 | packages/example_common/lib/src/components/center_component.dart:17-25 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×8
  • Duplicated block (14 lines × 2) packages/amplify_datastore/lib/src/method_channel_datastore.dart:175 — packages/amplify_datastore/lib/src/method_channel_datastore.dart:175-188 | packages/amplify_datastore/lib/src/method_channel_datastore.dart:192-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:47 — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:47-60 | packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_username_field.dart:64-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:112 — packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:112-125 | packages/worker_bee/worker_bee_builder/lib/src/impl/vm.dart:53-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:305 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:305-318 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:314-327 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (14 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadFileRequest.swift:38 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadFileRequest.swift:38-52 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageUploadFileRequest.swift:35-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (14 lines × 2) packages/amplify_datastore/example/lib/widgets/auth_view.dart:57 — packages/amplify_datastore/example/lib/widgets/auth_view.dart:57-70 | packages/amplify_datastore/example/lib/widgets/auth_view.dart:74-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/example/lib/widgets/auth_view.dart:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) packages/api/amplify_api/example/lib/rest_api_view.dart:29 — packages/api/amplify_api/example/lib/rest_api_view.dart:29-42 | packages/api/amplify_api/example/lib/rest_api_view.dart:47-60 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/api/amplify_api/example/lib/rest_api_view.dart:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:53 — packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:53-66 | packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart:53-66 — before extracting anything, compare `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart` and `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×7
  • Edited copy of a member (12 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/AWSModelReconciliationQueue.swift:272 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/AWSModelReconciliationQueue.swift:272-283 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/AWSModelReconciliationQueue.swift:285-298 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) packages/amplify_datastore/lib/amplify_datastore.dart:337 — packages/amplify_datastore/lib/amplify_datastore.dart:337-348 | packages/amplify_datastore/lib/amplify_datastore.dart:350-361 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_flutter.dart:56 — packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_flutter.dart:56-67 | packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_flutter.dart:69-80 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+Delete.swift:18 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+Delete.swift:18-29 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+Update.swift:19-31 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) packages/smithy/smithy/lib/src/ast/traits/aws/protocols/aws_query_trait.dart:21 — packages/smithy/smithy/lib/src/ast/traits/aws/protocols/aws_query_trait.dart:21-33 | packages/smithy/smithy/lib/src/ast/traits/aws/protocols/ec2_query_trait.dart:21-32 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:30 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:30-42 | packages/auth/amplify_auth_cognito/example/lib/screens/update_password.dart:31-42 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_up.dart:46 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_up.dart:46-57 | packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:73-84 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×7
  • Edited copy of a member (8 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:117 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:117-124 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:578-586 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Embedded.swift:27 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Embedded.swift:27-34 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/Model+Schema.swift:49-56 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin.swift:279 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin.swift:279-287 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:403-410 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) packages/smithy/smithy/lib/src/ast/traits/aws/protocols/aws_json_1_0_trait.dart:30 — packages/smithy/smithy/lib/src/ast/traits/aws/protocols/aws_json_1_0_trait.dart:30-37 | packages/smithy/smithy/lib/src/ast/traits/aws/protocols/aws_json_1_1_trait.dart:30-37 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) packages/smithy/smithy/lib/src/serialization/query/query_bool_serializer.dart:21 — packages/smithy/smithy/lib/src/serialization/query/query_bool_serializer.dart:21-28 | packages/smithy/smithy/lib/src/serialization/query/query_double_serializer.dart:21-28 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) packages/amplify_connect_client/amplify_connect_client/example/lib/main.dart:24 — packages/amplify_connect_client/amplify_connect_client/example/lib/main.dart:24-31 | packages/worker_bee/worker_bee/example/lib/main.dart:24-34 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) packages/api/amplify_api/example/lib/graphql_api_view.dart:45 — packages/api/amplify_api/example/lib/graphql_api_view.dart:45-52 | packages/api/amplify_api/example/lib/rest_api_view.dart:91-98 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×7
  • Duplicated block (6 lines × 2) packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:52 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:52-57 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart:55-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart:61` calls `add`, `XmlElementName` and `packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:58` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) packages/amplify_core/lib/src/types/temporal/temporal_datetime.dart:183 — packages/amplify_core/lib/src/types/temporal/temporal_datetime.dart:183-188 | packages/amplify_core/lib/src/types/temporal/temporal_time.dart:182-187 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:290 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:290-296 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/SyncMutationToCloudOperation.swift:198-203 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:290` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:115 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:115-120 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/Internal/InternalTask+Hub.swift:74-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:122 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:122-127 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/Internal/InternalTask+Hub.swift:105-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:196 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:196-201 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/AWSModelReconciliationQueue.swift:258-263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:203 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:203-208 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/AWSModelReconciliationQueue.swift:265-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×6
  • Edited copy of a member (19 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:70 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:70-88 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:134-154 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:296 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:296-319 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:343-361 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) packages/amplify_core/lib/src/types/models/model_field_definition.dart:24 — packages/amplify_core/lib/src/types/models/model_field_definition.dart:24-42 | packages/amplify_core/lib/src/types/models/model_field_definition.dart:44-62 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) packages/aws_common/lib/src/io/aws_file_platform_html.dart:69 — packages/aws_common/lib/src/io/aws_file_platform_html.dart:69-92 | packages/aws_common/lib/src/io/aws_file_platform_io.dart:49-67 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_up_form_field.dart:193 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_up_form_field.dart:193-211 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_in_form_field.dart:192-212 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) packages/authenticator/amplify_authenticator/example/lib/authenticator_with_controllers.dart:55 — packages/authenticator/amplify_authenticator/example/lib/authenticator_with_controllers.dart:55-73 | packages/storage/amplify_storage_s3/example/lib/main.dart:49-69 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×6
  • Edited copy of a member (14 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:458 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:458-471 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:475-496 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:320 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:320-333 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:298-312 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:236 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:236-249 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:251-264 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) packages/smithy/smithy/lib/src/serialization/xml/xml_num_serializer.dart:48 — packages/smithy/smithy/lib/src/serialization/xml/xml_num_serializer.dart:48-61 | packages/smithy/smithy/lib/src/serialization/json/double_serializer.dart:22-35 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) packages/storage/amplify_storage_s3/example/lib/main.dart:173 — packages/storage/amplify_storage_s3/example/lib/main.dart:173-188 | packages/storage/amplify_storage_s3/example/lib/main.dart:191-204 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) packages/kinesis/amplify_kinesis/example/lib/main.dart:209 — packages/kinesis/amplify_kinesis/example/lib/main.dart:209-222 | packages/kinesis/amplify_kinesis/example/lib/main.dart:224-240 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×6
  • Edited copy of a member (13 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Error/AuthError.swift:40 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Error/AuthError.swift:40-52 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Error/StorageError.swift:108-121 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:357 — packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:357-369 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:371-383 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart:29 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_selection_form_field.dart:29-46 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/mfa_setup_selection_form_field.dart:32-44 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) packages/amplify_core/lib/src/types/models/auth_rule.dart:71 — packages/amplify_core/lib/src/types/models/auth_rule.dart:71-84 | packages/amplify_core/lib/src/types/models/model_field.dart:64-76 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/Internal/HubCategory+CategoryConfigurable.swift:12 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/Internal/HubCategory+CategoryConfigurable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/Internal/HubCategory+CategoryConfigurable.swift:30-43 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:155 — packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:155-167 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_layout.dart:177-189 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×6
  • Edited copy of a member (11 corresponding lines) packages/smithy/smithy_codegen/lib/src/generator/visitors/symbol_visitor.dart:19 — packages/smithy/smithy_codegen/lib/src/generator/visitors/symbol_visitor.dart:19-29 | packages/smithy/smithy_codegen/lib/src/generator/visitors/symbol_visitor.dart:117-127 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:214 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:214-224 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreBridge.swift:12-25 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) packages/amplify_core/lib/src/types/analytics/analytics/custom_properties.dart:39 — packages/amplify_core/lib/src/types/analytics/analytics/custom_properties.dart:39-49 | packages/amplify_core/lib/src/types/analytics/analytics/custom_properties.dart:51-61 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:272 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:272-284 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:286-296 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) packages/smithy/smithy/lib/src/ast/shapes/shape_map.dart:137 — packages/smithy/smithy/lib/src/ast/shapes/shape_map.dart:137-147 | packages/smithy/smithy/lib/src/ast/shapes/collection_shape.dart:66-76 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations_en.dart:60 — packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations_en.dart:60-75 | packages/authenticator/amplify_authenticator/lib/src/l10n/generated/input_localizations_en.dart:104-114 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×6
  • Edited copy of a member (4 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:18 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:18-21 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:10-14 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:338 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:338-341 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:40-43 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:379 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:379-382 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:64-67 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_info_store_manager.dart:115 — packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_info_store_manager.dart:115-118 | packages/secure_storage/amplify_secure_storage/lib/src/amplify_secure_storage.web.dart:53-56 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) packages/secure_storage/amplify_secure_storage/ios/amplify_secure_storage/Sources/amplify_secure_storage/AmplifySecureStoragePlugin.swift:6 — packages/secure_storage/amplify_secure_storage/ios/amplify_secure_storage/Sources/amplify_secure_storage/AmplifySecureStoragePlugin.swift:6-9 | packages/secure_storage/amplify_secure_storage/macos/amplify_secure_storage/Sources/amplify_secure_storage/AmplifySecureStoragePlugin.swift:6-9 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) packages/authenticator/amplify_authenticator_test/lib/src/pages/sign_in_page.dart:21 — packages/authenticator/amplify_authenticator_test/lib/src/pages/sign_in_page.dart:21-24 | packages/authenticator/amplify_authenticator_test/lib/src/pages/sign_up_page.dart:38-41 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×5
  • Edited copy of a member (17 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:236 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:236-252 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:254-270 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) packages/amplify_datastore/lib/src/method_channel_datastore.dart:327 — packages/amplify_datastore/lib/src/method_channel_datastore.dart:327-343 | packages/amplify_datastore/lib/src/method_channel_datastore.dart:345-361 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) packages/aft/lib/src/commands/bootstrap_command.dart:64 — packages/aft/lib/src/commands/bootstrap_command.dart:64-87 | packages/aft/lib/src/commands/bootstrap_command.dart:89-105 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/authenticator_state.dart:614 — packages/authenticator/amplify_authenticator/lib/src/state/authenticator_state.dart:614-634 | packages/authenticator/amplify_authenticator/lib/src/state/authenticator_state.dart:636-652 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) packages/smithy/smithy/lib/src/ast/traits/aws/protocols/rest_json_1_trait.dart:35 — packages/smithy/smithy/lib/src/ast/traits/aws/protocols/rest_json_1_trait.dart:35-51 | packages/smithy/smithy/lib/src/ast/traits/aws/protocols/rest_xml_trait.dart:35-54 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:321 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:321-330 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:363-371 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:410-418 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:99 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:99-107 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:254-264 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:266-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Core/DataStoreListProvider.swift:88 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Core/DataStoreListProvider.swift:88-99 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Core/DataStoreModelProvider.swift:53-61 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Lazy/DefaultModelProvider.swift:37-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_flutter.dart:45 — packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_flutter.dart:45-54 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_html.dart:21-29 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:89-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) packages/api/amplify_api/example/lib/widgets/create.dart:30 — packages/api/amplify_api/example/lib/widgets/create.dart:30-40 | packages/api/amplify_api/example/lib/widgets/create.dart:44-53 | packages/api/amplify_api/example/lib/widgets/create.dart:57-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×5
  • Edited copy of a member (6 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:88 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:88-93 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:129-140 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:386 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:386-391 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RemoteSyncEngine.swift:404-409 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) packages/amplify_core/lib/src/config/auth/cognito/s3_transfer_utility.dart:21 — packages/amplify_core/lib/src/config/auth/cognito/s3_transfer_utility.dart:21-26 | packages/amplify_core/lib/src/config/storage/s3_config.dart:51-56 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) packages/amplify_core/lib/src/plugin/amplify_datastore_plugin_interface.dart:101 — packages/amplify_core/lib/src/plugin/amplify_datastore_plugin_interface.dart:101-106 | packages/amplify_datastore/lib/amplify_datastore.dart:217-223 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) packages/amplify_core/lib/src/types/query/query_field_operators.dart:276 — packages/amplify_core/lib/src/types/query/query_field_operators.dart:276-282 | packages/amplify_core/lib/src/types/query/query_predicate.dart:88-93 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×5
  • Duplicated block (15 lines × 2) packages/smithy/smithy_aws/lib/src/http/interceptors/s3/check_error_on_success.dart:41 — packages/smithy/smithy_aws/lib/src/http/interceptors/s3/check_error_on_success.dart:41-57 | packages/smithy/smithy_aws/lib/src/http/interceptors/s3/check_partial_response.dart:18-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy_aws/lib/src/http/interceptors/s3/check_error_on_success.dart:41` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:407 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:407-421 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:469-483 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:407` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift:12 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift:12-26 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift:43-57 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:58 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:58-72 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:113-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 2) packages/auth/amplify_auth_cognito/example/lib/main.dart:121 — packages/auth/amplify_auth_cognito/example/lib/main.dart:121-135 | packages/storage/amplify_storage_s3/example/lib/main.dart:71-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×5
  • Duplicated block (13 lines × 2) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:297 — packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:297-309 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:313-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_device_password_verifier_worker.dart:97 — packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_device_password_verifier_worker.dart:97-109 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_password_verifier_worker.dart:109-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_device_password_verifier_worker.dart:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) packages/storage/amplify_storage_s3/lib/src/utils/app_path_provider/app_path_provider_stub.dart:13 — packages/storage/amplify_storage_s3/lib/src/utils/app_path_provider/app_path_provider_stub.dart:13-25 | packages/storage/amplify_storage_s3_dart/lib/src/utils/app_path_provider/app_path_provider_stub.dart:13-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13 lines × 2) packages/storage/amplify_storage_s3/example/lib/main.dart:176 — packages/storage/amplify_storage_s3/example/lib/main.dart:176-188 | packages/storage/amplify_storage_s3/example/lib/main.dart:192-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:175 — packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:175-187 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_layout.dart:157-169 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×5
  • Duplicated block (10 lines × 2) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:153 — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:153-162 | packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_username_field.dart:180-189 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:185 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:185-194 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:204-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:185` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterDataStoreRequestUtils.swift:8 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterDataStoreRequestUtils.swift:8-17 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/modelHelpers.swift:42-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/GraphQLResponse+Decode.swift:23 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/GraphQLResponse+Decode.swift:23-32 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/GraphQLResponse+Decode.swift:45-54 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/GraphQLResponse+Decode.swift:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:133 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:133-142 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/StorageEngine.swift:247-256 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (4 members, 50+ identical tokens) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:338 — packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:338-355 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:385-402 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:404-421 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:423-440 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:34 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:34-57 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:32-69 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart:32-71 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart:33-56 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:59 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:59-84 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:71-124 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart:73-111 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart:58-82 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:142 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:142-168 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:170-189 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:191-214 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:246-272 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×4
  • Edited copy of a member (26 corresponding lines) packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:87 — packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:87-112 | packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_memory.dart:39-64 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreError.swift:30 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreError.swift:30-55 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreError.swift:57-83 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift:11 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift:11-36 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/Internal/LoggingCategory+CategoryConfigurable.swift:42-67 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) packages/analytics/amplify_analytics_pinpoint/example/lib/main.dart:36 — packages/analytics/amplify_analytics_pinpoint/example/lib/main.dart:36-69 | packages/kinesis/amplify_kinesis/example/lib/main.dart:70-95 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×4
  • Edited copy of a member (3 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Temporal/Date+Operation.swift:117 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Temporal/Date+Operation.swift:117-119 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Temporal/Time+Operation.swift:128-130 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Temporal/Date+Operation.swift:105 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Temporal/Date+Operation.swift:105-107 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Temporal/Time+Operation.swift:119-121 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) packages/aft/lib/src/config/config.dart:121 — packages/aft/lib/src/config/config.dart:121-123 | packages/aft/lib/src/config/raw_config.dart:210-212 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) packages/aws_common/lib/src/http/aws_http_request.dart:302 — packages/aws_common/lib/src/http/aws_http_request.dart:302-304 | packages/aws_common/lib/src/http/aws_http_response.dart:51-53 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×4
  • Duplicated block (11 lines × 2) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:61 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:61-72 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart:60-70 — before extracting anything, compare `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart` and `packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:637 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:637-647 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:915-925 — before extracting anything, compare `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart` and `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:52 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:52-62 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/Internal/InternalTask+Hub.swift:12-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:70 — packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:70-80 | packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart:70-80 — before extracting anything, compare `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart` and `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
P3 · Security & performance tooling · Analyzer excludes 1 path(s) that do not exist · ×4
  • Analyzer excludes 1 path(s) that do not exist packages/aft/analysis_options.yaml:1 — `packages/aft/analysis_options.yaml` excludes `external/` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do.
  • Analyzer excludes 1 path(s) that do not exist packages/api/amplify_api/analysis_options.yaml:1 — `packages/api/amplify_api/analysis_options.yaml` excludes `lib/src/native_api_plugin.dart` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do.
  • Analyzer excludes 1 path(s) that do not exist packages/auth/amplify_auth_cognito/analysis_options.yaml:1 — `packages/auth/amplify_auth_cognito/analysis_options.yaml` excludes `lib/src/native_auth_plugin.dart` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do.
  • Analyzer excludes 1 path(s) that do not exist packages/example_common/analysis_options.yaml:1 — `packages/example_common/analysis_options.yaml` excludes `lib/amplifyconfiguration.dart` from analysis, and no such path is in the repository. These entries are dead configuration: they silence nothing today, and each one is a name the analyzer will silently start honouring the moment a directory of that name appears — so the file's exclusion list is wider than anything anybody decided. Delete the entries that no longer name anything, and keep the ones that do.
X1 · Async correctness · `async` callback passed to `forEach` · ×4
  • `async` callback passed to `forEach` tool/bump_version.dart:40 — `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` tool/bump_version.dart:65 — `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` packages/amplify_datastore/lib/amplify_datastore.dart:405 — `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` packages/amplify_datastore/lib/amplify_datastore.dart:426 — `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×4
  • Recursive walk over a caller-supplied document has no depth cap packages/smithy/smithy/lib/src/serialization/xml/smithy_xml_plugin.dart:164 — `afterSerialize` is public, takes a document from its caller (line 21) and hands it to `_nest`, which calls itself at line 164 (`_nest`) with a piece of `value` (and at line 169) — and nowhere in `_nest` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `_nest` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/smithy/smithy/lib/src/serialization/xml/smithy_xml_plugin.dart:207 — `beforeDeserialize` is public, takes a document from its caller (line 178) and hands it to `_deserialize`, which calls itself at line 207 (`_deserialize`) with a piece of `node` (and at line 209, line 225) — and nowhere in `_deserialize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `_deserialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:691 — `deserializeNestedModel` is public and takes `serializedModelData: Map<String, Any ?>` from its caller, and it calls itself at line 691 with a piece of `serializedModelData` — the function is not `tailrec`, so every call is a real frame — and nowhere in `deserializeNestedModel` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25; Android's threads are smaller). kotlinx.serialization's `parseToJsonElement` accepts nested arrays to any depth and Android's built-in `org.json` sets no limit, while Jackson 2.15+ stops at 1,000 — on a cold JVM past the point the walk fails; Gson 2.12+ and Moshi stop at 255. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (e: Exception)` around the call does not stop it, and on Android an uncaught one ends the process. Thread a depth argument through `deserializeNestedModel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack or a `DeepRecursiveFunction`.
  • Recursive walk over a caller-supplied document has no depth cap packages/aft/lib/src/config/package_selector.dart:73 — `PackageSelector.fromJson` is public and takes `Object ? json` from its caller, and it calls itself at line 73 (`PackageSelector.fromJson`) with a piece of `json` (and at line 85, line 86, line 93, line 99) — and nowhere in `PackageSelector.fromJson` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. `jsonDecode` sets no nesting limit: 2 MB of brackets parse to a million levels, while a walk like this one throws `StackOverflowError` from about 20,000 levels — 40,000 bytes (Dart 3.13 VM; on the web the limit is the browser's stack). That is an `Error`, not an `Exception`: an `on Exception catch` around the call does not stop it, so the request, the frame or the isolate fails with it. Thread a depth argument through `PackageSelector.fromJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×3
  • Edited copy of a member (35 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:717 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:717-751 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:689-729 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:203 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:203-237 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:239-280 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:530 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:530-566 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:588-622 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 20+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:571 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:571-590 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:592-611 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:613-632 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:64 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:64-84 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift:86-109 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/Internal/InternalTask+Hub.swift:51-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/inherited_auth_bloc.dart:20 — packages/authenticator/amplify_authenticator/lib/src/state/inherited_auth_bloc.dart:20-39 | packages/authenticator/amplify_authenticator/lib/src/state/inherited_authenticator_builder.dart:20-41 | packages/authenticator/amplify_authenticator/lib/src/state/inherited_authenticator_state.dart:20-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 11+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:319 — packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:319-329 | packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:510-522 | packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:547-557 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsProfile.swift:35 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsProfile.swift:35-45 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Model/BasicUserProfile.swift:29-39 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Model/UserProfile.swift:57-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubError.swift:39 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubError.swift:39-49 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Logging/LoggingError.swift:40-50 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Error/CoreError.swift:53-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×3
  • Duplicated block (15–16 lines × 2) packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:376 — packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:376-391 | packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:483-497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15–16 lines × 2) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:669 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:669-684 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:718-732 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:669` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15–16 lines × 2) packages/kinesis/amplify_firehose/example/lib/main.dart:30 — packages/kinesis/amplify_firehose/example/lib/main.dart:30-44 | packages/kinesis/amplify_kinesis/example/lib/main.dart:35-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×3
  • Duplicated block (9 lines × 4) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:340 — packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:340-348 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:387-395 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:406-414 | packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:425-433 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:340` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 4) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:38 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:38-46 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:36-44 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart:36-44 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart:37-45 — before extracting anything, compare `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart` and `packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:38` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 4) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:410 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:410-418 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:422-430 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:477-485 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:516-524 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:410` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `flutterResult` to `flutterResult) case .success(let res` in one and `flutterResult) case .success(let model` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3
  • Duplicated block (19 lines × 2) packages/secure_storage/amplify_secure_storage_dart/lib/src/mixins/amplify_secure_storage_mixin.vm.dart:29 — packages/secure_storage/amplify_secure_storage_dart/lib/src/mixins/amplify_secure_storage_mixin.vm.dart:29-47 | packages/secure_storage/amplify_secure_storage_dart/lib/src/mixins/amplify_secure_storage_mixin.web.dart:14-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift:11 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift:11-29 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationProcessedEvent.swift:12-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (19 lines × 2) packages/authenticator/amplify_authenticator/example/lib/main.dart:229 — packages/authenticator/amplify_authenticator/example/lib/main.dart:229-247 | packages/authenticator/amplify_authenticator/example/lib/main.dart:253-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) packages/storage/amplify_storage_s3/lib/src/utils/app_path_provider/app_path_provider_html.dart:11 — packages/storage/amplify_storage_s3/lib/src/utils/app_path_provider/app_path_provider_html.dart:11-19 | packages/storage/amplify_storage_s3_dart/lib/src/utils/app_path_provider/app_path_provider_html.dart:13-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) packages/authenticator/amplify_authenticator/lib/src/services/amplify_auth_service.dart:89 — packages/authenticator/amplify_authenticator/lib/src/services/amplify_auth_service.dart:89-97 | packages/notifications/push/amplify_push_notifications_pinpoint/lib/src/pinpoint_provider.dart:55-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOperation.swift:275 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOperation.swift:275-283 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:130-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
R7 · Dead Code · Dead file (~54 LoC) · ×3
  • Dead file (~54 LoC) infra-gen2/infra-common/src/lambda-triggers/enable-sms-mfa.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~54 LoC) infra/lib/auth/stack.delete-device.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~54 LoC) infra/lib/auth/stack.enable-sms-mfa.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
D2 · Cognitive Complexity · DataStoreHubEventStreamHandler.sendPayload (cognitive 32) · ×2
  • DataStoreHubEventStreamHandler.sendPayload (cognitive 32) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/DataStoreHubEventStreamHandler.kt:82 — DataStoreHubEventStreamHandler.sendPayload has cognitive complexity 32 (threshold 15). Drivers by points: error handling 11 (21 pts), if/else 7 (10 pts), match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • DataStoreHubEventStreamHandler.sendPayload (cognitive 32) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreHubEventStreamHandler.swift:79 — DataStoreHubEventStreamHandler.sendPayload has cognitive complexity 32 (threshold 15). Drivers by points: error handling 10 (20 pts), if/else 5 (11 pts), match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: SwiftAmplifyDataStorePlugin.swift ↔ amplify_datastore.dart packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:1 — `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift` and `packages/amplify_datastore/lib/amplify_datastore.dart` change together 61% of the time (14 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `dc33017e` fix(datastore): Restart Sync Engine when network on/off (#5218) (at that commit the file was still `packages/amplify_datastore/ios/Classes/SwiftAmplifyDataStorePlugin.swift`); `d59a8047` fix(datastore): Clear subscriptions on Stop (#5253) (at that commit the file was still `packages/amplify_datastore/ios/Classes/SwiftAmplifyDataStorePlugin.swift`); `51c6485c` feat(datastore): Multi-auth (#1478) (at that commit the file was still `packages/amplify_datastore/ios/Classes/SwiftAmplifyDataStorePlugin.swift`) — run `git show` on any of them.
  • Change coupling: auth.dart ↔ amplify_auth_category.dart packages/amplify_core/doc/lib/auth.dart:1 — `packages/amplify_core/doc/lib/auth.dart` and `packages/amplify_core/lib/src/category/amplify_auth_category.dart` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c6a06efd` feat(Auth): Add fetchCurrentDevice API (#5251); `5efee22c` feat: rename sendUserAttributeVerificationCode (#3759); `4d50bb1b` docs(auth): Update TOTP snippets — run `git show` on any of them.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStoreError.swift:34 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStoreError.swift:34-46 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Error/AnalyticsError.swift:54-66 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Error/AuthError.swift:84-96 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Error/PushNotificationsError.swift:55-67 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Error/StorageError.swift:123-135 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:44 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:44-95 | packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_in.dart:45-79 | packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_up.dart:59-110 | packages/auth/amplify_auth_cognito/example/lib/screens/sign_up.dart:53-117 | packages/auth/amplify_auth_cognito/example/lib/screens/update_password.dart:44-93 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×2
  • Edited copy of a member (37 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:668 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:668-712 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:717-753 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) packages/storage/amplify_storage_s3_dart/lib/src/amplify_storage_s3_dart_impl.dart:253 — packages/storage/amplify_storage_s3_dart/lib/src/amplify_storage_s3_dart_impl.dart:253-289 | packages/storage/amplify_storage_s3_dart/lib/src/amplify_storage_s3_dart_impl.dart:291-329 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×2
  • Edited copy of a member (45 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:435 — packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:435-479 | packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:787-837 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:69 — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:69-113 | packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_username_field.dart:94-138 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 22+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:277 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:277-298 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:308-329 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:331-358 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:456 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:456-479 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:481-502 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:504-527 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×2
  • Edited copy of a member (33 corresponding lines) packages/kinesis/amplify_firehose_dart/lib/src/impl/firehose_sender.dart:25 — packages/kinesis/amplify_firehose_dart/lib/src/impl/firehose_sender.dart:25-57 | packages/kinesis/amplify_kinesis_dart/lib/src/impl/kinesis_sender.dart:23-63 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:75 — packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:75-107 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:115-147 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:28 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:28-50 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:62-82 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift:53 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift:53-73 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift:122-143 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:184 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:184-201 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:203-220 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:718 — packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:718-735 | packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:768-785 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyInProcessReportingOperation.swift:61 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyInProcessReportingOperation.swift:61-82 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyOperation.swift:120-143 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Operation/AmplifyOperation+APIPublishers.swift:21 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Operation/AmplifyOperation+APIPublishers.swift:21-43 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Operation/AmplifyOperation+APIPublishers.swift:59-80 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×2
  • Edited copy of a member (32 corresponding lines) packages/aft/lib/src/commands/publish_command.dart:305 — packages/aft/lib/src/commands/publish_command.dart:305-360 | packages/aft/lib/src/commands/version_bump_command.dart:17-48 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:65 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:65-96 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attribute.dart:81-114 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×2
  • Edited copy of a member (20 corresponding lines) packages/amplify_core/lib/src/types/models/model_field_definition.dart:104 — packages/amplify_core/lib/src/types/models/model_field_definition.dart:104-124 | packages/amplify_core/lib/src/types/models/model_field_definition.dart:126-145 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) packages/auth/amplify_auth_cognito/darwin/amplify_auth_cognito/Sources/amplify_auth_cognito/AmplifyAuthCognitoPlugin.swift:35 — packages/auth/amplify_auth_cognito/darwin/amplify_auth_cognito/Sources/amplify_auth_cognito/AmplifyAuthCognitoPlugin.swift:35-54 | packages/auth/amplify_auth_cognito/darwin/amplify_auth_cognito/Sources/amplify_auth_cognito/AmplifyAuthCognitoPlugin.swift:56-75 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 6+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:166 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:166-177 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:179-188 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:33-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) packages/amplify_core/lib/src/config/analytics/pinpoint_config.dart:82 — packages/amplify_core/lib/src/config/analytics/pinpoint_config.dart:82-87 | packages/amplify_core/lib/src/config/auth/cognito/pinpoint_analytics.dart:25-30 | packages/amplify_core/lib/src/config/notifications/notifications_pinpoint_config.dart:53-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 5+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:276 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:276-285 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:287-294 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory+Behavior.swift:58-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/button.dart:358 — packages/authenticator/amplify_authenticator/lib/src/widgets/button.dart:358-362 | packages/authenticator/amplify_authenticator/lib/src/widgets/form.dart:93-102 | packages/authenticator/amplify_authenticator/lib/src/widgets/progress.dart:21-25 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:551 — packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:551-567 | packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:590-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:551` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) packages/kinesis/amplify_kinesis/example/lib/main.dart:322 — packages/kinesis/amplify_kinesis/example/lib/main.dart:322-338 | packages/kinesis/amplify_kinesis/example/lib/main.dart:368-384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/kinesis/amplify_kinesis/example/lib/main.dart:322` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:330 — packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:330-345 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:354-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:330` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:50 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:50-65 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:75-90 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×2
  • Duplicated block (13 lines × 3) packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:56 — packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:56-68 | packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart:56-68 | packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations_en.dart:63-75 — before extracting anything, compare `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart` and `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_es.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations_en.dart:56` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (13 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadDataRequest.swift:33 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadDataRequest.swift:33-45 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageGetURLRequest.swift:32-44 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageRemoveRequest.swift:31-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_stub.dart:13 — packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_stub.dart:13-30 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_stub.dart:12-29 — before extracting anything, compare `packages/auth/amplify_auth_cognito/lib/src/flows/hosted_ui/hosted_ui_platform_stub.dart` and `packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_stub.dart` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 2) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:695 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:695-712 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:736-753 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:695` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) packages/authenticator/amplify_authenticator/lib/src/screens/authenticator_screen.dart:150 — packages/authenticator/amplify_authenticator/lib/src/screens/authenticator_screen.dart:150-154 | packages/authenticator/amplify_authenticator/lib/src/screens/authenticator_screen.dart:193-197 | packages/authenticator/amplify_authenticator/lib/src/state/inherited_authenticator_state.dart:43-47 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (5 lines × 3) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:27 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:27-31 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attribute.dart:38-42 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attributes.dart:45-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) packages/smithy/smithy/lib/src/ast/shapes/collection_shape.dart:25 — packages/smithy/smithy/lib/src/ast/shapes/collection_shape.dart:25-29 | packages/smithy/smithy/lib/src/ast/shapes/shape_map.dart:14-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/SelectionSet.swift:45 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/SelectionSet.swift:45-49 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/SelectionSet.swift:77-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/SelectionSet.swift:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×2
  • Duplicated block (5 lines × 4) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:21 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:21-25 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attribute.dart:32-36 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attributes.dart:39-43 | packages/auth/amplify_auth_cognito/example/lib/screens/view_user_attributes.dart:21-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
  • Duplicated block (5 lines × 4) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:33 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_user_attribute.dart:33-37 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attribute.dart:44-48 | packages/auth/amplify_auth_cognito/example/lib/screens/update_user_attributes.dart:51-55 | packages/auth/amplify_auth_cognito/example/lib/screens/view_user_attributes.dart:27-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: smithy_codegen — smithy_codegen: abstractness 0.22, instability 0.00, distance 0.78 — an application entry point, so it is concrete by design — the distance is expected; what is worth checking is that other projects depend on it at all, since a host should be a leaf of the graph.
  • Off the main sequence: smithy — smithy: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
GD1 · Unfinished & placeholder code · Unfinished stub · ×2
  • Unfinished stub — throws UnimplementedError packages/amplify_core/doc/lib/auth.dart:251 — `_promptUserPreference` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws UnimplementedError packages/amplify_core/doc/lib/auth.dart:272 — `_promptUserFirstFactorPreference` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws UnimplementedError packages/amplify_core/doc/lib/auth.dart:251 — `_promptUserPreference` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws UnimplementedError packages/amplify_core/doc/lib/auth.dart:272 — `_promptUserFirstFactorPreference` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×2
  • Duplicated block (15 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts:12 — infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts:12 · infra/lib/auth/stack.custom-sms-sender.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (15 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/pre-sign-up.ts:5 — infra-gen2/infra-common/src/lambda-triggers/pre-sign-up.ts:5 · infra/lib/auth/stack.pre-sign-up.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts:8 — infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts:8 · infra/lib/auth/custom-auth-without-srp/verify-auth-challenge.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (12 lines × 2 locations) REDACTED:141 — REDACTED:141 · infra/lib/auth/stack.delete-device.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×2
  • Duplicated block (8 lines × 2 locations) infra-gen2/backends/analytics/main/amplify/backend.ts:11 — infra-gen2/backends/analytics/main/amplify/backend.ts:11 · infra-gen2/backends/analytics/no-unauth-identities/amplify/backend.ts:14 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
  • Duplicated block (8 lines × 2 locations) infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:19 — infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:19 · infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:27 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×2
  • Duplicated block (7 lines × 2 locations) infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:74 — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:74 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:88 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
  • Duplicated block (7 lines × 2 locations) infra-gen2/infra-common/src/expiration.ts:15 — infra-gen2/infra-common/src/expiration.ts:15 · infra/lib/common.ts:22 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 18) · ×2
  • Complex function (anonymous) (cyclomatic 14, cognitive 18) REDACTED:49 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 14, cognitive 18) REDACTED:37 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R7 · Dead Code · Dead file (~50 LoC) · ×2
  • Dead file (~50 LoC) infra-gen2/infra-common/src/lambda-triggers/delete-user.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~50 LoC) infra/lib/auth/stack.delete-user.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~34 LoC) · ×2
  • Dead file (~34 LoC) infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~34 LoC) infra/lib/auth/custom-authorizer-user-pools/stack.api-handler.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
X2 · Cancellation propagation · Async function without AbortSignal · ×2
  • Async function without AbortSignal: decryptAndBroadcastCode infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:36 — `decryptAndBroadcastCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: decryptAndBroadcastCode infra/lib/auth/custom-sender.ts:34 — `decryptAndBroadcastCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
D1 · Cyclomatic Complexity · ModelSchema.compare (cyclomatic 52) · ×1
  • ModelSchema.compare (cyclomatic 52) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/Model+Compare.swift:30 — ModelSchema.compare has cyclomatic complexity 52 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GenerateWorkflowsCommand.generateForPackage (cyclomatic 36) · ×1
  • GenerateWorkflowsCommand.generateForPackage (cyclomatic 36) packages/aft/lib/src/commands/generate/generate_workflows_command.dart:270 — GenerateWorkflowsCommand.generateForPackage has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QueryPredicateBuilder.fromSerializedMap (cyclomatic 34) · ×1
  • QueryPredicateBuilder.fromSerializedMap (cyclomatic 34) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/QueryPredicateBuilder.swift:8 — QueryPredicateBuilder.fromSerializedMap has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QueryPredicateBuilder.fromSerializedMap (cyclomatic 33) · ×1
  • QueryPredicateBuilder.fromSerializedMap (cyclomatic 33) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/query/QueryPredicateBuilder.kt:26 — QueryPredicateBuilder.fromSerializedMap has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ModelSchema.comparator (cyclomatic 33) · ×1
  • ModelSchema.comparator (cyclomatic 33) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/Model+Sort.swift:86 — ModelSchema.comparator has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PublishCommand.run (cyclomatic 31) · ×1
  • PublishCommand.run (cyclomatic 31) packages/aft/lib/src/commands/publish_command.dart:387 — PublishCommand.run has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AWSHttpClientImpl._sendH2 (cyclomatic 29) · ×1
  • AWSHttpClientImpl._sendH2 (cyclomatic 29) packages/aws_common/lib/src/http/aws_http_client_io.dart:222 — AWSHttpClientImpl._sendH2 has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PackageSelector.fromJson (cyclomatic 27) · ×1
  • PackageSelector.fromJson (cyclomatic 27) packages/aft/lib/src/config/package_selector.dart:28 — PackageSelector.fromJson has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ShapeGenerator.valueToString (cyclomatic 26) · ×1
  • ShapeGenerator.valueToString (cyclomatic 26) packages/smithy/smithy_codegen/lib/src/generator/generator.dart:154 — ShapeGenerator.valueToString has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DataStoreHubEventStreamHandler.sendPayload (cyclomatic 26) · ×1
  • DataStoreHubEventStreamHandler.sendPayload (cyclomatic 26) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreHubEventStreamHandler.swift:79 — DataStoreHubEventStreamHandler.sendPayload has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · DataStoreHubEventStreamHandler.sendPayload (cyclomatic 25) · ×1
  • DataStoreHubEventStreamHandler.sendPayload (cyclomatic 25) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/DataStoreHubEventStreamHandler.kt:82 — DataStoreHubEventStreamHandler.sendPayload has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ShapeGenerator.valueFromString (cyclomatic 23) · ×1
  • ShapeGenerator.valueFromString (cyclomatic 23) packages/smithy/smithy_codegen/lib/src/generator/generator.dart:31 — ShapeGenerator.valueFromString has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · StructureXmlSerializerGenerator._builtXmlConstructor (cyclomatic 22) · ×1
  • StructureXmlSerializerGenerator._builtXmlConstructor (cyclomatic 22) packages/smithy/smithy_codegen/lib/src/generator/serialization/structure_xml_serializer_generator.dart:109 — StructureXmlSerializerGenerator._builtXmlConstructor has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuthIntegrationTestStackEnvironment.constructor (cyclomatic 21) · ×1
  • AuthIntegrationTestStackEnvironment.constructor (cyclomatic 21) infra/lib/auth/stack.ts:202 — AuthIntegrationTestStackEnvironment.constructor has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · StateMachineBloc._confirmSignIn (cyclomatic 20) · ×1
  • StateMachineBloc._confirmSignIn (cyclomatic 20) packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:209 — StateMachineBloc._confirmSignIn has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · WorkerBeeImpl.spawn (cyclomatic 20) · ×1
  • WorkerBeeImpl.spawn (cyclomatic 20) packages/worker_bee/worker_bee/lib/src/js/impl.dart:160 — WorkerBeeImpl.spawn has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PushNotificationMessage.fromJson (cyclomatic 19) · ×1
  • PushNotificationMessage.fromJson (cyclomatic 19) packages/amplify_core/lib/src/types/notifications/push/push_notification_message.dart:23 — PushNotificationMessage.fromJson has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · EventClient._flushEvents (cyclomatic 19) · ×1
  • EventClient._flushEvents (cyclomatic 19) packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/event_client/event_client.dart:109 — EventClient._flushEvents has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _SignUpFormState.runtimeFields (cyclomatic 19) · ×1
  • _SignUpFormState.runtimeFields (cyclomatic 19) packages/authenticator/amplify_authenticator/lib/src/widgets/form.dart:300 — _SignUpFormState.runtimeFields has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FlutterApiPlugin.subscribe (cyclomatic 19) · ×1
  • FlutterApiPlugin.subscribe (cyclomatic 19) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:96 — FlutterApiPlugin.subscribe has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FlutterModelFieldType.convertToNativeModelField (cyclomatic 19) · ×1
  • FlutterModelFieldType.convertToNativeModelField (cyclomatic 19) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelFieldType.swift:25 — FlutterModelFieldType.convertToNativeModelField has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · CascadeDeleteOperation.syncIfNeededAndFinish (cyclomatic 19) · ×1
  • CascadeDeleteOperation.syncIfNeededAndFinish (cyclomatic 19) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:273 — CascadeDeleteOperation.syncIfNeededAndFinish has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AWSInitialSyncOrchestrator.isUnauthorizedError (cyclomatic 19) · ×1
  • AWSInitialSyncOrchestrator.isUnauthorizedError (cyclomatic 19) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:210 — AWSInitialSyncOrchestrator.isUnauthorizedError has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · Model.graphQLInputForMutation (cyclomatic 18) · ×1
  • Model.graphQLInputForMutation (cyclomatic 18) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/Model+GraphQL.swift:33 — Model.graphQLInputForMutation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GenerateSdkCommand._generateForPackage (cyclomatic 17) · ×1
  • GenerateSdkCommand._generateForPackage (cyclomatic 17) packages/aft/lib/src/commands/generate/generate_sdk_command.dart:126 — GenerateSdkCommand._generateForPackage has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AftConfigLoader._processPubspecs (cyclomatic 17) · ×1
  • AftConfigLoader._processPubspecs (cyclomatic 17) packages/aft/lib/src/config/config_loader.dart:58 — AftConfigLoader._processPubspecs has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · GlobalConstraintsUpdater.update (cyclomatic 17) · ×1
  • GlobalConstraintsUpdater.update (cyclomatic 17) packages/aft/lib/src/constraints_updater.dart:28 — GlobalConstraintsUpdater.update has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QuerySnapshot.withSubscriptionEvent (cyclomatic 17) · ×1
  • QuerySnapshot.withSubscriptionEvent (cyclomatic 17) packages/amplify_core/lib/src/types/datastore/models/query_snapshot.dart:64 — QuerySnapshot.withSubscriptionEvent has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WebSocketBloc._eventTransformer (cyclomatic 17) · ×1
  • WebSocketBloc._eventTransformer (cyclomatic 17) packages/api/amplify_api_dart/lib/src/graphql/web_socket/blocs/web_socket_bloc.dart:172 — WebSocketBloc._eventTransformer has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CredentialStoreStateMachine._loadCredentialStore (cyclomatic 17) · ×1
  • CredentialStoreStateMachine._loadCredentialStore (cyclomatic 17) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart:111 — CredentialStoreStateMachine._loadCredentialStore has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · StructureGenerator._outputBuilder (cyclomatic 17) · ×1
  • StructureGenerator._outputBuilder (cyclomatic 17) packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart:728 — StructureGenerator._outputBuilder has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FlutterSerializedModel.deserializeValue (cyclomatic 17) · ×1
  • FlutterSerializedModel.deserializeValue (cyclomatic 17) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSerializedModel.swift:127 — FlutterSerializedModel.deserializeValue has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · SQLiteModelValueConverter.convertToTarget (cyclomatic 17) · ×1
  • SQLiteModelValueConverter.convertToTarget (cyclomatic 17) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/ModelValueConverter+SQLite.swift:25 — SQLiteModelValueConverter.convertToTarget has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · Model.sqlValues (cyclomatic 17) · ×1
  • Model.sqlValues (cyclomatic 17) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/Model+SQLite.swift:59 — Model.sqlValues has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AmplifyDataStore.configure (cyclomatic 16) · ×1
  • AmplifyDataStore.configure (cyclomatic 16) packages/amplify_datastore/lib/amplify_datastore.dart:51 — AmplifyDataStore.configure has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Repo.bumpVersion (cyclomatic 16) · ×1
  • Repo.bumpVersion (cyclomatic 16) packages/aft/lib/src/repo.dart:275 — Repo.bumpVersion has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FetchAuthSessionStateMachine.onFetchAuthSession (cyclomatic 16) · ×1
  • FetchAuthSessionStateMachine.onFetchAuthSession (cyclomatic 16) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/fetch_auth_session_state_machine.dart:194 — FetchAuthSessionStateMachine.onFetchAuthSession has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SignOutStateMachine._onInitiate (cyclomatic 16) · ×1
  • SignOutStateMachine._onInitiate (cyclomatic 16) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_out_state_machine.dart:66 — SignOutStateMachine._onInitiate has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · InheritedForms.updateShouldNotify (cyclomatic 16) · ×1
  • InheritedForms.updateShouldNotify (cyclomatic 16) packages/authenticator/amplify_authenticator/lib/src/state/inherited_forms.dart:102 — InheritedForms.updateShouldNotify has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: InheritedForms.[] (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · AWSHttpClientImpl._send (cyclomatic 16) · ×1
  • AWSHttpClientImpl._send (cyclomatic 16) packages/aws_common/lib/src/http/aws_http_client_js.dart:25 — AWSHttpClientImpl._send has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ServiceClientGenerator._operationMethods (cyclomatic 16) · ×1
  • ServiceClientGenerator._operationMethods (cyclomatic 16) packages/smithy/smithy_codegen/lib/src/generator/service_client_generator.dart:102 — ServiceClientGenerator._operationMethods has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FlutterSerializedModel.generateSerializedData (cyclomatic 16) · ×1
  • FlutterSerializedModel.generateSerializedData (cyclomatic 16) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSerializedModel.swift:194 — FlutterSerializedModel.generateSerializedData has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ProcessMutationErrorFromCloudOperation.main (cyclomatic 16) · ×1
  • ProcessMutationErrorFromCloudOperation.main (cyclomatic 16) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:52 — ProcessMutationErrorFromCloudOperation.main has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: packages/aft/lib/src/commands/generate/generate_workflows_command.dart packages/aft/lib/src/commands/generate/generate_workflows_command.dart:270 — packages/aft/lib/src/commands/generate/generate_workflows_command.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in GenerateWorkflowsCommand.generateForPackage at line 270. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 14:33:50 +01:00' --until='2026-11-12 14:33:50 +01:00' --full-history --no-merges -- packages/aft/lib/src/commands/generate/generate_workflows_command.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · ModelSchema.compare (cognitive 97) · ×1
  • ModelSchema.compare (cognitive 97) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/Model+Compare.swift:30 — ModelSchema.compare has cognitive complexity 97 (threshold 15). Drivers by points: if/else 25 (78 pts), boolean chains 13, error handling 1 (3 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 56). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WorkerBeeImpl.spawn (cognitive 63) · ×1
  • WorkerBeeImpl.spawn (cognitive 63) packages/worker_bee/worker_bee/lib/src/js/impl.dart:160 — WorkerBeeImpl.spawn has cognitive complexity 63 (threshold 15). Drivers by points: if/else 20 (57 pts), error handling 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GenerateWorkflowsCommand.generateForPackage (cognitive 55) · ×1
  • GenerateWorkflowsCommand.generateForPackage (cognitive 55) packages/aft/lib/src/commands/generate/generate_workflows_command.dart:270 — GenerateWorkflowsCommand.generateForPackage has cognitive complexity 55 (threshold 15). Drivers by points: if/else 24 (38 pts), loops 4 (8 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StructureXmlSerializerGenerator._builtXmlConstructor (cognitive 52) · ×1
  • StructureXmlSerializerGenerator._builtXmlConstructor (cognitive 52) packages/smithy/smithy_codegen/lib/src/generator/serialization/structure_xml_serializer_generator.dart:109 — StructureXmlSerializerGenerator._builtXmlConstructor has cognitive complexity 52 (threshold 15). Drivers by points: if/else 23 (50 pts), ternaries 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QueryPredicateBuilder.fromSerializedMap (cognitive 49) · ×1
  • QueryPredicateBuilder.fromSerializedMap (cognitive 49) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/query/QueryPredicateBuilder.kt:26 — QueryPredicateBuilder.fromSerializedMap has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (28 pts), match/switch 8 (21 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GlobalConstraintsUpdater.update (cognitive 46) · ×1
  • GlobalConstraintsUpdater.update (cognitive 46) packages/aft/lib/src/constraints_updater.dart:28 — GlobalConstraintsUpdater.update has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (39 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · QueryPredicateBuilder.fromSerializedMap (cognitive 45) · ×1
  • QueryPredicateBuilder.fromSerializedMap (cognitive 45) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/QueryPredicateBuilder.swift:8 — QueryPredicateBuilder.fromSerializedMap has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (29 pts), match/switch 5 (12 pts), boolean chains 4 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AWSHttpClientImpl._sendH2 (cognitive 37) · ×1
  • AWSHttpClientImpl._sendH2 (cognitive 37) packages/aws_common/lib/src/http/aws_http_client_io.dart:222 — AWSHttpClientImpl._sendH2 has cognitive complexity 37 (threshold 15). Drivers by points: if/else 25 (33 pts), boolean chains 3, error handling 1 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Model.graphQLInputForMutation (cognitive 36) · ×1
  • Model.graphQLInputForMutation (cognitive 36) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/Model+GraphQL.swift:33 — Model.graphQLInputForMutation has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 3 (8 pts), error handling 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ModelSchema.comparator (cognitive 35) · ×1
  • ModelSchema.comparator (cognitive 35) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/Support/Model+Sort.swift:86 — ModelSchema.comparator has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 11, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PublishCommand.run (cognitive 34) · ×1
  • PublishCommand.run (cognitive 34) packages/aft/lib/src/commands/publish_command.dart:387 — PublishCommand.run has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 11, ternaries 4, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · PackageSelector.fromJson (cognitive 32) · ×1
  • PackageSelector.fromJson (cognitive 32) packages/aft/lib/src/config/package_selector.dart:28 — PackageSelector.fromJson has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6, ternaries 2 (6 pts), match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ServiceClientGenerator._operationMethods (cognitive 31) · ×1
  • ServiceClientGenerator._operationMethods (cognitive 31) packages/smithy/smithy_codegen/lib/src/generator/service_client_generator.dart:102 — ServiceClientGenerator._operationMethods has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 6 (11 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CascadeDeleteOperation.syncIfNeededAndFinish (cognitive 31) · ×1
  • CascadeDeleteOperation.syncIfNeededAndFinish (cognitive 31) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:273 — CascadeDeleteOperation.syncIfNeededAndFinish has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 5 (11 pts), boolean chains 1 (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · EventClient._flushEvents (cognitive 30) · ×1
  • EventClient._flushEvents (cognitive 30) packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/event_client/event_client.dart:109 — EventClient._flushEvents has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (19 pts), error handling 5, loops 2 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CredentialStoreStateMachine._storeCredentials (cognitive 30) · ×1
  • CredentialStoreStateMachine._storeCredentials (cognitive 30) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart:234 — CredentialStoreStateMachine._storeCredentials has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AWSHttpClientImpl._send (cognitive 30) · ×1
  • AWSHttpClientImpl._send (cognitive 30) packages/aws_common/lib/src/http/aws_http_client_js.dart:25 — AWSHttpClientImpl._send has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SignInStateMachine._processChallenge (cognitive 29) · ×1
  • SignInStateMachine._processChallenge (cognitive 29) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:1170 — SignInStateMachine._processChallenge has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 7 (11 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FlutterSerializedModel.generateSerializedData (cognitive 29) · ×1
  • FlutterSerializedModel.generateSerializedData (cognitive 29) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSerializedModel.swift:194 — FlutterSerializedModel.generateSerializedData has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AmplifyDataStore.configure (cognitive 27) · ×1
  • AmplifyDataStore.configure (cognitive 27) packages/amplify_datastore/lib/amplify_datastore.dart:51 — AmplifyDataStore.configure has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), error handling 4 (7 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwiftAmplifyDataStorePlugin.getCustomTypeSchemasDependenciesOrder (cognitive 27) · ×1
  • SwiftAmplifyDataStorePlugin.getCustomTypeSchemasDependenciesOrder (cognitive 27) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:706 — SwiftAmplifyDataStorePlugin.getCustomTypeSchemasDependenciesOrder has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwiftAmplifyDataStorePlugin.createConflictHandler (cognitive 27) · ×1
  • SwiftAmplifyDataStorePlugin.createConflictHandler (cognitive 27) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:817 — SwiftAmplifyDataStorePlugin.createConflictHandler has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 2 (5 pts), match/switch 1 (4 pts), boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CredentialStoreStateMachine._loadCredentialStore (cognitive 26) · ×1
  • CredentialStoreStateMachine._loadCredentialStore (cognitive 26) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart:111 — CredentialStoreStateMachine._loadCredentialStore has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 6, ternaries 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StructureGenerator._outputBuilder (cognitive 26) · ×1
  • StructureGenerator._outputBuilder (cognitive 26) packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart:728 — StructureGenerator._outputBuilder has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (18 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ShapeMapSerializer.deserialize (cognitive 25) · ×1
  • ShapeMapSerializer.deserialize (cognitive 25) packages/smithy/smithy/lib/src/ast/shapes/shape_map.dart:25 — ShapeMapSerializer.deserialize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OperationGenerator._httpRequestBuilder (cognitive 25) · ×1
  • OperationGenerator._httpRequestBuilder (cognitive 25) packages/smithy/smithy_codegen/lib/src/generator/operation_generator.dart:79 — OperationGenerator._httpRequestBuilder has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 1 (4 pts), boolean chains 2, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Repo.bumpVersion (cognitive 24) · ×1
  • Repo.bumpVersion (cognitive 24) packages/aft/lib/src/repo.dart:275 — Repo.bumpVersion has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 7, loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LegacyCredentialProviderIOS.fetchLegacyCredentials (cognitive 24) · ×1
  • LegacyCredentialProviderIOS.fetchLegacyCredentials (cognitive 24) packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:32 — LegacyCredentialProviderIOS.fetchLegacyCredentials has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · FetchAuthSessionStateMachine.onRefresh (cognitive 24) · ×1
  • FetchAuthSessionStateMachine.onRefresh (cognitive 24) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/fetch_auth_session_state_machine.dart:352 — FetchAuthSessionStateMachine.onRefresh has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), error handling 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShapeGenerator.valueToString (cognitive 24) · ×1
  • ShapeGenerator.valueToString (cognitive 24) packages/smithy/smithy_codegen/lib/src/generator/generator.dart:154 — ShapeGenerator.valueToString has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 4 (7 pts), match/switch 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SQLiteStorageEngineAdapter.save (cognitive 24) · ×1
  • SQLiteStorageEngineAdapter.save (cognitive 24) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+SQLite.swift:155 — SQLiteStorageEngineAdapter.save has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 2, match/switch 1 (2 pts), error handling 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Model.sqlValues (cognitive 24) · ×1
  • Model.sqlValues (cognitive 24) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/Model+SQLite.swift:59 — Model.sqlValues has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 1 (3 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AWSRetryer.retry (cognitive 22) · ×1
  • AWSRetryer.retry (cognitive 22) packages/smithy/smithy_aws/lib/src/http/retry/aws_retryer.dart:152 — AWSRetryer.retry has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GenerateSdkCommand._generateForPackage (cognitive 21) · ×1
  • GenerateSdkCommand._generateForPackage (cognitive 21) packages/aft/lib/src/commands/generate/generate_sdk_command.dart:126 — GenerateSdkCommand._generateForPackage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 5 (6 pts), match/switch 1 (2 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SignOutStateMachine._onInitiate (cognitive 21) · ×1
  • SignOutStateMachine._onInitiate (cognitive 21) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_out_state_machine.dart:66 — SignOutStateMachine._onInitiate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 5 (7 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · _SignUpFormState.runtimeFields (cognitive 21) · ×1
  • _SignUpFormState.runtimeFields (cognitive 21) packages/authenticator/amplify_authenticator/lib/src/widgets/form.dart:300 — _SignUpFormState.runtimeFields has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · SmithyXmlPlugin._serialize (cognitive 20) · ×1
  • SmithyXmlPlugin._serialize (cognitive 20) packages/smithy/smithy/lib/src/serialization/xml/smithy_xml_plugin.dart:67 — SmithyXmlPlugin._serialize has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AmplifyDataStorePlugin.deserializeNestedModel (cognitive 20) · ×1
  • AmplifyDataStorePlugin.deserializeNestedModel (cognitive 20) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:668 — AmplifyDataStorePlugin.deserializeNestedModel has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AWSInitialSyncOrchestrator.isUnauthorizedError (cognitive 20) · ×1
  • AWSInitialSyncOrchestrator.isUnauthorizedError (cognitive 20) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/InitialSync/InitialSyncOrchestrator.swift:210 — AWSInitialSyncOrchestrator.isUnauthorizedError has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (8 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · common.createAmplifyConfig (cognitive 20) · ×1
  • common.createAmplifyConfig (cognitive 20) infra/lib/common.ts:351 — common.createAmplifyConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (20 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthIntegrationTestStackEnvironment.constructor (cognitive 20) · ×1
  • AuthIntegrationTestStackEnvironment.constructor (cognitive 20) infra/lib/auth/stack.ts:202 — AuthIntegrationTestStackEnvironment.constructor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 2, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · CredentialStoreStateMachine.onClearCredentials (cognitive 19) · ×1
  • CredentialStoreStateMachine.onClearCredentials (cognitive 19) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart:418 — CredentialStoreStateMachine.onClearCredentials has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FetchAuthSessionStateMachine._refreshUserPoolTokens (cognitive 19) · ×1
  • FetchAuthSessionStateMachine._refreshUserPoolTokens (cognitive 19) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/fetch_auth_session_state_machine.dart:508 — FetchAuthSessionStateMachine._refreshUserPoolTokens has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UriPattern.parse (cognitive 19) · ×1
  • UriPattern.parse (cognitive 19) packages/smithy/smithy/lib/src/ast/pattern/uri_pattern.dart:17 — UriPattern.parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AmplifyDataStorePlugin.deserializeNestedCustomType (cognitive 19) · ×1
  • AmplifyDataStorePlugin.deserializeNestedCustomType (cognitive 19) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:714 — AmplifyDataStorePlugin.deserializeNestedCustomType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SQLStatement+Condition.swift.translateQueryPredicate (cognitive 19) · ×1
  • SQLStatement+Condition.swift.translateQueryPredicate (cognitive 19) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+Condition.swift:20 — SQLStatement+Condition.swift.translateQueryPredicate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 5). None of this is in the body itself: all 19 points belong to 2 function items inside it that branch (translate, resolveColumn). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · BootstrapCommand.run (cognitive 18) · ×1
  • BootstrapCommand.run (cognitive 18) packages/aft/lib/src/commands/bootstrap_command.dart:107 — BootstrapCommand.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PublishConstraintsChecker.checkConstraints (cognitive 18) · ×1
  • PublishConstraintsChecker.checkConstraints (cognitive 18) packages/aft/lib/src/constraints_checker.dart:316 — PublishConstraintsChecker.checkConstraints has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (5 pts), ternaries 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuerySnapshot.withSubscriptionEvent (cognitive 18) · ×1
  • QuerySnapshot.withSubscriptionEvent (cognitive 18) packages/amplify_core/lib/src/types/datastore/models/query_snapshot.dart:64 — QuerySnapshot.withSubscriptionEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, match/switch 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AmplifyAPIDart._getEndpointConfig (cognitive 18) · ×1
  • AmplifyAPIDart._getEndpointConfig (cognitive 18) packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:194 — AmplifyAPIDart._getEndpointConfig has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (18 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ObserveQueryTaskRunner.onItemChangeAfterSync (cognitive 18) · ×1
  • ObserveQueryTaskRunner.onItemChangeAfterSync (cognitive 18) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Subscribe/DataStoreObserveQueryOperation.swift:314 — ObserveQueryTaskRunner.onItemChangeAfterSync has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Model.getModelIdentifierValues (cognitive 18) · ×1
  • Model.getModelIdentifierValues (cognitive 18) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Support/Model+GraphQL.swift:189 — Model.getModelIdentifierValues has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create-user.handler (cognitive 18) · ×1
  • create-user.handler (cognitive 18) REDACTED:47 — create-user.handler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 4 (7 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · stack.create-user.handler (cognitive 18) · ×1
  • stack.create-user.handler (cognitive 18) REDACTED:35 — stack.create-user.handler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 4 (7 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · GraphQLRequestFactory._buildDocumentInputs (cognitive 17) · ×1
  • GraphQLRequestFactory._buildDocumentInputs (cognitive 17) packages/api/amplify_api_dart/lib/src/graphql/factories/graphql_request_factory.dart:125 — GraphQLRequestFactory._buildDocumentInputs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · FetchAuthSessionStateMachine.onFetchAuthSession (cognitive 17) · ×1
  • FetchAuthSessionStateMachine.onFetchAuthSession (cognitive 17) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/fetch_auth_session_state_machine.dart:194 — FetchAuthSessionStateMachine.onFetchAuthSession has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 6. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · AWSProfileFileStandardizer.standardize (cognitive 17) · ×1
  • AWSProfileFileStandardizer.standardize (cognitive 17) packages/aws_common/lib/src/config/config_file/standardizer.dart:140 — AWSProfileFileStandardizer.standardize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 4, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CascadeDeleteOperation.syncDeletions (cognitive 17) · ×1
  • CascadeDeleteOperation.syncDeletions (cognitive 17) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/CascadeDeleteOperation.swift:442 — CascadeDeleteOperation.syncDeletions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (4 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SQLiteStorageEngineAdapter.save (cognitive 17) · ×1
  • SQLiteStorageEngineAdapter.save (cognitive 17) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/StorageEngineAdapter+UntypedModel.swift:12 — SQLiteStorageEngineAdapter.save has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PushNotificationMessage.fromJson (cognitive 16) · ×1
  • PushNotificationMessage.fromJson (cognitive 16) packages/amplify_core/lib/src/types/notifications/push/push_notification_message.dart:23 — PushNotificationMessage.fromJson has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 8 (15 pts), if/else 1 (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · GraphQLResponseDecoder.decode (cognitive 16) · ×1
  • GraphQLResponseDecoder.decode (cognitive 16) packages/api/amplify_api_dart/lib/src/graphql/helpers/graphql_response_decoder.dart:21 — GraphQLResponseDecoder.decode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WebSocketBloc._eventTransformer (cognitive 16) · ×1
  • WebSocketBloc._eventTransformer (cognitive 16) packages/api/amplify_api_dart/lib/src/graphql/web_socket/blocs/web_socket_bloc.dart:172 — WebSocketBloc._eventTransformer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · HostedUiPlatformImpl.signIn (cognitive 16) · ×1
  • HostedUiPlatformImpl.signIn (cognitive 16) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:199 — HostedUiPlatformImpl.signIn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SmithyXmlPlugin._deserialize (cognitive 16) · ×1
  • SmithyXmlPlugin._deserialize (cognitive 16) packages/smithy/smithy/lib/src/serialization/xml/smithy_xml_plugin.dart:202 — SmithyXmlPlugin._deserialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShapeGenerator.valueFromString (cognitive 16) · ×1
  • ShapeGenerator.valueFromString (cognitive 16) packages/smithy/smithy_codegen/lib/src/generator/generator.dart:31 — ShapeGenerator.valueFromString has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UnionGenerator._variantClasses (cognitive 16) · ×1
  • UnionGenerator._variantClasses (cognitive 16) packages/smithy/smithy_codegen/lib/src/generator/union_generator.dart:174 — UnionGenerator._variantClasses has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · render_score.render (cognitive 16) · ×1
  • render_score.render (cognitive 16) .github/composite_actions/package_score/render_score.py:7 — render_score.render has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (5 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FlutterApiPlugin.subscribe (cognitive 16) · ×1
  • FlutterApiPlugin.subscribe (cognitive 16) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterApiPlugin.swift:96 — FlutterApiPlugin.subscribe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, match/switch 3 (4 pts) (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FlutterModelSchema.init (cognitive 16) · ×1
  • FlutterModelSchema.init (cognitive 16) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterModelSchema.swift:15 — FlutterModelSchema.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwiftAmplifyDataStorePlugin.onConfigureDataStore (cognitive 16) · ×1
  • SwiftAmplifyDataStorePlugin.onConfigureDataStore (cognitive 16) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:264 — SwiftAmplifyDataStorePlugin.onConfigureDataStore has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 1 (3 pts), boolean chains 2, error handling 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreateTableStatement.stringValue (cognitive 16) · ×1
  • CreateTableStatement.stringValue (cognitive 16) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+CreateTable.swift:19 — CreateTableStatement.stringValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (24 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (24 members, 50+ identical tokens) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:125 — packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:125-147 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:149-171 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:203-225 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:227-249 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:251-273 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:275-297 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:299-321 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:371-393 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:395-417 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:419-441 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:443-466 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:468-490 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:492-514 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:516-538 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:540-562 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:564-586 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:588-610 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:612-634 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:636-658 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:660-682 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:684-706 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:708-730 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:732-754 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:756-778 — These 24 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 24 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 24 times.
D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (9 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift:12 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift:12-25 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+Resettable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Internal/AuthCategory+Resettable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Internal/DataStoreCategory+Resettable.swift:12-25 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Internal/GeoCategory+Resettable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/Internal/HubCategory+Resettable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Internal/PushNotificationsCategory+Resettable.swift:11-23 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Internal/PredictionsCategory+Resettable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Internal/StorageCategory+Resettable.swift:12-24 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift:10 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Internal/AuthCategory+CategoryConfigurable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Internal/DataStoreCategory+Configurable.swift:22-34 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Internal/GeoCategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Internal/PushNotificationsCategory+CategoryConfigurable.swift:9-21 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Internal/PredictionsCategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Internal/StorageCategory+CategoryConfigurable.swift:10-22 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (7 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:56 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:56-75 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsCategory.swift:52-73 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/AuthCategory.swift:50-69 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory.swift:53-72 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/GeoCategory.swift:52-73 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/PushNotificationsCategory.swift:51-72 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/StorageCategory.swift:53-72 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:19 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:19-44 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/AuthCategory.swift:16-41 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory.swift:19-44 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubCategory.swift:42-67 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/PredictionsCategory.swift:18-43 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/StorageCategory.swift:19-44 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (93 corresponding lines) · ×1
  • Edited copy of a member (93 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:753 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:753-845 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:731-825 — These two members are one piece of code written twice and then edited apart: 93 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (72 corresponding lines) · ×1
  • Edited copy of a member (72 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_device_password_verifier_worker.dart:77 — packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_device_password_verifier_worker.dart:77-148 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/srp/srp_password_verifier_worker.dart:86-165 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:199 — packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:199-261 | packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart:266-312 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:448 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:448-487 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift:489-527 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:376 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:376-433 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:436-489 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedCustomType.kt:32 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedCustomType.kt:32-62 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/types/model/FlutterSerializedModel.kt:41-86 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 23+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:49 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:49-71 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:74-100 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:103-128 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:131-156 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:159-184 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Persistable.swift:187-212 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:40 — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:40-67 | packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_username_field.dart:56-92 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:122 — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:122-151 | packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_username_field.dart:147-178 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 25+ corresponding lines) packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart:60 — packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart:60-84 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart:86-113 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_queries_factory.dart:38-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:323 — packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:323-345 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:347-369 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:691 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:691-715 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:662-687 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) packages/smithy/smithy_aws/lib/src/protocol/aws_query_protocol.dart:84 — packages/smithy/smithy_aws/lib/src/protocol/aws_query_protocol.dart:84-101 | packages/smithy/smithy_aws/lib/src/protocol/ec2_query.dart:25-40 | packages/smithy/smithy_aws/lib/src/protocol/rest_xml.dart:71-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:400 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:400-425 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:427-450 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 19+ corresponding lines) packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart:18 — packages/api/amplify_api_dart/lib/src/graphql/factories/model_mutations_factory.dart:18-41 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_queries_factory.dart:18-36 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:19-40 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:42-63 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:65-86 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) packages/amplify_native_legacy_wrapper/darwin/amplify_native_legacy_wrapper/Sources/amplify_native_legacy_wrapper/AmplifyNativeLegacyWrapperPlugin.swift:37 — packages/amplify_native_legacy_wrapper/darwin/amplify_native_legacy_wrapper/Sources/amplify_native_legacy_wrapper/AmplifyNativeLegacyWrapperPlugin.swift:37-46 | packages/amplify_native_legacy_wrapper/darwin/amplify_native_legacy_wrapper/Sources/amplify_native_legacy_wrapper/AmplifyNativeLegacyWrapperPlugin.swift:48-57 | packages/amplify_native_legacy_wrapper/darwin/amplify_native_legacy_wrapper/Sources/amplify_native_legacy_wrapper/AmplifyNativeLegacyWrapperPlugin.swift:59-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift:31 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift:31-51 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/Internal/AmplifyConfigurationInitialization.swift:100-120 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/DefaultPlugins/AWSUnifiedLoggingPlugin/Internal/ConsoleLoggingConfiguration.swift:33-53 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 9+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:81 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:81-89 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsCategory.swift:79-88 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/AuthCategory.swift:75-83 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory.swift:78-86 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/GeoCategory.swift:79-88 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubCategory.swift:102-110 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/PushNotificationsCategory.swift:78-87 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/StorageCategory.swift:78-86 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 11+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:232 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:232-242 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:244-254 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:256-267 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:269-280 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:282-293 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Schema/ModelSchema+Definition.swift:295-306 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 11+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:164 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:164-174 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:176-186 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:199-210 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:212-223 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+Model.swift:225-236 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) packages/authenticator/amplify_authenticator/lib/src/state/inherited_config.dart:19 — packages/authenticator/amplify_authenticator/lib/src/state/inherited_config.dart:19-36 | packages/authenticator/amplify_authenticator/lib/src/state/inherited_forms.dart:86-100 | packages/authenticator/amplify_authenticator/lib/src/state/inherited_strings.dart:17-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterNetworkStatusEvent.swift:10 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterNetworkStatusEvent.swift:10-16 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxStatusEvent.swift:10-16 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncQueriesStartedEvent.swift:10-16 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) packages/aft/lib/src/constraints_checker.dart:403 — packages/aft/lib/src/constraints_checker.dart:403-406 | packages/amplify_core/lib/src/config/config_map.dart:50-51 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) packages/aft/lib/src/config/serializers.dart:83 — packages/aft/lib/src/config/serializers.dart:83-90 | packages/smithy/smithy/lib/src/serialization/query/query_double_serializer.dart:12-19 | packages/smithy/smithy/lib/src/serialization/query/query_int_serializer.dart:12-19 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:91 — packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:91-112 | packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_memory.dart:43-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/kinesis/amplify_record_cache_dart/lib/src/storage/record_storage_indexeddb.dart:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:38 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:38-57 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart:37-56 — before extracting anything, compare `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart` and `packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:38` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) packages/smithy/smithy_codegen/lib/src/generator/service_server_generator.dart:212 — packages/smithy/smithy_codegen/lib/src/generator/service_server_generator.dart:212-231 | packages/smithy/smithy_codegen/lib/src/generator/service_server_generator.dart:271-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy_codegen/lib/src/generator/service_server_generator.dart:212` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 24) · ×1
  • Duplicated block (16 lines × 24) packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:132 — packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:132-147 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:156-171 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:210-225 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:234-249 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:258-273 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:282-297 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:306-321 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:378-393 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:402-417 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:426-441 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:451-466 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:475-490 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:499-514 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:523-538 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:547-562 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:571-586 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:595-610 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:619-634 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:643-658 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:667-682 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:691-706 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:715-730 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:739-754 | packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:763-778 — all 24 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:20 — packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:20-34 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:43-57 | packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:66-80 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/api/amplify_api_dart/lib/src/graphql/factories/model_subscriptions_factory.dart:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:61 — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:61-70 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart:73-82 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart:75-84 | packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart:60-69 — before extracting anything, compare `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart` and `packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8 lines × 17) · ×1
  • Duplicated block (8 lines × 17) packages/amplify_core/lib/src/types/auth/attribute/confirm_user_attribute_options.dart:21 — packages/amplify_core/lib/src/types/auth/attribute/confirm_user_attribute_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/attribute/fetch_user_attributes_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/attribute/send_user_attribute_verification_code_options.dart:22-29 | packages/amplify_core/lib/src/types/auth/attribute/update_user_attribute_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/attribute/update_user_attributes_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/auto_sign_in/auto_sign_in_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/mfa/totp_setup_options.dart:20-27 | packages/amplify_core/lib/src/types/auth/mfa/verify_totp_setup_options.dart:20-27 | packages/amplify_core/lib/src/types/auth/password/confirm_reset_password_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/password/reset_password_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/password/update_password_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/session/get_current_user_options.dart:20-27 | packages/amplify_core/lib/src/types/auth/sign_in/confirm_sign_in_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/sign_in/sign_in_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/sign_in/sign_in_with_web_ui_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/sign_up/confirm_sign_up_options.dart:21-28 | packages/amplify_core/lib/src/types/auth/sign_up/resend_sign_up_code_options.dart:21-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 17 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 17 times.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1
  • Duplicated block (11 lines × 6) packages/amplify_core/lib/src/types/storage/download_data_options.dart:23 — packages/amplify_core/lib/src/types/storage/download_data_options.dart:23-33 | packages/amplify_core/lib/src/types/storage/download_file_options.dart:23-33 | packages/amplify_core/lib/src/types/storage/get_properties_options.dart:23-33 | packages/amplify_core/lib/src/types/storage/get_url_options.dart:23-33 | packages/amplify_core/lib/src/types/storage/remove_many_options.dart:23-33 | packages/amplify_core/lib/src/types/storage/remove_options.dart:23-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:71 — packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart:71-78 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_out_state_machine.dart:57-64 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_up_state_machine.dart:46-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 10) · ×1
  • Duplicated block (10 lines × 10) packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:602 — packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:602-611 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart:673-682 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_up_form_field.dart:159-168 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_up_form_field.dart:245-254 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_in_form_field.dart:158-167 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_in_form_field.dart:236-245 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:648-657 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:848-857 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart:884-893 | packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/verify_user_form_field.dart:91-100 — before extracting anything, compare `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/confirm_sign_in_form_field.dart` and `packages/authenticator/amplify_authenticator/lib/src/widgets/form_fields/sign_up_form_field.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×1
  • Duplicated block (7 lines × 6) packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/configuration_state_machine.dart:60 — packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/configuration_state_machine.dart:60-66 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart:84-90 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/fetch_auth_session_state_machine.dart:88-94 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/hosted_ui_state_machine.dart:81-87 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_up_state_machine.dart:78-84 | packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/totp_setup_state_machine.dart:45-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 10) · ×1
  • Duplicated block (6 lines × 10) packages/smithy/smithy/lib/src/ast/shapes/apply_shape.dart:15 — packages/smithy/smithy/lib/src/ast/shapes/apply_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/enum_shape.dart:26-31 | packages/smithy/smithy/lib/src/ast/shapes/enum_shape.dart:50-55 | packages/smithy/smithy/lib/src/ast/shapes/list_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/map_shape.dart:14-19 | packages/smithy/smithy/lib/src/ast/shapes/operation_shape.dart:17-22 | packages/smithy/smithy/lib/src/ast/shapes/resource_shape.dart:17-22 | packages/smithy/smithy/lib/src/ast/shapes/service_shape.dart:17-22 | packages/smithy/smithy/lib/src/ast/shapes/set_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/union_shape.dart:15-20 — there are 10 copies across 9 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 10 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `b` to `ApplyShapeBuilder` in one and `StringEnumShapeBuilder` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (6 lines × 13) · ×1
  • Duplicated block (6 lines × 13) packages/smithy/smithy/lib/src/ast/shapes/big_decimal_shape.dart:16 — packages/smithy/smithy/lib/src/ast/shapes/big_decimal_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/big_integer_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/blob_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/boolean_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/byte_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/document_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/double_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/float_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/integer_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/long_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/short_shape.dart:15-20 | packages/smithy/smithy/lib/src/ast/shapes/string_shape.dart:16-21 | packages/smithy/smithy/lib/src/ast/shapes/timestamp_shape.dart:16-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 13 call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `b` to `BigDecimalShapeBuilder` in one and `BigIntegerShapeBuilder` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) packages/smithy/smithy/lib/src/ast/shapes/primitive_byte_shape.dart:19 — packages/smithy/smithy/lib/src/ast/shapes/primitive_byte_shape.dart:19-24 | packages/smithy/smithy/lib/src/ast/shapes/primitive_double_shape.dart:19-24 | packages/smithy/smithy/lib/src/ast/shapes/primitive_float_shape.dart:19-24 | packages/smithy/smithy/lib/src/ast/shapes/primitive_integer_shape.dart:19-24 | packages/smithy/smithy/lib/src/ast/shapes/primitive_short_shape.dart:19-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `b` to `PrimitiveByteShapeBuilder` in one and `PrimitiveDoubleShapeBuilder` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:377 — packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:377-408 | packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt:437-468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyConfiguration.swift:139 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyConfiguration.swift:139-174 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyOutputsData.swift:318-353 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyConfiguration.swift:139` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyOutputsData.swift:315` calls `_spi`, `configure` and `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/AmplifyConfiguration.swift:136` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsCategory.swift:19 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsCategory.swift:19-43 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/GeoCategory.swift:19-43 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/PushNotificationsCategory.swift:18-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (24 lines × 6) · ×1
  • Duplicated block (24 lines × 6) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:21 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:21-44 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/AuthCategory.swift:18-41 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory.swift:21-44 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/HubCategory.swift:44-67 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/PredictionsCategory.swift:20-43 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/StorageCategory.swift:21-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:21` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16–24 lines × 2) · ×1
  • Duplicated block (16–24 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:222 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:222-237 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:257-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/ProcessMutationErrorFromCloudOperation.swift:222` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 7) · ×1
  • Duplicated block (15–16 lines × 7) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:61 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:61-75 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/AnalyticsCategory.swift:58-73 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/AuthCategory.swift:55-69 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/DataStoreCategory.swift:58-72 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/GeoCategory.swift:58-73 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/PushNotificationsCategory.swift:57-72 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/StorageCategory.swift:58-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/APICategory.swift:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `plugin` to `APICategoryPlugin` in one and `AnalyticsCategoryPlugin` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (11–15 lines × 2) · ×1
  • Duplicated block (11–15 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:459 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:459-469 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:477-491 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/ReconcileAndLocalSave/ReconcileAndLocalSaveOperation.swift:477` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:76 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:76-88 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:141-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/AWSDataStorePlugin+DataStoreBaseBehavior.swift:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 8) · ×1
  • Duplicated block (13 lines × 8) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift:10 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Internal/AuthCategory+CategoryConfigurable.swift:12-24 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Internal/DataStoreCategory+Configurable.swift:22-34 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Internal/GeoCategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Internal/PushNotificationsCategory+CategoryConfigurable.swift:9-21 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Internal/PredictionsCategory+CategoryConfigurable.swift:10-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Internal/StorageCategory+CategoryConfigurable.swift:10-22 — before extracting anything, compare `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift` and `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+CategoryConfigurable.swift` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×1
  • Duplicated block (13 lines × 5) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStoreError.swift:34 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStoreError.swift:34-46 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Error/AnalyticsError.swift:54-66 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Error/AuthError.swift:84-96 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Error/PushNotificationsError.swift:55-67 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Error/StorageError.swift:123-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (10–13 lines × 4) · ×1
  • Duplicated block (10–13 lines × 4) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:158 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:158-168 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:180-189 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:202-214 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:262-272 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLRequest/GraphQLRequest+AnyModelWithSync.swift:158` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Error/APIError.swift:43 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Error/APIError.swift:43-55 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Types/Geo+Error.swift:30-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:28 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:28-38 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:62-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11 lines × 9) · ×1
  • Duplicated block (11 lines × 9) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift:12 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Internal/AuthCategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Internal/DataStoreCategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Internal/GeoCategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Hub/Internal/HubCategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Internal/PushNotificationsCategory+Resettable.swift:11-21 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Internal/PredictionsCategory+Resettable.swift:12-22 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Internal/StorageCategory+Resettable.swift:12-22 — before extracting anything, compare `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift` and `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+Resettable.swift` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+Resettable.swift:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLMutation.swift:13 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLMutation.swift:13-32 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLQuery.swift:13-32 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLSubscription.swift:13-32 — before extracting anything, compare `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLMutation.swift` and `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLQuery.swift` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLMutation.swift:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterReadyEvent.swift:9 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterReadyEvent.swift:9-17 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSubscriptionsEstablishedEvent.swift:9-17 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSyncQueriesReadyEvent.swift:9-17 — before extracting anything, compare `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterReadyEvent.swift` and `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterSubscriptionsEstablishedEvent.swift` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×1
  • Duplicated block (6 lines × 7) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift:28 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift:28-33 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+CategoryConfigurable.swift:28-33 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Auth/Internal/AuthCategory+CategoryConfigurable.swift:30-35 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Geo/Internal/GeoCategory+CategoryConfigurable.swift:28-33 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Notifications/PushNotifications/Internal/PushNotificationsCategory+CategoryConfigurable.swift:27-32 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Internal/PredictionsCategory+CategoryConfigurable.swift:28-33 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Internal/StorageCategory+CategoryConfigurable.swift:28-33 — before extracting anything, compare `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Internal/APICategory+CategoryConfigurable.swift` and `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Analytics/Internal/AnalyticsCategory+CategoryConfigurable.swift` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Response/GraphQLResponse.swift:78 — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Response/GraphQLResponse.swift:78-88 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Error/PredictionsError.swift:53-63 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Configuration/ConfigurationError.swift:78-88 | packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Plugin/PluginError.swift:55-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Edited copies of one member (3 members, 40+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 40+ corresponding lines) packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:28 — packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:28-67 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_layout.dart:20-59 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_onboarding.dart:12-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 31+ corresponding lines) packages/api/amplify_api/example/lib/widgets/create.dart:67 — packages/api/amplify_api/example/lib/widgets/create.dart:67-97 | packages/api/amplify_api/example/lib/widgets/query.dart:87-117 | packages/api/amplify_api/example/lib/widgets/subscribe.dart:92-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_in.dart:29 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_in.dart:29-43 | packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_up.dart:29-44 | packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:36-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 13+ corresponding lines) packages/api/amplify_api/example/lib/rest_api_view.dart:26 — packages/api/amplify_api/example/lib/rest_api_view.dart:26-42 | packages/api/amplify_api/example/lib/rest_api_view.dart:44-60 | packages/api/amplify_api/example/lib/rest_api_view.dart:62-75 | packages/api/amplify_api/example/lib/rest_api_view.dart:77-89 | packages/api/amplify_api/example/lib/rest_api_view.dart:114-130 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:86 — packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:86-114 | packages/auth/amplify_auth_cognito/example/lib/screens/sign_up.dart:53-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/auth/amplify_auth_cognito/example/lib/screens/sign_in.dart:82` calls `safePrint` and `packages/auth/amplify_auth_cognito/example/lib/screens/sign_up.dart:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20–21 lines × 3) · ×1
  • Duplicated block (20–21 lines × 3) packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:48 — packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:48-67 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_layout.dart:40-59 | packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_onboarding.dart:32-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/authenticator/amplify_authenticator/example/lib/customization/authenticator_with_custom_auth_flow.dart:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×1
  • Duplicated block (14 lines × 5) packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:82 — packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:82-95 | packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_in.dart:66-79 | packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_up.dart:97-110 | packages/auth/amplify_auth_cognito/example/lib/screens/sign_up.dart:104-117 | packages/auth/amplify_auth_cognito/example/lib/screens/update_password.dart:80-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/auth/amplify_auth_cognito/example/lib/screens/confirm_reset.dart:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/auth/amplify_auth_cognito/example/lib/screens/sign_up.dart:102` calls `Key` and `packages/auth/amplify_auth_cognito/example/lib/screens/confirm_sign_in.dart:64` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in infra/ ran and not one test passed (FAIL test/common.test.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience packages/auth/amplify_auth_cognito_dart/lib/src/state/cognito_state_machine.dart:37 — `http.Client(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (8 clone groups) REDACTED:17 — 8 of the duplicated blocks reported below have copies in at least two of the sibling directories infra, infra-gen2 under the repository root. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (6 clone groups) infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts:9 — 6 duplicated blocks under infra/lib/auth/ have copies in at least two of the sibling directories custom-auth-with-srp, custom-auth-without-srp, custom-authorizer-iam, custom-authorizer-user-pools — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (86 identical lines × 2 files) · ×1
  • Wholesale file copy (86 identical lines × 2 files) REDACTED:17 — REDACTED:17 · REDACTED:5 — these 2 files are line-for-line copies of one another — 86 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:28 — infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts:28 · infra/lib/auth/custom-sender.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/enable-sms-mfa.ts:26 — infra-gen2/infra-common/src/lambda-triggers/enable-sms-mfa.ts:26 · infra/lib/auth/stack.enable-sms-mfa.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1
  • Duplicated block (26 lines × 2 locations) infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts:9 — infra/lib/auth/custom-authorizer-iam/stack.api-handler.ts:9 · infra/lib/auth/custom-authorizer-user-pools/stack.api-handler.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) infra-gen2/backends/storage/dots-in-name/amplify/backend.ts:5 — infra-gen2/backends/storage/dots-in-name/amplify/backend.ts:5 · infra-gen2/backends/storage/main/amplify/backend.ts:4 — the two spans are one implementation copied and then locally edited — 105 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/delete-user.ts:26 — infra-gen2/infra-common/src/lambda-triggers/delete-user.ts:26 · infra/lib/auth/stack.delete-user.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) infra/lib/auth/stack.ts:316 — infra/lib/auth/stack.ts:316 · infra/lib/auth/stack.ts:340 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) infra-gen2/infra-common/src/auth-user-extensions/create-user-lambda.ts:11 — infra-gen2/infra-common/src/auth-user-extensions/create-user-lambda.ts:11 · infra-gen2/infra-common/src/auth-user-extensions/delete-user-lambda.ts:11 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (18 lines × 6 locations) · ×1
  • Duplicated block (18 lines × 6 locations) infra-gen2/backends/auth/mfa-optional-email-sms/amplify/backend.ts:8 — infra-gen2/backends/auth/mfa-optional-email-sms/amplify/backend.ts:8 · infra-gen2/backends/auth/mfa-optional-email-totp/amplify/backend.ts:8 · infra-gen2/backends/auth/mfa-optional-email/amplify/backend.ts:8 · infra-gen2/backends/auth/mfa-required-email-sms/amplify/backend.ts:8 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:7 — infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:7 · infra/lib/auth/stack.custom-email-sender.ts:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) infra/lib/auth/stack.ts:269 — infra/lib/auth/stack.ts:269 · infra/lib/auth/stack.ts:288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (13 lines × 3 locations) · ×1
  • Duplicated block (13 lines × 3 locations) infra-gen2/backends/storage/dots-in-name/amplify/storage/resource.ts:5 — infra-gen2/backends/storage/dots-in-name/amplify/storage/resource.ts:5 · infra-gen2/backends/storage/main/amplify/storage/resource.ts:6 · infra-gen2/backends/storage/main/amplify/storage/resource.ts:23 — the 3 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:10 — infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:10 · infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (10 lines × 11 locations) · ×1
  • Duplicated block (10 lines × 11 locations) infra-gen2/backends/auth/email-sign-in/amplify/backend.ts:4 — infra-gen2/backends/auth/email-sign-in/amplify/backend.ts:4 · infra-gen2/backends/auth/mfa-optional-email-sms/amplify/backend.ts:4 · infra-gen2/backends/auth/mfa-optional-email-totp/amplify/backend.ts:4 · infra-gen2/backends/auth/mfa-optional-email/amplify/backend.ts:4 · +7 more site(s) not listed — the 11 copies are spread across 11 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:6 — infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:6 · infra/lib/auth/custom-auth-without-srp/define-auth-challenge.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (7 lines × 3 locations) · ×1
  • Duplicated block (7 lines × 3 locations) infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:10 — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:10 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:114 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:138 — all 3 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×1
  • Duplicated block (6 lines × 2 locations) infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:97 — infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:97 · infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts:106 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (6 lines × 3 locations) · ×1
  • Duplicated block (6 lines × 3 locations) infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:4 — infra/lib/auth/custom-auth-with-srp/define-auth-challenge.ts:4 · infra/lib/auth/custom-auth-without-srp/create-auth-challenge.ts:9 · infra/lib/auth/custom-auth-without-srp/define-auth-challenge.ts:9 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (5 lines × 3 locations) · ×1
  • Duplicated block (5 lines × 3 locations) infra/lib/auth/custom-auth-with-srp/create-auth-challenge.ts:6 — infra/lib/auth/custom-auth-with-srp/create-auth-challenge.ts:6 · infra/lib/auth/custom-auth-with-srp/verify-auth-challenge.ts:6 · infra/lib/auth/custom-auth-without-srp/verify-auth-challenge.ts:6 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R3 · Large Files · infra/lib/auth/stack.ts · ×1
  • infra/lib/auth/stack.ts: 668 lines of code infra/lib/auth/stack.ts:1 — infra/lib/auth/stack.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · infra/lib/common.ts · ×1
  • infra/lib/common.ts: 496 lines of code infra/lib/common.ts:1 — infra/lib/common.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~734 LoC) · ×1
  • Dead file (~734 LoC) infra/lib/auth/stack.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (infra/lib/auth/custom-authorizer-iam/stack.ts, infra/lib/auth/custom-authorizer-user-pools/stack.ts, infra/lib/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~301 LoC) · ×1
  • Dead file (~301 LoC) infra/lib/stack.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~201 LoC) · ×1
  • Dead file (~201 LoC) infra/lib/github/github.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra/lib/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~178 LoC) · ×1
  • Dead file (~178 LoC) REDACTED — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~161 LoC) · ×1
  • Dead file (~161 LoC) REDACTED — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~156 LoC) · ×1
  • Dead file (~156 LoC) infra-gen2/backends/api/api-multi-auth/amplify/data/resource.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra-gen2/backends/api/api-multi-auth/amplify/backend.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~154 LoC) · ×1
  • Dead file (~154 LoC) infra/lib/auth/custom-authorizer-iam/stack.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra/lib/auth/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~112 LoC) · ×1
  • Dead file (~112 LoC) infra/lib/auth/custom-authorizer-user-pools/stack.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra/lib/auth/stack.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~106 LoC) · ×1
  • Dead file (~106 LoC) infra-gen2/backends/api/api-multi-auth/amplify/backend.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~77 LoC) · ×1
  • Dead file (~77 LoC) infra-gen2/infra-common/src/lambda-triggers/custom-sender.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts, infra-gen2/infra-common/src/lambda-triggers/custom-sms-sender.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~74 LoC) · ×1
  • Dead file (~74 LoC) infra/lib/auth/custom-sender.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (infra/lib/auth/stack.custom-email-sender.ts, infra/lib/auth/stack.custom-sms-sender.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~65 LoC) · ×1
  • Dead file (~65 LoC) infra-gen2/backends/storage/main/amplify/backend.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~60 LoC) · ×1
  • Dead file (~60 LoC) infra-gen2/infra-common/src/lambda-triggers/kinesis-consumer.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~59 LoC) · ×1
  • Dead file (~59 LoC) infra-gen2/backends/kinesis/firehose/amplify/backend.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~44 LoC) · ×1
  • Dead file (~44 LoC) infra/lib/github/github.list-amplify-apps.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~41 LoC) · ×1
  • Dead file (~41 LoC) infra/lib/auth/stack.list-auth-events.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~40 LoC) · ×1
  • Dead file (~40 LoC) infra-gen2/backends/storage/dots-in-name/amplify/backend.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~36 LoC) · ×1
  • Dead file (~36 LoC) infra-gen2/backends/storage/main/amplify/storage/resource.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (infra-gen2/backends/storage/main/amplify/backend.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~32 LoC) · ×1
  • Dead file (~32 LoC) infra/lib/auth/stack.pre-sign-up.ts — no import path from any entry point (18 application, 2 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency 'source-map-support' · ×1
  • Unused dependency 'source-map-support' infra/package.json:34 — Declared in infra/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'esbuild' · ×1
  • Unused dependency 'esbuild' infra-gen2/package.json:27 — Declared in infra-gen2/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'infra-common' · ×1
  • Unused dependency 'infra-common' infra-gen2/package.json:17 — Declared in infra-gen2/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×1
  • Owned disposable field is never released packages/authenticator/amplify_authenticator/lib/src/blocs/auth/auth_bloc.dart:105 — `StateMachineBloc` carries a disposal duty — it declares its own release — and it creates `_infoMessageController` itself (line 105, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_infoMessageController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_infoMessageController.close();` in `dispose()` before `super.dispose()`.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) packages/auth/amplify_auth_cognito/android/src/main/kotlin/com/amazonaws/amplify/amplify_auth_cognito/LegacyKeyProvider.kt:96 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Minor — 153 finding(s)
AX6 · Interface segregation · Fat interface · ×35
  • Fat interface: E2EMessage (17 abstract methods) packages/worker_bee/e2e/lib/e2e_message.dart:21 — `E2EMessage` declares 17 abstract methods: `bigInt`, `bool_`, `builtList`, `builtListMultimap`, `builtMap`, `builtSet`, `builtSetMultimap`, `dateTime`, `double_`, `duration`, `int_`, `int64`, `jsonObject`, `num_`, `regExp`, `string`, `uri`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: JsonProtocolServerBase (16 abstract methods) packages/smithy/goldens/lib/awsJson1_1/lib/src/json_protocol/json_protocol_server.dart:34 — `JsonProtocolServerBase` declares 16 abstract methods: `datetimeOffsets`, `emptyOperation`, `endpointOperation`, `endpointWithHostLabelOperation`, `fractionalSeconds`, `greetingWithErrors`, `hostWithPathOperation`, `jsonEnums`, `jsonIntEnums`, `jsonUnions`, `kitchenSinkOperation`, `nullOperation`, `operationWithOptionalInputOutput`, `putAndGetInlineDocuments`, `putWithContentEncoding`, `simpleScalarProperties`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: KitchenSink (26 abstract methods) packages/smithy/goldens/lib/awsJson1_1/lib/src/json_protocol/model/kitchen_sink.dart:21 — `KitchenSink` declares 26 abstract methods: `blob`, `boolean`, `double_`, `emptyStruct`, `float`, `httpdateTimestamp`, `integer`, `iso8601Timestamp`, `jsonValue`, `listOfLists`, `listOfMapsOfStrings`, `listOfStrings`, `listOfStructs`, `long`, `mapOfListsOfStrings`, `mapOfMaps`, `mapOfStrings`, `mapOfStructs`, `recursiveList`, `recursiveMap`, `recursiveStruct`, `simpleStruct`, `string`, `structWithJsonName`, `timestamp`, `unixTimestamp`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AppLocalizations (19 abstract methods) packages/authenticator/amplify_authenticator/example/lib/l10n/app_localizations.dart:13 — `AppLocalizations` declares 19 abstract methods: `signIn`, `signUp`, `confirm`, `submit`, `changePassword`, `sendCode`, `lostCode`, `noAccount`, `haveAccount`, `forgotPassword`, `confirmResetPassword`, `verify`, `skip`, `signOut`, `backTo`, `signInWith`, `us`, `selectDialCode`, `confirmSignInCustomAuth`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AllQueryStringTypesInput (21 abstract methods) packages/smithy/goldens/lib/restJson1/lib/src/rest_json_protocol/model/all_query_string_types_input.dart:17 — `AllQueryStringTypesInput` declares 21 abstract methods: `queryString`, `queryStringList`, `queryStringSet`, `queryByte`, `queryShort`, `queryInteger`, `queryIntegerList`, `queryIntegerSet`, `queryLong`, `queryFloat`, `queryDouble`, `queryDoubleList`, `queryBoolean`, `queryBooleanList`, `queryTimestamp`, `queryTimestampList`, `queryEnum`, `queryEnumList`, `queryIntegerEnum`, `queryIntegerEnumList`, `queryParamsMapOfStringList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: InputAndOutputWithHeadersIo (18 abstract methods) packages/smithy/goldens/lib/restJson1/lib/src/rest_json_protocol/model/input_and_output_with_headers_io.dart:17 — `InputAndOutputWithHeadersIo` declares 18 abstract methods: `headerString`, `headerByte`, `headerShort`, `headerInteger`, `headerLong`, `headerFloat`, `headerDouble`, `headerTrueBool`, `headerFalseBool`, `headerStringList`, `headerStringSet`, `headerIntegerList`, `headerBooleanList`, `headerTimestampList`, `headerEnum`, `headerEnumList`, `headerIntegerEnum`, `headerIntegerEnumList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: RestJsonProtocolServerBase (94 abstract methods) packages/smithy/goldens/lib/restJson1/lib/src/rest_json_protocol/rest_json_protocol_server.dart:116 — `RestJsonProtocolServerBase` declares 94 abstract methods: `allQueryStringTypes`, `constantAndVariableQueryString`, `constantQueryString`, `datetimeOffsets`, `documentType`, `documentTypeAsPayload`, `emptyInputAndEmptyOutput`, `endpointOperation`, `endpointWithHostLabelOperation`, `fractionalSeconds`, `greetingWithErrors`, `hostWithPathOperation`, `httpChecksumRequired`, `httpEnumPayload`, `httpPayloadTraits`, `httpPayloadTraitsWithMediaType`, `httpPayloadWithStructure`, `httpPrefixHeaders`, `httpPrefixHeadersInResponse`, `httpRequestWithFloatLabels`, `httpRequestWithGreedyLabelInPath`, `httpRequestWithLabels`, `httpRequestWithLabelsAndTimestampFormat`, `httpRequestWithRegexLiteral`, `httpResponseCode`, `httpStringPayload`, `ignoreQueryParamsInResponse`, `inputAndOutputWithHeaders`, `jsonBlobs`, `jsonEnums`, `jsonIntEnums`, `jsonLists`, `jsonMaps`, `jsonTimestamps`, `jsonUnions`, `malformedAcceptWithBody`, `malformedAcceptWithGenericString`, `malformedAcceptWithPayload`, `malformedBlob`, `malformedBoolean`, and 54 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MalformedUniqueItemsInput (16 abstract methods) packages/smithy/goldens/lib/restJson1/lib/src/rest_json_validation_protocol/model/malformed_unique_items_input.dart:21 — `MalformedUniqueItemsInput` declares 16 abstract methods: `blobList`, `booleanList`, `stringList`, `byteList`, `shortList`, `integerList`, `longList`, `timestampList`, `dateTimeList`, `httpDateList`, `enumList`, `intEnumList`, `listList`, `structureList`, `structureListWithNoKey`, `unionList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AllQueryStringTypesInput (21 abstract methods) packages/smithy/goldens/lib/restXml/lib/src/rest_xml_protocol/model/all_query_string_types_input.dart:17 — `AllQueryStringTypesInput` declares 21 abstract methods: `queryString`, `queryStringList`, `queryStringSet`, `queryByte`, `queryShort`, `queryInteger`, `queryIntegerList`, `queryIntegerSet`, `queryLong`, `queryFloat`, `queryDouble`, `queryDoubleList`, `queryBoolean`, `queryBooleanList`, `queryTimestamp`, `queryTimestampList`, `queryEnum`, `queryEnumList`, `queryIntegerEnum`, `queryIntegerEnumList`, `queryParamsMapOfStrings`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: InputAndOutputWithHeadersIo (16 abstract methods) packages/smithy/goldens/lib/restXml/lib/src/rest_xml_protocol/model/input_and_output_with_headers_io.dart:17 — `InputAndOutputWithHeadersIo` declares 16 abstract methods: `headerString`, `headerByte`, `headerShort`, `headerInteger`, `headerLong`, `headerFloat`, `headerDouble`, `headerTrueBool`, `headerFalseBool`, `headerStringList`, `headerStringSet`, `headerIntegerList`, `headerBooleanList`, `headerTimestampList`, `headerEnum`, `headerEnumList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: RestXmlProtocolServerBase (57 abstract methods) packages/smithy/goldens/lib/restXml/lib/src/rest_xml_protocol/rest_xml_protocol_server.dart:74 — `RestXmlProtocolServerBase` declares 57 abstract methods: `allQueryStringTypes`, `bodyWithXmlName`, `constantAndVariableQueryString`, `constantQueryString`, `datetimeOffsets`, `emptyInputAndEmptyOutput`, `endpointOperation`, `endpointWithHostLabelHeaderOperation`, `endpointWithHostLabelOperation`, `flattenedXmlMap`, `flattenedXmlMapWithXmlName`, `flattenedXmlMapWithXmlNamespace`, `fractionalSeconds`, `greetingWithErrors`, `httpPayloadTraits`, `httpPayloadTraitsWithMediaType`, `httpPayloadWithMemberXmlName`, `httpPayloadWithStructure`, `httpPayloadWithXmlName`, `httpPayloadWithXmlNamespace`, `httpPayloadWithXmlNamespaceAndPrefix`, `httpPrefixHeaders`, `httpRequestWithFloatLabels`, `httpRequestWithGreedyLabelInPath`, `httpRequestWithLabels`, `httpRequestWithLabelsAndTimestampFormat`, `httpResponseCode`, `ignoreQueryParamsInResponse`, `inputAndOutputWithHeaders`, `nestedXmlMaps`, `noInputAndNoOutput`, `noInputAndOutput`, `nullAndEmptyHeadersClient`, `nullAndEmptyHeadersServer`, `omitsNullSerializesEmptyString`, `putWithContentEncoding`, `queryIdempotencyTokenAutoFill`, `queryParamsAsStringListMap`, `queryPrecedence`, `recursiveShapes`, and 17 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AuthenticatorButtonLocalizations (18 abstract methods) packages/authenticator/amplify_authenticator/lib/src/l10n/generated/button_localizations.dart:12 — `AuthenticatorButtonLocalizations` declares 18 abstract methods: `signIn`, `signUp`, `confirm`, `continueLabel`, `submit`, `changePassword`, `sendCode`, `lostCode`, `noAccount`, `haveAccount`, `forgotPassword`, `confirmResetPassword`, `verify`, `skip`, `copyKey`, `signOut`, `backTo`, `signInWith`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AuthenticatorCountryLocalizations (246 abstract methods) packages/authenticator/amplify_authenticator/lib/src/l10n/generated/country_localizations.dart:12 — `AuthenticatorCountryLocalizations` declares 246 abstract methods: `selectDialCode`, `noDialCodeSearchResults`, `af`, `ax`, `al`, `dz`, `as1`, `ad`, `ao`, `ai`, `aq`, `ag`, `ar`, `am`, `aw`, `au`, `at`, `az`, `bs`, `bh`, `bd`, `bb`, `by`, `be`, `bz`, `bj`, `bm`, `bt`, `bo`, `bq`, `ba`, `bw`, `br`, `io`, `bn`, `bg`, `bf`, `bi`, `kh`, `cm`, and 206 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AuthenticatorInputLocalizations (37 abstract methods) packages/authenticator/amplify_authenticator/lib/src/l10n/generated/input_localizations.dart:12 — `AuthenticatorInputLocalizations` declares 37 abstract methods: `username`, `password`, `newPassword`, `email`, `phoneNumber`, `verificationCode`, `address`, `birthdate`, `familyName`, `middleName`, `gender`, `genders`, `givenName`, `name`, `nickname`, `or`, `preferredUsername`, `warnEmpty`, `warnInvalidFormat`, `promptFill`, `promptRefill`, `confirmAttribute`, `usernameRequirements`, `passwordRequirementsPreamble`, `passwordRequirementsCharacterType`, `passwordRequirementsAtLeast`, `passwordsDoNotMatch`, `rememberDevice`, `usernameType`, `optional`, `customChallenge`, `selectSms`, `selectTotp`, `selectEmail`, `totpCodePrompt`, `showPassword`, `hidePassword`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AuthService (18 abstract methods) packages/authenticator/amplify_authenticator/lib/src/services/amplify_auth_service.dart:11 — `AuthService` declares 18 abstract methods: `signIn`, `signInWithProvider`, `signOut`, `signUp`, `confirmSignUp`, `currentUser`, `isValidSession`, `isLoggedIn`, `resetPassword`, `confirmResetPassword`, `confirmSignIn`, `resendSignUpCode`, `getAttributeVerificationStatus`, `sendUserAttributeVerificationCode`, `confirmUserAttribute`, `waitForConfiguration`, `rememberDevice`, `hubEvents`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: JsonProtocolServerBase (16 abstract methods) packages/smithy/goldens/lib2/awsJson1_1/lib/src/json_protocol/json_protocol_server.dart:34 — `JsonProtocolServerBase` declares 16 abstract methods: `datetimeOffsets`, `emptyOperation`, `endpointOperation`, `endpointWithHostLabelOperation`, `fractionalSeconds`, `greetingWithErrors`, `hostWithPathOperation`, `jsonEnums`, `jsonIntEnums`, `jsonUnions`, `kitchenSinkOperation`, `nullOperation`, `operationWithOptionalInputOutput`, `putAndGetInlineDocuments`, `putWithContentEncoding`, `simpleScalarProperties`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: KitchenSink (26 abstract methods) packages/smithy/goldens/lib2/awsJson1_1/lib/src/json_protocol/model/kitchen_sink.dart:21 — `KitchenSink` declares 26 abstract methods: `blob`, `boolean`, `double_`, `emptyStruct`, `float`, `httpdateTimestamp`, `integer`, `iso8601Timestamp`, `jsonValue`, `listOfLists`, `listOfMapsOfStrings`, `listOfStrings`, `listOfStructs`, `long`, `mapOfListsOfStrings`, `mapOfMaps`, `mapOfStrings`, `mapOfStructs`, `recursiveList`, `recursiveMap`, `recursiveStruct`, `simpleStruct`, `string`, `structWithJsonName`, `timestamp`, `unixTimestamp`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: DefaultValuesInput (18 abstract methods) packages/smithy/goldens/lib2/custom/lib/src/custom/model/default_values_input.dart:15 — `DefaultValuesInput` declares 18 abstract methods: `requiredDefaultInt`, `optionalDefaultInt`, `nullifiedDefaultInt`, `requiredDefaultString`, `optionalDefaultString`, `nullifiedDefaultString`, `requiredDefaultEnum`, `optionalDefaultEnum`, `nullifiedDefaultEnum`, `requiredDefaultList`, `optionalDefaultList`, `nullifiedDefaultList`, `requiredDefaultMap`, `optionalDefaultMap`, `nullifiedDefaultMap`, `requiredDefaultBool`, `optionalDefaultBool`, `nullifiedDefaultBool`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: DefaultValuesOutput (18 abstract methods) packages/smithy/goldens/lib2/custom/lib/src/custom/model/default_values_output.dart:15 — `DefaultValuesOutput` declares 18 abstract methods: `requiredDefaultInt`, `optionalDefaultInt`, `nullifiedDefaultInt`, `requiredDefaultString`, `optionalDefaultString`, `nullifiedDefaultString`, `requiredDefaultEnum`, `optionalDefaultEnum`, `nullifiedDefaultEnum`, `requiredDefaultList`, `optionalDefaultList`, `nullifiedDefaultList`, `requiredDefaultMap`, `optionalDefaultMap`, `nullifiedDefaultMap`, `requiredDefaultBool`, `optionalDefaultBool`, `nullifiedDefaultBool`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AllQueryStringTypesInput (21 abstract methods) packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_protocol/model/all_query_string_types_input.dart:18 — `AllQueryStringTypesInput` declares 21 abstract methods: `queryString`, `queryStringList`, `queryStringSet`, `queryByte`, `queryShort`, `queryInteger`, `queryIntegerList`, `queryIntegerSet`, `queryLong`, `queryFloat`, `queryDouble`, `queryDoubleList`, `queryBoolean`, `queryBooleanList`, `queryTimestamp`, `queryTimestampList`, `queryEnum`, `queryEnumList`, `queryIntegerEnum`, `queryIntegerEnumList`, `queryParamsMapOfStringList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: InputAndOutputWithHeadersIo (18 abstract methods) packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_protocol/model/input_and_output_with_headers_io.dart:18 — `InputAndOutputWithHeadersIo` declares 18 abstract methods: `headerString`, `headerByte`, `headerShort`, `headerInteger`, `headerLong`, `headerFloat`, `headerDouble`, `headerTrueBool`, `headerFalseBool`, `headerStringList`, `headerStringSet`, `headerIntegerList`, `headerBooleanList`, `headerTimestampList`, `headerEnum`, `headerEnumList`, `headerIntegerEnum`, `headerIntegerEnumList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: RestJsonProtocolServerBase (94 abstract methods) packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_protocol/rest_json_protocol_server.dart:116 — `RestJsonProtocolServerBase` declares 94 abstract methods: `allQueryStringTypes`, `constantAndVariableQueryString`, `constantQueryString`, `datetimeOffsets`, `documentType`, `documentTypeAsPayload`, `emptyInputAndEmptyOutput`, `endpointOperation`, `endpointWithHostLabelOperation`, `fractionalSeconds`, `greetingWithErrors`, `hostWithPathOperation`, `httpChecksumRequired`, `httpEnumPayload`, `httpPayloadTraits`, `httpPayloadTraitsWithMediaType`, `httpPayloadWithStructure`, `httpPrefixHeaders`, `httpPrefixHeadersInResponse`, `httpRequestWithFloatLabels`, `httpRequestWithGreedyLabelInPath`, `httpRequestWithLabels`, `httpRequestWithLabelsAndTimestampFormat`, `httpRequestWithRegexLiteral`, `httpResponseCode`, `httpStringPayload`, `ignoreQueryParamsInResponse`, `inputAndOutputWithHeaders`, `jsonBlobs`, `jsonEnums`, `jsonIntEnums`, `jsonLists`, `jsonMaps`, `jsonTimestamps`, `jsonUnions`, `malformedAcceptWithBody`, `malformedAcceptWithGenericString`, `malformedAcceptWithPayload`, `malformedBlob`, `malformedBoolean`, and 54 more. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MalformedUniqueItemsInput (16 abstract methods) packages/smithy/goldens/lib2/restJson1/lib/src/rest_json_validation_protocol/model/malformed_unique_items_input.dart:22 — `MalformedUniqueItemsInput` declares 16 abstract methods: `blobList`, `booleanList`, `stringList`, `byteList`, `shortList`, `integerList`, `longList`, `timestampList`, `dateTimeList`, `httpDateList`, `enumList`, `intEnumList`, `listList`, `structureList`, `structureListWithNoKey`, `unionList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: AllQueryStringTypesInput (21 abstract methods) packages/smithy/goldens/lib2/restXml/lib/src/rest_xml_protocol/model/all_query_string_types_input.dart:18 — `AllQueryStringTypesInput` declares 21 abstract methods: `queryString`, `queryStringList`, `queryStringSet`, `queryByte`, `queryShort`, `queryInteger`, `queryIntegerList`, `queryIntegerSet`, `queryLong`, `queryFloat`, `queryDouble`, `queryDoubleList`, `queryBoolean`, `queryBooleanList`, `queryTimestamp`, `queryTimestampList`, `queryEnum`, `queryEnumList`, `queryIntegerEnum`, `queryIntegerEnumList`, `queryParamsMapOfStrings`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: InputAndOutputWithHeadersIo (16 abstract methods) packages/smithy/goldens/lib2/restXml/lib/src/rest_xml_protocol/model/input_and_output_with_headers_io.dart:17 — `InputAndOutputWithHeadersIo` declares 16 abstract methods: `headerString`, `headerByte`, `headerShort`, `headerInteger`, `headerLong`, `headerFloat`, `headerDouble`, `headerTrueBool`, `headerFalseBool`, `headerStringList`, `headerStringSet`, `headerIntegerList`, `headerBooleanList`, `headerTimestampList`, `headerEnum`, `headerEnumList`. Counted over its public methods with no body, once per name; concrete methods and `_`-private members are not counted, because no implementer that extends it is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • + 10 more in this group — see findings.md.
D19 · Documentation Quality · Documentation · ×32
  • Documentation: no build, run or usage example actions/README.md:1 — `actions` is runnable (`executables:` or `bin/` in its pub package) and neither `actions/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify/amplify_flutter/README.md:1 — `amplify_flutter` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify/amplify_flutter/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_connect_client/amplify_connect_client_dart/README.md:1 — `amplify_connect_client_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_connect_client/amplify_connect_client_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_core/README.md:1 — `amplify_core` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_core/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_datastore/README.md:1 — `amplify_datastore` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_datastore/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_datastore_plugin_interface/README.md:1 — `amplify_datastore_plugin_interface` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_datastore_plugin_interface/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_foundation/amplify_foundation_dart/README.md:1 — `amplify_foundation_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_foundation/amplify_foundation_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_foundation/amplify_foundation_dart_bridge/README.md:1 — `amplify_foundation_dart_bridge` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_foundation/amplify_foundation_dart_bridge/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/amplify_lints/README.md:1 — `amplify_lints` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/amplify_lints/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/analytics/amplify_analytics_pinpoint/README.md:1 — `amplify_analytics_pinpoint` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/analytics/amplify_analytics_pinpoint/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/analytics/amplify_analytics_pinpoint_dart/README.md:1 — `amplify_analytics_pinpoint_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/analytics/amplify_analytics_pinpoint_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/api/amplify_api/README.md:1 — `amplify_api` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/api/amplify_api/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/api/amplify_api_dart/README.md:1 — `amplify_api_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/api/amplify_api_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/auth/amplify_auth_cognito/README.md:1 — `amplify_auth_cognito` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/auth/amplify_auth_cognito/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/auth/amplify_auth_cognito_dart/README.md:1 — `amplify_auth_cognito_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/auth/amplify_auth_cognito_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/aws_common/README.md:1 — `aws_common` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/aws_common/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/common/amplify_db_common/README.md:1 — `amplify_db_common` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/common/amplify_db_common/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/common/amplify_db_common_dart/README.md:1 — `amplify_db_common_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/common/amplify_db_common_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/kinesis/amplify_firehose_dart/README.md:1 — `amplify_firehose_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/kinesis/amplify_firehose_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/kinesis/amplify_kinesis/README.md:1 — `amplify_kinesis` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/kinesis/amplify_kinesis/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/kinesis/amplify_kinesis_dart/README.md:1 — `amplify_kinesis_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/kinesis/amplify_kinesis_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/kinesis/amplify_record_cache_dart/README.md:1 — `amplify_record_cache_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/kinesis/amplify_record_cache_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/notifications/push/amplify_push_notifications/README.md:1 — `amplify_push_notifications` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/notifications/push/amplify_push_notifications/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/notifications/push/amplify_push_notifications_pinpoint/README.md:1 — `amplify_push_notifications_pinpoint` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/notifications/push/amplify_push_notifications_pinpoint/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/secure_storage/amplify_secure_storage_dart/README.md:1 — `amplify_secure_storage_dart` is a published pub package (`pubspec.yaml` without `publish_to: none`) and neither `packages/secure_storage/amplify_secure_storage_dart/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • + 7 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×20
  • Duplicated predicate packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart:77 — `_pendingControllerText != null && !force` appears character-identically in 2 files — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_text_field.dart, packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_username_field.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_download_task.dart:231 — `_state == StorageTransferState.canceled || _state == StorageTransferState.success || _state == StorageTransferState.failure` appears character-identically in 2 files — packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_download_task.dart, packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:94 — `accessKeyId != null && secretAccessKey != null` appears character-identically in 3 files — packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart, packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_store_data_extension.dart, packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart:58 — `accessToken != null && refreshToken != null && idToken != null` appears character-identically in 3 files — packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_provider_ios.dart, packages/auth/amplify_auth_cognito/lib/src/credentials/legacy_credential_store_data_extension.dart, packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/credential_store_state_machine.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform.dart:45 — `authOutputs?.oauth == null || authOutputs?.userPoolClientId == null` appears character-identically in 2 files — packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform.dart, packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/hosted_ui_state_machine.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart:130 — `authOutputs?.userPoolId == null || authOutputs?.userPoolClientId == null` appears character-identically in 4 files — packages/auth/amplify_auth_cognito_dart/lib/src/auth_plugin_impl.dart, packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_in_state_machine.dart, packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_out_state_machine.dart, packages/auth/amplify_auth_cognito_dart/lib/src/state/machines/sign_up_state_machine.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/smithy/smithy_codegen/lib/src/model/smithy_library.dart:21 — `basePath != null && !basePath.endsWith('/')` appears character-identically in 2 files — packages/smithy/smithy_codegen/lib/src/model/smithy_library.dart, packages/smithy/smithy_codegen/lib/src/util/shape_ext.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/amplify/amplify_flutter/lib/src/amplify_impl.dart:17 — `defaultTargetPlatform == TargetPlatform.android || defaultTargetPlatform == TargetPlatform.iOS` appears character-identically in 2 files — packages/amplify/amplify_flutter/lib/src/amplify_impl.dart, packages/auth/amplify_auth_cognito/lib/src/auth_plugin_impl.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/smithy/smithy/lib/src/protocol/json_serializer.dart:47 — `input is HasPayload && input.getPayload() == null` appears character-identically in 2 files — packages/smithy/smithy/lib/src/protocol/json_serializer.dart, packages/smithy/smithy/lib/src/protocol/xml_serializer.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/amplify_core/lib/src/types/temporal/temporal_datetime.dart:108 — `match.group(7) != null && match.group(7)!.isNotEmpty` appears character-identically in 2 files — packages/amplify_core/lib/src/types/temporal/temporal_datetime.dart, packages/amplify_core/lib/src/types/temporal/temporal_time.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_phone_field.dart:46 — `phoneNumber == null || phoneNumber.isEmpty` appears character-identically in 2 files — packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_phone_field.dart, packages/authenticator/amplify_authenticator/lib/src/utils/validators.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/amplify_core/lib/src/types/temporal/temporal_date.dart:53 — `regexString == null || regexString != iso8601String` appears character-identically in 3 files — packages/amplify_core/lib/src/types/temporal/temporal_date.dart, packages/amplify_core/lib/src/types/temporal/temporal_datetime.dart, packages/amplify_core/lib/src/types/temporal/temporal_time.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/aws_common/lib/src/http/aws_http_client_js.dart:81 — `request.method != AWSHttpMethod.get && request.method != AWSHttpMethod.head` appears character-identically in 2 files — packages/aws_common/lib/src/http/aws_http_client_js.dart, packages/aws_signature_v4/lib/src/configuration/services/s3.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/smithy/smithy/lib/src/protocol/json_serializer.dart:55 — `serialized == null || input is EmptyPayload` appears character-identically in 2 files — packages/smithy/smithy/lib/src/protocol/json_serializer.dart, packages/smithy/smithy/lib/src/protocol/xml_serializer.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart:951 — `shape.hasTrait<SensitiveTrait>() || member.hasTrait<SensitiveTrait>() || context.shapeFor(member.target).hasTrait<SensitiveTrait>()` appears character-identically in 2 files — packages/smithy/smithy_codegen/lib/src/generator/structure_generator.dart, packages/smithy/smithy_codegen/lib/src/generator/union_generator.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart:41 — `specifiedType.isUnspecified || specifiedType.parameters.isEmpty` appears character-identically in 4 files — packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart, packages/smithy/smithy/lib/src/serialization/xml/xml_built_map_serializer.dart, packages/smithy/smithy/lib/src/serialization/xml/xml_built_multimap_serializer.dart, packages/smithy/smithy/lib/src/serialization/xml/xml_built_set_serializer.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts:16 — `event.triggerSource === "CustomEmailSender_AdminCreateUser" || event.triggerSource == "CustomEmailSender_AccountTakeOverNotification"` appears character-identically in 2 files — infra-gen2/infra-common/src/lambda-triggers/custom-email-sender.ts, infra/lib/auth/stack.custom-email-sender.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift:333 — `fields.inProcess == false || fields.inProcess == nil` appears character-identically in 2 files — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/MutationSync/OutgoingMutationQueue/OutgoingMutationQueue.swift, packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/Support/MutationEvent+Query.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Error/PredictionsError+ClientError.swift:13 — `lhs.description == rhs.description && lhs.recoverySuggestion == rhs.recoverySuggestion` appears character-identically in 2 files — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Error/PredictionsError+ClientError.swift, packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Predictions/Error/PredictionsError+ServiceError.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Decorator/ConflictResolutionDecorator.swift:39 — `primaryKeysOnly && ModelRegistry.modelType(from: modelSchema.name)?.rootPath == nil` appears character-identically in 2 files — packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/Decorator/ConflictResolutionDecorator.swift, packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/ModelBasedGraphQLDocumentBuilder.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D24 · Comment Value · redundant comment · ×10
  • redundant comment infra-gen2/backends/api/api-multi-auth/amplify/backend.ts:29 — "create a new REST API" repeats the code it sits on: 4 of its 4 words (create, new, rest, api) are already in `const myRestApi = new RestApi(apiStack, "RestApi", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra-gen2/backends/api/api-multi-auth/amplify/backend.ts:43 — "create a new Lambda integration" repeats the code it sits on: 4 of its 4 words (create, new, lambda, integration) are already in `const lambdaIntegration = new LambdaIntegration(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra-gen2/backends/api/api-multi-auth/amplify/backend.ts:89 — "attach the policy to the authenticated and unauthenticated IAM roles" repeats the code it sits on: 5 of its 6 words (attach, policy, authenticated, iam, roles) are already in `backend.auth.resources.authenticatedUserIamRole.attachInlinePolicy(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra-gen2/backends/kinesis/firehose/amplify/backend.ts:32 — "Firehose delivery stream" repeats the code it sits on: 3 of its 3 words (firehose, delivery, stream) are already in `const deliveryStream = new firehose.CfnDeliveryStream(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra-gen2/infra-common/src/auth-user-extensions/custom-sender-lambda.ts:116 — "Mutation.createMFACode" repeats the code it sits on: 4 of its 4 words (mutation, create, mfa, code) are already in `mfaCodesSource.createResolver(`${name}-MutationCreateMFACodeResolver`, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra-gen2/infra-common/src/auth-user-extensions/custom-sender-lambda.ts:130 — "Query.listMFACodes" repeats the code it sits on: 4 of its 4 words (query, list, mfa, codes) are already in `mfaCodesSource.createResolver(`${name}-QueryListMFACodesResolver`, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra/lib/auth/custom-authorizer-user-pools/stack.ts:57 — "Create the User Pools authorizer" repeats the code it sits on: 4 of its 4 words (create, user, pools, authorizer) are already in `const authorizer = new apigw.CognitoUserPoolsAuthorizer(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra/lib/auth/stack.ts:258 — "Create Custom SMS handler + KMS key" repeats the code it sits on: 5 of its 6 words (create, custom, sms, kms, key) are already in `const customSenderKmsKey = new kms.Key(this, "CustomSenderKey", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra/lib/auth/stack.ts:601 — "Mutation.createMFACode" repeats the code it sits on: 4 of its 4 words (mutation, create, mfa, code) are already in `mfaCodesSource.createResolver("MutationCreateMFACodeResolver", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment infra/lib/auth/stack.ts:615 — "Query.listMFACodes" repeats the code it sits on: 4 of its 4 words (query, list, mfa, codes) are already in `mfaCodesSource.createResolver("QueryListMFACodesResolver", {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
IC1 · Incompleteness & stubs · Disabled test · ×7
  • Disabled test packages/amplify_datastore/example/integration_test/query_test/query_predicate_test/boolean_query_predicate_test.dart:128 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/amplify_datastore/example/integration_test/query_test/sort_order_test.dart:76 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/smithy/smithy_codegen/test/aws/endpoints_test.dart:67 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/smithy/smithy_codegen/test/aws/endpoints_test.dart:77 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/smithy/smithy_codegen/test/aws/endpoints_test.dart:87 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/storage/amplify_storage_s3/example/integration_test/download_data_test.dart:234 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/storage/amplify_storage_s3/example/integration_test/download_file_test.dart:303 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×6
  • Projects may be oversized for their cohesion packages/amplify_datastore/darwin/amplify_datastore/Package.swift:1 — `packages/amplify_datastore/darwin/amplify_datastore` (43609 LoC, 740 module-visible types across 101 directories) overshoots its size bounds. 6 of 80 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 8.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion packages/amplify_core/pubspec.yaml:1 — `packages/amplify_core` (15052 LoC, 407 module-visible types across 59 directories) overshoots its size bounds. 6 of 80 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 8.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion packages/auth/amplify_auth_cognito_dart/pubspec.yaml:1 — `packages/auth/amplify_auth_cognito_dart` (14658 LoC, 538 module-visible types across 33 directories) overshoots its size bounds. 6 of 80 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 8.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion packages/authenticator/amplify_authenticator/pubspec.yaml:1 — `packages/authenticator/amplify_authenticator` (16909 LoC, 183 module-visible types across 17 directories) overshoots its size bounds. 6 of 80 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 8.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion packages/smithy/smithy/pubspec.yaml:1 — `packages/smithy/smithy` (7421 LoC, 260 module-visible types across 25 directories) overshoots its size bounds. 6 of 80 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 8.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion packages/storage/amplify_storage_s3_dart/pubspec.yaml:1 — `packages/storage/amplify_storage_s3_dart` (4522 LoC, 260 module-visible types across 12 directories) overshoots its size bounds. 6 of 80 build unit(s) (Gradle, SwiftPM, Xcode, npm, pub) overshoot their size bounds, lowering Project Cohesion to 8.5/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D31 · IaC & Container Security · Low IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 9 significant file(s) lose their only recent owner: packages/aft/lib/src/commands/publish_command.dart, packages/amplify_datastore/lib/src/method_channel_datastore.dart, packages/worker_bee/worker_bee/lib/src/js/impl.dart, packages/aft/lib/src/commands/apache_license.dart, packages/aft/lib/src/publish_scheduler.dart, packages/aft/lib/src/commands/amplify_command.dart, actions/lib/src/android/sdk_manager.dart, packages/secure_storage/amplify_secure_storage/lib/src/amplify_secure_storage.vm.dart (+1 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart, packages/authenticator/amplify_authenticator/lib/src/l10n/input_resolver.dart, packages/authenticator/amplify_authenticator/lib/src/mixins/authenticator_phone_field.dart, packages/authenticator/amplify_authenticator/lib/src/widgets/authenticator_banner.dart. Pair on, review, or document these before any departure.
IC1 · Incompleteness & stubs · Member throws UnsupportedError · ×2
  • Member throws UnsupportedError actions/lib/src/node/process_manager.dart:152 — `canRun`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
  • Member throws UnsupportedError packages/smithy/smithy_codegen/lib/src/generator/visitors/symbol_visitor.dart:104 — `resourceShape`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
IC1 · Incompleteness & stubs · Blanket warning suppression · ×2
  • Blanket warning suppression packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/database_io.drift.dart:2 — `// ignore_for_file: type=lint` switches every lint off for the whole file — hidden debt. Ignore the specific lint on the specific line, with a justification, instead.
  • Blanket warning suppression packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/transfer/database/tables.drift.dart:2 — `// ignore_for_file: type=lint` switches every lint off for the whole file — hidden debt. Ignore the specific lint on the specific line, with a justification, instead.
P10 · Library API & versioning · Implementation type on the public API · ×2
  • Implementation type on the public API packages/amplify/amplify_flutter/lib/src/amplify_impl.dart:11 — 52 public types in `repository.src` are marked as implementation by their own namespace, folder or name: `AmplifyClassImpl` (packages/amplify/amplify_flutter/lib/src/amplify_impl.dart:11, name ends in `Impl`), `AmplifyHybridImpl` (packages/amplify/amplify_flutter/lib/src/hybrid_impl.dart:7, name ends in `Impl`), `AmplifyHubImpl` (packages/amplify_core/lib/src/hub/amplify_hub_impl.dart:11, name ends in `Impl`), `AnalyticsClient` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/analytics_client.dart:14, `impl`), `AWSPinpointUserProfile` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/aws_pinpoint_user_profile.dart:6, `impl`), `EndpointClient` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_client.dart:13, `impl`), `EndpointGlobalFieldsManager` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_global_fields_manager.dart:12, `impl`), `EndpointInfoStoreManager` (packages/analytics/amplify_analytics_pinpoint_dart/lib/src/impl/analytics_client/endpoint_client/endpoint_info_store_manager.dart:12, `impl`), and 44 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Embedded.swift:20 — 52 public types in `packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore` are marked as implementation by their own namespace, folder or name: `Embeddable` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Embedded.swift:20, `Internal`), `ModelDateFormatting` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+DateFormatting.swift:14, `Internal`), `JSONDecoder` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+DateFormatting.swift:37, `Internal`), `JSONEncoder` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+DateFormatting.swift:49, `Internal`), `EnumPersistable` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/Model+Enum.swift:25, `Internal`), `ModelListDecoderRegistry` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/ModelListDecoder.swift:17, `Internal`), `ModelListDecoder` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/ModelListDecoder.swift:38, `Internal`), `ModelListMarker` (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/DataStore/Model/Internal/ModelListProvider.swift:16, `Internal`), and 44 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (16 single-owned of 654 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 654 of the 2277 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/notifications/push/amplify_push_notifications/android/src/main/kotlin/com/amazonaws/amplify/amplify_push_notifications/PushNotificationBackgroundService.kt, packages/auth/amplify_auth_cognito_dart/lib/src/state/event/fetch_auth_session_event.dart.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found packages/worker_bee/e2e_flutter_test/macos/Runner.xcodeproj/project.pbxproj:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `packages/worker_bee/e2e_flutter_test/macos/Runner.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `getIDToken` spells `ID` where 707 names in the project spell it `Id` · ×1
  • `getIDToken` spells `ID` where 707 names in the project spell it `Id` actions/lib/src/node/actions/core.dart:88 — 707 of 709 names in project repository.src spell the token `Id` (707 of 709; unit: names in project repository.src containing `Id`). Peers: GitHubContext.runId (actions/lib/src/node/actions/github.dart:106); AmplifyConnectClientFlutter.create(deviceIdStore) (packages/amplify_connect_client/amplify_connect_client/lib/src/connect_client_flutter.dart:35); AmplifyConnectClientFlutter.createFromAmplifyOutputs(deviceIdStore) (packages/amplify_connect_client/amplify_connect_client/lib/src/connect_client_flutter.dart:65); repository.src.SharedPreferencesDeviceIdStore (packages/amplify_connect_client/amplify_connect_client/lib/src/shared_preferences_device_id_store.dart:8); SharedPreferencesDeviceIdStore.getOrCreateDeviceId (packages/amplify_connect_client/amplify_connect_client/lib/src/shared_preferences_device_id_store.dart:32). Rename to `getIdToken`. [rule N6]
D21 · Naming Consistency · `_subscriptionByID` spells `ID` where 24 names in the project spell it `Id` · ×1
  • `_subscriptionByID` spells `ID` where 24 names in the project spell it `Id` packages/api/amplify_api/example/lib/graphql_api_view.dart:31 — 24 of 25 names in project repository spell the token `Id` (24 of 25; unit: names in project repository containing `Id`). Peers: repository._FixedDeviceIdStore (packages/amplify_connect_client/amplify_connect_client_dart/tool/e2e_harness.dart:39); _FixedDeviceIdStore.getOrCreateDeviceId (packages/amplify_connect_client/amplify_connect_client_dart/tool/e2e_harness.dart:43); _FixedDeviceIdStore.readDeviceId (packages/amplify_connect_client/amplify_connect_client_dart/tool/e2e_harness.dart:45); NativeAmplifyApi.unsubscribe(subscriptionId) (packages/amplify_datastore/lib/amplify_datastore.dart:390); NativeApiPlugin.unsubscribe(subscriptionId) (packages/amplify_datastore/pigeons/native_plugin.dart:42). Rename to `_subscriptionById`. [rule N6]
D21 · Naming Consistency · `AmplifyAPI` spells `API` where 21 names in the project spell it `Api` · ×1
  • `AmplifyAPI` spells `API` where 21 names in the project spell it `Api` packages/api/amplify_api/lib/src/api_plugin_impl.dart:9 — 21 of 23 names in project repository.src spell the token `Api` (21 of 23; unit: names in project repository.src containing `Api`). Peers: AmplifyOutputs.AmplifyOutputs(restApi) (packages/amplify_core/lib/src/config/amplify_outputs/amplify_outputs.dart:23); AmplifyOutputs.restApi (packages/amplify_core/lib/src/config/amplify_outputs/amplify_outputs.dart:56); repository.src.RestApiOutputs (packages/amplify_core/lib/src/config/amplify_outputs/rest_api/rest_api_outputs.dart:9); ApiConfig.toRestApiOutputs (packages/amplify_core/lib/src/config/api/api_config.dart:65); repository.src.AWSApiConfig (packages/amplify_core/lib/src/config/api/appsync/api_config.dart:8). Rename to `AmplifyApi`. [rule N6]
D21 · Naming Consistency · `AmplifyAPIDart` spells `API` where 21 names in the project spell it `Api` · ×1
  • `AmplifyAPIDart` spells `API` where 21 names in the project spell it `Api` packages/api/amplify_api_dart/lib/src/api_plugin_impl.dart:26 — 21 of 23 names in project repository.src spell the token `Api` (21 of 23; unit: names in project repository.src containing `Api`). Peers: AmplifyOutputs.AmplifyOutputs(restApi) (packages/amplify_core/lib/src/config/amplify_outputs/amplify_outputs.dart:23); AmplifyOutputs.restApi (packages/amplify_core/lib/src/config/amplify_outputs/amplify_outputs.dart:56); repository.src.RestApiOutputs (packages/amplify_core/lib/src/config/amplify_outputs/rest_api/rest_api_outputs.dart:9); ApiConfig.toRestApiOutputs (packages/amplify_core/lib/src/config/api/api_config.dart:65); repository.src.AWSApiConfig (packages/amplify_core/lib/src/config/api/appsync/api_config.dart:8). Rename to `AmplifyApiDart`. [rule N6]
D21 · Naming Consistency · `setupURI` spells `URI` where 1059 names in the project spell it `Uri` · ×1
  • `setupURI` spells `URI` where 1059 names in the project spell it `Uri` packages/authenticator/amplify_authenticator/lib/src/state/auth_state.dart:141 — 1059 of 1060 names in project repository.src spell the token `Uri` (1059 of 1060; unit: names in project repository.src containing `Uri`). Peers: AmplifyPubLauncher.AmplifyPubLauncher(pubServerUri) (packages/aft/lib/src/commands/serve_command.dart:103); OAuthOutputs.OAuthOutputs(redirectSignInUri) (packages/amplify_core/lib/src/config/amplify_outputs/auth/oauth_outputs.dart:17); OAuthOutputs.OAuthOutputs(signInUri) (packages/amplify_core/lib/src/config/amplify_outputs/auth/oauth_outputs.dart:17); OAuthOutputs.OAuthOutputs(signInUriQueryParameters) (packages/amplify_core/lib/src/config/amplify_outputs/auth/oauth_outputs.dart:17); OAuthOutputs.OAuthOutputs(redirectSignOutUri) (packages/amplify_core/lib/src/config/amplify_outputs/auth/oauth_outputs.dart:17). Rename to `setupUri`. [rule N6]
D21 · Naming Consistency · `MockAWSHttpClient` spells `AWS` where 256 names in the project spell it `Aws` · ×1
  • `MockAWSHttpClient` spells `AWS` where 256 names in the project spell it `Aws` packages/aws_common/lib/src/http/mock.dart:16 — 256 of 259 names in project repository.src spell the token `Aws` (256 of 259; unit: names in project repository.src containing `Aws`). Peers: GenerateSdkCommand._generateAwsConfig (packages/aft/lib/src/commands/generate/generate_sdk_command.dart:275); repository.src.CredentialsAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/credentials.dart:67); repository.src.ExternalServiceExceptionAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/external_service_exception.dart:75); repository.src.GetCredentialsForIdentityInputAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/get_credentials_for_identity_input.dart:81); repository.src.GetCredentialsForIdentityResponseAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/get_credentials_for_identity_response.dart:67). Rename to `MockAwsHttpClient`. [rule N6]
D21 · Naming Consistency · `_unwrapJSError` spells `JS` where 12 names in the project spell it `Js` · ×1
  • `_unwrapJSError` spells `JS` where 12 names in the project spell it `Js` packages/aws_common/lib/src/js/readable_stream.dart:245 — 12 of 13 names in project repository.src spell the token `Js` (12 of 13; unit: names in project repository.src containing `Js`). Peers: OperationTestGenerator._maxSafeJsInt (packages/smithy/smithy_codegen/lib/src/generator/operation_test_generator.dart:587); JsGenerator.JsGenerator(declaresJsEntrypoint) (packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:13); JsGenerator.declaresJsEntrypoint (packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:23); JsGenerator._workersJs (packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:41); JsGenerator._workersJsPath (packages/worker_bee/worker_bee_builder/lib/src/impl/js.dart:42). Rename to `_unwrapJsError`. [rule N6]
D21 · Naming Consistency · `folderID` spells `ID` where 707 names in the project spell it `Id` · ×1
  • `folderID` spells `ID` where 707 names in the project spell it `Id` packages/secure_storage/amplify_secure_storage/lib/src/path_provider_local.dart:16 — 707 of 709 names in project repository.src spell the token `Id` (707 of 709; unit: names in project repository.src containing `Id`). Peers: GitHubContext.runId (actions/lib/src/node/actions/github.dart:106); AmplifyConnectClientFlutter.create(deviceIdStore) (packages/amplify_connect_client/amplify_connect_client/lib/src/connect_client_flutter.dart:35); AmplifyConnectClientFlutter.createFromAmplifyOutputs(deviceIdStore) (packages/amplify_connect_client/amplify_connect_client/lib/src/connect_client_flutter.dart:65); repository.src.SharedPreferencesDeviceIdStore (packages/amplify_connect_client/amplify_connect_client/lib/src/shared_preferences_device_id_store.dart:8); SharedPreferencesDeviceIdStore.getOrCreateDeviceId (packages/amplify_connect_client/amplify_connect_client/lib/src/shared_preferences_device_id_store.dart:32). Rename to `folderId`. [rule N6]
D21 · Naming Consistency · `_isAWSFileStream` spells `AWS` where 256 names in the project spell it `Aws` · ×1
  • `_isAWSFileStream` spells `AWS` where 256 names in the project spell it `Aws` packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:185 — 256 of 259 names in project repository.src spell the token `Aws` (256 of 259; unit: names in project repository.src containing `Aws`). Peers: GenerateSdkCommand._generateAwsConfig (packages/aft/lib/src/commands/generate/generate_sdk_command.dart:275); repository.src.CredentialsAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/credentials.dart:67); repository.src.ExternalServiceExceptionAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/external_service_exception.dart:75); repository.src.GetCredentialsForIdentityInputAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/get_credentials_for_identity_input.dart:81); repository.src.GetCredentialsForIdentityResponseAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/get_credentials_for_identity_response.dart:67). Rename to `_isAwsFileStream`. [rule N6]
D21 · Naming Consistency · `_checkIfAWSFileStream` spells `AWS` where 256 names in the project spell it `Aws` · ×1
  • `_checkIfAWSFileStream` spells `AWS` where 256 names in the project spell it `Aws` packages/storage/amplify_storage_s3_dart/lib/src/storage_s3_service/service/task/s3_upload_task.dart:812 — 256 of 259 names in project repository.src spell the token `Aws` (256 of 259; unit: names in project repository.src containing `Aws`). Peers: GenerateSdkCommand._generateAwsConfig (packages/aft/lib/src/commands/generate/generate_sdk_command.dart:275); repository.src.CredentialsAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/credentials.dart:67); repository.src.ExternalServiceExceptionAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/external_service_exception.dart:75); repository.src.GetCredentialsForIdentityInputAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/get_credentials_for_identity_input.dart:81); repository.src.GetCredentialsForIdentityResponseAwsJson11Serializer (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src/cognito_identity/model/get_credentials_for_identity_response.dart:67). Rename to `_checkIfAwsFileStream`. [rule N6]
D21 · Naming Consistency · `amplifyIosNewIssueUrl` spells `Url` where 12 names in the project spell it `URL` · ×1
  • `amplifyIosNewIssueUrl` spells `Url` where 12 names in the project spell it `URL` packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/DevMenu/View/IssueReporter.swift:32 — 12 of 13 names in project packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore spell the token `URL` (12 of 13; unit: names in project packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore containing `URL`). Peers: RequestRetryable.retryRequestAdvice(httpURLResponse) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RequestRetryable.swift:22); RequestRetryablePolicy.retryRequestAdvice(httpURLResponse) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/RequestRetryablePolicy.swift:17); packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore.StorageGetURLRequest (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageGetURLRequest.swift:13); packages~amplify_datastore~darwin~amplify_datastore~amplify_datastore.StorageGetURLOperation (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/StorageGetURLOperation.swift:11); Storage.getURL (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/StorageGetURLOperation.swift:15). Rename to `amplifyIosNewIssueURL`. [rule N6]
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body packages/secure_storage/amplify_secure_storage_dart/lib/src/amplify_secure_storage_dart.dart:67 — `registerWith` has an empty body — confirm it's an intentional no-op and not an unfinished method.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 27/55 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `actions`, `canaries`, `canaries/ios`, `packages/amplify/amplify_flutter/example`, `packages/amplify_connect_client/amplify_connect_client/example` and 23 more.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST .github/workflows/actions.yaml:11 — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 115 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch pip/gitsubmodule · ×1
  • Dependabot does not watch pip/gitsubmodule REDACTED:4 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate .github/workflows/publish-tag.yaml:160 — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected — This repository runs an HTTP server that is not bound to the loopback interface alone — or binds it at an address its source does not spell out — and nothing in its Dart source secures the transport: no `HttpServer.bindSecure` or `securityContext:`, no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: packages/smithy/smithy_codegen/pubspec.yaml:31 — depends on `shelf`.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Dart server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: packages/smithy/smithy_codegen/pubspec.yaml:31 — depends on `shelf`.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1
  • Diagnostic log message is built whether or not it is wanted packages/aft/lib/src/commands/run_command.dart:63 — `verbose` at line 63 is called with an argument built by `commandPaths.map((path) => '…' path)` (line 67), whose cost grows with the collection it walks. Dart evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLoggable` test, no `kDebugMode` or debug flag, no `assert`, no closure the logger calls only when the level is on.
X5 · Nullable reference types · Sound null safety is not on in every Dart package · ×1
  • Sound null safety is not on in every Dart package — 45/47 of this repository's Dart packages (a `pubspec.yaml` with product Dart beneath it) declare a language version of 2.12 or above in `environment: sdk:`, which is what turns sound null safety on. A pubspec with no SDK constraint, or a lower bound below 2.12, runs its code unsound: every type admits null, and a null reaching a method call throws `NoSuchMethodError` with nothing in the analyzer having said so.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure packages/amplify_connect_client/amplify_connect_client_dart/lib/src/services/connect_write_service.dart:113 — `_decode` answers `{}` when `FormatException` is thrown, with no log or rethrow — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Minor — 2 finding(s)
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names infra/lib/auth/stack.ts:127 — 1 of 10 documented parameters and 3 of 42 summaries in `infra` only repeat the member or parameter name (e.g. "The advanced security mode." for `advancedSecurityMode`). Delete the restating tags, or add what the name does not say.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: aws_common — aws_common: abstractness 0.25, instability 0.00, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-7cf1f15f53284f3f890cf3bf7af6b6c4/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-7cf1f15f53284f3f890cf3bf7af6b6c4/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=2553" --report-format json --report-path /tmp/watchdog-gitleaks-7cf1f15f53284f3f890cf3bf7af6b6c4/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=3553 --max-count=578" --report-format json --report-path /tmp/watchdog-gitleaks-7cf1f15f53284f3f890cf3bf7af6b6c4/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.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-7cf1f15f53284f3f890cf3bf7af6b6c4/tree.json --exit-code 0 --source .0artifacts/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 --exclude packages/aft/test/version_bump/data --exclude packages/amplify/amplify_flutter/example/android --exclude packages/amplify/amplify_flutter/example/ios --exclude packages/amplify/amplify_flutter/example/linux --exclude packages/amplify/amplify_flutter/example/macos --exclude packages/amplify/amplify_flutter/example/web/icons --exclude packages/amplify/amplify_flutter/example/windows --exclude packages/amplify_connect_client/amplify_connect_client/example/macos --exclude packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/pigeons --exclude packages/amplify_datastore/example/android --exclude packages/amplify_datastore/example/ios/Flutter --exclude packages/amplify_datastore/example/ios/Runner --exclude packages/amplify_datastore/example/ios/Runner.xcodeproj --exclude packages/amplify_datastore/example/ios/Runner.xcworkspace --exclude packages/amplify_datastore/example/lib/models --exclude packages/amplify_native_legacy_wrapper/android/src/main/kotlin/com/amazonaws/amplify/amplify_native_legacy_wrapper/pigeons --exclude packages/amplify_native_legacy_wrapper/example/android --exclude packages/amplify_native_legacy_wrapper/example/ios --exclude packages/analytics/amplify_analytics_pinpoint/android/src/main/java --exclude packages/analytics/amplify_analytics_pinpoint/example/android --exclude packages/analytics/amplify_analytics_pinpoint/example/ios --exclude packages/analytics/amplify_analytics_pinpoint/example/linux --exclude packages/analytics/amplify_analytics_pinpoint/example/macos --exclude packages/analytics/amplify_analytics_pinpoint/example/web/icons --exclude packages/analytics/amplify_analytics_pinpoint/example/windows --exclude packages/analytics/amplify_analytics_pinpoint_dart/lib/src/sdk/src --exclude packages/api/amplify_api/example/android --exclude packages/api/amplify_api/example/ios --exclude packages/api/amplify_api/example/lib/models --exclude packages/api/amplify_api/example/linux --exclude packages/api/amplify_api/example/macos --exclude packages/api/amplify_api/example/web/icons --exclude packages/api/amplify_api/example/windows --exclude packages/auth/amplify_auth_cognito/android/src/main/kotlin/com/amazonaws/amplify/amplify_auth_cognito/pigeons --exclude packages/auth/amplify_auth_cognito/example/android --exclude packages/auth/amplify_auth_cognito/example/ios --exclude packages/auth/amplify_auth_cognito/example/linux --exclude packages/auth/amplify_auth_cognito/example/macos --exclude packages/auth/amplify_auth_cognito/example/web/icons --exclude packages/auth/amplify_auth_cognito/example/windows --exclude packages/auth/amplify_auth_cognito_dart/lib/src/sdk/src --exclude packages/authenticator/amplify_authenticator/example/android --exclude packages/authenticator/amplify_authenticator/example/ios --exclude packages/authenticator/amplify_authenticator/example/linux --exclude packages/authenticator/amplify_authenticator/example/macos --exclude packages/authenticator/amplify_authenticator/example/web/icons --exclude packages/authenticator/amplify_authenticator/example/windows --exclude packages/authenticator/amplify_authenticator_test/example/android --exclude packages/authenticator/amplify_authenticator_test/example/ios --exclude packages/authenticator/amplify_authenticator_test/example/linux --exclude packages/authenticator/amplify_authenticator_test/example/macos --exclude packages/authenticator/amplify_authenticator_test/example/web/icons --exclude packages/authenticator/amplify_authenticator_test/example/windows --exclude packages/common/amplify_db_common/example/android --exclude packages/common/amplify_db_common/example/ios --exclude packages/common/amplify_db_common/example/linux --exclude packages/common/amplify_db_common/example/macos --exclude packages/common/amplify_db_common/example/web/icons --exclude packages/common/amplify_db_common/example/windows --exclude packages/kinesis/amplify_firehose/example/android --exclude packages/kinesis/amplify_firehose/example/ios --exclude packages/kinesis/amplify_firehose/example/linux --exclude packages/kinesis/amplify_firehose/example/macos --exclude packages/kinesis/amplify_firehose/example/web/icons --exclude packages/kinesis/amplify_firehose/example/windows --exclude packages/kinesis/amplify_firehose_dart/lib/src/sdk --exclude packages/kinesis/amplify_kinesis/example/android --exclude packages/kinesis/amplify_kinesis/example/ios --exclude packages/kinesis/amplify_kinesis/example/linux --exclude packages/kinesis/amplify_kinesis/example/macos --exclude packages/kinesis/amplify_kinesis/example/web/icons --exclude packages/kinesis/amplify_kinesis/example/windows --exclude packages/kinesis/amplify_kinesis_dart/lib/src/sdk --exclude packages/notifications/push/amplify_push_notifications/example/android --exclude packages/notifications/push/amplify_push_notifications/example/ios --exclude packages/notifications/push/amplify_push_notifications/example/linux --exclude packages/notifications/push/amplify_push_notifications/example/macos --exclude packages/notifications/push/amplify_push_notifications_pinpoint/example/android --exclude packages/notifications/push/amplify_push_notifications_pinpoint/example/ios/Flutter --exclude packages/notifications/push/amplify_push_notifications_pinpoint/example/ios/Runner --exclude packages/notifications/push/amplify_push_notifications_pinpoint/example/ios/Runner.xcodeproj --exclude packages/notifications/push/amplify_push_notifications_pinpoint/example/ios/Runner.xcworkspace --exclude packages/secure_storage/amplify_secure_storage/android/src/main/kotlin/com/amazonaws/amplify/amplify_secure_storage/pigeons --exclude packages/secure_storage/amplify_secure_storage/example/android --exclude packages/secure_storage/amplify_secure_storage/example/ios --exclude packages/secure_storage/amplify_secure_storage/example/linux --exclude packages/secure_storage/amplify_secure_storage/example/macos --exclude packages/secure_storage/amplify_secure_storage/example/web/icons --exclude packages/secure_storage/amplify_secure_storage/example/windows --exclude packages/secure_storage/amplify_secure_storage/lib/src/pigeons --exclude packages/smithy/goldens/lib --exclude packages/smithy/goldens/lib2 --exclude packages/smithy/goldens/models/awsJson1_0 --exclude packages/smithy/goldens/models/awsJson1_1 --exclude packages/smithy/goldens/models/awsQuery --exclude packages/smithy/goldens/models/ec2Query --exclude packages/smithy/goldens/models/restJson1 --exclude packages/smithy/goldens/models/restXml --exclude packages/smithy/goldens/models/restXmlWithNamespace --exclude packages/smithy/goldens/models/shared --exclude packages/storage/amplify_storage_s3/example/android --exclude packages/storage/amplify_storage_s3/example/ios --exclude packages/storage/amplify_storage_s3/example/linux --exclude packages/storage/amplify_storage_s3/example/macos --exclude packages/storage/amplify_storage_s3/example/web/icons --exclude packages/storage/amplify_storage_s3/example/windows --exclude packages/storage/amplify_storage_s3_dart/lib/src/sdk --exclude packages/test/amplify_integration_test/lib/src/sdk --exclude packages/worker_bee/worker_bee/example/android --exclude packages/worker_bee/worker_bee/example/lib/models --exclude packages/worker_bee/worker_bee/example/macos --exclude packages/worker_bee/worker_bee/example/web/icons --exclude templates/flutter-package/__brick__/example/android --exclude templates/flutter-package/__brick__/example/ios --exclude templates/flutter-package/__brick__/example/linux --exclude templates/flutter-package/__brick__/example/macos --exclude templates/flutter-package/__brick__/example/web/icons --exclude templates/flutter-package/__brick__/example/windows .281artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .57artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Storage/SQLite/SQLStatement+CreateTable.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/AWSIncomingEventReconciliationQueue.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Sync/SubscriptionSync/IncomingAsyncSubscriptionEventPublisher.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Keychain/KeychainStore.swift`, `packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/API/Operation/RetryableGraphQLOperation.swift`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1eb8e-be3f-7bb8-a588-64239f38a810 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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