Public report of stripe/stripe-ios, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 23:11 UTC · Survey ID cd_e641a18f79cb471aa5870ba3cc7f340a
stripe/stripe-ios
Measured 14 November 2026, 23:07 UTC, at code version 58ae92d
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 246,301 lines of product code in 21 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Accessibility, 24
Findings by how serious they are
35 critical1637 serious282 minor
21 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 23:07 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.
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 ▸
49of 49 dimensions measured by tools.
1931of 1954 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
49dimensions across 8 lenses, read from 246,301 lines of product code in 21 projects.
stripe/stripe-ios falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 42 out of 100 and is rated Weak, and 23 of its 35 critical findings are security problems.
Accessibility, at 24, is the weakest lens and counts most in the score. The best first steps are making the controls keyboard-usable and fixing focus, motion and contrast, each worth about 8 points. Raising Accessibility to 70 would lift the score to about 56.
Eleven passwords or keys are open to anyone who can read the repository. Six known security holes in the packages the code depends on can be used by attackers, and five places in the code run text as code, which an attacker could use. Replacing each exposed password or key, updating the vulnerable packages and replacing text run as code with direct calls would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The five parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 246,301 lines, about €330,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 24 to 70, the lowest score rated Strong, the score would rise from 42 to about 56.
Code composition: what the lines of code are
Product code 65%Tests 35%
New since the last survey: 534 findings
These 534 critical or serious findings weren't in the previous survey, on 29 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · TooManyMethods: CheckoutElementsController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController.swift
God Classes · MethodTooLong: CheckoutElementsController.confirmLink StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift
God Classes · MethodTooLong: PaneLayoutView.createFooterView StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift
God Classes · FileTooLong: AddressViewController/AddressViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift
God Classes · ClassTooLong: PaymentSheetAnalyticsHelper StripePaymentSheet/StripePaymentSheet/Source/Analytics/PaymentSheetAnalyticsHelper.swift
God Classes · MethodTooLong: CheckoutElementsController.makeConfirmationFlow StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift
Code Duplication · Near-duplicate member family (4 members, 35 shared lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift
Code Duplication · Near-duplicate member pair (56 shared lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift
Code Duplication · Edited copy of a member (109 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift
Code Duplication · Edited copy of a member (105 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copy of a member (83 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copy of a member (69 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift
Code Duplication · Edited copy of a member (66 corresponding lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift
Code Duplication · Edited copy of a member (67 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copy of a member (50 corresponding lines) StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift
Code Duplication · Edited copy of a member (60 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift
Code Duplication · Edited copy of a member (40 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift
Code Duplication · Edited copy of a member (32 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift
Code Duplication · Edited copy of a member (24 corresponding lines) Example/AppClipExample/Shared/BackendModel.swift
Code Duplication · Edited copy of a member (50 corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionAPI.swift
Code Duplication · Edited copies of one member (3 members, 48+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift
Code Duplication · Edited copy of a member (45 corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift
Code Duplication · Edited copy of a member (40 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift
Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift
Code Duplication · Edited copy of a member (32 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copy of a member (29 corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift
Code Duplication · Edited copy of a member (15 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+SEPADebit.swift
Code Duplication · Edited copy of a member (32 corresponding lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift
Code Duplication · Edited copy of a member (32 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/FinancialConnectionsFont.swift
Code Duplication · Edited copy of a member (40 corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift
Code Duplication · Edited copy of a member (48 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift
Code Duplication · Edited copy of a member (42 corresponding lines) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift
Code Duplication · Edited copy of a member (31 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift
Code Duplication · Edited copy of a member (33 corresponding lines) Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift
Code Duplication · Edited copy of a member (27 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift
Code Duplication · Edited copy of a member (66 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift
Code Duplication · Edited copy of a member (33 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copy of a member (38 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift
Code Duplication · Edited copy of a member (18 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenParams.swift
Code Duplication · Edited copy of a member (18 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift
Code Duplication · Edited copy of a member (48 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AccountNumberRetrievalErrorView.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSpecProvider.swift
Code Duplication · Edited copy of a member (25 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AttributedLabel.swift
Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift
Code Duplication · Edited copy of a member (25 corresponding lines) StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift
Code Duplication · Edited copy of a member (28 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift
Code Duplication · Edited copy of a member (32 corresponding lines) StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift
Code Duplication · Edited copy of a member (24 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/FormElement+Link.swift
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenClientContext.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift
Code Duplication · Edited copy of a member (16 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift
Code Duplication · Edited copy of a member (38 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift
Code Duplication · Edited copy of a member (24 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/InstantDebitsPaymentMethodElement.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift
Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift
Code Duplication · Edited copy of a member (26 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift
Code Duplication · Edited copy of a member (17 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCardParams.swift
Code Duplication · Edited copy of a member (16 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift
Code Duplication · Edited copy of a member (27 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift
Code Duplication · Edited copy of a member (17 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/UIButton+PaymentSheet.swift
Code Duplication · Edited copy of a member (15 corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/Extensions/CGRectExtension.swift
Code Duplication · Edited copy of a member (31 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift
Code Duplication · Edited copy of a member (35 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenClientContext.swift
Code Duplication · Edited copy of a member (19 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift
Code Duplication · Edited copy of a member (28 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift
Code Duplication · Edited copy of a member (18 corresponding lines) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift
Code Duplication · Edited copy of a member (15 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift
Code Duplication · Edited copy of a member (17 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift
Code Duplication · Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift
Code Duplication · Edited copy of a member (31 corresponding lines) StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift
Code Duplication · Edited copy of a member (31 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+CheckoutSession.swift
Code Duplication · Edited copy of a member (20 corresponding lines) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntent.swift
Code Duplication · Edited copy of a member (25 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/FinancialConnectionsSDK/FinancialConnectionsSDKImplementation.swift
Code Duplication · Edited copy of a member (12 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift
Code Duplication · Edited copy of a member (19 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift
Code Duplication · Edited copy of a member (21 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift
Code Duplication · Edited copy of a member (14 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift
Code Duplication · Edited copy of a member (23 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift
Code Duplication · Edited copy of a member (16 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/AddressAutocompleteModels.swift
Code Duplication · Edited copy of a member (22 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentFileUploadViewController+Strings.swift
Code Duplication · Edited copy of a member (18 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift
Code Duplication · Edited copy of a member (24 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionPickerViewController.swift
Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.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: 180 findings
These 180 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one. The first 100 are listed here.
€110,000 to €550,000, for 1,811 to 5,745 hours of work, about 2.2 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 246,301 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 4 points · Medium effort · Page structure
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 €330,000 to build again, about 2.2 person-years of work. Its weakest lens is Accessibility, at 24 (Critical). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for medium effort. 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.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 219,807 lines over the last 90 days, which is about 891,440 lines a year. At that pace, the extra work comes to an estimated 69.7 to 418.3 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.
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.
79 modules, with 559 dependencies between them. 2 loops run through 58 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 39 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 a module listed above itPart of a loopThe module itself
1→11 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeFinancialConnections~StripeFinancialConnections~Nativepart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeFinancialConnections~StripeFinancialConnections~Native.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeFinancialConnections~StripeFinancialConnections~Native, so a change to StripeFinancialConnections~StripeFinancialConnections~Native can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeFinancialConnections~StripeFinancialConnections~Native.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→13 StripeFinancialConnections~StripeFinancialConnections~Common uses repositorypart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in repository.
StripeFinancialConnections~StripeFinancialConnections~Common uses repository, so a change to repository can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→14 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeFinancialConnections~StripeFinancialConnections~Helperspart of a loop✕
Connections
9 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→15 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeFinancialConnections~StripeFinancialConnections~API Bindingspart of a loop✕
Connections
7 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeFinancialConnections~StripeFinancialConnections~API Bindings, so a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeFinancialConnections~StripeFinancialConnections~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→18 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeIdentity~StripeIdentity~Categories.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→19 StripeFinancialConnections~StripeFinancialConnections~Common uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripePaymentSheet~StripePaymentSheet~Helpers.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→21 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
5 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeCore~StripeCore~Connections Bindings.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→27 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
3 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeUICore~StripeUICore~Categories.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→30 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
3 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeCore~StripeCore~Analytics.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→33 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1→35 StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Common uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeFinancialConnections~StripeFinancialConnections~Common uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeFinancialConnections~StripeFinancialConnections~Common, while a change to StripeFinancialConnections~StripeFinancialConnections~Common can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→13 StripeIdentity~StripeIdentity~WebWrapper uses repositorypart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in repository.
StripeIdentity~StripeIdentity~WebWrapper uses repository, so a change to repository can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→17 StripeIdentity~StripeIdentity~WebWrapper uses StripeCore~StripeCore~UIpart of a loop✕
Connections
2 pairs of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeCore~StripeCore~UI.
StripeIdentity~StripeIdentity~WebWrapper uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→18 StripeIdentity~StripeIdentity~WebWrapper uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeIdentity~StripeIdentity~Categories.
StripeIdentity~StripeIdentity~WebWrapper uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→23 StripeIdentity~StripeIdentity~WebWrapper uses StripeConnect~StripeConnect~Internalpart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeConnect~StripeConnect~Internal.
StripeIdentity~StripeIdentity~WebWrapper uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeConnect~StripeConnect~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→25 StripeIdentity~StripeIdentity~WebWrapper uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeCore~StripeCore~Categories.
StripeIdentity~StripeIdentity~WebWrapper uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→27 StripeIdentity~StripeIdentity~WebWrapper uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeUICore~StripeUICore~Categories.
StripeIdentity~StripeIdentity~WebWrapper uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→30 StripeIdentity~StripeIdentity~WebWrapper uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeCore~StripeCore~Analytics.
StripeIdentity~StripeIdentity~WebWrapper uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→35 StripeIdentity~StripeIdentity~WebWrapper uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~WebWrapper uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeIdentity~StripeIdentity~WebWrapper uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeIdentity~StripeIdentity~WebWrapper, while a change to StripeIdentity~StripeIdentity~WebWrapper can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→12 StripePaymentSheet~StripePaymentSheet~Analytics uses StripePaymentSheet~StripePaymentSheet~PaymentSheetpart of a loop✕
Connections
9 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→16 StripePaymentSheet~StripePaymentSheet~Analytics uses StripePaymentSheet~StripePaymentSheet~Internalpart of a loop✕
Connections
17 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripePaymentSheet~StripePaymentSheet~Internal.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→18 StripePaymentSheet~StripePaymentSheet~Analytics uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripeIdentity~StripeIdentity~Categories.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→19 StripePaymentSheet~StripePaymentSheet~Analytics uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
3 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripePaymentSheet~StripePaymentSheet~Helpers.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→20 StripePaymentSheet~StripePaymentSheet~Analytics uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripePayments~StripePayments~API Bindings.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→30 StripePaymentSheet~StripePaymentSheet~Analytics uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
7 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripeCore~StripeCore~Analytics.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→38 StripePaymentSheet~StripePaymentSheet~Analytics uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
3 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Analytics uses a type in StripeApplePay~StripeApplePay~Extensions.
StripePaymentSheet~StripePaymentSheet~Analytics uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripePaymentSheet~StripePaymentSheet~Analytics, while a change to StripePaymentSheet~StripePaymentSheet~Analytics can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→23 StripePayments~StripePayments~Captcha uses StripeConnect~StripeConnect~Internalpart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Captcha uses a type in StripeConnect~StripeConnect~Internal.
StripePayments~StripePayments~Captcha uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripePayments~StripePayments~Captcha, while a change to StripePayments~StripePayments~Captcha can't break StripeConnect~StripeConnect~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→25 StripePayments~StripePayments~Captcha uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
3 pairs of types, where a type in StripePayments~StripePayments~Captcha uses a type in StripeCore~StripeCore~Categories.
StripePayments~StripePayments~Captcha uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripePayments~StripePayments~Captcha, while a change to StripePayments~StripePayments~Captcha can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→27 StripePayments~StripePayments~Captcha uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Captcha uses a type in StripeUICore~StripeUICore~Categories.
StripePayments~StripePayments~Captcha uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripePayments~StripePayments~Captcha, while a change to StripePayments~StripePayments~Captcha can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→29 StripePayments~StripePayments~Captcha uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Captcha uses a type in StripeCore~StripeCore~Coder.
StripePayments~StripePayments~Captcha uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePayments~StripePayments~Captcha, while a change to StripePayments~StripePayments~Captcha can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→31 StripePayments~StripePayments~Captcha uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Captcha uses a type in StripeCardScan~StripeCardScan~CardScan.
StripePayments~StripePayments~Captcha uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripePayments~StripePayments~Captcha, while a change to StripePayments~StripePayments~Captcha can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→7 StripePayments~StripePayments~PaymentHandler uses StripePayments~StripePayments~Internalpart of a loop✕
Connections
5 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripePayments~StripePayments~Internal.
StripePayments~StripePayments~PaymentHandler uses StripePayments~StripePayments~Internal, so a change to StripePayments~StripePayments~Internal can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripePayments~StripePayments~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→11 StripePayments~StripePayments~PaymentHandler uses StripeFinancialConnections~StripeFinancialConnections~Nativepart of a loop✕
Connections
3 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeFinancialConnections~StripeFinancialConnections~Native.
StripePayments~StripePayments~PaymentHandler uses StripeFinancialConnections~StripeFinancialConnections~Native, so a change to StripeFinancialConnections~StripeFinancialConnections~Native can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeFinancialConnections~StripeFinancialConnections~Native.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→13 StripePayments~StripePayments~PaymentHandler uses repositorypart of a loop✕
Connections
2 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in repository.
StripePayments~StripePayments~PaymentHandler uses repository, so a change to repository can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→17 StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~UIpart of a loop✕
Connections
5 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeCore~StripeCore~UI.
StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→18 StripePayments~StripePayments~PaymentHandler uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeIdentity~StripeIdentity~Categories.
StripePayments~StripePayments~PaymentHandler uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→20 StripePayments~StripePayments~PaymentHandler uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
9 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripePayments~StripePayments~API Bindings.
StripePayments~StripePayments~PaymentHandler uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→23 StripePayments~StripePayments~PaymentHandler uses StripeConnect~StripeConnect~Internalpart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeConnect~StripeConnect~Internal.
StripePayments~StripePayments~PaymentHandler uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeConnect~StripeConnect~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→24 StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
3 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeCore~StripeCore~Helpers.
StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→25 StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeCore~StripeCore~Categories.
StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→30 StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
4 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeCore~StripeCore~Analytics.
StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→36 StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripePayments~StripePayments~PaymentHandler uses a type in StripeCore~StripeCore~API Bindings.
StripePayments~StripePayments~PaymentHandler uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePayments~StripePayments~PaymentHandler, while a change to StripePayments~StripePayments~PaymentHandler can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→13 StripeUICore~StripeUICore~Controls uses repositorypart of a loop✕
Connections
3 pairs of types, where a type in StripeUICore~StripeUICore~Controls uses a type in repository.
StripeUICore~StripeUICore~Controls uses repository, so a change to repository can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→14 StripeUICore~StripeUICore~Controls uses StripeFinancialConnections~StripeFinancialConnections~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripeUICore~StripeUICore~Controls uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→17 StripeUICore~StripeUICore~Controls uses StripeCore~StripeCore~UIpart of a loop✕
Connections
1 pair of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeCore~StripeCore~UI.
StripeUICore~StripeUICore~Controls uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→19 StripeUICore~StripeUICore~Controls uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripePaymentSheet~StripePaymentSheet~Helpers.
StripeUICore~StripeUICore~Controls uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→26 StripeUICore~StripeUICore~Controls uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
2 pairs of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeUICore~StripeUICore~Elements.
StripeUICore~StripeUICore~Controls uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 StripeUICore~StripeUICore~Controls uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
6 pairs of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeUICore~StripeUICore~Categories.
StripeUICore~StripeUICore~Controls uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→29 StripeUICore~StripeUICore~Controls uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
1 pair of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeCore~StripeCore~Coder.
StripeUICore~StripeUICore~Controls uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→31 StripeUICore~StripeUICore~Controls uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
2 pairs of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeUICore~StripeUICore~Controls uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→33 StripeUICore~StripeUICore~Controls uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripeUICore~StripeUICore~Controls uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→35 StripeUICore~StripeUICore~Controls uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
1 pair of types, where a type in StripeUICore~StripeUICore~Controls uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeUICore~StripeUICore~Controls uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeUICore~StripeUICore~Controls, while a change to StripeUICore~StripeUICore~Controls can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripePayments~StripePayments~Internal uses StripePayments~StripePayments~PaymentHandler, so a change to StripePayments~StripePayments~PaymentHandler can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripePayments~StripePayments~PaymentHandler.
Position
Below the diagonal: StripePayments~StripePayments~Internal uses a module listed above it, which is the healthy direction.
7→18 StripePayments~StripePayments~Internal uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeIdentity~StripeIdentity~Categories.
StripePayments~StripePayments~Internal uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→20 StripePayments~StripePayments~Internal uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
10 pairs of types, where a type in StripePayments~StripePayments~Internal uses a type in StripePayments~StripePayments~API Bindings.
StripePayments~StripePayments~Internal uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→21 StripePayments~StripePayments~Internal uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
6 pairs of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeCore~StripeCore~Connections Bindings.
StripePayments~StripePayments~Internal uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→23 StripePayments~StripePayments~Internal uses StripeConnect~StripeConnect~Internalpart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeConnect~StripeConnect~Internal.
StripePayments~StripePayments~Internal uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeConnect~StripeConnect~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→24 StripePayments~StripePayments~Internal uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeCore~StripeCore~Helpers.
StripePayments~StripePayments~Internal uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→28 StripePayments~StripePayments~Internal uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeConnect~StripeConnect~Helpers.
StripePayments~StripePayments~Internal uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→30 StripePayments~StripePayments~Internal uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
6 pairs of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeCore~StripeCore~Analytics.
StripePayments~StripePayments~Internal uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→36 StripePayments~StripePayments~Internal uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
9 pairs of types, where a type in StripePayments~StripePayments~Internal uses a type in StripeCore~StripeCore~API Bindings.
StripePayments~StripePayments~Internal uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePayments~StripePayments~Internal, while a change to StripePayments~StripePayments~Internal can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeIdentity~StripeIdentity~NativeComponents uses StripeIdentity~StripeIdentity~WebWrapper, so a change to StripeIdentity~StripeIdentity~WebWrapper can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeIdentity~StripeIdentity~WebWrapper.
Position
Below the diagonal: StripeIdentity~StripeIdentity~NativeComponents uses a module listed above it, which is the healthy direction.
StripeIdentity~StripeIdentity~NativeComponents uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripeIdentity~StripeIdentity~NativeComponents uses a module listed above it, which is the healthy direction.
StripeIdentity~StripeIdentity~NativeComponents uses StripeUICore~StripeUICore~Controls, so a change to StripeUICore~StripeUICore~Controls can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeUICore~StripeUICore~Controls.
Position
Below the diagonal: StripeIdentity~StripeIdentity~NativeComponents uses a module listed above it, which is the healthy direction.
StripeIdentity~StripeIdentity~NativeComponents uses StripePayments~StripePayments~Internal, so a change to StripePayments~StripePayments~Internal can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripePayments~StripePayments~Internal.
Position
Below the diagonal: StripeIdentity~StripeIdentity~NativeComponents uses a module listed above it, which is the healthy direction.
8→10 StripeIdentity~StripeIdentity~NativeComponents uses StripeIdentity~StripeIdentity~API Bindingspart of a loop✕
Connections
18 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeIdentity~StripeIdentity~API Bindings.
StripeIdentity~StripeIdentity~NativeComponents uses StripeIdentity~StripeIdentity~API Bindings, so a change to StripeIdentity~StripeIdentity~API Bindings can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeIdentity~StripeIdentity~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→11 StripeIdentity~StripeIdentity~NativeComponents uses StripeFinancialConnections~StripeFinancialConnections~Nativepart of a loop✕
Connections
3 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeFinancialConnections~StripeFinancialConnections~Native.
StripeIdentity~StripeIdentity~NativeComponents uses StripeFinancialConnections~StripeFinancialConnections~Native, so a change to StripeFinancialConnections~StripeFinancialConnections~Native can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeFinancialConnections~StripeFinancialConnections~Native.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→12 StripeIdentity~StripeIdentity~NativeComponents uses StripePaymentSheet~StripePaymentSheet~PaymentSheetpart of a loop✕
Connections
3 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet.
StripeIdentity~StripeIdentity~NativeComponents uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→13 StripeIdentity~StripeIdentity~NativeComponents uses repositorypart of a loop✕
Connections
17 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in repository.
StripeIdentity~StripeIdentity~NativeComponents uses repository, so a change to repository can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→16 StripeIdentity~StripeIdentity~NativeComponents uses StripePaymentSheet~StripePaymentSheet~Internalpart of a loop✕
Connections
2 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripePaymentSheet~StripePaymentSheet~Internal.
StripeIdentity~StripeIdentity~NativeComponents uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→17 StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~UIpart of a loop✕
Connections
3 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCore~StripeCore~UI.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→18 StripeIdentity~StripeIdentity~NativeComponents uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
30 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeIdentity~StripeIdentity~Categories. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeIdentity~StripeIdentity~NativeComponents uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→19 StripeIdentity~StripeIdentity~NativeComponents uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
9 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripePaymentSheet~StripePaymentSheet~Helpers.
StripeIdentity~StripeIdentity~NativeComponents uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→20 StripeIdentity~StripeIdentity~NativeComponents uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripePayments~StripePayments~API Bindings.
StripeIdentity~StripeIdentity~NativeComponents uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→24 StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
15 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCore~StripeCore~Helpers.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→26 StripeIdentity~StripeIdentity~NativeComponents uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
3 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeUICore~StripeUICore~Elements.
StripeIdentity~StripeIdentity~NativeComponents uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→27 StripeIdentity~StripeIdentity~NativeComponents uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
28 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeUICore~StripeUICore~Categories. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeIdentity~StripeIdentity~NativeComponents uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→28 StripeIdentity~StripeIdentity~NativeComponents uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeConnect~StripeConnect~Helpers.
StripeIdentity~StripeIdentity~NativeComponents uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→29 StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
8 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCore~StripeCore~Coder.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→30 StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
10 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCore~StripeCore~Analytics.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→31 StripeIdentity~StripeIdentity~NativeComponents uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
29 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCardScan~StripeCardScan~CardScan. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→33 StripeIdentity~StripeIdentity~NativeComponents uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
24 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→35 StripeIdentity~StripeIdentity~NativeComponents uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
10 pairs of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→36 StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~NativeComponents uses a type in StripeCore~StripeCore~API Bindings.
StripeIdentity~StripeIdentity~NativeComponents uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeIdentity~StripeIdentity~NativeComponents, while a change to StripeIdentity~StripeIdentity~NativeComponents can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripePayments~StripePayments~Helpers uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripePayments~StripePayments~Helpers uses a module listed above it, which is the healthy direction.
StripePayments~StripePayments~Helpers uses StripePayments~StripePayments~PaymentHandler, so a change to StripePayments~StripePayments~PaymentHandler can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripePayments~StripePayments~PaymentHandler.
Position
Below the diagonal: StripePayments~StripePayments~Helpers uses a module listed above it, which is the healthy direction.
StripePayments~StripePayments~Helpers uses StripePayments~StripePayments~Internal, so a change to StripePayments~StripePayments~Internal can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripePayments~StripePayments~Internal.
Position
Below the diagonal: StripePayments~StripePayments~Helpers uses a module listed above it, which is the healthy direction.
9→20 StripePayments~StripePayments~Helpers uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
10 pairs of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripePayments~StripePayments~API Bindings.
StripePayments~StripePayments~Helpers uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→21 StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
4 pairs of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeCore~StripeCore~Connections Bindings.
StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→24 StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
2 pairs of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeCore~StripeCore~Helpers.
StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→25 StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeCore~StripeCore~Categories.
StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→29 StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
3 pairs of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeCore~StripeCore~Coder.
StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→30 StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeCore~StripeCore~Analytics.
StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→36 StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
4 pairs of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeCore~StripeCore~API Bindings.
StripePayments~StripePayments~Helpers uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→40 StripePayments~StripePayments~Helpers uses StripeApplePay~StripeApplePay~ApplePayContextpart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~Helpers uses a type in StripeApplePay~StripeApplePay~ApplePayContext.
StripePayments~StripePayments~Helpers uses StripeApplePay~StripeApplePay~ApplePayContext, so a change to StripeApplePay~StripeApplePay~ApplePayContext can break StripePayments~StripePayments~Helpers, while a change to StripePayments~StripePayments~Helpers can't break StripeApplePay~StripeApplePay~ApplePayContext.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeIdentity~StripeIdentity~API Bindings uses StripeIdentity~StripeIdentity~NativeComponents, so a change to StripeIdentity~StripeIdentity~NativeComponents can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeIdentity~StripeIdentity~NativeComponents.
Position
Below the diagonal: StripeIdentity~StripeIdentity~API Bindings uses a module listed above it, which is the healthy direction.
10→13 StripeIdentity~StripeIdentity~API Bindings uses repositorypart of a loop✕
Connections
2 pairs of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in repository.
StripeIdentity~StripeIdentity~API Bindings uses repository, so a change to repository can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→18 StripeIdentity~StripeIdentity~API Bindings uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripeIdentity~StripeIdentity~Categories.
StripeIdentity~StripeIdentity~API Bindings uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→19 StripeIdentity~StripeIdentity~API Bindings uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripePaymentSheet~StripePaymentSheet~Helpers.
StripeIdentity~StripeIdentity~API Bindings uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→24 StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
4 pairs of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripeCore~StripeCore~Helpers.
StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripeCore~StripeCore~Categories.
StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→29 StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
6 pairs of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripeCore~StripeCore~Coder.
StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→31 StripeIdentity~StripeIdentity~API Bindings uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
2 pairs of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeIdentity~StripeIdentity~API Bindings uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→36 StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~API Bindings uses a type in StripeCore~StripeCore~API Bindings.
StripeIdentity~StripeIdentity~API Bindings uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeIdentity~StripeIdentity~API Bindings, while a change to StripeIdentity~StripeIdentity~API Bindings can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeFinancialConnections~StripeFinancialConnections~Common.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeFinancialConnections~StripeFinancialConnections~Common, so a change to StripeFinancialConnections~StripeFinancialConnections~Common can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeFinancialConnections~StripeFinancialConnections~Common.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections~Native uses a module listed above it, which is the healthy direction.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeUICore~StripeUICore~Controls, so a change to StripeUICore~StripeUICore~Controls can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeUICore~StripeUICore~Controls.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections~Native uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeIdentity~StripeIdentity~API Bindings.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeIdentity~StripeIdentity~API Bindings, so a change to StripeIdentity~StripeIdentity~API Bindings can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeIdentity~StripeIdentity~API Bindings.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections~Native uses a module listed above it, which is the healthy direction.
11→13 StripeFinancialConnections~StripeFinancialConnections~Native uses repositorypart of a loop✕
Connections
16 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in repository.
StripeFinancialConnections~StripeFinancialConnections~Native uses repository, so a change to repository can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→14 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeFinancialConnections~StripeFinancialConnections~Helperspart of a loop✕
Connections
87 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→15 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeFinancialConnections~StripeFinancialConnections~API Bindingspart of a loop✕
Connections
212 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeFinancialConnections~StripeFinancialConnections~API Bindings, so a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeFinancialConnections~StripeFinancialConnections~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 StripeFinancialConnections~StripeFinancialConnections~Native uses StripePaymentSheet~StripePaymentSheet~Internalpart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripePaymentSheet~StripePaymentSheet~Internal.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→17 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~UIpart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCore~StripeCore~UI.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
4 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeIdentity~StripeIdentity~Categories.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 StripeFinancialConnections~StripeFinancialConnections~Native uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
7 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripePaymentSheet~StripePaymentSheet~Helpers.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
18 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCore~StripeCore~Connections Bindings.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→24 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
35 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCore~StripeCore~Helpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→25 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCore~StripeCore~Categories.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→26 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeUICore~StripeUICore~Elements.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→27 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
28 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeUICore~StripeUICore~Categories. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→30 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCore~StripeCore~Analytics.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→31 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
8 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→33 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
9 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→35 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→36 StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Native uses a type in StripeCore~StripeCore~API Bindings.
StripeFinancialConnections~StripeFinancialConnections~Native uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeFinancialConnections~StripeFinancialConnections~Native, while a change to StripeFinancialConnections~StripeFinancialConnections~Native can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripePaymentSheet~StripePaymentSheet~Analytics. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePaymentSheet~StripePaymentSheet~Analytics, so a change to StripePaymentSheet~StripePaymentSheet~Analytics can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePaymentSheet~StripePaymentSheet~Analytics.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePayments~StripePayments~PaymentHandler, so a change to StripePayments~StripePayments~PaymentHandler can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePayments~StripePayments~PaymentHandler.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeUICore~StripeUICore~Controls, so a change to StripeUICore~StripeUICore~Controls can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeUICore~StripeUICore~Controls.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePayments~StripePayments~Internal, so a change to StripePayments~StripePayments~Internal can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePayments~StripePayments~Internal.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePayments~StripePayments~Helpers, so a change to StripePayments~StripePayments~Helpers can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePayments~StripePayments~Helpers.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeFinancialConnections~StripeFinancialConnections~Native.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeFinancialConnections~StripeFinancialConnections~Native, so a change to StripeFinancialConnections~StripeFinancialConnections~Native can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeFinancialConnections~StripeFinancialConnections~Native.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a module listed above it, which is the healthy direction.
12→13 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses repositorypart of a loop✕
Connections
36 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses repository, so a change to repository can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→14 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeFinancialConnections~StripeFinancialConnections~Helperspart of a loop✕
Connections
26 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePaymentSheet~StripePaymentSheet~Internalpart of a loop✕
Connections
91 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripePaymentSheet~StripePaymentSheet~Internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→17 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~UIpart of a loop✕
Connections
9 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCore~StripeCore~UI.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→18 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
19 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeIdentity~StripeIdentity~Categories.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
40 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripePaymentSheet~StripePaymentSheet~Helpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→20 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
126 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripePayments~StripePayments~API Bindings. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→21 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
9 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCore~StripeCore~Connections Bindings.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→25 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
4 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCore~StripeCore~Categories.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→26 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
113 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeUICore~StripeUICore~Elements. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→27 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
47 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeUICore~StripeUICore~Categories. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
15 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCore~StripeCore~Coder.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→30 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
27 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCore~StripeCore~Analytics. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→31 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
22 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCardScan~StripeCardScan~CardScan.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→33 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
7 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→35 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
25 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→36 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
18 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeCore~StripeCore~API Bindings.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→38 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
14 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeApplePay~StripeApplePay~Extensions.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→40 StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeApplePay~StripeApplePay~ApplePayContextpart of a loop✕
Connections
5 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet uses a type in StripeApplePay~StripeApplePay~ApplePayContext.
StripePaymentSheet~StripePaymentSheet~PaymentSheet uses StripeApplePay~StripeApplePay~ApplePayContext, so a change to StripeApplePay~StripeApplePay~ApplePayContext can break StripePaymentSheet~StripePaymentSheet~PaymentSheet, while a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can't break StripeApplePay~StripeApplePay~ApplePayContext.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
repository uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break repository, while a change to repository can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
13→18 repository uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in repository uses a type in StripeIdentity~StripeIdentity~Categories.
repository uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break repository, while a change to repository can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→20 repository uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
3 pairs of types, where a type in repository uses a type in StripePayments~StripePayments~API Bindings.
repository uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break repository, while a change to repository can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses repository, so a change to repository can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break repository.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections~Helpers uses a module listed above it, which is the healthy direction.
14→16 StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripePaymentSheet~StripePaymentSheet~Internalpart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Helpers uses a type in StripePaymentSheet~StripePaymentSheet~Internal.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→17 StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeCore~StripeCore~UIpart of a loop✕
Connections
3 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Helpers uses a type in StripeCore~StripeCore~UI.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Helpers uses a type in StripeIdentity~StripeIdentity~Categories.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→24 StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Helpers uses a type in StripeCore~StripeCore~Helpers.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→27 StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Helpers uses a type in StripeUICore~StripeUICore~Categories.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→28 StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~Helpers uses a type in StripeConnect~StripeConnect~Helpers.
StripeFinancialConnections~StripeFinancialConnections~Helpers uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeFinancialConnections~StripeFinancialConnections~Helpers, while a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a module listed above it, which is the healthy direction.
15→18 StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeIdentity~StripeIdentity~Categories.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→21 StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
7 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeCore~StripeCore~Connections Bindings.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→24 StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
4 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeCore~StripeCore~Helpers.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
75 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeCore~StripeCore~Coder. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→36 StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
5 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeCore~StripeCore~API Bindings.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→38 StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings uses a type in StripeApplePay~StripeApplePay~Extensions.
StripeFinancialConnections~StripeFinancialConnections~API Bindings uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripeFinancialConnections~StripeFinancialConnections~API Bindings, while a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripePaymentSheet~StripePaymentSheet~Internal uses StripePaymentSheet~StripePaymentSheet~Analytics, so a change to StripePaymentSheet~StripePaymentSheet~Analytics can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripePaymentSheet~StripePaymentSheet~Analytics.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Internal uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Internal uses StripePayments~StripePayments~PaymentHandler, so a change to StripePayments~StripePayments~PaymentHandler can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripePayments~StripePayments~PaymentHandler.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeUICore~StripeUICore~Controls, so a change to StripeUICore~StripeUICore~Controls can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeUICore~StripeUICore~Controls.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
75 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~Internal uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Internal uses repository, so a change to repository can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break repository.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeFinancialConnections~StripeFinancialConnections~API Bindings, so a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeFinancialConnections~StripeFinancialConnections~API Bindings.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Internal uses a module listed above it, which is the healthy direction.
16→17 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~UIpart of a loop✕
Connections
5 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~UI.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~UI.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→18 StripePaymentSheet~StripePaymentSheet~Internal uses StripeIdentity~StripeIdentity~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeIdentity~StripeIdentity~Categories.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeIdentity~StripeIdentity~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→19 StripePaymentSheet~StripePaymentSheet~Internal uses StripePaymentSheet~StripePaymentSheet~Helperspart of a loop✕
Connections
28 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripePaymentSheet~StripePaymentSheet~Helpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~Internal uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→20 StripePaymentSheet~StripePaymentSheet~Internal uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
25 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripePayments~StripePayments~API Bindings.
StripePaymentSheet~StripePaymentSheet~Internal uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→21 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~Connections Bindings.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→24 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~Helpers.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→25 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~Categories.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→26 StripePaymentSheet~StripePaymentSheet~Internal uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
38 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeUICore~StripeUICore~Elements. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→27 StripePaymentSheet~StripePaymentSheet~Internal uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
21 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeUICore~StripeUICore~Categories.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→28 StripePaymentSheet~StripePaymentSheet~Internal uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeConnect~StripeConnect~Helpers.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→29 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
45 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~Coder. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→30 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
4 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~Analytics.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→31 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
3 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCardScan~StripeCardScan~CardScan.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→33 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
6 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→35 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
16 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→36 StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
5 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeCore~StripeCore~API Bindings.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→38 StripePaymentSheet~StripePaymentSheet~Internal uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
3 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Internal uses a type in StripeApplePay~StripeApplePay~Extensions.
StripePaymentSheet~StripePaymentSheet~Internal uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripePaymentSheet~StripePaymentSheet~Internal, while a change to StripePaymentSheet~StripePaymentSheet~Internal can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCore~StripeCore~UI uses repository, so a change to repository can break StripeCore~StripeCore~UI, while a change to StripeCore~StripeCore~UI can't break repository.
Position
Below the diagonal: StripeCore~StripeCore~UI uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~UI uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeCore~StripeCore~UI, while a change to StripeCore~StripeCore~UI can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeCore~StripeCore~UI uses a module listed above it, which is the healthy direction.
17→25 StripeCore~StripeCore~UI uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~UI uses a type in StripeCore~StripeCore~Categories.
StripeCore~StripeCore~UI uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeCore~StripeCore~UI, while a change to StripeCore~StripeCore~UI can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→27 StripeCore~StripeCore~UI uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~UI uses a type in StripeUICore~StripeUICore~Categories.
StripeCore~StripeCore~UI uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeCore~StripeCore~UI, while a change to StripeCore~StripeCore~UI can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→28 StripeCore~StripeCore~UI uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~UI uses a type in StripeConnect~StripeConnect~Helpers.
StripeCore~StripeCore~UI uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeCore~StripeCore~UI, while a change to StripeCore~StripeCore~UI can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeIdentity~StripeIdentity~Categories uses repository, so a change to repository can break StripeIdentity~StripeIdentity~Categories, while a change to StripeIdentity~StripeIdentity~Categories can't break repository.
Position
Below the diagonal: StripeIdentity~StripeIdentity~Categories uses a module listed above it, which is the healthy direction.
StripeIdentity~StripeIdentity~Categories uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeIdentity~StripeIdentity~Categories, while a change to StripeIdentity~StripeIdentity~Categories can't break StripeCore~StripeCore~UI.
Position
Below the diagonal: StripeIdentity~StripeIdentity~Categories uses a module listed above it, which is the healthy direction.
18→31 StripeIdentity~StripeIdentity~Categories uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~Categories uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeIdentity~StripeIdentity~Categories uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeIdentity~StripeIdentity~Categories, while a change to StripeIdentity~StripeIdentity~Categories can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→33 StripeIdentity~StripeIdentity~Categories uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeIdentity~StripeIdentity~Categories uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripeIdentity~StripeIdentity~Categories uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeIdentity~StripeIdentity~Categories, while a change to StripeIdentity~StripeIdentity~Categories can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Helpers uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Helpers uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Helpers uses a module listed above it, which is the healthy direction.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripePaymentSheet~StripePaymentSheet~Helpers uses a module listed above it, which is the healthy direction.
19→20 StripePaymentSheet~StripePaymentSheet~Helpers uses StripePayments~StripePayments~API Bindingspart of a loop✕
Connections
8 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripePayments~StripePayments~API Bindings.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripePayments~StripePayments~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→24 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeCore~StripeCore~Helpers.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→26 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeUICore~StripeUICore~Elements.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→27 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeUICore~StripeUICore~Categories.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→29 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeCore~StripeCore~Coder.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→30 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeCore~StripeCore~Analytics.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→31 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeCardScan~StripeCardScan~CardScan.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→33 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→36 StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripePaymentSheet~StripePaymentSheet~Helpers uses a type in StripeCore~StripeCore~API Bindings.
StripePaymentSheet~StripePaymentSheet~Helpers uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePaymentSheet~StripePaymentSheet~Helpers, while a change to StripePaymentSheet~StripePaymentSheet~Helpers can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripePayments~StripePayments~API Bindings uses StripePayments~StripePayments~Internal, so a change to StripePayments~StripePayments~Internal can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripePayments~StripePayments~Internal.
Position
Below the diagonal: StripePayments~StripePayments~API Bindings uses a module listed above it, which is the healthy direction.
StripePayments~StripePayments~API Bindings uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripePayments~StripePayments~API Bindings uses a module listed above it, which is the healthy direction.
StripePayments~StripePayments~API Bindings uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripePayments~StripePayments~API Bindings uses a module listed above it, which is the healthy direction.
StripePayments~StripePayments~API Bindings uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripePayments~StripePayments~API Bindings uses a module listed above it, which is the healthy direction.
20→21 StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Connections Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeCore~StripeCore~Connections Bindings.
StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeCore~StripeCore~Connections Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→24 StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
13 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeCore~StripeCore~Helpers.
StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→26 StripePayments~StripePayments~API Bindings uses StripeUICore~StripeUICore~Elementspart of a loop✕
Connections
4 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeUICore~StripeUICore~Elements.
StripePayments~StripePayments~API Bindings uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeUICore~StripeUICore~Elements.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→28 StripePayments~StripePayments~API Bindings uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeConnect~StripeConnect~Helpers.
StripePayments~StripePayments~API Bindings uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→29 StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
3 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeCore~StripeCore~Coder.
StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→30 StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
13 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeCore~StripeCore~Analytics.
StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→36 StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
4 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeCore~StripeCore~API Bindings.
StripePayments~StripePayments~API Bindings uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→38 StripePayments~StripePayments~API Bindings uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
2 pairs of types, where a type in StripePayments~StripePayments~API Bindings uses a type in StripeApplePay~StripeApplePay~Extensions.
StripePayments~StripePayments~API Bindings uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripePayments~StripePayments~API Bindings, while a change to StripePayments~StripePayments~API Bindings can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCore~StripeCore~Connections Bindings uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeCore~StripeCore~Connections Bindings, while a change to StripeCore~StripeCore~Connections Bindings can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeCore~StripeCore~Connections Bindings uses a module listed above it, which is the healthy direction.
21→29 StripeCore~StripeCore~Connections Bindings uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
9 pairs of types, where a type in StripeCore~StripeCore~Connections Bindings uses a type in StripeCore~StripeCore~Coder.
StripeCore~StripeCore~Connections Bindings uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCore~StripeCore~Connections Bindings, while a change to StripeCore~StripeCore~Connections Bindings can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→36 StripeCore~StripeCore~Connections Bindings uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
3 pairs of types, where a type in StripeCore~StripeCore~Connections Bindings uses a type in StripeCore~StripeCore~API Bindings.
StripeCore~StripeCore~Connections Bindings uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeCore~StripeCore~Connections Bindings, while a change to StripeCore~StripeCore~Connections Bindings can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→38 StripeCore~StripeCore~Connections Bindings uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
2 pairs of types, where a type in StripeCore~StripeCore~Connections Bindings uses a type in StripeApplePay~StripeApplePay~Extensions.
StripeCore~StripeCore~Connections Bindings uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripeCore~StripeCore~Connections Bindings, while a change to StripeCore~StripeCore~Connections Bindings can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripeFinancialConnections~StripeFinancialConnections~Common.
StripeFinancialConnections~StripeFinancialConnections uses StripeFinancialConnections~StripeFinancialConnections~Common, so a change to StripeFinancialConnections~StripeFinancialConnections~Common can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeFinancialConnections~StripeFinancialConnections~Common.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
StripeFinancialConnections~StripeFinancialConnections uses StripeIdentity~StripeIdentity~API Bindings, so a change to StripeIdentity~StripeIdentity~API Bindings can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeIdentity~StripeIdentity~API Bindings.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripePaymentSheet~StripePaymentSheet~PaymentSheet.
StripeFinancialConnections~StripeFinancialConnections uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripeFinancialConnections~StripeFinancialConnections uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
StripeFinancialConnections~StripeFinancialConnections uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeCore~StripeCore~UI.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
StripeFinancialConnections~StripeFinancialConnections uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeCore~StripeCore~Connections Bindings.
Position
Below the diagonal: StripeFinancialConnections~StripeFinancialConnections uses a module listed above it, which is the healthy direction.
22→23 StripeFinancialConnections~StripeFinancialConnections uses StripeConnect~StripeConnect~Internalpart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripeConnect~StripeConnect~Internal.
StripeFinancialConnections~StripeFinancialConnections uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeConnect~StripeConnect~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→25 StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripeCore~StripeCore~Categories.
StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→30 StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
1 pair of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripeCore~StripeCore~Analytics.
StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→36 StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripeFinancialConnections~StripeFinancialConnections uses a type in StripeCore~StripeCore~API Bindings.
StripeFinancialConnections~StripeFinancialConnections uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeFinancialConnections~StripeFinancialConnections, while a change to StripeFinancialConnections~StripeFinancialConnections can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeConnect~StripeConnect~Internal uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeConnect~StripeConnect~Internal uses a module listed above it, which is the healthy direction.
StripeConnect~StripeConnect~Internal uses repository, so a change to repository can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break repository.
Position
Below the diagonal: StripeConnect~StripeConnect~Internal uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeFinancialConnections~StripeFinancialConnections~API Bindings.
StripeConnect~StripeConnect~Internal uses StripeFinancialConnections~StripeFinancialConnections~API Bindings, so a change to StripeFinancialConnections~StripeFinancialConnections~API Bindings can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeFinancialConnections~StripeFinancialConnections~API Bindings.
Position
Below the diagonal: StripeConnect~StripeConnect~Internal uses a module listed above it, which is the healthy direction.
StripeConnect~StripeConnect~Internal uses StripeFinancialConnections~StripeFinancialConnections, so a change to StripeFinancialConnections~StripeFinancialConnections can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeFinancialConnections~StripeFinancialConnections.
Position
Below the diagonal: StripeConnect~StripeConnect~Internal uses a module listed above it, which is the healthy direction.
23→24 StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Helperspart of a loop✕
Connections
17 pairs of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCore~StripeCore~Helpers.
StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCore~StripeCore~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→25 StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
1 pair of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCore~StripeCore~Categories.
StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→27 StripeConnect~StripeConnect~Internal uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
6 pairs of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeUICore~StripeUICore~Categories.
StripeConnect~StripeConnect~Internal uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→28 StripeConnect~StripeConnect~Internal uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
6 pairs of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeConnect~StripeConnect~Helpers.
StripeConnect~StripeConnect~Internal uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
9 pairs of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCore~StripeCore~Coder.
StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→30 StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
5 pairs of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCore~StripeCore~Analytics.
StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→31 StripeConnect~StripeConnect~Internal uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
1 pair of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeConnect~StripeConnect~Internal uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→35 StripeConnect~StripeConnect~Internal uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
1 pair of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeConnect~StripeConnect~Internal uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→36 StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
1 pair of types, where a type in StripeConnect~StripeConnect~Internal uses a type in StripeCore~StripeCore~API Bindings.
StripeConnect~StripeConnect~Internal uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeConnect~StripeConnect~Internal, while a change to StripeConnect~StripeConnect~Internal can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCore~StripeCore~Helpers uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripeCore~StripeCore~Helpers, while a change to StripeCore~StripeCore~Helpers can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripeCore~StripeCore~Helpers uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Helpers uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCore~StripeCore~Helpers, while a change to StripeCore~StripeCore~Helpers can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCore~StripeCore~Helpers uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Helpers uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripeCore~StripeCore~Helpers, while a change to StripeCore~StripeCore~Helpers can't break StripeConnect~StripeConnect~Internal.
Position
Below the diagonal: StripeCore~StripeCore~Helpers uses a module listed above it, which is the healthy direction.
24→25 StripeCore~StripeCore~Helpers uses StripeCore~StripeCore~Categoriespart of a loop✕
Connections
3 pairs of types, where a type in StripeCore~StripeCore~Helpers uses a type in StripeCore~StripeCore~Categories.
StripeCore~StripeCore~Helpers uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeCore~StripeCore~Helpers, while a change to StripeCore~StripeCore~Helpers can't break StripeCore~StripeCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→28 StripeCore~StripeCore~Helpers uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~Helpers uses a type in StripeConnect~StripeConnect~Helpers.
StripeCore~StripeCore~Helpers uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeCore~StripeCore~Helpers, while a change to StripeCore~StripeCore~Helpers can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→29 StripeCore~StripeCore~Helpers uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~Helpers uses a type in StripeCore~StripeCore~Coder.
StripeCore~StripeCore~Helpers uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCore~StripeCore~Helpers, while a change to StripeCore~StripeCore~Helpers can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCore~StripeCore~Categories uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeCore~StripeCore~Categories, while a change to StripeCore~StripeCore~Categories can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~Categories uses a module listed above it, which is the healthy direction.
25→28 StripeCore~StripeCore~Categories uses StripeConnect~StripeConnect~Helperspart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~Categories uses a type in StripeConnect~StripeConnect~Helpers.
StripeCore~StripeCore~Categories uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeCore~StripeCore~Categories, while a change to StripeCore~StripeCore~Categories can't break StripeConnect~StripeConnect~Helpers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→30 StripeCore~StripeCore~Categories uses StripeCore~StripeCore~Analyticspart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~Categories uses a type in StripeCore~StripeCore~Analytics.
StripeCore~StripeCore~Categories uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeCore~StripeCore~Categories, while a change to StripeCore~StripeCore~Categories can't break StripeCore~StripeCore~Analytics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→31 StripeCore~StripeCore~Categories uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~Categories uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeCore~StripeCore~Categories uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeCore~StripeCore~Categories, while a change to StripeCore~StripeCore~Categories can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeUICore~StripeUICore~Elements uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses repository, so a change to repository can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break repository.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCore~StripeCore~UI.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCore~StripeCore~Connections Bindings.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Elements uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCore~StripeCore~Categories.
Position
Below the diagonal: StripeUICore~StripeUICore~Elements uses a module listed above it, which is the healthy direction.
26→27 StripeUICore~StripeUICore~Elements uses StripeUICore~StripeUICore~Categoriespart of a loop✕
Connections
14 pairs of types, where a type in StripeUICore~StripeUICore~Elements uses a type in StripeUICore~StripeUICore~Categories.
StripeUICore~StripeUICore~Elements uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeUICore~StripeUICore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→29 StripeUICore~StripeUICore~Elements uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
2 pairs of types, where a type in StripeUICore~StripeUICore~Elements uses a type in StripeCore~StripeCore~Coder.
StripeUICore~StripeUICore~Elements uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→31 StripeUICore~StripeUICore~Elements uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
4 pairs of types, where a type in StripeUICore~StripeUICore~Elements uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeUICore~StripeUICore~Elements uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→33 StripeUICore~StripeUICore~Elements uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
2 pairs of types, where a type in StripeUICore~StripeUICore~Elements uses a type in StripeCameraCore~StripeCameraCore~Categories.
StripeUICore~StripeUICore~Elements uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→35 StripeUICore~StripeUICore~Elements uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
4 pairs of types, where a type in StripeUICore~StripeUICore~Elements uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeUICore~StripeUICore~Elements uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeUICore~StripeUICore~Elements, while a change to StripeUICore~StripeUICore~Elements can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeUICore~StripeUICore~Categories uses repository, so a change to repository can break StripeUICore~StripeUICore~Categories, while a change to StripeUICore~StripeUICore~Categories can't break repository.
Position
Below the diagonal: StripeUICore~StripeUICore~Categories uses a module listed above it, which is the healthy direction.
StripeUICore~StripeUICore~Categories uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripeUICore~StripeUICore~Categories, while a change to StripeUICore~StripeUICore~Categories can't break StripeUICore~StripeUICore~Elements.
Position
Below the diagonal: StripeUICore~StripeUICore~Categories uses a module listed above it, which is the healthy direction.
StripeConnect~StripeConnect~Helpers uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeConnect~StripeConnect~Helpers, while a change to StripeConnect~StripeConnect~Helpers can't break StripeUICore~StripeUICore~Categories.
Position
Below the diagonal: StripeConnect~StripeConnect~Helpers uses a module listed above it, which is the healthy direction.
28→29 StripeConnect~StripeConnect~Helpers uses StripeCore~StripeCore~Coderpart of a loop✕
Connections
1 pair of types, where a type in StripeConnect~StripeConnect~Helpers uses a type in StripeCore~StripeCore~Coder.
StripeConnect~StripeConnect~Helpers uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeConnect~StripeConnect~Helpers, while a change to StripeConnect~StripeConnect~Helpers can't break StripeCore~StripeCore~Coder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→36 StripeConnect~StripeConnect~Helpers uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
1 pair of types, where a type in StripeConnect~StripeConnect~Helpers uses a type in StripeCore~StripeCore~API Bindings.
StripeConnect~StripeConnect~Helpers uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeConnect~StripeConnect~Helpers, while a change to StripeConnect~StripeConnect~Helpers can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCore~StripeCore~Coder uses StripeIdentity~StripeIdentity~NativeComponents, so a change to StripeIdentity~StripeIdentity~NativeComponents can break StripeCore~StripeCore~Coder, while a change to StripeCore~StripeCore~Coder can't break StripeIdentity~StripeIdentity~NativeComponents.
Position
Below the diagonal: StripeCore~StripeCore~Coder uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Coder uses StripeIdentity~StripeIdentity~API Bindings, so a change to StripeIdentity~StripeIdentity~API Bindings can break StripeCore~StripeCore~Coder, while a change to StripeCore~StripeCore~Coder can't break StripeIdentity~StripeIdentity~API Bindings.
Position
Below the diagonal: StripeCore~StripeCore~Coder uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Coder uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripeCore~StripeCore~Coder, while a change to StripeCore~StripeCore~Coder can't break StripeConnect~StripeConnect~Internal.
Position
Below the diagonal: StripeCore~StripeCore~Coder uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Coder uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeCore~StripeCore~Coder, while a change to StripeCore~StripeCore~Coder can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~Coder uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Coder uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeCore~StripeCore~Coder, while a change to StripeCore~StripeCore~Coder can't break StripeConnect~StripeConnect~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~Coder uses a module listed above it, which is the healthy direction.
29→31 StripeCore~StripeCore~Coder uses StripeCardScan~StripeCardScan~CardScanpart of a loop✕
Connections
6 pairs of types, where a type in StripeCore~StripeCore~Coder uses a type in StripeCardScan~StripeCardScan~CardScan.
StripeCore~StripeCore~Coder uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeCore~StripeCore~Coder, while a change to StripeCore~StripeCore~Coder can't break StripeCardScan~StripeCardScan~CardScan.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCore~StripeCore~Analytics uses StripePaymentSheet~StripePaymentSheet~Analytics, so a change to StripePaymentSheet~StripePaymentSheet~Analytics can break StripeCore~StripeCore~Analytics, while a change to StripeCore~StripeCore~Analytics can't break StripePaymentSheet~StripePaymentSheet~Analytics.
Position
Below the diagonal: StripeCore~StripeCore~Analytics uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Analytics uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCore~StripeCore~Analytics, while a change to StripeCore~StripeCore~Analytics can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCore~StripeCore~Analytics uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Analytics uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeCore~StripeCore~Analytics, while a change to StripeCore~StripeCore~Analytics can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeCore~StripeCore~Analytics uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Analytics uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeCore~StripeCore~Analytics, while a change to StripeCore~StripeCore~Analytics can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~Analytics uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~Analytics uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCore~StripeCore~Analytics, while a change to StripeCore~StripeCore~Analytics can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripeCore~StripeCore~Analytics uses a module listed above it, which is the healthy direction.
30→36 StripeCore~StripeCore~Analytics uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
3 pairs of types, where a type in StripeCore~StripeCore~Analytics uses a type in StripeCore~StripeCore~API Bindings.
StripeCore~StripeCore~Analytics uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeCore~StripeCore~Analytics, while a change to StripeCore~StripeCore~Analytics can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCardScan~StripeCardScan~CardScan uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardScan uses repository, so a change to repository can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break repository.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardScan uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardScan uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardScan uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardScan uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardScan uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripeCore~StripeCore~Analytics.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardScan uses a module listed above it, which is the healthy direction.
31→33 StripeCardScan~StripeCardScan~CardScan uses StripeCameraCore~StripeCameraCore~Categoriespart of a loop✕
Connections
26 pairs of types, where a type in StripeCardScan~StripeCardScan~CardScan uses a type in StripeCameraCore~StripeCameraCore~Categories. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeCardScan~StripeCardScan~CardScan uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→35 StripeCardScan~StripeCardScan~CardScan uses StripeCardScan~StripeCardScan~CardVerifypart of a loop✕
Connections
9 pairs of types, where a type in StripeCardScan~StripeCardScan~CardScan uses a type in StripeCardScan~StripeCardScan~CardVerify.
StripeCardScan~StripeCardScan~CardScan uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeCardScan~StripeCardScan~CardScan, while a change to StripeCardScan~StripeCardScan~CardScan can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses repository, so a change to repository can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break repository.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeCore~StripeCore~UI.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeUICore~StripeUICore~Categories.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
32 pairs of types, where a type in StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a type in StripeCore~StripeCore~Coder. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeCore~StripeCore~Analytics.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a module listed above it, which is the healthy direction.
32→34 StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCryptoOnramp~StripeCryptoOnramp~Componentspart of a loop✕
Connections
8 pairs of types, where a type in StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a type in StripeCryptoOnramp~StripeCryptoOnramp~Components.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCryptoOnramp~StripeCryptoOnramp~Components, so a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeCryptoOnramp~StripeCryptoOnramp~Components.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→36 StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
2 pairs of types, where a type in StripeCryptoOnramp~StripeCryptoOnramp~Internal uses a type in StripeCore~StripeCore~API Bindings.
StripeCryptoOnramp~StripeCryptoOnramp~Internal uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeCryptoOnramp~StripeCryptoOnramp~Internal, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCameraCore~StripeCameraCore~Categories uses repository, so a change to repository can break StripeCameraCore~StripeCameraCore~Categories, while a change to StripeCameraCore~StripeCameraCore~Categories can't break repository.
Position
Below the diagonal: StripeCameraCore~StripeCameraCore~Categories uses a module listed above it, which is the healthy direction.
StripeCameraCore~StripeCameraCore~Categories uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCameraCore~StripeCameraCore~Categories, while a change to StripeCameraCore~StripeCameraCore~Categories can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCameraCore~StripeCameraCore~Categories uses a module listed above it, which is the healthy direction.
StripeCameraCore~StripeCameraCore~Categories uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeCameraCore~StripeCameraCore~Categories, while a change to StripeCameraCore~StripeCameraCore~Categories can't break StripeCardScan~StripeCardScan~CardScan.
Position
Below the diagonal: StripeCameraCore~StripeCameraCore~Categories uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripePayments~StripePayments~PaymentHandler, so a change to StripePayments~StripePayments~PaymentHandler can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripePayments~StripePayments~PaymentHandler.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripeUICore~StripeUICore~Elements.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeCryptoOnramp~StripeCryptoOnramp~Internal, so a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripeCryptoOnramp~StripeCryptoOnramp~Internal.
Position
Below the diagonal: StripeCryptoOnramp~StripeCryptoOnramp~Components uses a module listed above it, which is the healthy direction.
34→36 StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeCore~StripeCore~API Bindingspart of a loop✕
Connections
3 pairs of types, where a type in StripeCryptoOnramp~StripeCryptoOnramp~Components uses a type in StripeCore~StripeCore~API Bindings.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripeCore~StripeCore~API Bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→38 StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
2 pairs of types, where a type in StripeCryptoOnramp~StripeCryptoOnramp~Components uses a type in StripeApplePay~StripeApplePay~Extensions.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→40 StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeApplePay~StripeApplePay~ApplePayContextpart of a loop✕
Connections
2 pairs of types, where a type in StripeCryptoOnramp~StripeCryptoOnramp~Components uses a type in StripeApplePay~StripeApplePay~ApplePayContext.
StripeCryptoOnramp~StripeCryptoOnramp~Components uses StripeApplePay~StripeApplePay~ApplePayContext, so a change to StripeApplePay~StripeApplePay~ApplePayContext can break StripeCryptoOnramp~StripeCryptoOnramp~Components, while a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can't break StripeApplePay~StripeApplePay~ApplePayContext.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeCardScan~StripeCardScan~CardVerify uses StripePayments~StripePayments~Captcha, so a change to StripePayments~StripePayments~Captcha can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripePayments~StripePayments~Captcha.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses repository, so a change to repository can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break repository.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeConnect~StripeConnect~Helpers.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeCore~StripeCore~Analytics.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in StripeCardScan~StripeCardScan~CardVerify uses a type in StripeCardScan~StripeCardScan~CardScan. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripeCardScan~StripeCardScan~CardVerify uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeCardScan~StripeCardScan~CardScan.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCardScan~StripeCardScan~CardVerify uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripeCardScan~StripeCardScan~CardVerify, while a change to StripeCardScan~StripeCardScan~CardVerify can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Below the diagonal: StripeCardScan~StripeCardScan~CardVerify uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses repository, so a change to repository can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break repository.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeIdentity~StripeIdentity~Categories, so a change to StripeIdentity~StripeIdentity~Categories can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeIdentity~StripeIdentity~Categories.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeConnect~StripeConnect~Internal, so a change to StripeConnect~StripeConnect~Internal can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeConnect~StripeConnect~Internal.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCore~StripeCore~Categories.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeConnect~StripeConnect~Helpers, so a change to StripeConnect~StripeConnect~Helpers can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeConnect~StripeConnect~Helpers.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCore~StripeCore~Analytics.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCryptoOnramp~StripeCryptoOnramp~Internal, so a change to StripeCryptoOnramp~StripeCryptoOnramp~Internal can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCryptoOnramp~StripeCryptoOnramp~Internal.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCryptoOnramp~StripeCryptoOnramp~Components, so a change to StripeCryptoOnramp~StripeCryptoOnramp~Components can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCryptoOnramp~StripeCryptoOnramp~Components.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
StripeCore~StripeCore~API Bindings uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Below the diagonal: StripeCore~StripeCore~API Bindings uses a module listed above it, which is the healthy direction.
36→38 StripeCore~StripeCore~API Bindings uses StripeApplePay~StripeApplePay~Extensionspart of a loop✕
Connections
1 pair of types, where a type in StripeCore~StripeCore~API Bindings uses a type in StripeApplePay~StripeApplePay~Extensions.
StripeCore~StripeCore~API Bindings uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripeCore~StripeCore~API Bindings, while a change to StripeCore~StripeCore~API Bindings can't break StripeApplePay~StripeApplePay~Extensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripePayments~StripePayments~Helpers, so a change to StripePayments~StripePayments~Helpers can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripePayments~StripePayments~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses repository, so a change to repository can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break repository.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in StripePaymentsUI~StripePaymentsUI~UI Components uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCore~StripeCore~UI.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCore~StripeCore~Connections Bindings.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCore~StripeCore~Helpers, so a change to StripeCore~StripeCore~Helpers can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCore~StripeCore~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeUICore~StripeUICore~Elements, so a change to StripeUICore~StripeUICore~Elements can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeUICore~StripeUICore~Elements.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeUICore~StripeUICore~Categories.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCardScan~StripeCardScan~CardScan.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~UI Components uses a module listed above it, which is the healthy direction.
37→39 StripePaymentsUI~StripePaymentsUI~UI Components uses StripePaymentsUI~StripePaymentsUI~Internalpart of a loop✕
Connections
26 pairs of types, where a type in StripePaymentsUI~StripePaymentsUI~UI Components uses a type in StripePaymentsUI~StripePaymentsUI~Internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
StripePaymentsUI~StripePaymentsUI~UI Components uses StripePaymentsUI~StripePaymentsUI~Internal, so a change to StripePaymentsUI~StripePaymentsUI~Internal can break StripePaymentsUI~StripePaymentsUI~UI Components, while a change to StripePaymentsUI~StripePaymentsUI~UI Components can't break StripePaymentsUI~StripePaymentsUI~Internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
StripeApplePay~StripeApplePay~Extensions uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeApplePay~StripeApplePay~Extensions, while a change to StripeApplePay~StripeApplePay~Extensions can't break StripeCore~StripeCore~API Bindings.
Position
Below the diagonal: StripeApplePay~StripeApplePay~Extensions uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripePayments~StripePayments~Helpers, so a change to StripePayments~StripePayments~Helpers can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripePayments~StripePayments~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses repository, so a change to repository can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break repository.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in StripePaymentsUI~StripePaymentsUI~Internal uses a type in StripeFinancialConnections~StripeFinancialConnections~Helpers.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeFinancialConnections~StripeFinancialConnections~Helpers, so a change to StripeFinancialConnections~StripeFinancialConnections~Helpers can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeFinancialConnections~StripeFinancialConnections~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCore~StripeCore~UI, so a change to StripeCore~StripeCore~UI can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCore~StripeCore~UI.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripePaymentSheet~StripePaymentSheet~Helpers, so a change to StripePaymentSheet~StripePaymentSheet~Helpers can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripePaymentSheet~StripePaymentSheet~Helpers.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripePayments~StripePayments~API Bindings, so a change to StripePayments~StripePayments~API Bindings can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripePayments~StripePayments~API Bindings.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCore~StripeCore~Connections Bindings, so a change to StripeCore~StripeCore~Connections Bindings can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCore~StripeCore~Connections Bindings.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCore~StripeCore~Categories, so a change to StripeCore~StripeCore~Categories can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCore~StripeCore~Categories.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeUICore~StripeUICore~Categories.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCore~StripeCore~Coder, so a change to StripeCore~StripeCore~Coder can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCore~StripeCore~Coder.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCardScan~StripeCardScan~CardScan, so a change to StripeCardScan~StripeCardScan~CardScan can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCardScan~StripeCardScan~CardScan.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCameraCore~StripeCameraCore~Categories, so a change to StripeCameraCore~StripeCameraCore~Categories can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCameraCore~StripeCameraCore~Categories.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripeCardScan~StripeCardScan~CardVerify, so a change to StripeCardScan~StripeCardScan~CardVerify can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripeCardScan~StripeCardScan~CardVerify.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripePaymentsUI~StripePaymentsUI~Internal uses StripePaymentsUI~StripePaymentsUI~UI Components, so a change to StripePaymentsUI~StripePaymentsUI~UI Components can break StripePaymentsUI~StripePaymentsUI~Internal, while a change to StripePaymentsUI~StripePaymentsUI~Internal can't break StripePaymentsUI~StripePaymentsUI~UI Components.
Position
Below the diagonal: StripePaymentsUI~StripePaymentsUI~Internal uses a module listed above it, which is the healthy direction.
StripeApplePay~StripeApplePay~ApplePayContext uses StripePaymentSheet~StripePaymentSheet~PaymentSheet, so a change to StripePaymentSheet~StripePaymentSheet~PaymentSheet can break StripeApplePay~StripeApplePay~ApplePayContext, while a change to StripeApplePay~StripeApplePay~ApplePayContext can't break StripePaymentSheet~StripePaymentSheet~PaymentSheet.
Position
Below the diagonal: StripeApplePay~StripeApplePay~ApplePayContext uses a module listed above it, which is the healthy direction.
StripeApplePay~StripeApplePay~ApplePayContext uses StripePaymentSheet~StripePaymentSheet~Internal, so a change to StripePaymentSheet~StripePaymentSheet~Internal can break StripeApplePay~StripeApplePay~ApplePayContext, while a change to StripeApplePay~StripeApplePay~ApplePayContext can't break StripePaymentSheet~StripePaymentSheet~Internal.
Position
Below the diagonal: StripeApplePay~StripeApplePay~ApplePayContext uses a module listed above it, which is the healthy direction.
StripeApplePay~StripeApplePay~ApplePayContext uses StripeUICore~StripeUICore~Categories, so a change to StripeUICore~StripeUICore~Categories can break StripeApplePay~StripeApplePay~ApplePayContext, while a change to StripeApplePay~StripeApplePay~ApplePayContext can't break StripeUICore~StripeUICore~Categories.
Position
Below the diagonal: StripeApplePay~StripeApplePay~ApplePayContext uses a module listed above it, which is the healthy direction.
StripeApplePay~StripeApplePay~ApplePayContext uses StripeCore~StripeCore~Analytics, so a change to StripeCore~StripeCore~Analytics can break StripeApplePay~StripeApplePay~ApplePayContext, while a change to StripeApplePay~StripeApplePay~ApplePayContext can't break StripeCore~StripeCore~Analytics.
Position
Below the diagonal: StripeApplePay~StripeApplePay~ApplePayContext uses a module listed above it, which is the healthy direction.
StripeApplePay~StripeApplePay~ApplePayContext uses StripeCore~StripeCore~API Bindings, so a change to StripeCore~StripeCore~API Bindings can break StripeApplePay~StripeApplePay~ApplePayContext, while a change to StripeApplePay~StripeApplePay~ApplePayContext can't break StripeCore~StripeCore~API Bindings.
Position
Below the diagonal: StripeApplePay~StripeApplePay~ApplePayContext uses a module listed above it, which is the healthy direction.
StripeApplePay~StripeApplePay~ApplePayContext uses StripeApplePay~StripeApplePay~Extensions, so a change to StripeApplePay~StripeApplePay~Extensions can break StripeApplePay~StripeApplePay~ApplePayContext, while a change to StripeApplePay~StripeApplePay~ApplePayContext can't break StripeApplePay~StripeApplePay~Extensions.
Position
Below the diagonal: StripeApplePay~StripeApplePay~ApplePayContext uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 55% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
18
High / Critical
A07:2025 — Authentication Failures
12
High / Critical
A03:2025 — Software Supply Chain Failures
10
High / Critical
A01:2025 — Broken Access Control
1
Medium
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 — 35
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 — 1637
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 — 282
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 21
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 49 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 49 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1931 of 1954 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (Stripe), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — 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 a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — 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 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — 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 on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Stripe/StripeiOSTests/Resources/MockFiles/paymentIntentResponse.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — 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. `Example/CryptoOnramp Example/CryptoOnramp Example/AttachWalletAddressView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/CheckoutSuccessView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/ComplianceIdentifiersEntryView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift`, … (+77 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.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
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.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — 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.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — 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 web-security 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 web-security controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X18 Disposal-pattern correctness — 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.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X21 Side-effecting pattern guard — 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.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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 — 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.
X30 Support guard that admits what it rejects — 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.
Repo exclusion declarations: 1 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
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.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
68 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was STPPaymentMethodType.makeImage at 71. A further 17 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 STPPaymentMethodType.displayName at 70 — they are counted neither in the figure above nor in this dimension's score. 11 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: StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodEnums.swift (STPPaymentMethodType.displayName at 70), StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift (STPPaymentMethodParams.init at 59), StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift (PaymentSheetFormFactory.makePaymentMethodForm at 39), StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/CryptoOnrampAnalyticsEvent.swift (CryptoOnrampAnalyticsEvent.eventName at 34), StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetError.swift (PaymentSheetError.debugDescription at 33), and 6 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.
+ 63 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with STPPaymentMethodType.makeImage (cyclomatic 71), STPPaymentHandler._handleAuthenticationForCurrentAction (cyclomatic 68). — 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 Cyclomatic Complexity from 6.4 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: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 114 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with STPPaymentHandler._handleAuthenticationForCurrentAction (cognitive 139), STPPaymentHandler._retrieveAndCheckIntentForCurrentAction (cognitive 108), STPPaymentCardTextField.recalculateSubviewLayout (cognitive 86). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 5.7 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.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 34 FileTooLong finding(s) in God Classes — start with STPPaymentHandler.swift, STPPaymentCardTextField.swift, NativeFlowController.swift. — One of this dimension's main actionable groups (34 warning-level).
Resolve the 31 TooManyMethods finding(s) in God Classes — start with STPAPIClient.swift, PaymentSheetFormFactory.swift, STPPaymentMethodParams.swift. — One of this dimension's main actionable groups (31 warning-level).
Resolve the 25 MethodTooLong finding(s) in God Classes — start with PaymentSheet+API.swift (2), STPPaymentHandler.swift (2), STPPaymentMethodEnums.swift (2). — One of this dimension's main actionable groups (25 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
388 duplicated block group(s) detected. 9.6 % of the production lines (23,716 of 246,301) are in a reported copy. A further 513 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 185 of the 901 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.
Edited copy of a member (10 corresponding lines) · ×24StripeUICore/StripeUICore/Source/Categories/UIView+StripeUICore.swift:28
Edited copy of a member (8 corresponding lines) · ×23StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:180
+ 207 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with PaymentSheetTestPlaygroundSettings.swift (3), PaymentSheet+ConfirmationTokens.swift (2), BottomSheetViewController.swift (2). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 25 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with RoundedTextField.swift (2), CustomerSavedPaymentMethodsCollectionViewController.swift (2), PaymentSheetTestPlaygroundSettings.swift (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 24 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with PaymentElement.swift (2), UIView+StripeUICore.swift, PMMEPromotionTextView.swift. — One of this dimension's main actionable groups (24 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.1 / 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.
21 production modules (SwiftPM+Xcode), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 1 module(s) off the main sequence, with abstractness counted on 16 of the 21 (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).
Unstable project StripePaymentSheet
Off the main sequence: StripeCore
What to do
Resolve the 1 Unstable project StripePaymentSheet finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 64 Low cohesion finding(s) in Cohesion (LCOM4) — start with SceneDelegate.swift (4), MainViewController.swift (2), View+WalletOwnershipVerification.swift. — One of this dimension's main actionable groups (64 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.2 / 10Adequategated by 3 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
15 skipped, 173 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3269 tests (1 harness-style project(s) excluded from the assertion penalty).
Test project verifies nothing: Extensions · ×3StripeConnect/StripeConnectTests/Internal/Extensions/URL+ExtensionTests.swift:12
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with TestJSONEncoder.swift, SPMTestUITests.swift. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with IntegrationTesterUITests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 142 No assertions finding(s) in Test Quality — start with ConnectComponentWebViewControllerTests.swift (13), AuthenticatedWebViewManagerTests.swift (7), ConnectOutboundSourceValidationTests.swift (7). — One of this dimension's main actionable groups (142 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
2 outdated direct SwiftPM dependencies, 1 pinning defect(s). 5 of 8 direct dependencies had their releases listed (0 naming no readable repository, 3 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 1 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.
Floating branch dependency: ohhttpstubs
Outdated: swift-custom-dump · ×2
What to do
Resolve the 1 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
REDACTED scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
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.
1 of 142 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 142 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 3 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, 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.
Banned license: colorize
What to do
Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 17 Hotspot finding(s) in Churn × Complexity Hotspots — start with PaymentOption+Images.swift, CheckoutElementsController+Confirm.swift, PaymentSheet+API.swift. — One of this dimension's main actionable groups (17 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.9 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
89 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift. Counted over 847 of the 1673 production source files in this repository: 825 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 · ×8
Further sole-owners (lower concentration)
What to do
Resolve the 8 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (8 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
233 deducted task-comment markers across 246301 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.
Resolve the 193 TodoComment finding(s) in Explicit Debt — start with PaymentSheetLPMConfirmFlowTests.swift (6), LinkController.swift (6), PaymentMethodType.swift (5). — One of this dimension's main actionable groups (193 warning-level).
Resolve the 38 HackComment finding(s) in Explicit Debt — start with PlaygroundController.swift (4), EmbeddedPaymentMethodsView.swift (3), SectionContainerView.swift (2). — One of this dimension's main actionable groups (38 warning-level).
Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with TestJSONEncoder.swift (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundTesters/IntegrationTester/IntegrationTester.xcodeproj/project.pbxproj:1
What to do
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.
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.
2 naming inconsistencies among 48 declarations measured against a convention their peers follow.
`tellUsAboutYourSourceOfFunds` spells `Us` where 15 names in the project spell it `US`StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/String+Localized.swift:90
`sanitizedExpirationDateFromOCRString` spells `OCR` where 34 names in the project spell it `Ocr`StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPStringUtils.swift:77
What to do
Resolve the 1 `tellUsAboutYourSourceOfFunds` spells `Us` where 15 names in the project… finding(s) in Naming Consistency — start with String+Localized.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `sanitizedExpirationDateFromOCRString` spells `OCR` where 34 names in… finding(s) in Naming Consistency — start with STPStringUtils.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
9 of 18 build units (Bundler, Xcode) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
12 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (6), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
18 finding(s): 0 critical, 6 high, 12 medium, 0 low. semgrep hit a parse error in 12 file(s) — `Example/PaymentSheet Example/PaymentSheetUITest/MockFiles/elements_sessions_paymentMethod_200.json`, `Stripe/StripeiOSTests/Resources/MockFiles/paymentIntentResponse.json`, `Stripe3DS2/Stripe3DS2/STDSChallengeResponse.h` (line 19, line 41, line 44, …), `Stripe3DS2/Stripe3DS2/include/STDSSwiftTryCatch.h` (line 32, line 37, line 41, …), `StripeCore/StripeCore/Source/Attestation/StripeAttest.swift` (lines 418–421), … (+7 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.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no REDACTED 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.
Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 82 file(s) — `Example/CryptoOnramp Example/CryptoOnramp Example/AttachWalletAddressView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/CheckoutSuccessView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/ComplianceIdentifiersEntryView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift`, `Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift`, … (+77 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
195 of 848 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift. Counted over 848 of the 1673 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 190 Orphaned file finding(s) in Knowledge Freshness — start with ErrorViewController.swift (2), Button.swift, InstitutionTableView.swift. — One of this dimension's main actionable groups (190 recommendation-level).
Resolve the 5 Orphaned knowledge finding(s) in Knowledge Freshness — start with RoundedTextField.swift, IdentityAnalyticsClient.swift, SheetViewController.swift. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 14 Change coupling finding(s) in Change Coupling — start with DocumentScanner.swift, STPPaymentIntent.swift, STPPaymentIntentConfirmParams.swift. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with HostViewController.swift. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with NetworkingLinkVerificationDataSource.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 16 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels5.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — REDACTED:7
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:139
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure4.8 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — REDACTED:2, Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:3
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — REDACTED:71
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:3
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — REDACTED:29
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.input-field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:87
`.method-title` moves (`transition: margin-left .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — stripe3ds2-support/doc/html/css/style.css:1, stripe3ds2-support/doc/html/css/scss/_object.scss:14
`.method-info` moves (`transition: height .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — stripe3ds2-support/doc/html/css/style.css:1, stripe3ds2-support/doc/html/css/scss/_object.scss:31
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ 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.
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.
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.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
stripe3ds2-support/Pods/iOSSnapshotTestCase/README.md links to `FBSnapshotTestCaseDemo/Scheme_FB_REFERENCE_IMAGE_DIR.png`, but `stripe3ds2-support/Pods/iOSSnapshotTestCase/FBSnapshotTestCaseDemo/Scheme_FB_REFERENCE_IMAGE_DIR.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — stripe3ds2-support/Pods/iOSSnapshotTestCase/README.md:57
What to do
Reconcile the README with reality: stripe3ds2-support/Pods/iOSSnapshotTestCase/README.md links to `FBSnapshotTestCaseDemo/Scheme_FB_REFERENCE_IMAGE_DIR.png`, but `stripe3ds2-support/Pods/iOSSnapshotTestCase/FBSnapshotTestCaseDemo/Scheme_FB_REFERENCE_IMAGE_DIR.png` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
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.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning9.5 / 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.
1 public type in `StripeConnect~StripeConnect~Internal` is marked as implementation by its own namespace, folder or name: `ConnectActivityIndicator` (StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:14, `Internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:14
1 public type in `StripeCryptoOnramp~StripeCryptoOnramp~Internal` is marked as implementation by its own namespace, folder or name: `StripeCryptoOnrampBundleLocator` (StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/StripeCryptoOnrampBundleLocator.swift:11, `Internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/StripeCryptoOnrampBundleLocator.swift:11
5 public types in `StripePaymentSheet~StripePaymentSheet~Internal` are marked as implementation by their own namespace, folder or name: `LinkPaymentMethodType` (StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/LinkPaymentMethodType.swift:13, `Internal`), `LinkRequestSurface` (StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/LinkRequestSurface.swift:10, `Internal`), `STPElementsSession` (StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:13, `Internal`), `VerifyKYCInfo` (StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCInfo.swift:11, `Internal`), `VerifyKYCResult` (StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCResult.swift:11, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/LinkPaymentMethodType.swift:13
10 public types in `StripePayments~StripePayments~Internal` are marked as implementation by their own namespace, folder or name: `APIRequest` (StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:19, `Internal`), `STPEmptyStripeResponse` (StripePayments/StripePayments/Source/Internal/API Bindings/STPEmptyStripeResponse.swift:13, `Internal`), `STPFormEncoder` (StripePayments/StripePayments/Source/Internal/API Bindings/STPFormEncoder.swift:11, `Internal`), `STPPaymentMethodListDeserializer` (StripePayments/StripePayments/Source/Internal/API Bindings/STPPaymentMethodListDeserializer.swift:12, `Internal`), `PaymentAnalytic` (StripePayments/StripePayments/Source/Internal/Analytics/STPAnalyticsClient+Payments.swift:310, `Internal`), `FinancialConnectionsSDKAvailability` (StripePayments/StripePayments/Source/Internal/Helpers/ConnectionsSDKAvailability.swift:13, `Internal`), `STPPaymentHandlerPollingStatus` (StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:19, `Internal`), `STPPaymentHandlerPollingResult` (StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:26, `Internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:19
12 public types in `StripePaymentsUI~StripePaymentsUI~Internal` are marked as implementation by their own namespace, folder or name: `CardBrandView` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/CardBrandView.swift:16, `Internal`), `STPCardCVCInputTextField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardCVCInputTextField.swift:14, `Internal`), `STPCardNumberInputTextField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextField.swift:14, `Internal`), `InputMode` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextField.swift:17, `Internal`), `STPPostalCodeInputTextField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPPostalCodeInputTextField.swift:13, `Internal`), `STPCountryPickerInputField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPCountryPickerInputField.swift:12, `Internal`), `STPGenericInputPickerFieldDataSource` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPGenericInputPickerField.swift:12, `Internal`), `STPGenericInputPickerField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPGenericInputPickerField.swift:26, `Internal`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/CardBrandView.swift:16
What to do
Hide `StripeConnect~StripeConnect~Internal` (`ConnectActivityIndicator`) (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 `StripeCryptoOnramp~StripeCryptoOnramp~Internal` (`StripeCryptoOnrampBundleLocator`) (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 `StripePaymentSheet~StripePaymentSheet~Internal` (`LinkPaymentMethodType`, `LinkRequestSurface`, `STPElementsSession`, `VerifyKYCInfo`, `VerifyKYCResult`) (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 `StripePayments~StripePayments~Internal` (`APIRequest`, `STPEmptyStripeResponse`, `STPFormEncoder`, `STPPaymentMethodListDeserializer`, `PaymentAnalytic`, `FinancialConnectionsSDKAvailability`, `STPPaymentHandlerPollingStatus`, `STPPaymentHandlerPollingResult`, and 2 more) (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 `StripePaymentsUI~StripePaymentsUI~Internal` (`CardBrandView`, `STPCardCVCInputTextField`, `STPCardNumberInputTextField`, `InputMode`, `STPPostalCodeInputTextField`, `STPCountryPickerInputField`, `STPGenericInputPickerFieldDataSource`, `STPGenericInputPickerField`, and 4 more) (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.
Do you agree with this assessment?
P2 · Observability6.1 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `Stripe`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · 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. — StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutSessionPoller.swift:25
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.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
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.
`rescue => e` 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. — REDACTED:45
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. (×3) — StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:166, StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:269, StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:297
`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) — StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/CustomPaymentMethod.swift:41, StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/ExternalPaymentMethod.swift:36, StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:229, …
Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 47 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 35 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 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 image/media element found in the parsed markup — AC1 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no class or module declares an abstract method
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed 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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rb, .swift source were not judged.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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 — Swift suite
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
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
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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Ruby, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines), javascript (93 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 — X30 reached only 2% of this repository's production lines — swift (240,346 lines), objectivec (9,404 lines), c (3,964 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Orphaned knowledge StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/SheetViewController.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge StripeCardScan/StripeCardScan/Source/CardScan/UI/ScanBaseViewController.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Assertions commented out: test_codingOfDecimal StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:568— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: testExample Tests/installation_tests/size_test/SPMTestUITests/SPMTestUITests.swift:26— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name REDACTED:7— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:139— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<html> without a lang Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): testNull Testers/IntegrationTester/IntegrationTesterUITests/IntegrationTesterUITests.swift:47— Test method has an empty body — it asserts nothing and exercises no code.
Banned license: colorize — `colorize` 1.1.0 is published on rubygems.org under GPL-2.0, which this policy bans, and it is in the RUNTIME closure of this repository's Bundler manifests — so it is installed by everything that installs this repository, not just by its test harness. Replace it, or record an accepted exception.
TodoComment Testers/IntegrationTester/IntegrationTesterUITests/IntegrationTesterUIPMTests.swift:87— // TODO: AU BECS Debit is broken in testmode. — 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 StripeUICore/StripeUICoreTests/Unit/Elements/TextFieldElement+AddressFactoryTest.swift:201— // TODO(mludowise): These should get migrated to a shared StripeUICoreTestUtils target — 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 Stripe/StripeiOSTests/TextFieldElement+IBANTest.swift:117— // TODO(mludowise): These should get migrated to a shared StripeUICoreTestUtils target — 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 StripeUICore/StripeUICoreTests/Unit/Elements/TextFieldFormatterTest.swift:13— // TODO: Test that we don't get lagging characters (e.g. `###-##-` should always drop the last `-` when formatted — 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 StripeUICore/StripeUICore/Source/Elements/Form/FormView.swift:30— // TODO(iOS 26): Does this need to respect corner radius = nil? — 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 StripeUICore/StripeUICore/Source/Elements/Factories/IDNumberTextFieldConfiguration.swift:14— // TODO(mludowise|IDPROD-2596): Check if these are the formats needed to support IDV.
TodoComment StripeUICore/StripeUICore/Source/Controls/Button.swift:17— // TODO(ramont): move to `Configuration` — 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 StripeUICore/StripeUICore/Source/Controls/OneTimeCodeTextField.swift:384— // TODO(ramont): Move this to DigitView — 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 StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:951— // TODO: Figure out actual padding (not 14px) — 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 StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/CardBrandView.swift:19— // TODO(ramont): unify icon sizes. — 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 StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/CardBrandView.swift:45— /// TODO(ramont): remove baked-in padding and perform alignment in code. — 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 StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPPaymentCardTextFieldViewModel.swift:205— // TODO: BIN retrieval is broken if you don't use STPAPIClient.shared (https://jira.corp.stripe.com/browse/MOBILESDK-4322)
TodoComment StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldValidator.swift:73— // TODO: BIN retrieval is broken if you don't use STPAPIClient.shared (https://jira.corp.stripe.com/browse/MOBILESDK-4322)
TodoComment StripePayments/StripePayments/Source/Helpers/STPBINController.swift:271— // TODO: BIN retrieval is broken if you don't use STPAPIClient.shared (https://jira.corp.stripe.com/browse/MOBILESDK-4322)
TodoComment StripePayments/StripePayments/Source/Helpers/STPCardValidator.swift:451— // TODO: BIN retrieval is broken if you don't use STPAPIClient.shared (https://jira.corp.stripe.com/browse/MOBILESDK-4322)
TodoComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/TextField/TextFieldElement+Card.swift:191— // TODO: BIN retrieval is broken if you don't use STPAPIClient.shared (https://jira.corp.stripe.com/browse/MOBILESDK-4322)
TodoComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:256— // TODO: BIN retrieval is broken if you don't use STPAPIClient.shared (https://jira.corp.stripe.com/browse/MOBILESDK-4322)
TodoComment StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldValidator.swift:63— // TODO: We should be more specific here e.g. "Your card's expiration year is in the past." — 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 StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPBSBNumberValidator.swift:103— // TODO: This is broken for integrations that don't use STPAPIClient.shared — 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 StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1848— // TODO: Make currentAction an enum, stop optionally casting it — 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 StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2262— // TODO: Make currentAction an enum, stop optionally casting it — 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 StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2316— // TODO: Make currentAction an enum, stop optionally casting it — 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 StripePayments/StripePayments/Source/Internal/API Bindings/STPFormEncoder.swift:70— // TODO remove — 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 StripePayments/StripePayments/Source/Internal/API Bindings/STPFormEncoder.swift:78— // TODO remove — 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 StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1534— // TODO: Remove this logic when we stand up an endpoint to do this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
No assertions: testUpdateShouldCallTheCompletionBlock Stripe/StripeiOSTests/ConfirmButtonTests.swift:60— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testUpdateShouldCallTheCompletionBlockWhenAnimated Stripe/StripeiOSTests/ConfirmButtonTests.swift:75— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testPaymentSheetAnalyticEvents Stripe/StripeiOSTests/HostedSurfaceTest.swift:31— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCustomerSheetAnalyticEvents Stripe/StripeiOSTests/HostedSurfaceTest.swift:36— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEnqueueShouldDebounce Stripe/StripeiOSTests/OperationDebouncerTests.swift:19— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testExpiredCard Stripe/StripeiOSTests/STPCardFormViewTests.swift:272— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testIncorrectCVC Stripe/StripeiOSTests/STPCardFormViewTests.swift:276— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testIncorrectCardNumber Stripe/StripeiOSTests/STPCardFormViewTests.swift:280— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCardDeclined Stripe/StripeiOSTests/STPCardFormViewTests.swift:284— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessingError Stripe/StripeiOSTests/STPCardFormViewTests.swift:288— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTokenCreation_customer Stripe/StripeiOSTests/STPConnectAccountFunctionalTest.swift:47— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTokenCreation_company Stripe/StripeiOSTests/STPConnectAccountFunctionalTest.swift:53— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTokenCreation_empty_init Stripe/StripeiOSTests/STPConnectAccountFunctionalTest.swift:59— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCardIconMethods Stripe/StripeiOSTests/STPImageLibraryTests.swift:32— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testBrandImageForCardBrand Stripe/StripeiOSTests/STPImageLibraryTests.swift:67— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCVCImageForCardBrand Stripe/StripeiOSTests/STPImageLibraryTests.swift:132— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testErrorImageForCardBrand Stripe/StripeiOSTests/STPImageLibraryTests.swift:151— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testUpdatingObservers Stripe/StripeiOSTests/STPInputTextFieldValidatorTests.swift:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEnterForegroundDoesNotRefreshResourceKeyIfNotExpiring StripeIssuing/StripeIssuingTests/STPEphemeralKeyManagerTest.swift:137— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testThrottlingEnterForegroundRefreshes StripeIssuing/StripeIssuingTests/STPEphemeralKeyManagerTest.swift:144— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testForeignChallengeDocumentCannotCompleteChallenge StripePayments/StripePaymentsTests/IntentConfirmationChallengeViewControllerTests.swift:186— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testForeignChallengeDocumentCannotReportWebError StripePayments/StripePaymentsTests/IntentConfirmationChallengeViewControllerTests.swift:259— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testNewInstancesReportShownIndependently StripePaymentsUI/StripePaymentsUITests/CardElementAnalyticsTests.swift:67— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTextChangesReportInteractionWithoutFocus StripePaymentsUI/StripePaymentsUITests/CardElementAnalyticsTests.swift:98— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidationChangesAloneDoNotReportInteraction StripePaymentsUI/StripePaymentsUITests/CardElementAnalyticsTests.swift:164— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Low cohesion: View (LCOM4 20) Example/CryptoOnramp Example/CryptoOnramp Example/View+WalletOwnershipVerification.swift:10— View's methods fall into 20 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 20 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: WalletViewController (LCOM4 16) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:453— WalletViewController's methods fall into 16 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 16 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: String (LCOM4 16) Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1278— String's methods fall into 16 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 16 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: UIView (LCOM4 15) Example/PaymentSheet Example/PaymentSheet Example/AppDelegate+BrokenConstraints.swift:72— UIView'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: Dictionary (LCOM4 13) StripeCore/StripeCore/Source/Categories/Dictionary+Stripe.swift:11— Dictionary's methods fall into 13 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 13 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: BottomSheetViewController (LCOM4 13) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/BottomSheetViewController.swift:17— BottomSheetViewController's methods fall into 13 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 13 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: PlaygroundController (LCOM4 12) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:21— PlaygroundController'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: STPAPIClient (LCOM4 11) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:13— STPAPIClient'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: ConnectWebViewController (LCOM4 10) StripeConnect/StripeConnect/Source/Internal/Webview/ConnectWebViewController.swift:26— ConnectWebViewController'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: OneTimeCodeTextField (LCOM4 10) StripeUICore/StripeUICore/Source/Controls/OneTimeCodeTextField.swift:13— OneTimeCodeTextField'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: Array (LCOM4 10) Example/CryptoOnramp Example/CryptoOnramp Example/ComplianceIdentifiersEntryView.swift:374— Array'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: NativeSheetContainerViewController (LCOM4 9) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:18— NativeSheetContainerViewController'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: DocumentCaptureViewController (LCOM4 8) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:15— DocumentCaptureViewController'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: AddressViewController (LCOM4 8) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:25— AddressViewController'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: MainViewController (LCOM4 8) Example/IdentityVerification Example/IdentityVerification Example/MainViewController.swift:10— MainViewController'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: UIViewController (LCOM4 8) Example/PaymentSheet Example/PaymentSheet Example/ViewController.swift:53— UIViewController'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: VerificationFlowWebViewController (LCOM4 7) StripeIdentity/StripeIdentity/Source/WebWrapper/VerificationFlowWebViewController.swift:35— VerificationFlowWebViewController's methods fall into 7 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 7 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: STPApplePayContext (LCOM4 6) StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:159— STPApplePayContext's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SSDOcrOutput (LCOM4 6) StripeCardScan/StripeCardScan/Source/CardScan/MLModels/SSDOcr.swift:85— SSDOcrOutput's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SelfieCaptureViewController (LCOM4 6) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:15— SelfieCaptureViewController's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AutoCompleteViewController (LCOM4 6) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/AutoComplete/AutoCompleteViewController.swift:23— AutoCompleteViewController's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SceneDelegate (LCOM4 6) StripePayments/StripePaymentsTestHostApp/SceneDelegate.swift:10— SceneDelegate's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SceneDelegate (LCOM4 6) Example/IdentityVerification Example/IdentityVerification Example/SceneDelegate.swift:10— SceneDelegate's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SceneDelegate (LCOM4 6) Example/PaymentSheet Example/PaymentSheet Example/SceneDelegate.swift:13— SceneDelegate's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MainViewController (LCOM4 6) Example/StripeConnectExample/StripeConnectExample/MainViewController.swift:12— MainViewController's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
HackComment StripeUICore/StripeUICoreTests/Unit/Elements/AddressSectionElementTest.swift:106— // Hack to switch the country — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripeUICore/StripeUICore/Source/Views/DoneButtonToolbar.swift:108— // Hack: To tell if the touch is inside a button vs. the background, look at the touched view's width. The button is observed to be 38 points wide. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripeUICore/StripeUICore/Source/Elements/TextField/TextFieldView.swift:98— // Hack, disable the ability for the picker to take focus while it's being added as a sub view — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripeUICore/StripeUICore/Source/Elements/Section/SectionContainerView.swift:119— // Hack: Give the new stack view a dummy view with the same height as the current stack view's first view — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripeUICore/StripeUICore/Source/Elements/Section/SectionContainerView.swift:148— // Hack: Swap the dummy first view and real first view — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/PaymentSheet+APITest.swift:922— // Hack: Use contains b/c the test backend prepends "Error creating PaymentIntent:" and appends "(request_id: ...)" to its returned error string — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/PaymentSheetFormFactoryTest.swift:619— // Hacky way to differentiate the save checkbox from other checkboxes — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/PaymentSheetFormFactoryTest.swift:667— // Hacky way to differentiate the save checkbox from other checkboxes — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/PaymentSheetLPMConfirmFlowTests.swift:1428— // Hack to PaymentSheet-specific local actions that happen before control is handed over to STPPaymentHandler. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/PaymentSheetLPMConfirmFlowTests.swift:2228— // Hack to compare `paymentMethodParams` objects; consider them equal if their serialized versions are the same — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/TextFieldElement+CardTest.swift:150— // Hack to let STPBINRange finish network calls before running another test — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheetTests/PaymentSheet/TextFieldElement+CardTest.swift:211— // Hack to let STPBINRange finish network calls before running another test — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetAppearance+Helpers.swift:44— // Hack: `ElementsAppearance` doesn't have a primary button corner radius. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:410— // Hack: This line causes PaymentSheetSnapshotTests to fail on iOS 26 - the sheet becomes transparent. I can't figure out a fix, so just remove it out for tests. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:325— // Hack: Payment container needs to extend to the edges, so we'll 'cancel out' the layout margins with negative padding — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:240— // Hack: Payment container needs to extend to the edges, so we'll 'cancel out' the layout margins with negative padding — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:495— // Hack: PaymentHandler calls the completion block while SafariVC is still being dismissed - "wait" until it's finished before updating UI — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:730— // Hack: PaymentHandler calls the completion block while SafariVC is still being dismissed - "wait" until it's finished before updating UI — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:345— // Hack: PaymentHandler calls the completion block while SafariVC is still being dismissed - "wait" until it's finished before updating UI — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/New Payment Method Screen/PaymentMethodTypeCollectionView.swift:345— // Hacky workaround: If we update unconditionally, we'll overwrite the current PM's valid image with a 1x1 placeholder here — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+SwiftUI.swift:130— // Hack: If Embedded has not been presented yet, we may not have a VC. If that's the case, populate it with the default VC for the window. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:120— /// Hacky - ideally we have a RowButtonViewModel type of object that keeps track of this state. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:604— // Hack: We assume the accessory view is "Change >" — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:620— // Hack: We assume the accessory view is "Change >" — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:284— // Hack to get the accessory view to update — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
FileTooLong: PaymentHandler/STPPaymentHandler.swift StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift— FileTooLong — 1827 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: STPPaymentHandler (100-2488). The bar is 500 significant lines; this is 1327 over it, 3.65× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: UI Components/STPPaymentCardTextField.swift StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift— FileTooLong — 1420 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: STPPaymentCardTextField (21-2434). The bar is 500 significant lines; this is 920 over it, 2.84× 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: Native/NativeFlowController.swift StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift— FileTooLong — 1236 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 736 over it, 2.47× 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: API Bindings/STPAPIClient+Payments.swift StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift— FileTooLong — 1091 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 591 over it, 2.18× 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: PaymentSheetFormFactory/PaymentSheetFormFactory.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift— FileTooLong — 1042 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 542 over it, 2.08× 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: Link/LinkController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift— FileTooLong — 1002 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 502 over it, 2.00× 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: PaymentMethods/STPPaymentMethodParams.swift StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift— FileTooLong — 1001 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: STPPaymentMethodParams (16-1223). The bar is 500 significant lines; this is 501 over it, 2.00× 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: ViewControllers/SelfieCaptureViewController.swift StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift— FileTooLong — 892 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 392 over it, 1.78× 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: Vertical Main Screen/PaymentSheetVerticalViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift— FileTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: PaymentSheetVerticalViewController (14-890). The bar is 500 significant lines; this is 318 over it, 1.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: PaymentSheet/PaymentSheet+API.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift— FileTooLong — 784 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 284 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 754 significant lines (blank, comment-only and punctuation-only lines excluded), about 62% of them inside a single declaration: CryptoOnrampCoordinator (257-926). The bar is 500 significant lines; this is 254 over it, 1.51× 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: Selfie/SelfieScanningView.swift StripeIdentity/StripeIdentity/Source/NativeComponents/Views/Selfie/SelfieScanningView.swift— FileTooLong — 732 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: SelfieScanningView (16-820). The bar is 500 significant lines; this is 232 over it, 1.46× 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: Helpers/STPBankAccountCollector.swift StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift— FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: STPBankAccountCollector (29-966). The bar is 500 significant lines; this is 207 over it, 1.41× 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: PaymentSheet/PaymentSheetFlowController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFlowController.swift— 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: CustomerSheet/CustomerSavedPaymentMethodsViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift— FileTooLong — 705 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: CustomerSavedPaymentMethodsViewController (22-844). The bar is 500 significant lines; this is 205 over it, 1.41× 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: API Bindings/FinancialConnectionsAsyncAPIClient.swift StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift— FileTooLong — 700 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 200 over it, 1.40× 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: Saved Payment Method Screen/SavedPaymentOptionsViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift— FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 168 over it, 1.34× 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: Selfie/CaptureTickMarksView.swift StripeIdentity/StripeIdentity/Source/NativeComponents/Views/Selfie/CaptureTickMarksView.swift— FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: CaptureTickMarksView (12-874). The bar is 500 significant lines; this is 159 over it, 1.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Link/STPAPIClient+Link.swift StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift— FileTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 151 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Embedded/EmbeddedPaymentElement+Internal.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift— FileTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 100 over it, 1.20× 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: Controllers/PayWithLinkViewController.swift StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift— FileTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 97 over it, 1.19× 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: ApplePayContext/STPApplePayContext.swift StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift— FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: STPApplePayContext (160-939). The bar is 500 significant lines; this is 79 over it, 1.16× 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: Coordinators/VerificationSheetFlowController.swift StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift— FileTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 77 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controllers/PayWithLinkViewController-WalletViewController.swift StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift— FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 69 over it, 1.14× 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: ViewControllers/PaymentSheetFlowControllerViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift— FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: PaymentSheetFlowControllerViewController (17-622). The bar is 500 significant lines; this is 66 over it, 1.13× 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.
TooManyMethods: STPAPIClient StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:13— TooManyMethods — 200 methods, declared across 17 files: API Bindings/STPAPIClient+Payments.swift (75), Link/STPAPIClient+Link.swift (26), API Bindings/STPAPIClient+CryptoOnramp.swift (24), API Bindings/STPAPIClient.swift (22), +13 more file(s). The bar is 30 methods; this is 170 over it, 6.67× 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: PaymentSheetFormFactory StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:20— TooManyMethods — 86 methods, declared across 13 files: PaymentSheetFormFactory/PaymentSheetFormFactory.swift (48), PaymentSheetFormFactory/PaymentSheetFormFactory+Mandates.swift (17), PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift (4), PaymentSheetFormFactory/PaymentSheetFormFactory+Card.swift (3), +9 more file(s). The bar is 30 methods; this is 56 over it, 2.87× 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: STPPaymentMethodParams StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:16— TooManyMethods — 83 methods, declared across 3 files: PaymentMethods/STPPaymentMethodParams.swift (78), StripePaymentsTestUtils/STPFixtures+Swift.swift (4), PaymentSheet/PaymentOption+Images.swift (1). The bar is 30 methods; this is 53 over it, 2.77× 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: NativeFlowController StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:31— TooManyMethods — 82 methods. The bar is 30 methods; this is 52 over it, 2.73× 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: STPAnalyticsClient StripeCore/StripeCore/Source/Analytics/STPAnalyticsClient.swift:26— TooManyMethods — 77 methods, declared across 9 files: Analytics/STPAnalyticsClient+Payments.swift (21), Analytics/STPAnalyticsClient.swift (12), Analytics/STPAnalyticsClient+CustomerSheet.swift (12), Analytics/STPAnalyticsClient+Address.swift (10), +5 more file(s). The bar is 30 methods; this is 47 over it, 2.57× 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: STPPaymentCardTextField StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:19— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× 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: STPPaymentHandler StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:100— TooManyMethods — 59 methods, declared across 2 files: PaymentHandler/STPPaymentHandler.swift (50), PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift (9). The bar is 30 methods; this is 29 over it, 1.97× 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: LinkController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:17— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: FinancialConnectionsAsyncAPIClient StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:11— TooManyMethods — 50 methods, declared across 2 files: API Bindings/FinancialConnectionsAsyncAPIClient+Wrappers.swift (37), API Bindings/FinancialConnectionsAsyncAPIClient.swift (13). The bar is 30 methods; this is 20 over it, 1.67× 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: PaymentSheet StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet.swift:46— TooManyMethods — 50 methods, declared across 6 files: PaymentSheet/PaymentSheet.swift (17), PaymentSheet/PaymentSheet+API.swift (10), PaymentSheet/PaymentSheet+DeferredAPI.swift (7), PaymentSheet/PaymentSheet+PaymentMethodAvailability.swift (7), +2 more file(s). The bar is 30 methods; this is 20 over it, 1.67× 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: CheckoutElementsController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController.swift:18— TooManyMethods — 48 methods, declared across 8 files: Checkout/CheckoutElementsController.swift (22), Checkout/CheckoutElementsController+Internal.swift (11), Checkout/CheckoutElementsController+Confirm.swift (9), Checkout/CheckoutElementsController+Confirm+Link.swift (2), +4 more file(s). The bar is 30 methods; this is 18 over it, 1.60× 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: CryptoOnrampCoordinator REDACTED:256— TooManyMethods — 47 methods, declared across 2 files: REDACTED (39), Errors/CryptoOnrampCoordinator+ErrorMapping.swift (8). The bar is 30 methods; this is 17 over it, 1.57× 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: SelfieCaptureViewController StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:15— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: PaymentSheetVerticalViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:14— 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: EmbeddedPaymentElement StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement.swift:15— TooManyMethods — 43 methods, declared across 2 files: Embedded/EmbeddedPaymentElement+Internal.swift (32), Embedded/EmbeddedPaymentElement.swift (11). The bar is 30 methods; this is 13 over it, 1.43× 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: ScanBaseViewController StripeCardScan/StripeCardScan/Source/CardScan/UI/ScanBaseViewController.swift:9— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OneTimeCodeTextField StripeUICore/StripeUICore/Source/Controls/OneTimeCodeTextField.swift:13— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× 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: AddressViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:25— 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: CustomerSavedPaymentMethodsViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:21— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: STPPaymentMethod StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethod.swift:15— TooManyMethods — 37 methods, declared across 9 files: StripePaymentsTestUtils/STPFixtures+Swift.swift (9), Categories/STPPaymentMethod+PaymentSheet.swift (8), PaymentSheet/PaymentOption+Images.swift (8), PaymentMethods/STPPaymentMethod.swift (7), +5 more file(s). The bar is 30 methods; this is 7 over it, 1.23× 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: SimpleScanViewController StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:67— TooManyMethods — 35 methods, declared across 2 files: UI/SimpleScanViewController.swift (34), CardVerify/SimpleScanViewController+Verify.swift (1). The bar is 30 methods; this is 5 over it, 1.17× 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: NativeSheetContainerViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:18— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: ConnectWebViewController StripeConnect/StripeConnect/Source/Internal/Webview/ConnectWebViewController.swift:26— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VerificationSheetController StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:134— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PaymentSheetFlowControllerViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:17— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentFooterView.swift:73— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentFooterView.swift:73-83 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:287-296 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentFooterView.swift:73` 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.
Duplicated block (10 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:134— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:134-143 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupViewController.swift:179-188 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:134` 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 (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:622— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:622-631 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:644-653 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:622` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:783— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:783-792 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:317-326 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:783` 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 (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:380— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:380-389 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:608-617 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:380` 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 (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:85— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:85-94 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:155-164 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:85` 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 after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:166` calls `validatePaymentMethod` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:97` 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.
Duplicated block (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:125— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:125-134 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:196-205 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:125` 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 after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:207` calls `validatePaymentMethod` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:137` 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.
Duplicated block (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:428— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:428-437 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:441-450 — 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 (10 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:468— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:468-477 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:774-783 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:468` 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 (10 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:600— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:600-609 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:806-815 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:600` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:598` calls `isNextActionSuccessState` and `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:804` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) Example/AppClipExample/Shared/BackendModel.swift:42— Example/AppClipExample/Shared/BackendModel.swift:42-51 | Testers/IntegrationTester/IntegrationTester/Source/Models/BackendModel.swift:53-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Example/AppClipExample/Shared/BackendModel.swift:42` 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 (10 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:80— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:80-89 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:72-81 — 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 `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:80` 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 (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Analytics/Experiments/ConnectionsFCLiteVsNative.swift:17— StripePaymentSheet/StripePaymentSheet/Source/Analytics/Experiments/ConnectionsFCLiteVsNative.swift:17-26 | StripePaymentSheet/StripePaymentSheet/Source/Analytics/Experiments/ConnectionsFCLiteVsNativeAA.swift:17-26 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:328— StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:328-337 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteContainerViewController.swift:309-318 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:447— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:447-456 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:398-407 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:61— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:61-70 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:667-676 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/New Payment Method Screen/WalletHeaderView.swift:253— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/New Payment Method Screen/WalletHeaderView.swift:253-262 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RightAccessoryButton.swift:148-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:590— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:590-599 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:720-729 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginDataSource.swift:75— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginDataSource.swift:75-84 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupDataSource.swift:73-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:18— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:18-27 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/LegalDetailsNoticeViewController.swift:18-27 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:180— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:180-189 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:680-689 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:676` calls `VStack`, `Text`, `font` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:179` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIViews.swift:113— Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIViews.swift:113-122 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:733-742 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIViews.swift:113` 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 (10 lines × 2) Example/CardImageVerification Example/CardImageVerification Example/View Controllers/VerificationExplanationViewController.swift:67— Example/CardImageVerification Example/CardImageVerification Example/View Controllers/VerificationExplanationViewController.swift:67-76 | Example/CardImageVerification Example/CardImageVerification Example/View Controllers/ViewController.swift:12-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 both call sites, so a change lands once.
Duplicated block (10 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:381— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:381-390 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:570-579 — 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) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:48— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:48-57 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:48-57 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
MethodTooLong: PaymentSheet.confirmAfterHandlingLocalActions StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:248— MethodTooLong — confirmAfterHandlingLocalActions runs 308 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 208 over it, 3.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPPaymentHandler._handleAuthenticationForCurrentAction StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1153— MethodTooLong — _handleAuthenticationForCurrentAction runs 301 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 201 over it, 3.01× 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: STPPaymentCardTextField.recalculateSubviewLayout StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1320— MethodTooLong — recalculateSubviewLayout runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PaymentSheet.confirmLinkPaymentOption StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:652— MethodTooLong — confirmLinkPaymentOption runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LinkAccountPickerViewController.didSelectConnectAccounts StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:250— MethodTooLong — didSelectConnectAccounts runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPPaymentMethodType.makeImage StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift:219— MethodTooLong — makeImage 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: STPAUBECSDebitFormView.init StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPAUBECSDebitFormView.swift:45— MethodTooLong — init 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: STPPaymentMethodType.displayName StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodEnums.swift:149— MethodTooLong — displayName runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPPaymentHandler._retrieveAndCheckIntentForCurrentAction StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1626— MethodTooLong — _retrieveAndCheckIntentForCurrentAction runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPApplePayContext._completePayment StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:660— MethodTooLong — _completePayment runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPDecodingContainerProtocol.castFromNSObject StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:570— MethodTooLong — castFromNSObject runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ErrorViewController.viewDidLoad StripeFinancialConnections/StripeFinancialConnections/Source/Native/Error/ErrorViewController.swift:41— MethodTooLong — viewDidLoad runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPPaymentMethod.decodedObject StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethod.swift:295— MethodTooLong — decodedObject runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: STPPaymentMethodType.identifier StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodEnums.swift:294— MethodTooLong — identifier runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: CheckoutElementsController.confirmLink StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:24— MethodTooLong — confirmLink runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: STPPaymentMethodParams.init StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:1580— MethodTooLong — init 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: NativeFlowController.closeAuthFlow StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:359— MethodTooLong — closeAuthFlow runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: STPIntentAction.decodedObject StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift:353— MethodTooLong — decodedObject runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PaymentSheet.handleDeferredIntentConfirmation StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:63— MethodTooLong — handleDeferredIntentConfirmation runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AccountPickerNoAccountEligibleErrorView.init StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerNoAccountEligibleErrorView.swift:16— MethodTooLong — init runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PaymentSheetFormFactory.makeCard StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Card.swift:42— MethodTooLong — makeCard runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: ConfirmButton.update StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/ConfirmButton.swift:292— MethodTooLong — update runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PaneLayoutView.createFooterView StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:255— MethodTooLong — createFooterView 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: PaymentSheetLoader.load StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:63— MethodTooLong — load 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: CheckoutElementsController.makeConfirmationFlow StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:146— MethodTooLong — makeConfirmationFlow runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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.
Duplicated block (8 lines × 2) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:35— StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:35-42 | StripeApplePay/StripeApplePay/Source/PaymentsCore/API/SetupIntent+API.swift:34-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. Read the line range as the matched WINDOW rather than a finished unit: at `StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:35` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `completion` to `@escaping PaymentIntentCompletionBlock` in one and `@escaping SetupIntentCompletionBlock` 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.
Duplicated block (8 lines × 2) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/OcrPriorsGen.swift:95— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/OcrPriorsGen.swift:95-102 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/OcrPriorsGen.swift:109-116 — 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 `StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/OcrPriorsGen.swift:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) StripeConnect/StripeConnect/Source/Internal/Webview/ConnectComponentWebViewController.swift:80— StripeConnect/StripeConnect/Source/Internal/Webview/ConnectComponentWebViewController.swift:80-87 | StripeConnect/StripeConnect/Source/Internal/Webview/ConnectComponentWebViewController.swift:157-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripeConnect/StripeConnect/Source/Internal/Webview/ConnectComponentWebViewController.swift:80` 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, `StripeConnect/StripeConnect/Source/Internal/Webview/ConnectComponentWebViewController.swift:79` calls `escaping` and `StripeConnect/StripeConnect/Source/Internal/Webview/ConnectComponentWebViewController.swift:156` 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.
Duplicated block (8 lines × 2) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:354— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:354-361 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:398-405 — 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 `StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:354` 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) StripeFinancialConnections/StripeFinancialConnections/Source/Analytics/FinancialConnectionsAnalyticsClient.swift:156— StripeFinancialConnections/StripeFinancialConnections/Source/Analytics/FinancialConnectionsAnalyticsClient.swift:156-163 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:692-699 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/Analytics/FinancialConnectionsAnalyticsClient.swift:156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:178— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:178-185 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/Button+Link.swift:69-76 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Services/LinkAccountService.swift:152— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Services/LinkAccountService.swift:152-161 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Services/LinkAccountService.swift:230-237 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Services/LinkAccountService.swift:152` 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 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 (8 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:581— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:581-588 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/STPApplePayContext+PaymentSheet.swift:150-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:581` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement.swift:383— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement.swift:383-390 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:36-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement.swift:383` 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 (8 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:183— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:183-190 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:197-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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:183` 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 (8 lines × 2) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPCardFormView.swift:618— StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPCardFormView.swift:618-625 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:2415-2422 — 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) StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.swift:71— StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.swift:71-78 | StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.swift:219-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionOXXODisplayDetails.swift:53— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionOXXODisplayDetails.swift:53-60 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionVerifyWithMicrodeposits.swift:71-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 `StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionOXXODisplayDetails.swift: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.
Duplicated block (8 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:550— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:550-557 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:296-303 — before extracting anything, compare `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift` and `StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:564— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:564-571 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:311-318 — before extracting anything, compare `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift` and `StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:138— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:138-145 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:171-178 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:343— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:343-350 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:492-499 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:514— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:514-521 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:602-609 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:668— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:668-675 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:571-578 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionCashAppRedirectToApp.swift:37— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionCashAppRedirectToApp.swift:37-44 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionSwishHandleRedirect.swift:35-42 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPayNowDisplayQrCode.swift:35— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPayNowDisplayQrCode.swift:35-42 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPromptPayDisplayQrCode.swift:35-42 — 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) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntentParams.swift:96— StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntentParams.swift:96-103 | StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntentConfirmParams.swift:199-206 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Views/BottomAlignedLabel.swift:85— StripeIdentity/StripeIdentity/Source/NativeComponents/Views/BottomAlignedLabel.swift:85-92 | StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityHTMLView/IconLabelHTMLView.swift:92-99 — 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) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:95— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:95-102 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:95-102 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:147— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:147-154 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:147-154 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×24
Edited copy of a member (10 corresponding lines) StripeUICore/StripeUICore/Source/Categories/UIView+StripeUICore.swift:28— StripeUICore/StripeUICore/Source/Categories/UIView+StripeUICore.swift:28-37 | StripeUICore/StripeUICore/Source/Categories/UIView+StripeUICore.swift:39-48 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEPromotionTextView.swift:50— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEPromotionTextView.swift:50-59 | StripeUICore/StripeUICore/Source/Views/LinkOpeningTextView.swift:41-56 — 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) StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/OcrObject.swift:21— StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/OcrObject.swift:21-30 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedSSDBox.swift:37-50 — 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) Example/AppClipExample/Shared/BackendModel.swift:31— Example/AppClipExample/Shared/BackendModel.swift:31-40 | Testers/IntegrationTester/IntegrationTester/Source/Models/BackendModel.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) StripeUICore/StripeUICore/Source/Elements/ElementsUI.swift:51— StripeUICore/StripeUICore/Source/Elements/ElementsUI.swift:51-61 | StripeUICore/StripeUICore/Source/Elements/ElementsUI.swift:63-72 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/SFSafariViewController+Extensions.swift:13— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/SFSafariViewController+Extensions.swift:13-23 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/UIViewController+SafariExtension.swift:14-23 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBoletoParams.swift:25— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBoletoParams.swift:25-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodThreeDSecureUsage.swift:18-31 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityFlowView.swift:558— StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityFlowView.swift:558-567 | StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityFlowView.swift:570-579 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:232— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:232-241 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:243-252 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardNetworks.swift:21— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardNetworks.swift:21-31 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardNetworksParams.swift:26-35 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodiDEAL.swift:21— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodiDEAL.swift:21-31 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodFPX.swift:19-28 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/ProofOfAddressView.swift:156— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/ProofOfAddressView.swift:156-165 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/SourceOfFundsDocumentView.swift:173-182 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/UIButton+PaymentSheet.swift:16— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/UIButton+PaymentSheet.swift:16-25 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/SheetNavigationBar.swift:292-301 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:97— StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:97-107 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:92-101 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:55— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:55-66 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:58-67 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:89— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:89-100 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardParams.swift:93-102 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:267— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:267-276 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:1327-1336 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:423— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:423-432 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:161-170 — 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) StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPCBCController.swift:110— StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPCBCController.swift:110-119 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPPaymentCardTextFieldViewModel.swift:118-127 — 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) StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:152— StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:152-161 | StripeConnect/StripeConnect/Source/Components/CheckScanningController.swift:113-122 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:857— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:857-866 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:1340-1351 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerPaymentOption.swift:30— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerPaymentOption.swift:30-39 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton.swift:688-699 — 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) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:816— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:816-825 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:834-848 — 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) Example/StripeConnectExample/StripeConnectExample/SceneDelegate.swift:14— Example/StripeConnectExample/StripeConnectExample/SceneDelegate.swift:14-23 | Example/UI Examples/UI Examples/Source/SceneDelegate.swift:12-27 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×23
Edited copy of a member (8 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:180— StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:180-187 | StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:218-225 — 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) StripeCore/StripeCore/Source/Attestation/StripeAttestBackend.swift:25— StripeCore/StripeCore/Source/Attestation/StripeAttestBackend.swift:25-32 | StripeCore/StripeCore/Source/Attestation/StripeAttestBackend.swift:34-41 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton.swift:487— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton.swift:487-495 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/VerticalPaymentMethodListViewController.swift:283-290 — 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) StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:51— StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:51-58 | StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:60-67 — 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) StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:361— StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:361-368 | StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:382-389 — 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) StripeCardScan/StripeCardScan/Source/CardScan/Extensions/Image+utils.swift:30— StripeCardScan/StripeCardScan/Source/CardScan/Extensions/Image+utils.swift:30-38 | StripeCardScan/StripeCardScan/Source/CardScan/Extensions/UIImage+pixelBuffer.swift:240-247 — 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) StripeCardScan/StripeCardScan/Source/CardScan/Extensions/Image+utils.swift:30— StripeCardScan/StripeCardScan/Source/CardScan/Extensions/Image+utils.swift:30-38 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionResult.swift:76-83 — 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) StripePayments/StripePayments/Source/Internal/Analytics/Analytic+Payments.swift:28— StripePayments/StripePayments/Source/Internal/Analytics/Analytic+Payments.swift:28-37 | Stripe/StripeiOS/Source/STPAnalyticsClient+Payments.swift:19-26 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:856— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:856-863 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewController.swift:465-473 — 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) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPPostalCodeInputTextField.swift:40— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPPostalCodeInputTextField.swift:40-49 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPGenericInputTextField.swift:47-54 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:332— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:332-341 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:391-398 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/Additional KYC/AdditionalKYCRequirement.swift:30— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/Additional KYC/AdditionalKYCRequirement.swift:30-41 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/Additional KYC/AdditionalKYCQuestionnaire.swift:27-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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Saved Payment Method Screen/VerticalSavedPaymentMethodsViewController.swift:260— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Saved Payment Method Screen/VerticalSavedPaymentMethodsViewController.swift:260-267 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/UpdatePaymentMethodViewController.swift:207-214 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardChecks.swift:94— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardChecks.swift:94-101 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardPresent.swift: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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerNewAccountRowView.swift:60— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerNewAccountRowView.swift:60-67 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/InstitutionIconView.swift:67-74 — 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) StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/CloseWebView.swift:12— StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/CloseWebView.swift:12-19 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/DebugMessageHandler.swift:13-20 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:72— StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:72-79 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement+Configuration.swift:328-335 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:560— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:560-567 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:254-261 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:61— StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:61-68 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement+Configuration.swift:328-335 — 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) StripeCore/StripeCore/Source/Analytics/AnalyticsHelper.swift:40— StripeCore/StripeCore/Source/Analytics/AnalyticsHelper.swift:40-48 | StripePaymentSheet/StripePaymentSheet/Source/Analytics/PaymentSheetAnalyticsHelper.swift:579-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) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:24— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:24-31 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteSecureAuthFlowViewController.swift:20-27 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Intent.swift:78— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Intent.swift:78-85 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet.swift:52-59 — 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) Example/FinancialConnections Example/FinancialConnections Example/ExampleListViewController.swift:82— Example/FinancialConnections Example/FinancialConnections Example/ExampleListViewController.swift:82-90 | Example/IdentityVerification Example/IdentityVerification Example/MainViewController.swift:14-21 — 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.
Duplicated block (9 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:102— StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:102-110 | StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:119-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.
Duplicated block (9 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:539— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:539-547 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:837-845 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:539` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:548` calls `reloadData` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:846` 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 (9 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:268— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:268-276 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:290-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:268` 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 (9 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:827— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:827-835 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:853-861 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:827` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1460— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1460-1468 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1471-1479 — 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 (9 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:390— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:390-398 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AttachLinkedPaymentAccountViewController.swift:164-172 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:426— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:426-434 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:726-734 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodOXXO.swift:31— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodOXXO.swift:31-39 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSwish.swift:30-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 (9 lines × 2) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:245— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:245-253 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:322-330 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:255— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:255-263 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkLoginWarmup/NetworkingLinkLoginWarmupBodyView.swift:97-105 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNetBanking.swift:21— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNetBanking.swift:21-29 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAutomaticPaymentMethods.swift:17-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. 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) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardCVCInputTextField.swift:49— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardCVCInputTextField.swift:49-57 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextField.swift:29-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) Example/CryptoOnramp Example/CryptoOnramp Example/UI Helpers/PrimaryButtonStyle.swift:11— Example/CryptoOnramp Example/CryptoOnramp Example/UI Helpers/PrimaryButtonStyle.swift:11-19 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:725-733 — 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) Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:92— Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:92-100 | Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:68-76 — 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:174— Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:174-182 | Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:188-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:174` 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 (9 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:413— Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:413-421 | Example/PaymentSheet Example/PaymentSheet Example/AppearancePlaygroundView.swift:445-453 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `selection` to `customHeadlineFontBinding` in one and `primaryButtonFontBinding` 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.
Duplicated block (9 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:932— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:932-940 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:932-940 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/HitTestStackView.swift:16— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/HitTestStackView.swift:16-24 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/HitTestView.swift:16-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 both call sites, so a change lands once.
Duplicated block (9 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:67— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:67-75 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:604-612 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:206— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:206-214 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:853-861 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:206` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:53— Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:53-61 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:52-60 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:110— Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:110-118 | Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift:105-113 — before extracting anything, compare `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift` and `Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:45— StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:45-56 | StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSectionElement.swift:61-67 — 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 `StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:45` 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) StripeConnect/StripeConnect/Source/Helpers/Appearance+Encoding.swift:67— StripeConnect/StripeConnect/Source/Helpers/Appearance+Encoding.swift:67-73 | StripeConnect/StripeConnect/Source/Helpers/Appearance+Encoding.swift:82-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:187— StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:187-193 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:302-308 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Components/Consent/LinkFullConsent-EmailView.swift:47— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Components/Consent/LinkFullConsent-EmailView.swift:47-53 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Components/Consent/LinkFullConsent-ScopesView.swift:125-131 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:31— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElement.swift:31-37 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Shipping Address Element/ShippingAddressElement.swift:77-83 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:341— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:341-347 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/VerticalPaymentMethodListViewController.swift:224-230 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:819— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:819-825 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:662-668 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:671` calls `set` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:829` 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.
Duplicated block (7 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAlipay.swift:29— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAlipay.swift:29-35 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBLIK.swift:30-36 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionBoletoDisplayDetails.swift:61— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionBoletoDisplayDetails.swift:61-67 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionMultibancoDisplayDetails.swift:66-72 — 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) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardCVCInputTextFieldFormatter.swift:30— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardCVCInputTextFieldFormatter.swift:30-36 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPNumericDigitInputTextFormatter.swift:43-49 — 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) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPCardFormView.swift:599— StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPCardFormView.swift:599-605 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:2396-2402 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:69— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:69-75 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AttachLinkedPaymentAccountViewController.swift:53-59 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/CVCReconfirmationVerticalViewController.swift:23— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/CVCReconfirmationVerticalViewController.swift:23-29 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/CVCReconfirmationViewController.swift:55-61 — 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 (7 lines × 2) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:1001— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:1001-1007 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2503-2509 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `code` to `STPCollectBankAccountError` in one and `STPPaymentHandlerErrorCode` 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.
Duplicated block (7 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:519— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:519-525 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:537-543 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:296— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:296-302 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:552-558 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:551` calls `constraint` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:295` 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 (7 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/BoletoExampleViewController.swift:167— Example/Non-Card Payment Examples/Non-Card Payment Examples/BoletoExampleViewController.swift:167-173 | Example/PaymentSheet Example/PaymentSheet Example/EmbeddedPaymentElementWrapperViewController.swift:46-52 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:216— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:216-222 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:28-34 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:216` 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 (7 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:32— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:32-38 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:248-254 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:32` 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 (7 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:940— Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:940-946 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:1053-1059 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:181— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:181-187 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:373-379 — 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) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:59— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:59-65 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:614-620 — 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 (6 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:763— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:763-768 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:25-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:45— StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:45-50 | StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:182-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) StripeCore/StripeCore/Source/Analytics/AnalyticsClientV2.swift:128— StripeCore/StripeCore/Source/Analytics/AnalyticsClientV2.swift:128-133 | StripeCore/StripeCore/Source/Analytics/STPAnalyticsClient.swift:211-216 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:25— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:25-30 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/Button+Link.swift:60-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/Button+Link.swift:60` 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. 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 (6 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:671— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:671-676 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:696-701 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:671` 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 (6 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetDeferredValidator.swift:60— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetDeferredValidator.swift:60-65 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetDeferredValidator.swift:77-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetDeferredValidator.swift:60` 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 (6 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+SEPADebit.swift:22— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+SEPADebit.swift:22-27 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+USBankAccount.swift:25-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+SEPADebit.swift:22` 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 (6 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift:44— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift:44-49 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsParams.swift:58-63 — 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 `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift:44` 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 (6 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountCompanyParams.swift:107— StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountCompanyParams.swift:107-112 | StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountIndividualParams.swift:124-129 — 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 `StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountCompanyParams.swift:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountCompanyParams.swift:104` calls `NSNumber` and `StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountIndividualParams.swift:123` 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.
Duplicated block (6 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:149— StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:149-154 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccountParams.swift:100-105 — 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 `StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:149` 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 (6 lines × 2) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1087— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1087-1097 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1138-1143 — 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 `StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1087` 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 (6 lines × 2) StripeUICore/StripeUICore/Source/Helpers/InputFormColors.swift:17— StripeUICore/StripeUICore/Source/Helpers/InputFormColors.swift:17-22 | StripeUICore/StripeUICore/Source/Helpers/InputFormColors.swift:39-44 — 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 (6 lines × 2) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedAllBoxes.swift:12— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedAllBoxes.swift:12-17 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedAllOcrBoxes.swift:13-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 (6 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:91— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:91-96 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:90-95 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:52— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:52-57 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AttachLinkedPaymentAccountViewController.swift:36-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKrCard.swift:39— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKrCard.swift:39-44 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgCard.swift:40-45 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCard.swift:174— StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCard.swift:174-179 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPSourceCardDetails.swift:105-114 — 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) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:671— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:671-676 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:778-783 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:671` 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 (6 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:665— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:665-671 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:709-714 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:665` 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 (6 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:57— Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:57-62 | Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:68-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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:57` 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 (6 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIEmbeddedPaymentElement.swift:40— Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIEmbeddedPaymentElement.swift:40-45 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIEmbeddedPaymentElement.swift:138-143 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIEmbeddedPaymentElement.swift:40` 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) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:259— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:259-264 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:326-331 — 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 `Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:259` 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 (16 corresponding lines) · ×21
Edited copy of a member (16 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:101— StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:101-116 | StripePaymentSheet/StripePaymentSheet/Source/Analytics/STPAnalyticsClient+Address.swift:118-134 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:512— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:512-527 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:529-546 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/AddressAutocompleteModels.swift:177— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/AddressAutocompleteModels.swift:177-197 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:82-97 — 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) StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:48— StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:48-63 | StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:95-111 — 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) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:39— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:39-54 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:57-72 — 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) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:187— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:187-202 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:204-219 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:885— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:885-900 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/AutoComplete/AutoCompleteViewController.swift:247-268 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:408— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:408-423 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:639-658 — 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) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1666— StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1666-1681 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1683-1698 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:741— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:741-756 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:774-794 — 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) StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:612— StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:612-628 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:630-645 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPMandateDataParams.swift:68— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPMandateDataParams.swift:68-85 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPMandateOnlineParams.swift:87-102 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:109— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:109-124 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodBillingDetails.swift:83-99 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityFlowView.swift:417— StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityFlowView.swift:417-433 | StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityHTMLView/MultilineIconLabelHTMLView.swift:64-79 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:199— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:199-214 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:302-317 — 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) StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:106— StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:106-121 | StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:201-216 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.swift:208— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.swift:208-223 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.swift:225-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) Example/CryptoOnramp Example/CryptoOnramp Example/KYCInfoView.swift:453— Example/CryptoOnramp Example/CryptoOnramp Example/KYCInfoView.swift:453-470 | Example/CryptoOnramp Example/CryptoOnramp Example/UpdateAddressView.swift:153-168 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient.swift:111— Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient.swift:111-128 | Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient.swift:130-145 — 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) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:164— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:164-179 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:390-410 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:16— Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:16-31 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift:15-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.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×21
Edited copy of a member (11 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/SheetViewController.swift:357— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/SheetViewController.swift:357-381 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/Button+Link.swift:56-66 — 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) StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:127— StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:127-137 | StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:222-232 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardArt.swift:31— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardArt.swift:31-44 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardArt.swift:56-66 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:276— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:276-286 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:196-206 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodFPX.swift:35— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodFPX.swift:35-45 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodiDEAL.swift:38-50 — 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) StripeCore/StripeCore/Source/Coder/StripeJSONEncoder.swift:213— StripeCore/StripeCore/Source/Coder/StripeJSONEncoder.swift:213-223 | StripeCore/StripeCore/Source/Coder/StripeJSONEncoder.swift:350-362 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:103— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:103-118 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:102-112 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:516— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:516-530 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:410-420 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionTableLoadingView.swift:80— StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionTableLoadingView.swift:80-91 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionTableLoadingView.swift:106-116 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:45— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:45-55 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:147-157 — 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) StripeCore/StripeCore/Source/Connections Bindings/URL+LinkBankPaymentMethod.swift:37— StripeCore/StripeCore/Source/Connections Bindings/URL+LinkBankPaymentMethod.swift:37-47 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ACH/InstantDebitsOnlyFinancialConnectionsAuthManager.swift:154-164 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardWallet.swift:70— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardWallet.swift:70-80 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:65-75 — 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) StripeCardScan/StripeCardScan/Source/CardVerify/PaymentCard.swift:32— StripeCardScan/StripeCardScan/Source/CardVerify/PaymentCard.swift:32-47 | StripeCardScan/StripeCardScan/Source/CardVerify/PaymentCard.swift:49-59 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/IDConsentContent/IDConsentContentDataSource.swift:27— StripeFinancialConnections/StripeFinancialConnections/Source/Native/IDConsentContent/IDConsentContentDataSource.swift:27-39 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionDataSource.swift:35-45 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryDataSource.swift:29— StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryDataSource.swift:29-41 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/ResetFlow/ResetFlowDataSource.swift:25-35 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:330— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:330-340 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:68-78 — 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) StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:40— StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:40-50 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:83-96 — 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) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:326— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:326-336 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:1348-1358 — 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) Example/PaymentSheet Example/PaymentSheet Example/EmbeddedPlaygroundViewController.swift:331— Example/PaymentSheet Example/PaymentSheet Example/EmbeddedPlaygroundViewController.swift:331-341 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:84-95 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:628— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:628-638 | Example/PaymentSheet Example/PaymentSheet Example/ViewController.swift:55-69 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:162— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:162-173 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:628-638 — 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 (12 corresponding lines) · ×18
Edited copy of a member (12 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:78— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:78-89 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:70-81 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:177— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:177-189 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/Button+Link.swift:68-79 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:506— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:506-518 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:520-531 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:431— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:431-446 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:448-459 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:426— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:426-437 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:439-450 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PaymentSheet-LinkConfirmOption.swift:76— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PaymentSheet-LinkConfirmOption.swift:76-87 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PaymentSheet-LinkConfirmOption.swift:112-123 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient+Wrappers.swift:13— StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient+Wrappers.swift:13-24 | StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient+Wrappers.swift:27-38 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Views/DocumentCapture/AnimatedBorderView.swift:155— StripeIdentity/StripeIdentity/Source/NativeComponents/Views/DocumentCapture/AnimatedBorderView.swift:155-166 | StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift:186-202 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:349— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:349-367 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:369-380 — 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) StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:418— StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:418-431 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1543-1554 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/PaymentMethodElement/PaymentMethodElementWrapper.swift:51— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/PaymentMethodElement/PaymentMethodElementWrapper.swift:51-62 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/PaymentMethodElement/PaymentMethodElementWrapper.swift:78-89 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:448— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:448-459 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:461-472 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:298— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:298-309 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:344-355 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:400— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:400-411 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:452-464 — 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) StripePayments/StripePayments/Source/API Bindings/Models/ACH/STPCollectBankAccountParams.swift:25— StripePayments/StripePayments/Source/API Bindings/Models/ACH/STPCollectBankAccountParams.swift:25-38 | StripePayments/StripePayments/Source/API Bindings/Models/ACH/STPCollectBankAccountParams.swift:43-54 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:378— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:378-389 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:147-159 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:802— StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:802-813 | StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:434-445 — 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) StripeApplePay/StripeApplePay/Source/PaymentsCore/Analytics/STPAnalyticsClient+PaymentsAPI.swift:48— StripeApplePay/StripeApplePay/Source/PaymentsCore/Analytics/STPAnalyticsClient+PaymentsAPI.swift:48-59 | StripePayments/StripePayments/Source/Internal/Analytics/STPAnalyticsClient+Payments.swift:93-106 — 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.
Duplicated block (14 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:131— StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:131-144 | StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:156-169 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:131` 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) StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/String+Extensions.swift:100— StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/String+Extensions.swift:100-113 | StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/String+Extensions.swift:119-132 — 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) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/API Client/FCLiteApiClient.swift:40— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/API Client/FCLiteApiClient.swift:40-53 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/API Client/FCLiteApiClient.swift:61-74 — 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 `StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/API Client/FCLiteApiClient.swift:40` 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:835— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:835-848 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:858-871 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:835` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+Card.swift:63— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+Card.swift:63-76 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+Link.swift:52-65 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+Card.swift:63` 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 (14 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:29— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:29-42 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift:39-52 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:29` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:231— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:231-244 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:269-282 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:560— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:560-573 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:683-696 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:560` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:225— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:225-238 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:171-184 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:225` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:653— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:653-666 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:556-569 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:651— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:651-664 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:733-746 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:666— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:666-679 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:748-761 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/LogInSignUpView.swift:51— Example/CryptoOnramp Example/CryptoOnramp Example/LogInSignUpView.swift:51-64 | Example/CryptoOnramp Example/CryptoOnramp Example/SeamlessSignInView.swift:51-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 `Example/CryptoOnramp Example/CryptoOnramp Example/LogInSignUpView.swift:51` 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) Example/CryptoOnramp Example/CryptoOnramp Example/PaymentView.swift:967— Example/CryptoOnramp Example/CryptoOnramp Example/PaymentView.swift:967-980 | Example/CryptoOnramp Example/CryptoOnramp Example/PaymentView.swift:1018-1031 — 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 `Example/CryptoOnramp Example/CryptoOnramp Example/PaymentView.swift:967` 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) Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:66— Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:66-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:65-78 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:66` 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) Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:66— Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:66-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:68-81 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:66` 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:656— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:656-669 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:693-706 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:656` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:653` calls `InfoRow` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:691` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:80— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:80-93 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:80-93 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupBodyView.swift:64— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupBodyView.swift:64-74 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:151-161 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupBodyView.swift:64` 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 (11 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:288— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:288-298 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:364-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:122— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:122-132 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:154-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:122` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:192— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:192-202 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:210-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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:192` 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 (11 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMESinglePartnerView.swift:109— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMESinglePartnerView.swift:109-119 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/AfterpayPriceBreakdownView.swift:135-145 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMESinglePartnerView.swift:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift:222— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift:222-232 | StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntentConfirmParams.swift:137-147 — 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 `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift:222` 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 (11 lines × 2) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:652— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:652-662 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:905-915 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:24— StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:24-34 | StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:114-124 — 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 `StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:24` 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmLinkOptions.swift:25— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmLinkOptions.swift:25-35 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmUSBankAccountOptions.swift:18-46 — 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 `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmLinkOptions.swift: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.
Duplicated block (11 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:196— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:196-206 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:255-265 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:632— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:632-642 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:388-398 — before extracting anything, compare `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift` and `StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet.swift:239— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet.swift:239-249 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFlowController+AsyncPublicAPIs.swift:86-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:373— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:373-383 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:75-85 — 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 `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:373` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:93— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:93-103 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:94-104 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:93` 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 (11 lines × 2) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:453— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:453-463 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:491-501 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) StripePayments/StripePaymentsTestUtils/STPFixtures+Swift.swift:290— StripePayments/StripePaymentsTestUtils/STPFixtures+Swift.swift:290-300 | StripePayments/StripePaymentsTestUtils/STPFixtures+Swift.swift:305-315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePaymentsTestUtils/STPFixtures+Swift.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 (11 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:920— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:920-930 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:920-930 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:407— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:407-417 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:116-126 — 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 `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:407` 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.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift:219— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in STPPaymentMethodType.makeImage at line 219. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:525— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CheckoutElementsController.confirmCheckoutSession at line 525. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:248— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in PaymentSheet.confirmAfterHandlingLocalActions at line 248. 2 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift:642— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PayWithLinkViewController.launchFinancialConnections at line 642. 4 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:1476— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in NativeFlowController.swift.CreatePaneViewController at line 1476. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:183— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PaymentSheetFlowControllerViewController.init at line 183. 3 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:471— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PaymentMethodFormViewController.handleCollectBankAccount at line 471. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripeCore/StripeCore/Source/Connections Bindings/HostedAuthUrlBuilder.swift StripeCore/StripeCore/Source/Connections Bindings/HostedAuthUrlBuilder.swift:12— StripeCore/StripeCore/Source/Connections Bindings/HostedAuthUrlBuilder.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in HostedAuthUrlBuilder.build at line 12. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripeCore/StripeCore/Source/Connections Bindings/HostedAuthUrlBuilder.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift:217— Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PlaygroundViewController.requestVerificationSession at line 217. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:16— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in STPAPIClient.makeElementsSessionsParams at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripeCore/StripeCore/Source/Helpers/STPError.swift StripeCore/StripeCore/Source/Helpers/STPError.swift:164— StripeCore/StripeCore/Source/Helpers/STPError.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in NSError.stp_error at line 164. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripeCore/StripeCore/Source/Helpers/STPError.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:153— StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in FinancialConnectionsWebFlowViewController.startAuthenticationSession at line 153. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:146— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AccountPickerViewController.pollAuthSessionAccounts at line 146. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:172— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in STPElementsSession.decodedObject at line 172. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift:53— Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in CryptoOnrampExampleView.body at line 53. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift:244— Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CryptoOnrampFlowCoordinator.advanceToNextStep at line 244. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Example/CryptoOnramp Example/CryptoOnramp Example/KYCInfoView.swift Example/CryptoOnramp Example/CryptoOnramp Example/KYCInfoView.swift:186— Example/CryptoOnramp Example/CryptoOnramp Example/KYCInfoView.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in KYCInfoView.body at line 186. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:34:32 -08:00' --until='2026-11-13 17:34:32 -08:00' --full-history --no-merges -- Example/CryptoOnramp Example/CryptoOnramp Example/KYCInfoView.swift`: 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.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×16
Edited copy of a member (17 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCardParams.swift:151— StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCardParams.swift:151-168 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPSourceCardDetails.swift:118-134 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/UIButton+PaymentSheet.swift:27— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/UIButton+PaymentSheet.swift:27-43 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/SheetNavigationBar.swift:302-321 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:456— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:456-472 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:756-772 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:186— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:186-202 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsControllerLoader.swift:204-220 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:503— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:503-519 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:596-618 — 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) StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:394— StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:394-416 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:433-449 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Views/BottomSheetView.swift:192— StripeIdentity/StripeIdentity/Source/NativeComponents/Views/BottomSheetView.swift:192-209 | StripeIdentity/StripeIdentity/Source/NativeComponents/Views/IdentityFlowView.swift:417-433 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:364— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:364-385 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/VerticalPaymentMethodListViewController.swift:232-248 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+SwiftUI.swift:61— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+SwiftUI.swift:61-77 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+SwiftUI.swift:39-55 — 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) StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:75— StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:75-91 | StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift:111-128 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:73— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:73-91 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:90-106 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentDataSource.swift:46— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentDataSource.swift:46-62 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupDataSource.swift:39-55 — 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) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:97— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:97-113 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:522-538 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:369— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:369-387 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1111-1127 — 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) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPMultiFormTextField.swift:47— StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPMultiFormTextField.swift:47-63 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:23-39 — 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) StripeCore/StripeCoreTestUtils/KeyPathExpectation.swift:13— StripeCore/StripeCoreTestUtils/KeyPathExpectation.swift:13-29 | StripeCore/StripeCoreTestUtils/KeyPathExpectation.swift:31-47 — 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 copy of a member (7 corresponding lines) · ×16
Edited copy of a member (7 corresponding lines) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:44— StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:44-50 | StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:181-187 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:707— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:707-713 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:269-275 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:293— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentMethodsView.swift:293-299 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/VerticalPaymentMethodListViewController.swift:216-222 — 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) StripeUICore/StripeUICore/Source/Elements/PickerField/PickerFieldView.swift:183— StripeUICore/StripeUICore/Source/Elements/PickerField/PickerFieldView.swift:183-194 | StripeUICore/StripeUICore/Source/Elements/TextField/FloatingPlaceholderTextFieldView.swift:81-87 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:607— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:607-613 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:737-743 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:624— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:624-630 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:379-385 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSessionAdapter/CustomerSessionAdapter.swift:117— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSessionAdapter/CustomerSessionAdapter.swift:117-123 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:367-373 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Web/AuthenticationSessionManager.swift:132— StripeFinancialConnections/StripeFinancialConnections/Source/Web/AuthenticationSessionManager.swift:132-141 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Helpers/URL+MatchesSchemeHostAndPath.swift:11-17 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:583— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:583-589 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:332-338 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:591— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:591-597 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:341-347 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:423— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:423-429 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:807-815 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:341— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:341-347 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:410-416 — 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) Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundConfiguration.swift:601— Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundConfiguration.swift:601-607 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollectorUserInterfaceStyle.swift:24-30 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:11— Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:11-17 | Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:19-25 — 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) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:28— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:28-34 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:36-44 — 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) Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:18— Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:18-25 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:14-20 — 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 (14 corresponding lines) · ×15
Edited copy of a member (14 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift:36— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift:36-49 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsParams.swift:46-63 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:216— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:216-232 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:264-277 — 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) Example/Non-Card Payment Examples/Non-Card Payment Examples/KeyboardAvoidingScrollView.swift:93— Example/Non-Card Payment Examples/Non-Card Payment Examples/KeyboardAvoidingScrollView.swift:93-106 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verification/LinkAuthFlowViewController-PresentationController.swift:190-205 — 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) StripePaymentSheet/StripePaymentSheet/Source/Categories/AddressDetails+STPAddress.swift:22— StripePaymentSheet/StripePaymentSheet/Source/Categories/AddressDetails+STPAddress.swift:22-38 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Session+ShippingAddress.swift:31-44 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement.swift:505— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement.swift:505-525 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:114-127 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:28— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:28-43 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionWeChatPayRedirectToApp.swift:21-34 — 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) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:33— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:33-46 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteContainerViewController.swift:48-65 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerNewAccountRowView.swift:92— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerNewAccountRowView.swift:92-105 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AccountPickerRowView.swift:171-184 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:170— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:170-183 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:525-538 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:772— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:772-785 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:802-815 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerAccountLoadErrorView.swift:107— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerAccountLoadErrorView.swift:107-121 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AccountNumberRetrievalErrorView.swift:87-100 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:785— StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:785-800 | StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:413-426 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:770— StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:770-783 | StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:398-411 — 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) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:279— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:279-292 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIViews.swift:112-129 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/LogInSignUpView.swift:121— Example/CryptoOnramp Example/CryptoOnramp Example/LogInSignUpView.swift:121-134 | Example/CryptoOnramp Example/CryptoOnramp Example/LogInSignUpView.swift:136-149 — 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) · ×15
Edited copy of a member (13 corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1080— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1080-1098 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1133-1145 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:409— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:409-422 | StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:249-261 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:315— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:315-330 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:443-455 — 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) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionResult.swift:39— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionResult.swift:39-55 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionResult.swift:57-69 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/CustomPaymentMethod.swift:32— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/CustomPaymentMethod.swift:32-44 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/ExternalPaymentMethod.swift:27-39 — 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) StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:292— StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:292-305 | StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:429-441 — 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) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:1133— Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:1133-1145 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+CheckoutSession.swift:52-66 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionCashAppRedirectToApp.swift:22— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionCashAppRedirectToApp.swift:22-35 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionSwishHandleRedirect.swift:21-33 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPayNowDisplayQrCode.swift:21— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPayNowDisplayQrCode.swift:21-33 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPromptPayDisplayQrCode.swift:21-33 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerAdapter.swift:189— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerAdapter.swift:189-203 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerAdapter.swift:205-217 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/BottomSheet/BottomSheetPresentationController.swift:72— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/BottomSheet/BottomSheetPresentationController.swift:72-86 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/BottomSheet/BottomSheetPresentationController.swift:94-106 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:651— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:651-663 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:409-421 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:342— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:342-354 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:80-92 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/AppAttestationUnavailableError.swift:41— StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/AppAttestationUnavailableError.swift:41-53 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/PaymentMethodKYCRegionChangedError.swift:24-41 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/String+Localized.swift:14— StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/String+Localized.swift:14-26 | StripePaymentSheet/StripePaymentSheet/Source/Categories/String+Localized.swift:36-48 — 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.
Duplicated block (12 lines × 2) Example/AppClipExample/Shared/ContentView.swift:41— Example/AppClipExample/Shared/ContentView.swift:41-52 | Testers/IntegrationTester/IntegrationTester/Source/HelperViews/HelperViews.swift:39-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. Read the line range as the matched WINDOW rather than a finished unit: at `Example/AppClipExample/Shared/ContentView.swift:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Testers/IntegrationTester/IntegrationTester/Source/HelperViews/HelperViews.swift:52` calls `Text` and `Example/AppClipExample/Shared/ContentView.swift:53` 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.
Duplicated block (12 lines × 2) StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:111— StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:111-122 | StripeConnect/StripeConnect/Source/Components/CheckScanningController.swift:82-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:111` 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:431— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:431-442 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:605-616 — 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 `StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:431` 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 (12 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:425— StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:425-436 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:437-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:67— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:67-78 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionRedirectToURL.swift:84-95 — 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 before the matched lines, `StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:66` calls `URL` and `StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionRedirectToURL.swift:83` 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.
Duplicated block (12 lines × 2) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Helpers/STPVisionSupport.swift:13— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Helpers/STPVisionSupport.swift:13-24 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Helpers/STPVisionSupport.swift:13-24 — before extracting anything, compare `StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Helpers/STPVisionSupport.swift` and `StripePaymentSheet/StripePaymentSheet/Source/Internal/Helpers/STPVisionSupport.swift` as WHOLE FILES: 85% 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 (12 lines × 2) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:189— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:189-200 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:260-271 — 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 (12 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:205— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:205-216 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingSaveToLinkVerification/NetworkingSaveToLinkVerificationViewController.swift:207-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:246— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:246-257 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartPaymentButton.swift:46-57 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:246` 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 (12 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:46— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:46-57 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:43-54 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:63— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:63-74 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:66-77 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 105 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:63` 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) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:527— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:527-538 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:527-538 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:116— Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:116-127 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:111-122 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:116` 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 (12 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:135— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:135-146 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:135-146 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:540— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:540-551 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:540-551 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:180— StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:180-184 | StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:218-222 — before extracting anything, compare `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift` and `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:180` 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 (5 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/AddressAutocompleteModels.swift:185— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/AddressAutocompleteModels.swift:185-189 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:89-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:461— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:461-465 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:542-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/UpdatePaymentMethodViewController.swift:244— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/UpdatePaymentMethodViewController.swift:244-248 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/UpdatePaymentMethodViewController.swift:260-264 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/UpdatePaymentMethodViewController.swift:244` 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 (5 lines × 2) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/RegisterWalletRequest.swift:26— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/RegisterWalletRequest.swift:26-30 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/WalletOwnershipChallengeRequest.swift: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 both call sites, so a change lands once.
Duplicated block (5 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:125— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:125-129 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingSaveToLinkVerification/NetworkingSaveToLinkVerificationViewController.swift:138-142 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingSaveToLinkVerification/NetworkingSaveToLinkVerificationViewController.swift:135` calls `showLoadingView` and `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:121` 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.
Duplicated block (5 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:296— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:296-300 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:317-321 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:601— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:601-605 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:731-735 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Common/FinancialConnectionsNavigationController.swift:204— StripeFinancialConnections/StripeFinancialConnections/Source/Common/FinancialConnectionsNavigationController.swift:204-208 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AccountPickerRowView.swift:163-168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) StripeIdentity/StripeIdentity/Source/Elements/IdentityTextButtonElement.swift:49— StripeIdentity/StripeIdentity/Source/Elements/IdentityTextButtonElement.swift:49-53 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/CountryNotListedViewController.swift:100-104 — 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 (5 lines × 2) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:212— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:212-216 | StripeCore/StripeCore/Source/Helpers/STPDeviceUtils.swift:15-19 — 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 (5 lines × 2) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:671— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:671-675 | StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:172-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCard.swift:218— StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCard.swift:218-222 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPSourceCardDetails.swift:125-129 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:248— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:248-252 | Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:477-482 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:248` 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.
Duplicated block (5 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:422— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:422-426 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:1322-1326 — 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.
ClassTooLong: STPPaymentHandler StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:100— ClassTooLong — 1549 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 1149 over it, 3.87× 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: STPPaymentCardTextField StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:19— ClassTooLong — 1390 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 990 over it, 3.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: STPPaymentMethodParams StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:16— ClassTooLong — 682 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 282 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: CaptureTickMarksView StripeIdentity/StripeIdentity/Source/NativeComponents/Views/Selfie/CaptureTickMarksView.swift:12— ClassTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 239 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: STPBankAccountCollector StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:29— ClassTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 235 over it, 1.59× 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: CustomerSavedPaymentMethodsViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:21— ClassTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 198 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: PaymentSheetVerticalViewController StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:14— ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 186 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SelfieScanningView StripeIdentity/StripeIdentity/Source/NativeComponents/Views/Selfie/SelfieScanningView.swift:16— ClassTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 184 over it, 1.46× 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: STPApplePayContext StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:159— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CryptoOnrampCoordinator REDACTED:256— ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 65 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PartnerAuthViewController StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:34— ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 19 over it, 1.05× 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: DocumentCaptureViewController StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:15— ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 18 over it, 1.05× 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: PaymentSheetAnalyticsHelper StripePaymentSheet/StripePaymentSheet/Source/Analytics/PaymentSheetAnalyticsHelper.swift:12— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 10 over it, 1.03× 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: IdentityAnalyticsClient StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:45— ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 5 over it, 1.01× 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.
Change coupling: DocumentScanner.swift ↔ DocumentCaptureViewController.swift StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageScanner/DocumentScanner/DocumentScanner.swift:1— `StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageScanner/DocumentScanner/DocumentScanner.swift` and `StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift` change together 80% of the time (16 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `c8d7c3d0` Remove CaptureCore dependency (#3702); `49cf867d` [Identity] Add blur detector for document scanner (#2873); `d5b7e12c` Log analytics to track image scanning performance (#1250) — run `git show` on any of them.
Change coupling: STPPaymentIntent.swift ↔ STPSetupIntent.swift StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:1— `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift` and `StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift` change together 80% of the time (12 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `e3ceaf35` Fix more NSNumber? to Bool? in API Bindings (#5771); `b3a233e0` Replace optional NSNumber with Bool (#4735); `ceaca9de` Revert "Bindings and update CS & PS to get SPMS from elements/session… — run `git show` on any of them.
Change coupling: STPPaymentIntentConfirmParams.swift ↔ STPSetupIntentConfirmParams.swift StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift:1— `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift` and `StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntentConfirmParams.swift` change together 74% of the time (14 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `79686d93` Add Kakao Pay API bindings (#7052); `38a76509` Add Korean cards API bindings (#7053); `8e9fd1d8` Add Naver Pay API bindings (#7051) — run `git show` on any of them.
Change coupling: STPPaymentMethodParams.swift ↔ STPPaymentHandler.swift StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift:1— `StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodParams.swift` and `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift` change together 65% of the time (30 of the 46 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 30 shared commits counted here, the most recent 3 are `923bbeb3` Add the Stripe balance payment method type (#7639); `2d72f6b4` Add Scalapay API bindings (#7124); `79686d93` Add Kakao Pay API bindings (#7052) — run `git show` on any of them.
Change coupling: FinancialConnectionsSheet.swift ↔ FinancialConnectionsSessionFetcher.swift StripeFinancialConnections/StripeFinancialConnections/Source/FinancialConnectionsSheet.swift:1— `StripeFinancialConnections/StripeFinancialConnections/Source/FinancialConnectionsSheet.swift` and `StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsSessionFetcher.swift` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f13aff64` [BANKCON-11476] Refactor FinancialConnectionsAPIClient to support usi…; `9c97eab2` Renames Host View Controller (#1156); `514d3455` Adds FinancialConnections iOS docs (#1056) (at that commit the file was still `StripeFinancialConnections/StripeFinancialConnections/Source/Host/FinancialConnectionsSessionFetcher.swift`) — run `git show` on any of them.
Change coupling: StripeServiceError.swift ↔ STPError.swift StripeCore/StripeCore/Source/API Bindings/StripeServiceError.swift:1— `StripeCore/StripeCore/Source/API Bindings/StripeServiceError.swift` and `StripeCore/StripeCore/Source/Helpers/STPError.swift` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `211f966f` CS — add generic fallback text when server error messages are missing…; `554b579f` CS — implement private preview error handling (#7408); `56e65857` Include request IDs in live-mode API error descriptions (#7404) — run `git show` on any of them.
Change coupling: PaymentSheetFormFactory+Card.swift ↔ PaymentSheetFormFactoryConfig.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Card.swift:1— `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Card.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactoryConfig.swift` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `ea332fb3` Require flag for funding filter (#5895); `df72a2a2` Filtering funding type in card field (#5880); `a47b7642` opensCardScannerAutomatically implementation (#5431) — run `git show` on any of them.
Change coupling: REDACTED ↔ STPAPIClient+CryptoOnramp.swift REDACTED:1— `REDACTED` and `StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift` change together 59% of the time (13 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `9b60765a` Thread a country hint through crypto onramp platform settings and pay…; `82f6ebd5` Allow crypto onramp Apple Pay before Link authentication (#7183); `eec2c28b` CryptoOnramp SDK: Swapped Terms and Conditions + Terms of Service (#7… — run `git show` on any of them.
Change coupling: STPPaymentMethod.swift ↔ STPPaymentHandler.swift StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethod.swift:1— `StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethod.swift` and `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift` change together 55% of the time (23 of the 42 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 23 shared commits counted here, the most recent 3 are `2d72f6b4` Add Scalapay API bindings (#7124); `79686d93` Add Kakao Pay API bindings (#7052); `9e45cce1` Add SeQura API bindings (#7070) — run `git show` on any of them.
Change coupling: CustomerSheetDataSource.swift ↔ PaymentSheetLoader.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheetDataSource.swift:1— `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheetDataSource.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `b9ef40c4` [Customer Refactor] Authenticate Elements Sessions through the custom…; `7dcc2002` Make API calls to internal endpoint to set defaults (#4588); `171edb3d` Read the default_payment_method field from elements session and use t… — run `git show` on any of them.
Change coupling: FinancialConnectionsAsyncAPIClient.swift ↔ NativeFlowController.swift StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:1— `StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift` and `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `73c091ba` Add generic error pane for FC SDK (#6900); `a6405f19` [link] Refactor FC link brand resolution (#6489); `3a8f641f` Add client_attribution_metadata to payment details and adjust for Lin… — run `git show` on any of them.
Change coupling: PayWithLinkController.swift ↔ PayWithNativeLinkController.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift:1— `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithNativeLinkController.swift` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `c5d12f59` Set Checkout's payment_user_agent with the confirming Checkout Elemen…; `3a5d9b8e` [Native sheets] Enable native sheets for FlowController and Embedded …; `f4d8cc5c` PS MainActor Isolate Link coordinators (#6950) — run `git show` on any of them.
Change coupling: CustomerSheet+API.swift ↔ PaymentSheet+API.swift StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheet+API.swift:1— `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheet+API.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `dc3f8c99` Only attach tokens for card pms (#5846); `0097be55` [v25] Async everywhere pt 2.1 - STPPaymentHandler (#5293); `7399be71` Send top-level in addition to under payment_method_data or payment_me… — run `git show` on any of them.
Change coupling: IdentityAPIClient.swift ↔ VerificationSheetFlowController.swift StripeIdentity/StripeIdentity/Source/API Bindings/IdentityAPIClient.swift:1— `StripeIdentity/StripeIdentity/Source/API Bindings/IdentityAPIClient.swift` and `StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `b4ed817d` [Identity] Implementing `is_stripe` and `skip_success_page` functiona…; `179cbba4` [Identity] Support phone number collection; `9b8696ad` [Identity] Image upload analytic (#1271) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×14
Edited copy of a member (15 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+SEPADebit.swift:13— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+SEPADebit.swift:13-27 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+USBankAccount.swift:13-31 — 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) StripeCardScan/StripeCardScan/Source/CardScan/Extensions/CGRectExtension.swift:11— StripeCardScan/StripeCardScan/Source/CardScan/Extensions/CGRectExtension.swift:11-30 | StripeIdentity/StripeIdentity/Source/NativeComponents/ML/Helpers/NonMaxSuppression.swift:39-53 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:52— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:52-66 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSEPADebit.swift:30-45 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:427— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:427-446 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Saved Payment Method Screen/VerticalSavedPaymentMethodsViewController.swift:531-545 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:229— StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:229-244 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteContainerViewController.swift:278-292 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:401— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:401-415 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:421-442 — 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) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2354— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2354-2368 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2370-2384 — 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) StripeCameraCore/StripeCameraCore/Source/Coordinators/Torch.swift:38— StripeCameraCore/StripeCameraCore/Source/Coordinators/Torch.swift:38-52 | StripeCardScan/StripeCardScan/Source/CardScan/UI/Torch.swift:29-46 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginDataSource.swift:59— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginDataSource.swift:59-73 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupDataSource.swift:57-71 — 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) StripeUICore/StripeUICore/Source/Controls/OneTimeCodeTextField.swift:433— StripeUICore/StripeUICore/Source/Controls/OneTimeCodeTextField.swift:433-447 | StripeUICore/StripeUICore/Source/Controls/OneTimeCodeTextField.swift:449-463 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkLoginWarmup/NetworkingLinkLoginWarmupDataSource.swift:42— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkLoginWarmup/NetworkingLinkLoginWarmupDataSource.swift:42-56 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Success/SuccessDataSource.swift:36-54 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient+Wrappers.swift:425— StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient+Wrappers.swift:425-441 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowDataManager.swift:162-176 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:63— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:63-77 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:66-82 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/PaymentSummaryView.swift:269— Example/CryptoOnramp Example/CryptoOnramp Example/PaymentSummaryView.swift:269-283 | Example/CryptoOnramp Example/CryptoOnramp Example/PaymentView.swift:1106-1121 — 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 (18 corresponding lines) · ×14
Edited copy of a member (18 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenParams.swift:48— StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenParams.swift:48-65 | StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntentConfirmParams.swift:121-147 — 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) StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:173— StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:173-191 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSourceParams.swift:116-133 — 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) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:25— StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:25-42 | StripeApplePay/StripeApplePay/Source/PaymentsCore/API/SetupIntent+API.swift:24-41 — 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) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2632— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2632-2649 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2652-2672 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Klarna.swift:11— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Klarna.swift:11-45 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:955-972 — 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) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:556— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:556-574 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:578-595 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:61— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:61-82 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:150-167 — 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) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:273— StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:273-290 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:305-322 — 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) StripeCardScan/StripeCardScan/Source/CardScan/Extensions/UIImage+pixelBuffer.swift:170— StripeCardScan/StripeCardScan/Source/CardScan/Extensions/UIImage+pixelBuffer.swift:170-187 | StripeCardScan/StripeCardScan/Source/CardScan/Extensions/UIImage+pixelBuffer.swift:190-207 — 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) StripeCardScan/StripeCardScan/Source/CardScan/UI/ScanStats.swift:34— StripeCardScan/StripeCardScan/Source/CardScan/UI/ScanStats.swift:34-51 | StripeCardScan/StripeCardScan/Source/CardScan/Utils/DeviceUtils.swift:33-50 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEMultiPartnerView.swift:48— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEMultiPartnerView.swift:48-65 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMESinglePartnerView.swift:29-47 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:751— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:751-770 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:817-834 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton+PaymentMethodMessagingSublabelView.swift:145— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton+PaymentMethodMessagingSublabelView.swift:145-162 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/BNPLFormHeaderView.swift:89-108 — 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) StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:156— StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:156-174 | StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:175-192 — 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 (9 corresponding lines) · ×14
Edited copy of a member (9 corresponding lines) StripeCore/StripeCore/Source/Helpers/STPAssert.swift:72— StripeCore/StripeCore/Source/Helpers/STPAssert.swift:72-83 | StripeCore/StripeCore/Source/Helpers/STPAssert.swift:87-95 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsParams.swift:77— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsParams.swift:77-86 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodBillingDetails.swift:48-56 — 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) StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:218— StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:218-226 | StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:353-362 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/HTML Confirmation/HTMLConfirmationViewController.swift:34— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/HTML Confirmation/HTMLConfirmationViewController.swift:34-55 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCViewController.swift:32-40 — 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) StripeCardScan/StripeCardScan/Source/CardVerify/ZoomedInCGImage.swift:150— StripeCardScan/StripeCardScan/Source/CardVerify/ZoomedInCGImage.swift:150-160 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/DownloadManager.swift:155-163 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:448— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:448-456 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1184-1193 — 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) StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:160— StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:160-168 | StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/SetupIntent.swift:49-57 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/InlineAddressForm/InlineAddressFormView.swift:46— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/InlineAddressForm/InlineAddressFormView.swift:46-55 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElementView.swift:39-47 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Affirm.swift:10— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Affirm.swift:10-19 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:885-893 — 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) StripePayments/StripePayments/Source/API Bindings/Models/STPFile.swift:90— StripePayments/StripePayments/Source/API Bindings/Models/STPFile.swift:90-98 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:159-169 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift:36— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentConfirmParams.swift:36-44 | StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntentConfirmParams.swift:35-44 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:286— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerPreviewView.swift:286-294 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:737-745 — 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) Example/UI Examples/UI Examples/Source/BrowseViewController.swift:77— Example/UI Examples/UI Examples/Source/BrowseViewController.swift:77-86 | Example/UI Examples/UI Examples/Source/ThemeViewController.swift:53-61 — 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) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:405— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartContentView.swift:405-413 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsView.swift: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.
Duplicated block (13 lines × 2) StripeApplePay/StripeApplePay/Source/Extensions/PKPayment+Stripe.swift:19— StripeApplePay/StripeApplePay/Source/Extensions/PKPayment+Stripe.swift:19-31 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.swift:198-210 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:113— StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:113-125 | StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift:150-162 — before extracting anything, compare `StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift` and `StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:240— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:240-252 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:287-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:283— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:283-295 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:538-550 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:551` calls `constraint` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:296` 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 (13 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:510— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:510-522 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:528-540 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:510` 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:24— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:24-36 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:48-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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:24` 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 (13 lines × 2) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:84— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:84-96 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:122-134 — 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 `StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:84` 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 (13 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1717— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1717-1729 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1803-1815 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1717` 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) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2690— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2690-2702 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2725-2738 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2690` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) StripeCameraCore/StripeCameraCore/Source/Coordinators/Torch.swift:22— StripeCameraCore/StripeCameraCore/Source/Coordinators/Torch.swift:22-36 | StripeCardScan/StripeCardScan/Source/CardScan/UI/Torch.swift:14-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartView.swift:155— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartView.swift:155-167 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:229-241 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartView.swift:155` 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) StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:157— StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:157-169 | StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:176-188 — 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 `StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:157` 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 (13 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:284— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:284-296 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:284-296 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewModel.swift:204— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewModel.swift:204-218 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.swift:470-484 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewModel.swift:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:86— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:86-100 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:115-129 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:86` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:130` calls `complete` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm+Link.swift:101` 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.
Duplicated block (15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:456— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:456-470 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:756-770 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:336— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:336-350 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:721-735 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:403— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:403-417 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:830-844 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:403` 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 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:88— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:88-102 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:128-142 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:88` 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 (15 lines × 2) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:337— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:337-351 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:761-775 — 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 `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:337` 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) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:213— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:213-227 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:284-298 — 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 `StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:213` 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 (15 lines × 2) Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:37— Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:37-51 | Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift:62-76 — before extracting anything, compare `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift` and `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:37` 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) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutPlaygroundView.swift:70— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutPlaygroundView.swift:70-84 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutPlaygroundView.swift:87-101 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutPlaygroundView.swift:70` 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) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift:44— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift:44-58 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift:71-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift: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. Note first that the copies are not typed on the same thing: the declarations holding them bind `spacing` to `8` in one and `4` 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.
Duplicated block (15 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:190— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:190-204 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:1289-1303 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:190` 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· Edited copy of a member (20 corresponding lines) · ×11
Edited copy of a member (20 corresponding lines) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntent.swift:121— StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntent.swift:121-140 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:351-370 — 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) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:17— StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:17-36 | StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:101-122 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1376— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1376-1399 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1597-1616 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:722— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:722-741 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:815-834 — 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) StripeCore/StripeCore/Source/API Bindings/STPAPIClient+FileUpload.swift:80— StripeCore/StripeCore/Source/API Bindings/STPAPIClient+FileUpload.swift:80-99 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient+FileUpload.swift:194-214 — 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) StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:313— StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:313-333 | StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:398-417 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:848— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:848-870 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:872-891 — 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) StripeCameraCore/StripeCameraCore/Source/Coordinators/CameraSession.swift:277— StripeCameraCore/StripeCameraCore/Source/Coordinators/CameraSession.swift:277-296 | StripeCameraCore/StripeCameraCore/Source/Coordinators/CameraSession.swift:299-318 — 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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/ProofOfAddressView.swift:174— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/ProofOfAddressView.swift:174-193 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/SourceOfFundsView.swift:88-108 — 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) StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:52— StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:52-71 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:98-119 — 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) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift:44— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift:44-63 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDetailsComponents.swift:71-92 — 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.
Duplicated block (17 lines × 2) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:20— StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:20-36 | StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:106-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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:106` 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, `StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:105` calls `init` and `StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:19` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 2) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntent.swift:124— StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/PaymentIntent.swift:124-140 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:354-370 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:259— StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:259-275 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:98-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:560— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:560-576 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:578-594 — 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 (17 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:289— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:289-305 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:209-225 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:289` 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 (17 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift:90— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift:90-106 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithNativeLinkController.swift:309-325 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift:90` 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 (17 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:543— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:543-559 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:665-681 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:543` 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 (17 lines × 2) Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:66— Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:66-82 | Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift:67-83 — before extracting anything, compare `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift` and `Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 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 `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:66` 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 (17 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartView.swift:177— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartView.swift:177-193 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:248-264 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartView.swift:177` 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 (17 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:232— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:232-248 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:561-577 — 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 `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:232` 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 (17 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:243— Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:243-259 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:360-376 — 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 (16 lines × 2) StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:127— StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:127-142 | StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift:164-179 — before extracting anything, compare `StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift` and `StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:53— StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:53-68 | StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:73-88 — before extracting anything, compare `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift` and `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:53` 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 (16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Elements/InlineSignup/LinkInlineSignupView.swift:348— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Elements/InlineSignup/LinkInlineSignupView.swift:348-363 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewController.swift:421-436 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Elements/InlineSignup/LinkInlineSignupView.swift:348` 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 (16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:864— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:864-880 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1013-1028 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:864` 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 (16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Initialization.swift:21— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Initialization.swift:21-36 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Initialization.swift:80-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Initialization.swift:21` 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 (16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:97— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:97-112 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:168-183 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:166` calls `validatePaymentMethod` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:94` 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.
Duplicated block (16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:158— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:158-173 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:199-214 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:158` 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 (16 lines × 2) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:392— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:392-407 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:815-830 — 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 `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:392` 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 (16 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:223— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:223-238 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:481-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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:223` 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.
Duplicated block (16 lines × 2) Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:698— Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:698-713 | Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:723-738 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:92— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:92-107 | Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift:416-431 — before extracting anything, compare `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift` and `Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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· Edited copy of a member (6 corresponding lines) · ×9
Edited copy of a member (6 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/TwoOptionSelectorView.swift:37— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/TwoOptionSelectorView.swift:37-42 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/Appearance+FontScaling.swift:20-27 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:644— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:644-649 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:401-406 — 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) StripeCore/StripeCore/Source/Telemetry/FraudDetectionData.swift:31— StripeCore/StripeCore/Source/Telemetry/FraudDetectionData.swift:31-41 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:56-61 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerAdapter.swift:238— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerAdapter.swift:238-245 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSessionAdapter/CustomerSessionAdapter.swift:160-165 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:617— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:617-622 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:371-376 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:61— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:61-67 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/InlineAddressForm/InlineAddressFormState.swift:38-43 — 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) StripeCore/StripeCore/Source/Helpers/STPNumericStringValidator.swift:20— StripeCore/StripeCore/Source/Helpers/STPNumericStringValidator.swift:20-25 | StripePayments/StripePayments/Source/Helpers/STPCardValidator.swift:67-73 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheetConfiguration.swift:145— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheetConfiguration.swift:145-150 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentElementConfiguration.swift:72-77 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNetBankingParams.swift:23— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNetBankingParams.swift:23-28 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayByBankParams.swift:23-28 — 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· Edited copy of a member (31 corresponding lines) · ×7
Edited copy of a member (31 corresponding lines) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldFormatter.swift:45— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldFormatter.swift:45-81 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:77-162 — 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.
Edited copy of a member (31 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:109— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:109-139 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:141-171 — 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.
Edited copy of a member (31 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift:80— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithLinkController.swift:80-110 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/PayWithNativeLinkController.swift:299-329 — 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.
Edited copy of a member (31 corresponding lines) StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:420— StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:420-450 | StripeIdentity/StripeIdentity/Source/Analytics/IdentityAnalyticsClient.swift:453-487 — 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.
Edited copy of a member (31 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+CheckoutSession.swift:138— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+CheckoutSession.swift:138-170 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+CheckoutSession.swift:172-202 — 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.
Edited copy of a member (31 corresponding lines) StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:74— StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:74-104 | StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:169-199 — 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.
Edited copy of a member (31 corresponding lines) Example/FinancialConnections Example/FinancialConnections Example/WebViewViewController.swift:97— Example/FinancialConnections Example/FinancialConnections Example/WebViewViewController.swift:97-127 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:130-172 — 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 copy of a member (24 corresponding lines) · ×7
Edited copy of a member (24 corresponding lines) Example/AppClipExample/Shared/BackendModel.swift:42— Example/AppClipExample/Shared/BackendModel.swift:42-65 | Testers/IntegrationTester/IntegrationTester/Source/Models/BackendModel.swift:53-83 — 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.
Edited copy of a member (24 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/FormElement+Link.swift:36— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/FormElement+Link.swift:36-59 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Extensions/FormElement+Link.swift:65-88 — 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.
Edited copy of a member (24 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/InstantDebitsPaymentMethodElement.swift:284— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/InstantDebitsPaymentMethodElement.swift:284-322 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/USBankAccountPaymentMethodElement.swift:213-236 — 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.
Edited copy of a member (24 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionPickerViewController.swift:219— StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionPickerViewController.swift:219-249 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionPickerViewController.swift:251-274 — 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.
Edited copy of a member (24 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:289— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:289-312 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:209-232 — 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.
Edited copy of a member (24 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/LinkSheetContainer.swift:31— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/LinkSheetContainer.swift:31-54 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetContainer.swift:47-74 — 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.
Edited copy of a member (24 corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:179— StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:179-205 | StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:327-350 — 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 copy of a member (30 corresponding lines) · ×7
Edited copy of a member (30 corresponding lines) StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSpecProvider.swift:28— StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSpecProvider.swift:28-57 | StripeUICore/StripeUICore/Source/Elements/Factories/BSB/BSBNumberProvider.swift:22-59 — 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.
Edited copy of a member (30 corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:67— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:67-96 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:99-134 — 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.
Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:275— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:275-309 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:311-340 — 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.
Edited copy of a member (30 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:51— StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:51-80 | StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:71-100 — 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.
Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:482— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:482-511 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1117-1149 — 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.
Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:238— StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:238-267 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:269-303 — 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.
Edited copy of a member (30 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:391— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:391-421 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:819-848 — 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 copy of a member (21 corresponding lines) · ×7
Edited copy of a member (21 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:135— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:135-156 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:131-151 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:481— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:481-501 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:641-662 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:153— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:153-173 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:210-231 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupViewController.swift:266— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupViewController.swift:266-290 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:606-626 — 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) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:207— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPInputTextField.swift:207-227 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:278-298 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerDataSource.swift:61— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerDataSource.swift:61-85 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AttachLinkedPaymentAccountDataSource.swift:34-54 — 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) StripeCore/StripeCore/Source/Connections Bindings/LinkConsumerIncentive.swift:15— StripeCore/StripeCore/Source/Connections Bindings/LinkConsumerIncentive.swift:15-36 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ConfirmationChallenge/PassiveCaptchaChallenge.swift:29-49 — 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 (22 corresponding lines) · ×7
Edited copy of a member (22 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:827— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:827-848 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:850-871 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/STPAPIClient+Address.swift:22— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/STPAPIClient+Address.swift:22-43 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/STPAPIClient+Address.swift:52-73 — 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) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:457— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:457-481 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:878-899 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:738— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:738-759 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:761-791 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:36— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:36-59 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:62-83 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/PhoneCountryCodeSelectorView.swift:183— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/PhoneCountryCodeSelectorView.swift:183-204 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/PhoneTextField.swift:239-265 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:203— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:203-233 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:469-490 — 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) StripeIssuing/StripeIssuing/Source/STPEphemeralKey.swift:37— StripeIssuing/StripeIssuing/Source/STPEphemeralKey.swift:37-80 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethod.swift:295-493 | StripePayments/StripePayments/Source/API Bindings/Models/STPFile.swift:106-133 | StripePayments/StripePayments/Source/API Bindings/Models/STPToken.swift:104-132 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:204— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:204-239 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/CVCReconfirmationViewController.swift:84-118 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:299-345 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:221-262 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:389— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:389-425 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:792-824 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1129-1162 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Saved Payment Method Screen/VerticalSavedPaymentMethodsViewController.swift:497-529 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:29— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:29-91 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift:39-102 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithRadioView.swift:64-112 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFloating.swift:87-131 — 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) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:129— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:129-142 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:426-439 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift:129-142 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:426-439 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:108— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:108-121 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:146-161 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:159-172 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:128-142 — 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 (3 corresponding lines) · ×6
Edited copy of a member (3 corresponding lines) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/ProofOfAddressViewController.swift:22— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/ProofOfAddressViewController.swift:22-24 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/ProofOfAddressViewController.swift:34-42 — 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) StripeUICore/StripeUICore/Source/Elements/Checkbox/CheckboxElement.swift:67— StripeUICore/StripeUICore/Source/Elements/Checkbox/CheckboxElement.swift:67-69 | StripeUICore/StripeUICore/Source/Elements/TextField/TextFieldElement.swift:250-252 — 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) StripeCardScan/StripeCardScan/Source/CardScan/Utils/AppInfoUtils.swift:32— StripeCardScan/StripeCardScan/Source/CardScan/Utils/AppInfoUtils.swift:32-34 | StripeCardScan/StripeCardScan/Source/CardScan/Utils/DeviceUtils.swift:52-54 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Internal.swift:116— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Internal.swift:116-118 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController.swift:325-327 — 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCard.swift:50— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCard.swift:50-52 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCard.swift:63-66 — 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) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:117— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift:117-120 | StripePayments/StripePayments/Source/Internal/IntentConfirmationChallengeViewController.swift:330-332 — 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.
Duplicated block (22 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:768— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:768-789 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:593-614 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:21— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:21-42 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:44-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:83— StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:83-104 | StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:178-199 — 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 `StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:83` 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 (22 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:248— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:248-269 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:502-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:248` 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 (22 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:69— Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:69-90 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:117-138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:486— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:486-507 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:526-547 — 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 (20 lines × 2) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedSSDBox.swift:16— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedSSDBox.swift:16-35 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/DetectedSSDOcrBox.swift:16-35 — 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 (20 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Analytics/Experiments/LinkGlobalHoldback.swift:25— StripePaymentSheet/StripePaymentSheet/Source/Analytics/Experiments/LinkGlobalHoldback.swift:25-44 | StripePaymentSheet/StripePaymentSheet/Source/Analytics/Experiments/LinkGlobalHoldbackAA.swift:25-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.
Duplicated block (20 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElementView.swift:54— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElementView.swift:54-73 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/InlineAddressForm/InlineAddressFormView.swift:62-81 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElementView.swift:54` 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 (20 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:308— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:308-327 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:853-872 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:308` 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 (20 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:137— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:137-156 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:209-228 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:137` 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, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:207` calls `validatePaymentMethod` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:134` 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.
Duplicated block (20 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:89— Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:89-108 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift:49-68 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:89` 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.
Swallowed exception (caught, then discarded) REDACTED:45— `rescue => e` 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/CustomPaymentMethod.swift:41— `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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/ExternalPaymentMethod.swift:36— `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) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:229— `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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/ProofOfAddressView.swift:187— `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) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/SourceOfFundsView.swift:102— `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.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×5
Edited copy of a member (32 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:275— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:275-306 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:530-562 — 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) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:405— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:405-437 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:703-734 — 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) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:354— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:354-385 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:777-808 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/FinancialConnectionsFont.swift:67— StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/FinancialConnectionsFont.swift:67-98 | StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/FinancialConnectionsFont.swift:114-145 — 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) StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:145— StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:145-176 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:189-223 — 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 copies of one member (3 members, 14+ corresponding lines) · ×5
Edited copies of one member (3 members, 14+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenClientContext.swift:69— StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenClientContext.swift:69-82 | StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenParams.swift:74-87 | StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntentConfirmParams.swift:177-191 — 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.
Edited copies of one member (3 members, 14+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionKonbiniDisplayDetails.swift:29— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionKonbiniDisplayDetails.swift:29-42 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionOXXODisplayDetails.swift:53-68 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionVerifyWithMicrodeposits.swift: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 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.
Edited copies of one member (3 members, 14+ corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:49— StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:49-62 | StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:64-77 | StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:115-128 — 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.
Edited copies of one member (3 members, 14+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheet+SwiftUI.swift:15— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheet+SwiftUI.swift:15-28 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+SwiftUI.swift:20-33 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+SwiftUI.swift:39-55 — 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.
Edited copies of one member (3 members, 14+ corresponding lines) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:49— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:49-62 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:64-83 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:98-119 — 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 (3 members, 22+ corresponding lines) · ×5
Edited copies of one member (3 members, 22+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:15— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:15-36 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:38-60 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+BankDebits.swift:62-89 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:346— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:346-367 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:388-410 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:279-306 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentFileUploadViewController+Strings.swift:33— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentFileUploadViewController+Strings.swift:33-54 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentFileUploadViewController+Strings.swift:56-77 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentFileUploadViewController+Strings.swift:79-100 — 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:173— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:173-198 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:200-221 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:223-244 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:894— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:894-915 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:929-950 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:964-985 — 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 copies of one member (3 members, 16+ corresponding lines) · ×5
Edited copies of one member (3 members, 16+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:39— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:39-57 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:46-64 | StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountAddress.swift:45-60 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:127— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:127-142 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodBillingDetails.swift:102-117 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardWallet.swift:87-102 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionBoletoDisplayDetails.swift:26— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionBoletoDisplayDetails.swift:26-41 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionMultibancoDisplayDetails.swift:28-44 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPixDisplayQrCode.swift:31-46 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:487— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:487-504 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:507-523 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:526-541 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentLastPaymentError.swift:126— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentLastPaymentError.swift:126-145 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetails.swift:51-66 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:59-76 — 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 copies of one member (3 members, 15+ corresponding lines) · ×5
Edited copies of one member (3 members, 15+ corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:81— StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:81-95 | StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:97-111 | StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift:130-144 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1641— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1641-1656 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1673-1687 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1704-1721 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAUBECSDebit.swift:49— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAUBECSDebit.swift:49-63 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionBoletoDisplayDetails.swift:45-59 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionMultibancoDisplayDetails.swift:48-64 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:325— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:325-340 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:357-374 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:413-427 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Intent.swift:99— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Intent.swift:99-115 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Intent.swift:117-133 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:614-628 — 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, 8+ corresponding lines) · ×5
Edited copies of one member (3 members, 8+ corresponding lines) StripeCore/StripeCore/Source/Connections Bindings/BillingAddress.swift:19— StripeCore/StripeCore/Source/Connections Bindings/BillingAddress.swift:19-35 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Address.swift:42-56 | StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSectionElement.swift:60-67 — 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.
Edited copies of one member (3 members, 8+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBacsDebit.swift:25— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBacsDebit.swift:25-35 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKrCard.swift:22-29 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgCard.swift:23-30 — 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.
Edited copies of one member (3 members, 8+ corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:382— StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:382-389 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:168-175 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:177-186 — 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.
Edited copies of one member (3 members, 8+ corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:130— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:130-137 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:163-170 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:174-182 — 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.
Edited copies of one member (3 members, 8+ corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:778— Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:778-786 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:803-810 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:811-818 — 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· Edited copy of a member (5 corresponding lines) · ×5
Edited copy of a member (5 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:202— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:202-206 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/Button+Extensions.swift:217-221 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:834— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:834-845 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFlowController.swift:1069-1073 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:81— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:81-85 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:78-82 — 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) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteSecureAuthFlowViewController.swift:29— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteSecureAuthFlowViewController.swift:29-38 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/SepaMandateViewController.swift:47-51 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Internal.swift:85— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Internal.swift:85-89 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEMultiPartnerView.swift:38-42 — 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 (4 corresponding lines) · ×5
Edited copy of a member (4 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:309— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:309-312 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:417-424 — 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) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:59— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:59-62 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupViewController.swift:54-57 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:40— Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:40-45 | Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Crypto_V1.swift:26-29 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:47— Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:47-50 | Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Crypto_V1.swift:31-35 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:52— Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Auth_V1.swift:52-55 | Example/CryptoOnramp Example/CryptoOnramp Example/Example API Bindings/APIClient+Crypto_V1.swift:11-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.
Duplicated block (14–15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:430— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:430-443 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1165-1179 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:430` 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 first that the copies are not typed on the same thing: the declarations holding them bind `paymentMethod` to `StripePayments.STPPaymentMethod` in one and `STPPaymentMethod` 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.
Duplicated block (14–15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+iDEAL.swift:11— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+iDEAL.swift:11-25 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:759-772 — 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 (14–15 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:487— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:487-501 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:594-607 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:487` 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–15 lines × 2) Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift:20— Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift:20-34 | Testers/IntegrationTester/IntegrationTester/Source/Views/CardView.swift:20-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift:20` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (14–15 lines × 2) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:87— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:87-100 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:107-121 — before extracting anything, compare `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift` and `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 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 `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:87` 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 (11 lines × 3) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:285— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:285-295 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:541-551 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:663-673 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/InstantBankPaymentsController.swift:285` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:36— Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:36-46 | Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift:61-71 | Testers/IntegrationTester/IntegrationTester/Source/Views/SEPADebitView.swift:43-53 — before extracting anything, compare `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift` and `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:36` 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 × 3) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginDataSource.swift:135— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginDataSource.swift:135-145 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkLoginWarmup/NetworkingLinkLoginWarmupDataSource.swift:87-97 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupDataSource.swift:139-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (11 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:252— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:252-262 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:309-319 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:306-316 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:252` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:74— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:74-84 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:94-104 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:110-120 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:74` 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 after the matched lines, `Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:122` calls `deferredSwitchDidChangeValue`, `loadBackend` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:108` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:329— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:329-338 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:375-382 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:420-427 — 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 `StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:329` 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 × 3) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:439— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:439-446 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:843-850 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1175-1182 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:439` 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 × 3) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:50— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:50-57 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:57-64 | StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountAddress.swift:53-60 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddress.swift:50` 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 (8 lines × 3) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:146— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:146-153 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+Card.swift:65-72 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+Link.swift:54-61 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:146` 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 (8 lines × 3) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:146— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:146-153 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/LinkSignupFormView.swift:215-222 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupBodyView.swift:149-156 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard stripe3ds2-support/doc/html/css/style.css:1— `.method-title` moves (`transition: margin-left .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard stripe3ds2-support/doc/html/css/style.css:1— `.method-info` moves (`transition: height .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard stripe3ds2-support/doc/html/css/scss/_object.scss:14— `.method-title` moves (`transition: margin-left .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard stripe3ds2-support/doc/html/css/scss/_object.scss:31— `.method-info` moves (`transition: height .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×4
Edited copy of a member (40 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:16— StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:16-62 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController+Strings.swift:18-57 — These two members are one piece of code written twice and then edited apart: 40 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 (40 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:306— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:306-347 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:850-889 — These two members are one piece of code written twice and then edited apart: 40 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 (40 corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:257— StripeCardScan/StripeCardScan/Source/CardScan/UI/SimpleScanViewController.swift:257-299 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:94-133 — These two members are one piece of code written twice and then edited apart: 40 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 (40 corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:249— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:249-288 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:306-345 — These two members are one piece of code written twice and then edited apart: 40 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 (27 corresponding lines) · ×4
Edited copy of a member (27 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:437— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:437-463 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:695-724 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:380— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:380-406 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:608-637 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationDataSource.swift:37— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationDataSource.swift:37-63 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingSaveToLinkVerification/NetworkingSaveToLinkVerificationDataSource.swift:31-57 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:305— Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:305-331 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIEmbeddedPaymentElement.swift:94-125 — These two members are one piece of code written twice and then edited apart: 27 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) · ×4
Edited copy of a member (25 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AttributedLabel.swift:48— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AttributedLabel.swift:48-74 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AttributedTextView.swift:211-235 — 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.
Edited copy of a member (25 corresponding lines) StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:110— StripeConnect/StripeConnect/Source/Components/AccountOnboardingController.swift:110-134 | StripeConnect/StripeConnect/Source/Components/CheckScanningController.swift:76-105 — 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.
Edited copy of a member (25 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/FinancialConnectionsSDK/FinancialConnectionsSDKImplementation.swift:100— StripeFinancialConnections/StripeFinancialConnections/Source/FinancialConnectionsSDK/FinancialConnectionsSDKImplementation.swift:100-126 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteContainerViewController.swift:252-276 — 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.
Edited copy of a member (25 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElementView.swift:49— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Payment Element/PaymentElementView.swift:49-73 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/InlineAddressForm/InlineAddressFormView.swift:57-81 — 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 copy of a member (19 corresponding lines) · ×4
Edited copy of a member (19 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:427— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:427-446 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1164-1182 — 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) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift:110— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift:110-128 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift:131-149 — 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) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/SSDOcrDetect.swift:96— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/SSDOcrDetect.swift:96-114 | StripeCardScan/StripeCardScan/Source/CardVerify/UxAnalyzer.swift:66-84 — 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) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:579— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:579-597 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:655-675 — 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.
Duplicated block (21 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:232— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:232-252 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:279-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:232` 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 (21 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:81— Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:81-101 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:79-99 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:81` 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 (21 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:30— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:30-50 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:112-132 — 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 `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlayground.swift:30` 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 (21 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:33— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:33-53 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:37-57 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:218— StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:218-235 | StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift:249-266 — before extracting anything, compare `StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift` and `StripeUICore/StripeUICore/Source/Controls/ActivityIndicator.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardWalletMasterpass.swift:48— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardWalletMasterpass.swift:48-65 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardWalletVisaCheckout.swift:29-46 — 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 (18 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:52— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:52-69 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:103-120 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:52` 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 (18 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:595— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:595-612 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:666-683 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:595` 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, `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:594` calls `paymentSheet` and `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlayground.swift:665` 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.
Duplicated block (5 lines × 4) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:86— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:86-90 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:102-106 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:156-160 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:173-177 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:86` 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 (5 lines × 4) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:126— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:126-130 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:142-146 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:197-201 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:214-218 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:126` 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 (5 lines × 4) StripeIssuing/StripeIssuing/Source/STPEphemeralKey.swift:37— StripeIssuing/StripeIssuing/Source/STPEphemeralKey.swift:37-45 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethod.swift:295-303 | StripePayments/StripePayments/Source/API Bindings/Models/STPFile.swift:106-115 | StripePayments/StripePayments/Source/API Bindings/Models/STPToken.swift:104-108 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripeIssuing/StripeIssuing/Source/STPEphemeralKey.swift: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 4) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:220— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:220-224 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:908-912 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift:220-224 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:908-912 — `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:204— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:204-212 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:236-244 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:228-236 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:87— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:87-95 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:124-132 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:145-153 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:102— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:102-110 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:123-131 | Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift:444-452 — before extracting anything, compare `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift` and `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:280— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:280-288 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:311-319 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:346-354 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:356` calls `UIFont`, `monospacedSystemFont` and `Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:290` 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.
D10 · Test Quality· Test project verifies nothing · ×3
Test project verifies nothing: Extensions StripeConnect/StripeConnectTests/Internal/Extensions/URL+ExtensionTests.swift:12— No conventional assertion call was detected in 1 of 1 tests in `Extensions` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Test project verifies nothing: IntegrationTesterUITests Testers/IntegrationTester/IntegrationTesterUITests/IntegrationTesterUITests.swift:47— No conventional assertion call was detected in 1 of 1 tests in `IntegrationTesterUITests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Test project verifies nothing: PaymentsCore StripeApplePay/StripeApplePayTests/PaymentsCore/PaymentIntentCodableTest.swift:9— No conventional assertion call was detected in 1 of 1 tests in `PaymentsCore` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×3
Edited copy of a member (29 corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:569— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:569-598 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:979-1007 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:583— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:583-612 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:351-379 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageUploaders/IdentityImageUploader.swift:52— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageUploaders/IdentityImageUploader.swift:52-82 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageUploaders/IdentityImageUploader.swift:84-112 — These two members are one piece of code written twice and then edited apart: 29 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 (28 corresponding lines) · ×3
Edited copy of a member (28 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:419— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:419-446 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetController.swift:580-620 — 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.
Edited copy of a member (28 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift:150— StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift:150-179 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/NetworkingOTPView/NetworkingOTPView.swift:146-173 — 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.
Edited copy of a member (28 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:552— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:552-579 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:581-608 — 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 (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:581— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:581-607 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/STPApplePayContext+PaymentSheet.swift:150-175 — 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) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:644— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:644-669 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:675-706 — 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) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:149— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:149-178 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:170-195 — 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 copies of one member (4 members, 20+ corresponding lines) · ×3
Edited copies of one member (4 members, 20+ corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:122— StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:122-144 | StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:147-169 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/API Client/FCLiteApiClient.swift:34-53 | StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/API Client/FCLiteApiClient.swift:55-74 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 20+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:136— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:136-155 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+LinkAccountSession.swift:157-176 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1887-1906 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1913-1932 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 20+ corresponding lines) Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift:16— Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift:16-38 | Testers/IntegrationTester/IntegrationTester/Source/Views/CardSetupIntentsView.swift:16-35 | Testers/IntegrationTester/IntegrationTester/Source/Views/CardView.swift:16-35 | Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodView.swift:17-36 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×3
Edited copies of one member (4 members, 16+ corresponding lines) Example/AppClipExample/Shared/ContentView.swift:41— Example/AppClipExample/Shared/ContentView.swift:41-56 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIViews.swift:35-51 | Testers/IntegrationTester/IntegrationTester/Source/HelperViews/HelperViews.swift:15-32 | Testers/IntegrationTester/IntegrationTester/Source/HelperViews/HelperViews.swift:39-56 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 16+ corresponding lines) StripeConnect/StripeConnect/Source/Components/AccountManagementViewController.swift:28— StripeConnect/StripeConnect/Source/Components/AccountManagementViewController.swift:28-46 | StripeConnect/StripeConnect/Source/Components/PaymentDetailsViewController.swift:19-34 | StripeConnect/StripeConnect/Source/Components/PaymentsViewController.swift:24-42 | StripeConnect/StripeConnect/Source/Components/PayoutsViewController.swift:15-30 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 16+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:708— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:708-724 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:961-977 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1191-1206 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1779-1795 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 14+ corresponding lines) · ×3
Edited copies of one member (5 members, 14+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:554— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:554-567 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:843-856 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1758-1771 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1803-1817 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1831-1849 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 14+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionCashAppRedirectToApp.swift:50— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionCashAppRedirectToApp.swift:50-63 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPayNowDisplayQrCode.swift:48-61 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionPromptPayDisplayQrCode.swift:48-61 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionSwishHandleRedirect.swift:48-62 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionWeChatPayRedirectToApp.swift:49-62 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 14+ corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:87— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:87-103 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:69-84 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:89-104 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:89-104 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:107-120 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×3
Edited copies of one member (3 members, 4+ corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionSearchBar.swift:287— StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionSearchBar.swift:287-293 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AttributedTextView.swift:197-205 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:284-287 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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, 4+ corresponding lines) StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/FetchAppInfoMessageHandler.swift:16— StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/FetchAppInfoMessageHandler.swift:16-19 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/FetchClientSecretMessageHandler.swift:13-16 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/FetchInitParamsMessageHandler.swift:18-21 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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, 4+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:24— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:24-27 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithRadioView.swift:23-26 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFloating.swift:46-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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.
Duplicated block (31 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:177— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:177-207 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:172-202 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:52— StripeApplePay/StripeApplePay/Source/PaymentsCore/API/PaymentIntent+API.swift:52-82 | StripeApplePay/StripeApplePay/Source/PaymentsCore/API/SetupIntent+API.swift:51-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `completion` to `@escaping PaymentIntentCompletionBlock` in one and `@escaping SetupIntentCompletionBlock` 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.
Duplicated block (31 lines × 2) Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:34— Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:34-64 | Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift:35-65 — before extracting anything, compare `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift` and `Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:436— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:436-454 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:736-754 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:592— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:592-610 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:360-378 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:592` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:153— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:153-171 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:176-194 — before extracting anything, compare `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift` and `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:173` calls `setNeedsStatusBarAppearanceUpdate` and `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:150` 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 (15–16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:135— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:135-149 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:208-223 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:135` 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.
Duplicated block (15–16 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:240— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:240-254 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:358-373 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 2) Example/CryptoOnramp Example/CryptoOnramp Example/AttachWalletAddressView.swift:71— Example/CryptoOnramp Example/CryptoOnramp Example/AttachWalletAddressView.swift:71-85 | Example/CryptoOnramp Example/CryptoOnramp Example/WalletOwnershipVerificationSheet.swift:113-128 — 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 `Example/CryptoOnramp Example/CryptoOnramp Example/AttachWalletAddressView.swift:71` 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–14 lines × 2) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/FCLiteImplementation.swift:16— StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/FCLiteImplementation.swift:16-28 | StripePayments/StripePayments/Source/Internal/Helpers/ConnectionsSDKAvailability.swift:101-114 — 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 `StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/FCLiteImplementation.swift:16` 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 (13–14 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1504— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1504-1516 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1533-1546 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1504` 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 (13–14 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:154— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:154-167 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:187-199 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBancontactParams.swift:15— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBancontactParams.swift:15-21 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodEPSParams.swift:15-21 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGrabPayParams.swift:16-22 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTwintParams.swift:14-20 — 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 (7 lines × 4) StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:77— StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:77-84 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:109-116 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/STPSource.swift:138-145 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:103-109 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 4) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:371— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:371-377 | Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:404-410 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:73-79 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:113-119 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×3
Edited copy of a member (44 corresponding lines) Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:81— Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:81-127 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:79-122 — These two members are one piece of code written twice and then edited apart: 44 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 (44 corresponding lines) Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:65— Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:65-108 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:66-118 — These two members are one piece of code written twice and then edited apart: 44 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 (44 corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:395— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:395-438 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:525-571 — These two members are one piece of code written twice and then edited apart: 44 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.
Duplicated block (5 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:666— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:666-671 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:710-714 | Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:774-778 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:666` 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 (5 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:373— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:373-377 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:210-214 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:75-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:271— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:271-275 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:303-307 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:337-341 — 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.
Swallowed exception (empty catch) StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:166— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:269— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:297— 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.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
FixmeComment StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:1093— // FIXME: Import from %S/Inputs/Coding/SharedTypes.swift somehow. — 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 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:1213— // FIXME: This property is present only in order to test the expected result of Codable synthesis in the compiler. — 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.
D4 · Code Duplication· Edited copy of a member (66 corresponding lines) · ×2
Edited copy of a member (66 corresponding lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:387— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:387-454 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:810-875 — These two members are one piece of code written twice and then edited apart: 66 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 (66 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:356— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:356-421 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:94-159 — These two members are one piece of code written twice and then edited apart: 66 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 (50 corresponding lines) · ×2
Edited copy of a member (50 corresponding lines) StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:37— StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:37-86 | StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:90-141 — These two members are one piece of code written twice and then edited apart: 50 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 (50 corresponding lines) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionAPI.swift:27— StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionAPI.swift:27-76 | StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PredictionUtilOcr.swift:16-66 — These two members are one piece of code written twice and then edited apart: 50 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) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:630— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:630-679 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:888-932 — 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) Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:68— Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:68-114 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:116-160 — 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 copy of a member (48 corresponding lines) · ×2
Edited copy of a member (48 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:91— StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:91-138 | StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:113-173 — These two members are one piece of code written twice and then edited apart: 48 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 (48 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AccountNumberRetrievalErrorView.swift:16— StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AccountNumberRetrievalErrorView.swift:16-70 | StripeFinancialConnections/StripeFinancialConnections/Source/Web/ContinueStateView.swift:19-66 — These two members are one piece of code written twice and then edited apart: 48 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 (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:19— Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:19-51 | Testers/IntegrationTester/IntegrationTester/Source/Views/SEPADebitView.swift:19-61 — 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) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2675— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2675-2707 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2710-2743 — 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 (38 corresponding lines) · ×2
Edited copy of a member (38 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:843— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:843-880 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:987-1028 — These two members are one piece of code written twice and then edited apart: 38 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 (38 corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:384— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift:384-421 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:338-378 — These two members are one piece of code written twice and then edited apart: 38 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, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenClientContext.swift:44— StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenClientContext.swift:44-60 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:133-154 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccountParams.swift:89-105 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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, 17+ corresponding lines) StripeUICore/StripeUICore/Source/Controls/Button.swift:402— StripeUICore/StripeUICore/Source/Controls/Button.swift:402-418 | StripeUICore/StripeUICore/Source/Controls/Button.swift:420-436 | StripeUICore/StripeUICore/Source/Controls/Button.swift:438-454 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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) · ×2
Edited copy of a member (23 corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:62— StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionAlipayHandleRedirect.swift:62-86 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentActionRedirectToURL.swift:81-103 — 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.
Edited copy of a member (23 corresponding lines) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:439— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:439-461 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:463-488 — 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 copies of one member (3 members, 19+ corresponding lines) · ×2
Edited copies of one member (3 members, 19+ corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDiagnostics.swift:25— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutSessionDiagnostics.swift:25-43 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/AppAttestationError.swift:55-75 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/AppAttestationError.swift:77-97 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 19+ corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:219— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:219-237 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:261-279 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:282-300 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×2
Edited copies of one member (4 members, 12+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1442— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1442-1456 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1495-1506 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1636-1655 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:1663-1680 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 12+ corresponding lines) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:125— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:125-140 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:228-239 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:269-286 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:339-356 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×2
Edited copies of one member (4 members, 9+ corresponding lines) StripePayments/StripePayments/Source/Internal/IntentConfirmationChallengeViewController.swift:427— StripePayments/StripePayments/Source/Internal/IntentConfirmationChallengeViewController.swift:427-435 | StripePayments/StripePayments/Source/Internal/IntentConfirmationChallengeViewController.swift:437-445 | StripePayments/StripePayments/Source/Internal/IntentConfirmationChallengeViewController.swift:447-455 | StripePayments/StripePayments/Source/Internal/IntentConfirmationChallengeViewController.swift:457-465 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2812— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2812-2820 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2822-2830 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2832-2841 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2843-2852 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×2
Edited copies of one member (3 members, 3+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift:315— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift:315-317 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/HTML Confirmation/HTMLConfirmationViewController.swift:57-59 | StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCViewController.swift:42-44 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 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, 3+ corresponding lines) StripeUICore/StripeUICore/Source/Elements/ContainerElement.swift:75— StripeUICore/StripeUICore/Source/Elements/ContainerElement.swift:75-77 | StripeUICore/StripeUICore/Source/Elements/Element.swift:107-109 | StripeUICore/StripeUICore/Source/Elements/Section/SectionElement.swift:149-151 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 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) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCContentViewController.swift:42— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCContentViewController.swift:42-46 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:805-809 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheet3DS2ViewController.swift:34-38 — 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) Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift:286— Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampFlowCoordinator.swift:286-291 | Example/FinancialConnections Example/FinancialConnections Example/Playground/helpers/UIAlertController+Extensions.swift:14-32 | Example/StripeConnectExample/StripeConnectExample/MainViewController.swift:245-249 — 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.
Duplicated block (26 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:64— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:64-89 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:92-117 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/STPAPIClient+Link.swift:64` 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 (26 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:193— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:193-218 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift:193-218 — `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11–12 lines × 2) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:1016— StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:1016-1027 | StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:1098-1108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:1016` 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 (11–12 lines × 2) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:94— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:94-105 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:297-307 — 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 `StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:94` 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 `completion` to `STPTokenCompletionBlock?` in one and `STPTokenCompletionBlock? = nil` 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.
Duplicated block (10–11 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:867— Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:867-877 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Shipping Address Element/ShippingAddressElement+AddressViewController.swift:20-29 — 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 `Example/PaymentSheet Example/PaymentSheet Example/Checkout Playground/CheckoutCartViewController.swift:867` 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. 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 (10–11 lines × 2) StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:19— StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:19-28 | StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:71-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 `StripePayments/StripePaymentsTestUtils/STPTestingAPIClient+Swift.swift:19` 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.
Duplicated block (9–10 lines × 3) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:340— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:340-349 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:725-734 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:491-499 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:340` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:179— StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:179-188 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccount.swift:159-167 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPCard.swift:250-258 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 3) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:415— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:415-428 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:836-850 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:941-950 — 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 `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:415` 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 (10 lines × 3) Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:19— Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:19-28 | Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift:22-31 | Testers/IntegrationTester/IntegrationTester/Source/Views/SEPADebitView.swift:19-28 — before extracting anything, compare `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift` and `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:202— StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:202-210 | StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:224-233 — 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 `StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/ConsumerSession.swift:202` 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 (9–10 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEPromotionTextView.swift:51— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEPromotionTextView.swift:51-59 | StripeUICore/StripeUICore/Source/Views/LinkOpeningTextView.swift:47-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `StripeUICore/StripeUICore/Source/Views/LinkOpeningTextView.swift:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 4) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirm.swift:28— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirm.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMobilePay.swift:26-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMultibanco.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodVipps.swift:25-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 4 call sites, so a change lands once.
Duplicated block (9 lines × 4) Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:111— Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:111-119 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:151-159 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:162-170 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:131-139 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:111` 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 (10 lines × 4) StripeUICore/StripeUICore/Source/Elements/PickerField/PickerFieldView.swift:231— StripeUICore/StripeUICore/Source/Elements/PickerField/PickerFieldView.swift:231-240 | StripeUICore/StripeUICore/Source/Elements/Section/SectionContainerView.swift:188-197 | StripeUICore/StripeUICore/Source/Elements/TextField/FloatingPlaceholderTextFieldView.swift:197-206 | StripeUICore/StripeUICore/Source/Elements/TextField/TextFieldView.swift:340-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (10 lines × 4) StripeApplePay/StripeApplePay/Source/PaymentsCore/Analytics/STPAnalyticsClient+PaymentsAPI.swift:13— StripeApplePay/StripeApplePay/Source/PaymentsCore/Analytics/STPAnalyticsClient+PaymentsAPI.swift:13-22 | StripeApplePay/StripeApplePay/Source/PaymentsCore/Analytics/STPAnalyticsClient+PaymentsAPI.swift:24-33 | StripeApplePay/StripeApplePay/Source/PaymentsCore/Analytics/STPAnalyticsClient+PaymentsAPI.swift:35-46 | StripePayments/StripePayments/Source/Internal/Analytics/STPAnalyticsClient+Payments.swift:27-38 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:437— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:437-473 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:475-511 — 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) Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:66— Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:66-108 | Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift:67-103 — 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.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×1
Heading level jumps from h1 to h4 REDACTED:71— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Anchor without href · ×1
Anchor without href REDACTED:29— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement Stripe3DS2/Stripe3DS2DemoUI/Resources/acs_challenge.html:87— `.input-field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
STPPaymentMethodType.makeImage (cyclomatic 71) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.swift:219— STPPaymentMethodType.makeImage has cyclomatic complexity 71 (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.
STPPaymentHandler._handleAuthenticationForCurrentAction (cyclomatic 68) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1153— STPPaymentHandler._handleAuthenticationForCurrentAction has cyclomatic complexity 68 (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.
STPPaymentHandler._retrieveAndCheckIntentForCurrentAction (cyclomatic 53) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1626— STPPaymentHandler._retrieveAndCheckIntentForCurrentAction has cyclomatic complexity 53 (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.
NativeFlowController.swift.CreatePaneViewController (cyclomatic 42) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:1476— NativeFlowController.swift.CreatePaneViewController has cyclomatic complexity 42 (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.
STPPaymentCardTextField.recalculateSubviewLayout (cyclomatic 39) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1320— STPPaymentCardTextField.recalculateSubviewLayout has cyclomatic complexity 39 (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.
HostedAuthUrlBuilder.build (cyclomatic 38) StripeCore/StripeCore/Source/Connections Bindings/HostedAuthUrlBuilder.swift:12— HostedAuthUrlBuilder.build has cyclomatic complexity 38 (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.
ConfirmButton.update (cyclomatic 36) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/ConfirmButton.swift:292— ConfirmButton.update has cyclomatic complexity 36 (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.
STPDecodingContainerProtocol.castFromNSObject (cyclomatic 35) StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:570— STPDecodingContainerProtocol.castFromNSObject has cyclomatic complexity 35 (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.
PaymentSheet.confirmAfterHandlingLocalActions (cyclomatic 35) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:248— PaymentSheet.confirmAfterHandlingLocalActions has cyclomatic complexity 35 (threshold 15). Of this number, 21 points are the body's own statements and 14 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PaymentSheetVerticalViewController.calculateInitialSelection (cyclomatic 35) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:376— PaymentSheetVerticalViewController.calculateInitialSelection has cyclomatic complexity 35 (threshold 15). Of this number, 27 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
STPIntentAction.decodedObject (cyclomatic 35) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift:353— STPIntentAction.decodedObject has cyclomatic complexity 35 (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.
STPApplePayContext._completePayment (cyclomatic 33) StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:660— STPApplePayContext._completePayment has cyclomatic complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
STPIntentAction.description (cyclomatic 33) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift:232— STPIntentAction.description 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.
CardVerifyAccurateStateMachine.transition (cyclomatic 30) StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.swift:215— CardVerifyAccurateStateMachine.transition has cyclomatic complexity 30 (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.
PaymentSheetAnalyticsHelper.logPayment (cyclomatic 30) StripePaymentSheet/StripePaymentSheet/Source/Analytics/PaymentSheetAnalyticsHelper.swift:394— PaymentSheetAnalyticsHelper.logPayment has cyclomatic complexity 30 (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.
StripeEncodingContainer.castToNSObject (cyclomatic 26) StripeCore/StripeCore/Source/Coder/StripeJSONEncoder.swift:489— StripeEncodingContainer.castToNSObject has cyclomatic complexity 26 (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.
PaymentSheetFormFactory.makeCard (cyclomatic 24) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Card.swift:42— PaymentSheetFormFactory.makeCard has cyclomatic complexity 24 (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.
SelfieCaptureViewController.statusText (cyclomatic 23) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:577— SelfieCaptureViewController.statusText has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LinkAccountPickerViewController.didSelectConnectAccounts (cyclomatic 22) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:250— LinkAccountPickerViewController.didSelectConnectAccounts 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.
STPPaymentCardTextField.paymentMethodParams (cyclomatic 22) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:441— STPPaymentCardTextField.paymentMethodParams has cyclomatic complexity 22 (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.
AccountPickerViewController.pollAuthSessionAccounts (cyclomatic 21) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:146— AccountPickerViewController.pollAuthSessionAccounts has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
STPElementsSession.decodedObject (cyclomatic 21) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:172— STPElementsSession.decodedObject has cyclomatic complexity 21 (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.
STPPaymentHandler._handleRedirect (cyclomatic 21) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1880— STPPaymentHandler._handleRedirect has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InterfaceCache.load! (cyclomatic 21) ci_scripts/api_diff/interface_cache.rb:8— InterfaceCache.load! has cyclomatic complexity 21 (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.
NSError.stp_error (cyclomatic 20) StripeCore/StripeCore/Source/Helpers/STPError.swift:164— NSError.stp_error has cyclomatic complexity 20 (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.
NativeFlowController.closeAuthFlow (cyclomatic 20) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:359— NativeFlowController.closeAuthFlow 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.
CustomerSession.decoded (cyclomatic 20) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/CustomerSession.swift:21— CustomerSession.decoded has cyclomatic complexity 20 (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.
PaymentSheet.confirmLinkPaymentOption (cyclomatic 20) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:652— PaymentSheet.confirmLinkPaymentOption 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.
CheckoutElementsController.confirmCheckoutSession (cyclomatic 20) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:525— CheckoutElementsController.confirmCheckoutSession 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.
VerificationSheetFlowController.nextViewController (cyclomatic 19) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:424— VerificationSheetFlowController.nextViewController 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.
DocumentCaptureViewController.scanningTextWithNoInput (cyclomatic 19) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController+Strings.swift:18— DocumentCaptureViewController.scanningTextWithNoInput has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LinkAuthFlowViewController.render (cyclomatic 19) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verification/LinkAuthFlowViewController.swift:202— LinkAuthFlowViewController.render 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.
CheckoutElementsController.confirm (cyclomatic 19) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:278— CheckoutElementsController.confirm 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.
STPAPIClient.makeElementsSessionsParams (cyclomatic 18) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:16— STPAPIClient.makeElementsSessionsParams 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.
STPAnalyticsEventTranslator.translateEvent (cyclomatic 18) StripeCore/StripeCore/Source/Analytics/Eventing/STPAnalyticsEventTranslator.swift:27— STPAnalyticsEventTranslator.translateEvent 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.
ErrorViewController.viewDidLoad (cyclomatic 18) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Error/ErrorViewController.swift:41— ErrorViewController.viewDidLoad 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.
PartnerAuthViewController.openInstitutionAuthenticationWebView (cyclomatic 18) StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:393— PartnerAuthViewController.openInstitutionAuthenticationWebView 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.
DocumentSide.instruction (cyclomatic 18) StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:16— DocumentSide.instruction has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PayWithLinkViewController.launchFinancialConnections (cyclomatic 18) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift:642— PayWithLinkViewController.launchFinancialConnections has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
STPImageLibrary.brandImage (cyclomatic 18) StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPImageLibrary.swift:140— STPImageLibrary.brandImage 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.
STPFormView.configureFooter (cyclomatic 18) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:346— STPFormView.configureFooter has cyclomatic complexity 18 (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.
STPConnectAccountIndividualParams.description (cyclomatic 18) StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountIndividualParams.swift:78— STPConnectAccountIndividualParams.description has cyclomatic complexity 18 (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.
FinancialConnectionsWebFlowViewController.startAuthenticationSession (cyclomatic 17) StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:153— FinancialConnectionsWebFlowViewController.startAuthenticationSession 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.
Intent.fulfilledRequirements (cyclomatic 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+PaymentMethodAvailability.swift:220— Intent.fulfilledRequirements 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.
PaymentSheet.createConfirmationTokenParams (cyclomatic 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:158— PaymentSheet.createConfirmationTokenParams 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.
STPFormTextField.autoFormattingBehavior (cyclomatic 17) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:77— STPFormTextField.autoFormattingBehavior 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.
STPPaymentCardTextField.formTextFieldTextDidChange (cyclomatic 17) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1760— STPPaymentCardTextField.formTextFieldTextDidChange 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.
STPCustomer.sources (cyclomatic 17) StripePayments/StripePayments/Source/API Bindings/Models/STPCustomer.swift:150— STPCustomer.sources 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.
STPPaymentIntent.decodedObject (cyclomatic 17) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:254— STPPaymentIntent.decodedObject has cyclomatic complexity 17 (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.
STPPaymentHandler.confirmPaymentIntent (cyclomatic 17) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:200— STPPaymentHandler.confirmPaymentIntent 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.
STPPaymentHandler.handleNextAction (cyclomatic 17) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:454— STPPaymentHandler.handleNextAction 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.
AddressSectionElement.updateAddressFields (cyclomatic 17) StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSectionElement.swift:354— AddressSectionElement.updateAddressFields 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.
StackViewWithSeparator.layoutSubviews (cyclomatic 17) StripeUICore/StripeUICore/Source/Helpers/StackViewWithSeparator.swift:142— StackViewWithSeparator.layoutSubviews 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.
PaneLayoutView.createFooterView (cyclomatic 16) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:255— PaneLayoutView.createFooterView 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.
STPCardScanner.processVNRequest (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:301— STPCardScanner.processVNRequest 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.
LinkAuthFlowCoordinator.sendCode (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verification/LinkAuthFlowCoordinator.swift:326— LinkAuthFlowCoordinator.sendCode 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.
PaymentSheet.handleDeferredIntentConfirmation_confirmationToken (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:12— PaymentSheet.handleDeferredIntentConfirmation_confirmationToken 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.
PaymentSheet.handleDeferredIntentConfirmation (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:63— PaymentSheet.handleDeferredIntentConfirmation 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.
PaymentSheetVerticalViewController.selectedPaymentOption (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:21— PaymentSheetVerticalViewController.selectedPaymentOption has cyclomatic complexity 16 (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.
PaymentMethodFormViewController.handleCollectBankAccount (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:471— PaymentMethodFormViewController.handleCollectBankAccount has cyclomatic complexity 16 (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.
PaymentMethodFormViewController.handleCollectInstantDebits (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:581— PaymentMethodFormViewController.handleCollectInstantDebits has cyclomatic complexity 16 (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.
PaymentSheetFlowControllerViewController.init (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:183— PaymentSheetFlowControllerViewController.init 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.
PaymentSheetViewController.updateUI (cyclomatic 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:309— PaymentSheetViewController.updateUI 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.
STPTextFieldDelegateProxy.textField (cyclomatic 16) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:383— STPTextFieldDelegateProxy.textField 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.
STPCardExpiryInputTextFieldFormatter.isAllowedInput (cyclomatic 16) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldFormatter.swift:15— STPCardExpiryInputTextFieldFormatter.isAllowedInput 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.
STPPaymentCardTextField.updateImage (cyclomatic 16) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:2168— STPPaymentCardTextField.updateImage 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.
STPPaymentHandler.confirmSetupIntent (cyclomatic 16) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:553— STPPaymentHandler.confirmSetupIntent 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.
SectionContainerView.updateUI (cyclomatic 16) StripeUICore/StripeUICore/Source/Elements/Section/SectionContainerView.swift:99— SectionContainerView.updateUI 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.
Floating branch dependency: ohhttpstubs — Dependency `ohhttpstubs` is resolved in Stripe.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `stripe-mock` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
STPPaymentHandler._handleAuthenticationForCurrentAction (cognitive 139) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1153— STPPaymentHandler._handleAuthenticationForCurrentAction has cognitive complexity 139 (threshold 15). Drivers by points: if/else 57 (126 pts), ternaries 2 (8 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 77). 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.
STPPaymentHandler._retrieveAndCheckIntentForCurrentAction (cognitive 108) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1626— STPPaymentHandler._retrieveAndCheckIntentForCurrentAction has cognitive complexity 108 (threshold 15). Drivers by points: if/else 32 (80 pts), boolean chains 28 (nesting depth added 48). 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.
STPPaymentCardTextField.recalculateSubviewLayout (cognitive 86) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1320— STPPaymentCardTextField.recalculateSubviewLayout has cognitive complexity 86 (threshold 15). Drivers by points: if/else 34 (56 pts), loops 5 (19 pts), ternaries 4 (7 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 41). 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.
HostedAuthUrlBuilder.build (cognitive 69) StripeCore/StripeCore/Source/Connections Bindings/HostedAuthUrlBuilder.swift:12— HostedAuthUrlBuilder.build has cognitive complexity 69 (threshold 15). Drivers by points: if/else 21 (53 pts), boolean chains 15, ternaries 1 (nesting depth added 32). 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.
STPApplePayContext._completePayment (cognitive 52) StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:660— STPApplePayContext._completePayment has cognitive complexity 52 (threshold 15). Drivers by points: if/else 27 (42 pts), boolean chains 6, error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 17). Of this number, 48 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaymentSheet.confirmAfterHandlingLocalActions (cognitive 45) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:248— PaymentSheet.confirmAfterHandlingLocalActions has cognitive complexity 45 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 6 (11 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 26). Of this number, 23 points are the body's own statements and 22 belong to 2 function items inside it that branch. 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.
NativeFlowController.swift.CreatePaneViewController (cognitive 44) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:1476— NativeFlowController.swift.CreatePaneViewController has cognitive complexity 44 (threshold 15). Drivers by points: if/else 26 (38 pts), boolean chains 5, match/switch 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.
PaymentSheetAnalyticsHelper.logPayment (cognitive 44) StripePaymentSheet/StripePaymentSheet/Source/Analytics/PaymentSheetAnalyticsHelper.swift:394— PaymentSheetAnalyticsHelper.logPayment has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 9 (26 pts), if/else 8 (12 pts), match/switch 4 (6 pts) (nesting depth added 23). 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.
PaymentSheetVerticalViewController.calculateInitialSelection (cognitive 42) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:376— PaymentSheetVerticalViewController.calculateInitialSelection has cognitive complexity 42 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 10, match/switch 3 (5 pts) (nesting depth added 13). Of this number, 35 points are the body's own statements and 7 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.
ErrorViewController.viewDidLoad (cognitive 40) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Error/ErrorViewController.swift:41— ErrorViewController.viewDidLoad has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (29 pts), ternaries 2 (6 pts), boolean chains 5 (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.
NativeFlowController.closeAuthFlow (cognitive 38) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:359— NativeFlowController.closeAuthFlow has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (28 pts), match/switch 2 (6 pts), boolean chains 3, ternaries 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.
PaymentSheet.handleDeferredIntentConfirmation (cognitive 38) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:63— PaymentSheet.handleDeferredIntentConfirmation has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (33 pts), match/switch 2 (4 pts), error handling 1 (nesting depth added 23). 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.
STPDecodingContainerProtocol.castFromNSObject (cognitive 36) StripeCore/StripeCore/Source/Coder/StripeJSONDecoder.swift:570— STPDecodingContainerProtocol.castFromNSObject has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 3 (5 pts), boolean chains 4, loops 2 (4 pts), error handling 1 (2 pts) (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LinkAccountPickerViewController.didSelectConnectAccounts (cognitive 36) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:250— LinkAccountPickerViewController.didSelectConnectAccounts has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (26 pts), match/switch 3 (7 pts), boolean chains 3 (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.
PaymentSheet.handleDeferredIntentConfirmation_confirmationToken (cognitive 36) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:12— PaymentSheet.handleDeferredIntentConfirmation_confirmationToken has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (30 pts), match/switch 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 21). 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.
STPPaymentHandler._handleRedirect (cognitive 36) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1880— STPPaymentHandler._handleRedirect has cognitive complexity 36 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 4 (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.
StackViewWithSeparator.layoutSubviews (cognitive 36) StripeUICore/StripeUICore/Source/Helpers/StackViewWithSeparator.swift:142— StackViewWithSeparator.layoutSubviews has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (22 pts), match/switch 2 (8 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 21). 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.
AccountPickerViewController.pollAuthSessionAccounts (cognitive 34) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:146— AccountPickerViewController.pollAuthSessionAccounts has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 8, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
STPCustomer.sources (cognitive 34) StripePayments/StripePayments/Source/API Bindings/Models/STPCustomer.swift:150— STPCustomer.sources has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (26 pts), boolean chains 7, loops 1 (nesting depth added 17). 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.
AccountPickerNoAccountEligibleErrorView.init (cognitive 33) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerNoAccountEligibleErrorView.swift:16— AccountPickerNoAccountEligibleErrorView.init has cognitive complexity 33 (threshold 15). Drivers by points: if/else 22 (33 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.
STPPaymentCardTextField.formTextFieldTextDidChange (cognitive 33) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:1760— STPPaymentCardTextField.formTextFieldTextDidChange has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 1, match/switch 1 (nesting depth added 19). 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.
ElementsCustomer.parsePaymentMethods (cognitive 31) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/ElementsCustomer.swift:56— ElementsCustomer.parsePaymentMethods has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfirmButton.update (cognitive 31) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/ConfirmButton.swift:292— ConfirmButton.update has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 5 (8 pts), match/switch 5 (6 pts), boolean chains 5 (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.
STPPaymentCardTextField.paymentMethodParams (cognitive 31) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:441— STPPaymentCardTextField.paymentMethodParams has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 4, ternaries 1 (3 pts), match/switch 1 (2 pts) (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.
STPIntentAction.decodedObject (cognitive 31) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift:353— STPIntentAction.decodedObject has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 1, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinkAccountPickerViewController.linkAccountPickerBodyView (cognitive 30) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:573— LinkAccountPickerViewController.linkAccountPickerBodyView has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
STPIntentAction.description (cognitive 29) StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift:232— STPIntentAction.description has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (28 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
STPAPIClient.updatePaymentMethodParameters (cognitive 28) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+CheckoutSession.swift:315— STPAPIClient.updatePaymentMethodParameters has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (28 pts) (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.
DocumentSide.instruction (cognitive 28) StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:16— DocumentSide.instruction has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 4 (11 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 9). Of this number, 26 points are the body's own statements and 2 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.
PartnerAuthViewController.openInstitutionAuthenticationWebView (cognitive 27) StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PartnerAuthViewController.swift:393— PartnerAuthViewController.openInstitutionAuthenticationWebView has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 6 (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.
DocumentCaptureViewController.scanningTextWithNoInput (cognitive 27) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController+Strings.swift:18— DocumentCaptureViewController.scanningTextWithNoInput has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 8 (9 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 9). Of this number, 26 points are the body's own statements and 1 belongs 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.
PaymentSheet.confirmLinkPaymentOption (cognitive 27) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+API.swift:652— PaymentSheet.confirmLinkPaymentOption has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 5 (10 pts), ternaries 1 (3 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.
STPFormTextField.autoFormattingBehavior (cognitive 27) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:77— STPFormTextField.autoFormattingBehavior has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (5 pts), boolean chains 2, match/switch 1 (nesting depth added 13). 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.
CheckoutElementsController.confirm (cognitive 25) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:278— CheckoutElementsController.confirm has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 3 (6 pts), ternaries 1 (3 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
STPAPIClient.makeElementsSessionsParams (cognitive 24) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/STPAPIClient+PaymentSheet.swift:16— STPAPIClient.makeElementsSessionsParams has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (4 pts), match/switch 2 (3 pts), boolean chains 2 (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.
NSError.stp_error (cognitive 24) StripeCore/StripeCore/Source/Helpers/STPError.swift:164— NSError.stp_error has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 6, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
PaneLayoutView.createFooterView (cognitive 24) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/PaneLayoutView/PaneLayoutView+Extensions.swift:255— PaneLayoutView.createFooterView has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 4 (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.
FinancialConnectionsWebFlowViewController.startAuthenticationSession (cognitive 24) StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:153— FinancialConnectionsWebFlowViewController.startAuthenticationSession has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 1 (3 pts), boolean chains 1, match/switch 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.
STPCardScanner.processVNRequest (cognitive 24) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:301— STPCardScanner.processVNRequest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3 (4 pts), boolean chains 2 (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.
CustomerSession.decoded (cognitive 24) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/CustomerSession.swift:21— CustomerSession.decoded has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 8 (11 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CustomerSavedPaymentMethodsViewController.updateUI (cognitive 24) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:250— CustomerSavedPaymentMethodsViewController.updateUI has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 3 (8 pts), match/switch 2, 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.
BillingDetails.init (cognitive 23) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:67— BillingDetails.init has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 2 (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.
STPAPIClient.billingDetails (cognitive 23) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.swift:92— STPAPIClient.billingDetails has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 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.
CryptoOnrampCoordinator.collectPaymentMethod (cognitive 23) REDACTED:713— CryptoOnrampCoordinator.collectPaymentMethod has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (4 pts), error handling 1 (2 pts) (nesting depth added 13). 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.
LinkAuthFlowViewController.render (cognitive 23) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verification/LinkAuthFlowViewController.swift:202— LinkAuthFlowViewController.render has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, ternaries 1 (2 pts), match/switch 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.
PaymentSheetLoader.load (cognitive 23) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:63— PaymentSheetLoader.load has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, ternaries 2 (4 pts), error handling 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.
LinkController.authorize (cognitive 23) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:724— LinkController.authorize has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 3 (12 pts), if/else 5 (11 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PaymentSheetFlowControllerViewController.updateButton (cognitive 23) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:459— PaymentSheetFlowControllerViewController.updateButton has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 2 (6 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AppleCreditCardOcr.recognizeCard (cognitive 22) StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/AppleCreditCardOcr.swift:11— AppleCreditCardOcr.recognizeCard has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 2, loops 1 (nesting depth added 11). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
CryptoOnrampCoordinator.performCheckout (cognitive 22) REDACTED:846— CryptoOnrampCoordinator.performCheckout has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 1 (2 pts), error handling 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.
NSMutableAttributedString.pmmePromoString (cognitive 22) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMESinglePartnerView.swift:80— NSMutableAttributedString.pmmePromoString has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PayWithLinkViewController.launchFinancialConnections (cognitive 22) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController.swift:642— PayWithLinkViewController.launchFinancialConnections has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 4 (5 pts), ternaries 1 (nesting depth added 9). Of this number, 21 points are the body's own statements and 1 belongs 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.
UpdatePaymentMethodViewController.update (cognitive 22) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/UpdatePaymentMethodViewController.swift:232— UpdatePaymentMethodViewController.update has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (19 pts), ternaries 1 (2 pts), match/switch 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.
STPPostalCodeValidator.validationState (cognitive 22) StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPPostalCodeValidator.swift:116— STPPostalCodeValidator.validationState has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (22 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.
STPFormView.set (cognitive 22) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:125— STPFormView.set has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, ternaries 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.
TextFieldFormatter.applyFormat (cognitive 22) StripeUICore/StripeUICore/Source/Elements/TextField/TextFieldFormatter.swift:51— TextFieldFormatter.applyFormat has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 5, loops 2 (3 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.
SelfieCaptureViewController.statusText (cognitive 21) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:577— SelfieCaptureViewController.statusText has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (6 pts), match/switch 3 (5 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.
PaymentSheetLoader.fetchElementsSessionAndIntent (cognitive 21) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetLoader.swift:247— PaymentSheetLoader.fetchElementsSessionAndIntent has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 3 (6 pts), 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.
CustomerSavedPaymentMethodsViewController.didTapActionButton (cognitive 21) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:397— CustomerSavedPaymentMethodsViewController.didTapActionButton has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 2 (4 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PaymentMethodMessagingElement.init (cognitive 21) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+Initialization.swift:15— PaymentMethodMessagingElement.init has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 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.
PaymentSheetFormFactory.makeCard (cognitive 21) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory+Card.swift:42— PaymentSheetFormFactory.makeCard has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 5, boolean chains 4, match/switch 2 (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.
PaymentSheetViewController.updateUI (cognitive 21) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:309— PaymentSheetViewController.updateUI has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 4 (9 pts), match/switch 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.
STPFormView.configureFooter (cognitive 21) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:346— STPFormView.configureFooter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 10. 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.
STPPaymentHandler.confirmSetupIntent (cognitive 21) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:553— STPPaymentHandler.confirmSetupIntent has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 5 (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.
STPElementsSession.decodedObject (cognitive 20) StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:172— STPElementsSession.decodedObject has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 9. 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.
Intent.fulfilledRequirements (cognitive 20) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+PaymentMethodAvailability.swift:220— Intent.fulfilledRequirements has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 6, match/switch 1 (nesting depth added 7). 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.
CheckoutElementsController.applyDefaults (cognitive 20) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController.swift:501— CheckoutElementsController.applyDefaults has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
STPCardFormView.shouldAutoAdvance (cognitive 20) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPCardFormView.swift:436— STPCardFormView.shouldAutoAdvance has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (20 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.
STPPaymentHandler._markChallengeCompleted (cognitive 20) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2272— STPPaymentHandler._markChallengeCompleted has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3 (nesting depth added 4). Of this number, 13 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
SectionContainerView.updateUI (cognitive 20) StripeUICore/StripeUICore/Source/Elements/Section/SectionContainerView.swift:99— SectionContainerView.updateUI has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
InterfaceCache.load! (cognitive 20) ci_scripts/api_diff/interface_cache.rb:8— InterfaceCache.load! has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 9, error handling 1. 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.
LinkAuthFlowCoordinator.sendCode (cognitive 19) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verification/LinkAuthFlowCoordinator.swift:326— LinkAuthFlowCoordinator.sendCode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 7, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaymentSheet.createConfirmationTokenParams (cognitive 19) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:158— PaymentSheet.createConfirmationTokenParams has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 3, boolean chains 2 (nesting depth added 6). 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.
CheckoutSessionPoller.poll (cognitive 19) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutSessionPoller.swift:73— CheckoutSessionPoller.poll has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), error handling 1 (2 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaymentSheetFlowControllerViewController.init (cognitive 19) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:183— PaymentSheetFlowControllerViewController.init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 7, match/switch 1 (3 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.
STPTextFieldDelegateProxy.textField (cognitive 19) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:383— STPTextFieldDelegateProxy.textField has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 7 (nesting depth added 3). 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.
STPCardExpiryInputTextFieldFormatter.isAllowedInput (cognitive 19) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldFormatter.swift:15— STPCardExpiryInputTextFieldFormatter.isAllowedInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5 (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.
STPPaymentHandler.confirmPaymentIntent (cognitive 19) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:200— STPPaymentHandler.confirmPaymentIntent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 8 (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.
STPPaymentHandler.handleNextAction (cognitive 19) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:454— STPPaymentHandler.handleNextAction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 8 (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.
STPAnalyticsEventTranslator.translateEvent (cognitive 18) StripeCore/StripeCore/Source/Analytics/Eventing/STPAnalyticsEventTranslator.swift:27— STPAnalyticsEventTranslator.translateEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (nesting depth added 8). 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.
URLEncoder.swift.queryComponents (cognitive 18) StripeCore/StripeCore/Source/Helpers/URLEncoder.swift:54— URLEncoder.swift.queryComponents has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (6 pts), if/else 4 (5 pts), ternaries 2 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 2 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.
AccountPickerViewController.didSelectLinkAccounts (cognitive 18) StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:400— AccountPickerViewController.didSelectLinkAccounts has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, match/switch 2 (4 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.
AuthenticationSessionManager.start (cognitive 18) StripeFinancialConnections/StripeFinancialConnections/Source/Web/AuthenticationSessionManager.swift:38— AuthenticationSessionManager.start has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 3). 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.
STPEphemeralKey.decodedObject (cognitive 18) StripeIssuing/StripeIssuing/Source/STPEphemeralKey.swift:37— STPEphemeralKey.decodedObject has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinkInlineSignupViewModel.action (cognitive 18) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.swift:265— LinkInlineSignupViewModel.action has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 2 (4 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TwoOptionSelectorView.handlePan (cognitive 18) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/TwoOptionSelectorView.swift:294— TwoOptionSelectorView.handlePan has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5 (7 pts), boolean chains 1, match/switch 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.
PaymentMethodFormViewController.paymentOption (cognitive 18) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:33— PaymentMethodFormViewController.paymentOption has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
STPImageLibrary.brandImage (cognitive 18) StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPImageLibrary.swift:140— STPImageLibrary.brandImage has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 1, match/switch 1 (nesting depth added 8). 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.
STPCardValidator.validationState (cognitive 18) StripePayments/StripePayments/Source/Helpers/STPCardValidator.swift:333— STPCardValidator.validationState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (6 pts), boolean chains 4, match/switch 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.
CryptoOnrampCoordinator.createCryptoPaymentToken (cognitive 17) REDACTED:797— CryptoOnrampCoordinator.createCryptoPaymentToken has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FCLiteContainerViewController.completeFlow (cognitive 17) StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteContainerViewController.swift:113— FCLiteContainerViewController.completeFlow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 1 (3 pts), match/switch 1 (nesting depth added 7). 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.
FinancialConnectionsWebFlowViewController.fetchSession (cognitive 17) StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift:255— FinancialConnectionsWebFlowViewController.fetchSession has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstantDebitsOnlyAuthenticationSessionManager.start (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ACH/InstantDebitsOnlyFinancialConnectionsAuthManager.swift:71— InstantDebitsOnlyAuthenticationSessionManager.start has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), match/switch 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
IntentConfirmParams.setAllowRedisplay (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/IntentConfirmParams.swift:144— IntentConfirmParams.setAllowRedisplay has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 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.
CheckoutApplePayContext.makeSummaryItems (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutApplePayContext.swift:359— CheckoutApplePayContext.makeSummaryItems has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 2 (4 pts), ternaries 1 (4 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.
CheckoutElementsController.confirmCheckoutSession (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutElementsController+Confirm.swift:525— CheckoutElementsController.confirmCheckoutSession has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, match/switch 4 (7 pts), error handling 1 (nesting depth added 3). 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.
CustomerSheet.retrievePaymentOptionSelection (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSheet.swift:359— CustomerSheet.retrievePaymentOptionSelection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (5 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.
VerticalListMandateProvider.mandate (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/MandateTextProvider.swift:38— VerticalListMandateProvider.mandate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 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.
PaymentSheetVerticalViewController.updatePrimaryButton (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:299— PaymentSheetVerticalViewController.updatePrimaryButton has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, ternaries 4 (7 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.
VerticalPaymentMethodListViewController.renderContent (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/VerticalPaymentMethodListViewController.swift:99— VerticalPaymentMethodListViewController.renderContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 2, 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.
AutoCompleteViewController.tableView (cognitive 17) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/AutoComplete/AutoCompleteViewController.swift:444— AutoCompleteViewController.tableView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 1 (3 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.
STPFormView.previousField (cognitive 17) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:273— STPFormView.previousField has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 pts), boolean chains 2 (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. This shape REPEATS in the file: one other method here (STPFormView.nextInSequenceFirstResponderField) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
STPFormView.nextInSequenceFirstResponderField (cognitive 17) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFormView.swift:305— STPFormView.nextInSequenceFirstResponderField has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 pts), boolean chains 2 (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. This shape REPEATS in the file: one other method here (STPFormView.previousField) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
STPConnectAccountIndividualParams.description (cognitive 17) StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountIndividualParams.swift:78— STPConnectAccountIndividualParams.description has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 17. 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.
STPBINController.retrieveBINRanges (cognitive 17) StripePayments/StripePayments/Source/Helpers/STPBINController.swift:270— STPBINController.retrieveBINRanges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, loops 1 (2 pts) (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.
AddressSectionElement.updateAddressFields (cognitive 17) StripeUICore/StripeUICore/Source/Elements/Factories/Address/AddressSectionElement.swift:354— AddressSectionElement.updateAddressFields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
CreditCardUtils.determineCardType (cognitive 16) StripeCardScan/StripeCardScan/Source/CardScan/CardUtils/CreditCardUtils.swift:252— CreditCardUtils.determineCardType has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 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.
PostDetectionAlgorithm.combineCloseBoxes (cognitive 16) StripeCardScan/StripeCardScan/Source/CardScan/MLRuntime/PostDetectionAlgorithm.swift:102— PostDetectionAlgorithm.combineCloseBoxes has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 2 (6 pts), boolean chains 3 (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.
VideoFeed.configureSession (cognitive 16) StripeCardScan/StripeCardScan/Source/CardScan/UI/VideoFeed.swift:75— VideoFeed.configureSession has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), 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.
InstitutionTableView.load (cognitive 16) StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionTableView.swift:232— InstitutionTableView.load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinkAccountPickerViewController.presentAccountUpdateRequiredDrawer (cognitive 16) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerViewController.swift:460— LinkAccountPickerViewController.presentAccountUpdateRequiredDrawer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
SelfieCaptureViewController.imageScanningSessionDidScanImage (cognitive 16) StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/SelfieCaptureViewController.swift:845— SelfieCaptureViewController.imageScanningSessionDidScanImage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
STPCardScanner.setupCamera (cognitive 16) StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift:203— STPCardScanner.setupCamera has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ApplePayContextClosureDelegate.applePayContext (cognitive 16) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/STPApplePayContext+PaymentSheet.swift:50— ApplePayContextClosureDelegate.applePayContext has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 7). 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.
STPPaymentCardTextField.textFieldDidEndEditing (cognitive 16) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:2010— STPPaymentCardTextField.textFieldDidEndEditing has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, match/switch 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.
STPPaymentCardTextField.updateImage (cognitive 16) StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPPaymentCardTextField.swift:2168— STPPaymentCardTextField.updateImage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, match/switch 1 (2 pts), ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
STPPaymentIntent.decodedObject (cognitive 16) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntent.swift:254— STPPaymentIntent.decodedObject has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 6, if/else 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.
STPFormEncoder.formEncodableValue (cognitive 16) StripePayments/StripePayments/Source/Internal/API Bindings/STPFormEncoder.swift:58— STPFormEncoder.formEncodableValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 7). 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.
STPPaymentHandler._markChallengeCanceled (cognitive 16) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:2183— STPPaymentHandler._markChallengeCanceled has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, match/switch 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.
FunctionTooLong: NativeFlowController.swift.CreatePaneViewController StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:1476— FunctionTooLong — CreatePaneViewController runs 324 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× 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.
Change-coupling hub: HostViewController.swift → FinancialConnectionsSheet.swift, NativeFlowController.swift, FinancialConnectionsWebFlowViewController.swift StripeFinancialConnections/StripeFinancialConnections/Source/Common/HostViewController.swift— `StripeFinancialConnections/StripeFinancialConnections/Source/Common/HostViewController.swift` changes together with 3 other files — `StripeFinancialConnections/StripeFinancialConnections/Source/FinancialConnectionsSheet.swift`, `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift`, `StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change coupling clique: NetworkingLinkVerificationDataSource.swift, NetworkingSaveToLinkVerificationDataSource.swift, NetworkingOTPView.swift StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationDataSource.swift— 3 files — `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationDataSource.swift`, `StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingSaveToLinkVerification/NetworkingSaveToLinkVerificationDataSource.swift`, `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/NetworkingOTPView/NetworkingOTPView.swift` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Near-duplicate member family (4 members, 35 shared lines) · ×1
Near-duplicate member family (4 members, 35 shared lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:126— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:126-196 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:210-282 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:551-620 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:634-706 — These 4 members are variants of one another: a block of 35 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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.
Near-duplicate member pair (56 shared lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:12— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+ConfirmationTokens.swift:12-156 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheet+DeferredAPI.swift:63-228 — These two members are variants of one another: 56 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (109 corresponding lines) · ×1
Edited copy of a member (109 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:471— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:471-579 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:581-703 — These two members are one piece of code written twice and then edited apart: 109 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 (105 corresponding lines) · ×1
Edited copy of a member (105 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:200— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:200-304 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:553-660 — These two members are one piece of code written twice and then edited apart: 105 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 (83 corresponding lines) · ×1
Edited copy of a member (83 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:454— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:454-544 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:760-842 — These two members are one piece of code written twice and then edited apart: 83 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 (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:438— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:438-506 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:176-244 — These two members are one piece of code written twice and then edited apart: 69 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 (67 corresponding lines) · ×1
Edited copy of a member (67 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1004— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1004-1070 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1073-1151 — These two members are one piece of code written twice and then edited apart: 67 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 (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:267— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:267-328 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:336-395 — These two members are one piece of code written twice and then edited apart: 60 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, 48+ corresponding lines) · ×1
Edited copies of one member (3 members, 48+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:310— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedFormViewController.swift:310-357 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:679-743 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:459-509 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 48 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, 50+ corresponding lines) · ×1
Edited copies of one member (3 members, 50+ corresponding lines) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:52— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:52-103 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupBodyView.swift:63-112 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:150-201 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:67— StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:67-113 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.swift:92-133 — These two members are one piece of code written twice and then edited apart: 42 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 (4 members, 24+ corresponding lines) · ×1
Edited copies of one member (4 members, 24+ corresponding lines) StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:518— StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:518-541 | StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:543-566 | StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:568-591 | StripeApplePay/StripeApplePay/Source/ApplePayContext/STPApplePayContext.swift:593-616 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:23— StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:23-45 | StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:65-92 | StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:113-135 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:931— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:931-965 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:967-1001 — 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 (4 members, 23+ corresponding lines) · ×1
Edited copies of one member (4 members, 23+ corresponding lines) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:293— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:293-315 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:327-351 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:717-739 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:751-775 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:254— StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:254-267 | StripePayments/StripePayments/Source/API Bindings/Models/STPConnectAccountAddress.swift:65-76 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPBankAccountParams.swift:113-123 — 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· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:207— StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:207-235 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:237-270 | StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/VerificationSheetFlowController.swift:272-303 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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, 18+ corresponding lines) · ×1
Edited copies of one member (5 members, 18+ corresponding lines) StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:327— StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:327-348 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:353-370 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:373-392 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:397-414 | StripeCore/StripeCore/Source/API Bindings/STPAPIClient.swift:418-437 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 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 (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:328— StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:328-350 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:352-373 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:451-471 | StripePaymentSheet/StripePaymentSheet/Source/Helpers/PaymentSheetLinkAccount.swift:473-500 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:311— StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:311-331 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:364-383 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/API Bindings/STPAPIClient+CryptoOnramp.swift:391-410 — 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 (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1621— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1621-1639 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1657-1671 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1689-1702 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1723-1736 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 15+ corresponding lines) · ×1
Edited copies of one member (8 members, 15+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:492— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:492-506 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:691-705 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:791-805 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:945-959 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1243-1258 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1288-1302 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1336-1351 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:1380-1394 — These 8 members are one piece of code written 8 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 8 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) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmAlipayOptions.swift:37— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmAlipayOptions.swift:37-48 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmCardOptions.swift:25-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPConfirmWeChatPayOptions.swift:24-33 — 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 (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) StripeCardScan/StripeCardScan/Source/CardVerify/FadeInAnimation.swift:12— StripeCardScan/StripeCardScan/Source/CardVerify/FadeInAnimation.swift:12-22 | StripeCardScan/StripeCardScan/Source/CardVerify/FadeInAnimation.swift:24-37 | StripeCardScan/StripeCardScan/Source/CardVerify/FadeInAnimation.swift:39-49 | StripeCardScan/StripeCardScan/Source/CardVerify/FadeInAnimation.swift:53-66 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:90— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:90-105 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:158-169 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:295-307 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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 (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:311— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:311-320 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:386-396 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:441-452 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:667-676 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:684-694 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:738-749 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) Example/AppClipExample/Shared/BackendModel.swift:20— Example/AppClipExample/Shared/BackendModel.swift:20-29 | Testers/IntegrationTester/IntegrationTester/Source/Models/BackendModel.swift:21-30 | Testers/IntegrationTester/IntegrationTester/Source/Models/BackendModel.swift:32-40 — 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 copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:875— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:875-887 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:838-852 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:688-702 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×1
Edited copies of one member (4 members, 4+ corresponding lines) StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:870— StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/PayWithLinkViewController-WalletViewController.swift:870-883 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/AddressViewController/AddressViewController.swift:309-312 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/AutoComplete/AutoCompleteViewController.swift:241-245 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:417-424 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.swift:19— StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.swift:19-29 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:49-58 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:112-125 | StripePayments/StripePayments/Source/API Bindings/STPAPIClient+Payments.swift:259-268 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 9+ corresponding lines) · ×1
Edited copies of one member (6 members, 9+ corresponding lines) StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/InvalidWalletOwnershipChallengeError.swift:45— StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/InvalidWalletOwnershipChallengeError.swift:45-53 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/InvalidWalletOwnershipSignatureError.swift:45-53 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/UncategorizedError.swift:45-53 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/UnsupportedNetworkError.swift:45-53 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/WalletNotFoundError.swift:45-53 | StripeCryptoOnramp/StripeCryptoOnramp/Source/Components/Errors/Concrete Error Types/WalletOwnershipChallengeExpiredError.swift:45-53 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
Duplicated block (62 lines × 2) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:130— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:130-191 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:215-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:130` 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 (47 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:460— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:460-506 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:198-244 — before extracting anything, compare `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift` and `StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:460` 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 (44–45 lines × 2) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:410— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:410-454 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:832-875 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:410` 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 (53 lines × 2) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:555— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:555-607 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:639-691 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:555` 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 (37 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:273— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:273-309 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:340-376 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Link/LinkController.swift:273` 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 (34 lines × 2) Example/AppClipExample/Shared/ApplePayModel.swift:16— Example/AppClipExample/Shared/ApplePayModel.swift:16-49 | Testers/IntegrationTester/IntegrationTester/Source/Models/ApplePayModel.swift:16-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (33–34 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1025— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1025-1057 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1096-1129 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1025` 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 (36 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:45— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:45-80 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift:56-91 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.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.
Duplicated block (27–30 lines × 2) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldFormatter.swift:52— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldFormatter.swift:52-78 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPFormTextField.swift:92-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (24–28 lines × 3) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:76— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:76-103 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupBodyView.swift:87-112 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:178-201 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentBodyView.swift:76` 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 (27–28 lines × 2) StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:59— StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:59-86 | StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:115-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `StripeIssuing/StripeIssuing/Source/STPPinManagementService.swift:59` 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 (24–25 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:363— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:363-387 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentMethodFormViewController.swift:493-516 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerAddPaymentMethodViewController.swift:363` 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 (24 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:302— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:302-325 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:323-346 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 4) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:394— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:394-416 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:797-819 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.swift:1134-1156 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Saved Payment Method Screen/VerticalSavedPaymentMethodsViewController.swift:503-525 — 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. 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 first that the copies are not typed on the same thing: the declarations holding them bind `paymentMethod` to `StripePayments.STPPaymentMethod` in one and `STPPaymentMethod` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:821` calls `updateUI` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Saved Payment Method Screen/VerticalSavedPaymentMethodsViewController.swift:527` 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.
Duplicated block (13–23 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/InstantDebitsPaymentMethodElement.swift:295— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/InstantDebitsPaymentMethodElement.swift:295-317 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/USBankAccountPaymentMethodElement.swift:224-236 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/USBankAccount/USBankAccountPaymentMethodElement.swift:224` 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 (22–23 lines × 2) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1663— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1663-1685 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1764-1785 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1663` 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.
Duplicated block (21–22 lines × 2) StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:156— StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:156-176 | StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:202-223 — 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 `StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardAddViewController.swift:156` 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 (20–22 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift:151— StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift:151-172 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/NetworkingOTPView/NetworkingOTPView.swift:150-169 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift:151` 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 (19–22 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:221— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:221-239 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:241-262 — 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:221` 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 (19–20 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:439— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:439-457 | StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift:176-195 — before extracting anything, compare `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift` and `StripePaymentsUI/StripePaymentsUI/Source/UI Components/STPFloatingPlaceholderTextField.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/RoundedTextField.swift:439` 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 (18–19 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:135— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:135-153 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift:131-148 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 122 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.swift:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–17 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:393— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:393-405 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:284-300 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 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. 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 (16 lines × 3) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:151— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:151-166 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:189-204 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:217-232 — 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 `StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:151` 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 (14–16 lines × 3) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:346— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:346-359 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:388-401 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:279-294 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:346` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 3) StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:221— StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:221-236 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/LinkSettings.swift:152-166 | StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift:491-505 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.swift:221` 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. 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 (13–15 lines × 2) StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentLogoView.swift:130— StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentLogoView.swift:130-142 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PrepaneImageView.swift:103-117 — 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 (3–15 lines × 3) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:77— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:77-91 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift:88-102 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithRadioView.swift:98-100 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:77` 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. 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 (14 lines × 3) StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:410— StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:410-423 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:434-447 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:460-473 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:50— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:50-62 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift:61-73 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithRadioView.swift:73-85 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFloating.swift:97-109 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithDisclosure.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 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 `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButtonFlatWithCheckmark.swift:50` 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–13 lines × 4) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:152— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:152-164 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:237-249 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:577-588 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:661-672 — 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 `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:152` 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–14 lines × 2) StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:108— StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:108-119 | StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:136-149 — before extracting anything, compare `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift` and `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/FaceDetector/FaceDetectorOutput.swift:108` 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 (11–13 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:408— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:408-418 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift:639-651 — before extracting anything, compare `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift` and `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Saved Payment Method Screen/SavedPaymentOptionsViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsCollectionViewController.swift:408` 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.
Duplicated block (12 lines × 4) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:139— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:139-150 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:224-235 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:564-575 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:648-659 — 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 `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:139` 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 × 4) StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:177— StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:177-187 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:262-272 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:601-611 | StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:685-695 — 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 `StripePayments/StripePayments/Source/Helpers/STPBankAccountCollector.swift:177` 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 (9–11 lines × 2) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton.swift:90— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton.swift:90-100 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton.swift:356-364 — 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. 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 (7–9 lines × 4) StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:230— StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerSheet/CustomerSavedPaymentMethodsViewController.swift:230-236 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/CVCReconfirmationViewController.swift:109-115 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetFlowControllerViewController.swift:331-337 | StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetViewController.swift:251-259 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (6–8 lines × 3) StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:78— StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:78-83 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/STPPaymentMethodAddress.swift:70-75 | StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:254-261 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `StripePayments/StripePayments/Source/API Bindings/Models/PaymentIntents/STPPaymentIntentShippingDetailsAddressParams.swift:78` 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 (7–8 lines × 2) StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldFormatter.swift:15— StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldFormatter.swift:15-22 | StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldFormatter.swift:19-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldFormatter.swift:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextFieldFormatter.swift:15` calls `init` and `StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldFormatter.swift:13` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1460— StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1460-1465 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1471-1476 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1507-1512 | StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1536-1541 — 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 `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1460` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1469` calls `presentPollingVCForAction` and `StripePayments/StripePayments/Source/PaymentHandler/STPPaymentHandler.swift:1506` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (88 lines × 2) Example/AppClipExample/Shared/PaymentButton.swift:20— Example/AppClipExample/Shared/PaymentButton.swift:20-107 | Testers/IntegrationTester/IntegrationTester/Source/HelperViews/PaymentButton.swift:20-107 — before extracting anything, compare `Example/AppClipExample/Shared/PaymentButton.swift` and `Testers/IntegrationTester/IntegrationTester/Source/HelperViews/PaymentButton.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. Read the line range as the matched WINDOW rather than a finished unit: at `Example/AppClipExample/Shared/PaymentButton.swift: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.
Duplicated block (9 lines × 6) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirmParams.swift:14— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirmParams.swift:14-22 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAfterpayClearpayParams.swift:15-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCashAppParams.swift:15-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKlarnaParams.swift:15-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMultibancoParams.swift:14-22 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodRevolutPayParams.swift:12-20 — 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.
Duplicated block (5 lines × 5) StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/AccountSessionClaimedMessageHandler.swift:17— StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/AccountSessionClaimedMessageHandler.swift:17-24 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/CallSupplementalFunctionMessageHandler.swift:24-28 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/OpenAuthenticatedWebViewMessageHandler.swift:21-28 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/OpenFinancialConnectionsMessageHandler.swift:25-32 | StripeConnect/StripeConnect/Source/Internal/Webview/MessageHandlers/PageDidLoadMessageHandler.swift:17-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.
Duplicated block (8 lines × 4) StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:148— StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkLogin/LinkLoginViewController.swift:148-155 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkSignupPane/NetworkingLinkSignupViewController.swift:196-204 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingLinkVerification/NetworkingLinkVerificationViewController.swift:71-79 | StripeFinancialConnections/StripeFinancialConnections/Source/Native/NetworkingSaveToLinkVerification/NetworkingSaveToLinkVerificationViewController.swift:88-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (7 lines × 19) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAfterpayClearpay.swift:28— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAfterpayClearpay.swift:28-35 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAlma.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAmazonPay.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBillie.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBoleto.swift:48-55 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCashApp.swift:29-37 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCrypto.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKlarna.swift:29-37 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNetBanking.swift:32-38 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayByBank.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayPal.swift:28-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayPay.swift:27-33 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPrzelewy24.swift:28-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodRevolutPay.swift:26-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSEPADebit.swift:48-54 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSatispay.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSunbit.swift:28-36 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodWeChatPay.swift:28-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodWero.swift:28-36 — 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 19 call sites, so a change lands once.
Duplicated block (6 lines × 7) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBacsDebit.swift:38— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBacsDebit.swift:38-43 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBancontact.swift:28-33 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodEPS.swift:28-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGrabPay.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodLink.swift:29-34 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTwint.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/Sources/Types/STPSourceCardDetails.swift:54-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
Duplicated block (6 lines × 15) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGCash.swift:27— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGCash.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGoPay.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKakaoPay.swift:26-31 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMomo.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMondu.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgBankTransfer.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgUSSD.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgWallet.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayco.swift:26-31 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodQRIS.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodScalapay.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSequra.swift:26-31 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodShopeePay.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTouchNGo.swift:27-32 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTrueMoney.swift:27-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 15 call sites, so a change lands once.
Duplicated block (6 lines × 3) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKrCard.swift:32— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKrCard.swift:32-37 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNaverPay.swift:32-37 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgCard.swift:33-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 all 3 call sites, so a change lands once.
Duplicated block (6 lines × 45) StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirm.swift:18— StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirm.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAfterpayClearpay.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAlipay.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAlma.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAmazonPay.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBLIK.swift:19-26 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBancontact.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodBillie.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCardPresent.swift:17-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCashApp.swift:19-26 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodCrypto.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodEPS.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGCash.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGoPay.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodGrabPay.swift:17-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKakaoPay.swift:18-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodKlarna.swift:19-26 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodLink.swift:19-26 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMobilePay.swift:16-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMomo.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMondu.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodMultibanco.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgBankTransfer.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgUSSD.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodNgWallet.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodOXXO.swift:17-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayByBank.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayPal.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayPay.swift:17-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPayco.swift:18-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodPrzelewy24.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodQRIS.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodRevolutPay.swift:16-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSatispay.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodScalapay.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSequra.swift:18-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodShopeePay.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSunbit.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodSwish.swift:16-23 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTouchNGo.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTrueMoney.swift:19-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodTwint.swift:17-24 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodVipps.swift:16-22 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodWeChatPay.swift:18-25 | StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodWero.swift:18-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 45 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodOXXO.swift:27` calls `init` and `StripePayments/StripePayments/Source/API Bindings/Models/PaymentMethods/Types/STPPaymentMethodAffirm.swift:28` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22–25 lines × 2) ci_scripts/notify.rb:15— ci_scripts/notify.rb:15-39 | ci_scripts/notify_ci.rb:10-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `ci_scripts/notify.rb:15` 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· Near-duplicate member family (11 members, 26 shared lines) · ×1
Near-duplicate member family (11 members, 26 shared lines) Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:66— Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:66-101 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:68-110 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:68-110 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:68-110 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:66-112 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:69-111 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:67-109 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:66-108 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:67-109 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:68-110 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:65-100 — These 11 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 11 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 11 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 19 shared lines) · ×1
Near-duplicate member family (5 members, 19 shared lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:19— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:19-67 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:20-77 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:234-304 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:80-128 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift:40-80 — These 5 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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.
Near-duplicate member pair (20 shared lines) Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:259— Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:259-291 | Example/StripeConnectExample/StripeConnectExample/Settings/Appearance/AppSettings+AppearanceInfo.swift:326-361 — These two members are variants of one another: 20 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (17 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (17 members, 50+ identical tokens) Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:33— Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:32-49 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:35-52 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:37-54 | Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:32-49 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:32-49 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:33-50 — These 17 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 17 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 17 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) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:346— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:346-390 | Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:392-417 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:206-220 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:66-92 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:109-126 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:853-870 — 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:120— Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:120-129 | Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift:115-124 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:136-145 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:157-166 | Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift:454-472 — 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 (106 corresponding lines) · ×1
Edited copy of a member (106 corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:168— Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:168-273 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:275-382 — These two members are one piece of code written twice and then edited apart: 106 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 (73 corresponding lines) · ×1
Edited copy of a member (73 corresponding lines) Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1016— Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1016-1088 | Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1090-1167 — These two members are one piece of code written twice and then edited apart: 73 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, 43+ corresponding lines) · ×1
Edited copies of one member (3 members, 43+ corresponding lines) Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:65— Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:65-107 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:66-110 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:68-112 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:355— Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:355-393 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkControllerView.swift:440-483 — 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 copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) Example/CryptoOnramp Example/CryptoOnramp Example/IdentityVerificationView.swift:88— Example/CryptoOnramp Example/CryptoOnramp Example/IdentityVerificationView.swift:88-118 | Example/CryptoOnramp Example/CryptoOnramp Example/TermsOfServicePresentingView.swift:61-103 | Example/CryptoOnramp Example/CryptoOnramp Example/UserAttestationPresentingView.swift:56-86 — 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.
Duplicated block (65 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:827— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:827-891 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:827-891 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (3–57 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:144— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundController.swift:144-146 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:170-226 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:296-352 — 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 (42–43 lines × 2) Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1024— Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1024-1065 | Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1099-1141 — 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 `Example/FinancialConnections Example/FinancialConnections Example/Playground/PlaygroundViewModel.swift:1024` 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 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 (42 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:241— Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:241-282 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:241-282 — `Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 16 separate duplicated blocks between them, totalling at least 255 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (39 lines × 2) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:41— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:41-79 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:51-89 — before extracting anything, compare `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift` and `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (33 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:40— Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:40-72 | Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:255-287 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleWalletButtonsView.swift:255` 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 (29–30 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:171— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:171-200 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:203-232 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:197-225 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:193` calls `addAction`, `present` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:166` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25–26 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:434— Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:434-458 | Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:475-500 — 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 `Example/PaymentSheet Example/PaymentSheet Example/PlaygroundController.swift:475` 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 (25 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:264— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:264-288 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:321-345 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:264` 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 (23 lines × 2) Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:112— Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:112-134 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:133-155 — before extracting anything, compare `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift` and `Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–18 lines × 18) Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:93— Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:93-106 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:103-116 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:86-99 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:89-106 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:89-106 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:89-106 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:91-108 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:90-107 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:88-105 | Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:92-105 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:89-106 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:91-108 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:87-104 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:88-105 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:89-106 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:84-97 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:198-212 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:166-179 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:93` 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 (17–18 lines × 17) Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:33— Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:33-49 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:35-52 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:37-54 | Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:32-49 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:32-49 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:33-50 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:34-51 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:33-50 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 4) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:39— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:39-54 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:43-58 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:94-109 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift:54-69 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:39` 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 (11–14 lines × 11) Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:66— Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:66-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:68-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:68-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:68-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:66-76 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:69-80 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:67-78 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:66-77 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:67-78 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:68-79 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:65-76 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:66` 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 × 5) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:44— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:44-57 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:48-61 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:268-281 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:99-112 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift:59-72 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:266` calls `ComputedTotals` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:42` 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 (14 lines × 4) Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:129— Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift:129-142 | Example/PaymentSheet Example/PaymentSheet Example/PaymentSheetTestPlaygroundSettings.swift:426-439 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift:129-142 | Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/PaymentSheetTestPlaygroundSettings.swift:426-439 — `Example/PaymentSheet Example/PaymentSheet Example/CustomerSheetTestPlaygroundSettings.swift` and `Example/PaymentSheet Example/PaymentSheetLocalizationScreenshotGenerator/CustomerSheetTestPlaygroundSettings.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 5) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:174— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:174-186 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:205-217 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:206-218 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:237-249 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:199-211 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:174` 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 (10–12 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:75— Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:75-84 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:159-170 — 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:75` 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 (10–12 lines × 3) Example/UI Examples/UI Examples/Source/MockCustomerContext.swift:38— Example/UI Examples/UI Examples/Source/MockCustomerContext.swift:38-49 | Example/UI Examples/UI Examples/Source/MockCustomerContext.swift:53-64 | Example/UI Examples/UI Examples/Source/MockCustomerContext.swift:66-75 — 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 `Example/UI Examples/UI Examples/Source/MockCustomerContext.swift:38` 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 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 × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:139— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:139-150 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:172-183 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:184-195 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–10 lines × 2) Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:93— Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:93-102 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BoletoExampleViewController.swift:237-244 — 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 `Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:93` 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.
Duplicated block (4–9 lines × 3) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:224— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:224-232 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:256-264 | Example/PaymentSheet Example/PaymentSheet Example/ExampleEmbeddedElementCheckoutViewController.swift:245-248 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (8–9 lines × 2) Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:70— Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:70-78 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:111-118 — 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 `Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomerSheet.swift:70` 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 (8 lines × 5) Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:122— Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:122-129 | Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift:117-124 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewController.swift:138-145 | Example/IdentityVerification Example/IdentityVerification Example/ExampleVerificationViewControllerNativeUI.swift:159-166 | Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift:465-472 — before extracting anything, compare `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift` and `Example/FinancialConnections Example/FinancialConnections Example/ConnectAccountViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 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 `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:122` 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, `Example/FinancialConnections Example/FinancialConnections Example/CollectBankAccountTokenViewController.swift:120` calls `displayAlert`, `UIAlertController` and `Example/IdentityVerification Example/IdentityVerification Example/PlaygroundViewController.swift:464` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 7) Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:219— Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift:219-223 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutViewController.swift:31-35 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomCheckoutViewController.swift:35-39 | Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift:251-255 | Example/PaymentSheet Example/PaymentSheet Example/ExampleLinkPaymentCheckoutViewController.swift:40-44 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUICustomPaymentFlow.swift:87-91 | Example/PaymentSheet Example/PaymentSheet Example/ExampleSwiftUIPaymentSheet.swift:47-51 — before extracting anything, compare `Example/PaymentSheet Example/PaymentSheet Example/ExampleCheckoutDeferredViewController.swift` and `Example/PaymentSheet Example/PaymentSheet Example/ExampleCustomDeferredCheckoutViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 3) Example/IdentityVerification Example/IdentityVerification Example/AppDelegate.swift:13— Example/IdentityVerification Example/IdentityVerification Example/AppDelegate.swift:13-30 | Example/StripeConnectExample/StripeConnectExample/AppDelegate.swift:13-30 | StripePayments/StripePaymentsTestHostApp/AppDelegate.swift:13-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 8) Example/CryptoOnramp Example/CryptoOnramp Example/ComplianceIdentifiersEntryView.swift:72— Example/CryptoOnramp Example/CryptoOnramp Example/ComplianceIdentifiersEntryView.swift:72-80 | Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift:33-41 | Example/CryptoOnramp Example/CryptoOnramp Example/IdentityVerificationView.swift:25-33 | Example/CryptoOnramp Example/CryptoOnramp Example/PaymentSummaryView.swift:50-58 | Example/CryptoOnramp Example/CryptoOnramp Example/PaymentView.swift:213-221 | Example/CryptoOnramp Example/CryptoOnramp Example/UserAttestationPresentingView.swift:25-33 | Example/CryptoOnramp Example/CryptoOnramp Example/WalletOwnershipVerificationSheet.swift:33-41 | Example/CryptoOnramp Example/CryptoOnramp Example/WalletSelectionView.swift:32-40 — 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 8 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Example/CryptoOnramp Example/CryptoOnramp Example/CryptoOnrampExampleView.swift:29` calls `AppStorage`, `Environment` and `Example/CryptoOnramp Example/CryptoOnramp Example/PaymentSummaryView.swift:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 18) Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:14— Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:14-19 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlipayExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BacsDebitViewController.swift:21-26 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:13-18 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:16-21 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:14-19 | Example/Non-Card Payment Examples/Non-Card Payment Examples/GrabPayExampleViewController.swift:18-23 | Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:14-19 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:13-18 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:13-18 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:14-19 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:15-20 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SwishExampleViewController.swift:14-19 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 16) Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:52— Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift:52-60 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift:53-61 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AlmaExampleViewController.swift:53-63 | Example/Non-Card Payment Examples/Non-Card Payment Examples/AmazonPayExampleViewController.swift:53-63 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BillieExampleViewController.swift:53-63 | Example/Non-Card Payment Examples/Non-Card Payment Examples/BlikExampleViewController.swift:51-61 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CashAppExampleViewController.swift:54-64 | Example/Non-Card Payment Examples/Non-Card Payment Examples/CryptoExampleViewController.swift:52-62 | Example/Non-Card Payment Examples/Non-Card Payment Examples/KlarnaExampleViewController.swift:52-60 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MobilePayExampleViewController.swift:51-61 | Example/Non-Card Payment Examples/Non-Card Payment Examples/MultibancoExampleViewController.swift:53-63 | Example/Non-Card Payment Examples/Non-Card Payment Examples/RevolutPayExampleViewController.swift:51-61 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SatispayExampleViewController.swift:52-62 | Example/Non-Card Payment Examples/Non-Card Payment Examples/SunbitExampleViewController.swift:53-63 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountConnectionsExampleViewController.swift:129-137 | Example/Non-Card Payment Examples/Non-Card Payment Examples/USBankAccountExampleViewController.swift:124-132 — before extracting anything, compare `Example/Non-Card Payment Examples/Non-Card Payment Examples/AffirmExampleViewController.swift` and `Example/Non-Card Payment Examples/Non-Card Payment Examples/AfterpayClearpayExampleViewController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 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.
Off the main sequence: StripeCore — StripeCore: abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
Sync-over-async blocking StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutSessionPoller.swift:25— `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.
Orphaned file StripeUICore/StripeUICore/Source/Controls/Button.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionTableView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeConnect/StripeConnect/Source/Internal/Webview/ConnectWebViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeConnect/StripeConnect/Source/EmbeddedComponentManager+Appearance.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerNoAccountEligibleErrorView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeCardScan/StripeCardScan/Source/CardScan/CardUtils/CreditCardUtils.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/OcrMainLoop.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeIdentity/StripeIdentity/Source/NativeComponents/Views/DebugView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/GenericInfoScreen/GenericInfoBodyView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/DataAccessNoticeViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/Error/ErrorViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/LinkAccountPicker/LinkAccountPickerBodyView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeCardScan/StripeCardScan/Source/CardVerify/VerifyCardViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripePayments/StripePayments/Source/API Bindings/Models/STPAddress.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file fastlane/SnapshotHelper.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionSearchBar.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeConnect/StripeConnect/Source/Internal/Analytics/ComponentAnalyticsClient.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeCardScan/StripeCardScan/Source/CardScan/Extensions/Image+utils.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/PartnerAuth/PrepaneViews.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeIdentity/StripeIdentity/Source/NativeComponents/Detectors/IDDetector/IDDetectorOutput.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryFormView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeFinancialConnections/StripeFinancialConnections/Source/Native/Shared/AttributedTextView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageScanningSession/ImageScanningSessionDelegate.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageUploaders/IdentityImageUploader.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate ci_scripts/notify.rb:22— `!env_sdk_failure_notif_endpoint || !env_sdk_failure_notif_endpoint_hmac_key` appears character-identically in 2 files — ci_scripts/notify.rb, ci_scripts/notify_ci.rb. 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 ci_scripts/push_snapshots.rb:24— `ENV['BITRISE_GIT_BRANCH'] || `git rev-parse --abbrev-ref HEAD`.strip` appears character-identically in 2 files — ci_scripts/push_snapshots.rb, ci_scripts/trigger_react_native_ci_for_release.rb. 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 ci_scripts/size_report_modules.rb:62— `env['BITRISE_PULL_REQUEST'].to_s.empty? || env['BITRISE_GIT_BRANCH'].to_s.start_with?('releases/')` appears character-identically in 2 files — ci_scripts/size_report_modules.rb, ci_scripts/snapshot_test_selection.rb. 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 StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewModel.swift:109— `!linkAccount.isRegistered && requiresNameCollection` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/SignUp/LinkSignUpViewModel.swift, StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.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 StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift:426— `!session.accounts.data.isEmpty || session.paymentAccount != nil || session.bankAccountToken != nil` appears character-identically in 2 files — StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowController.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Web/FinancialConnectionsWebFlowViewController.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 StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift:430— `LiquidGlassDetector.isEnabledInMerchantApp && theme.cornerRadius == nil` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/CardSection/CardSectionElement.swift, StripeUICore/StripeUICore/Source/Elements/SegmentedSelectorElement.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 StripeCore/StripeCore/Source/Analytics/STPAnalyticsClient.swift:104— `NSClassFromString("XCTest") != nil || ProcessInfo.processInfo.environment["UITesting"] != nil` appears character-identically in 2 files — StripeCore/StripeCore/Source/Analytics/STPAnalyticsClient.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/RotatingCardBrandsView.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 StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/LinkSheetContainer.swift:39— `SheetImplementationResolver.isRequiredForDevice || usesNativeSheet` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Controllers/LinkSheetContainer.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/PaymentSheetContainer.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 StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/New Payment Method Screen/PaymentMethodTypeCollectionView.swift:188— `UIDevice.current.userInterfaceIdiom == .pad || UIDevice.current.userInterfaceIdiom == .mac` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/New Payment Method Screen/PaymentMethodTypeCollectionView.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/BottomSheetViewController.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 StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:94— `billingDetails?.email == nil && shippingAddress?.email != nil` appears character-identically in 2 files — StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift, StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.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 StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift:100— `billingDetails?.phone == nil && shippingAddress?.phone != nil` appears character-identically in 2 files — StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift, StripePayments/StripePayments/Source/API Bindings/STPAPIClient+ApplePay.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 StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/SetupIntent.swift:52— `components.count >= 2 && components[0].hasPrefix("seti_")` appears character-identically in 2 files — StripeApplePay/StripeApplePay/Source/PaymentsCore/API/Models/SetupIntent.swift, StripePayments/StripePayments/Source/API Bindings/Models/SetupIntents/STPSetupIntent.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 StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/LinkUI.swift:235— `configuration.appearance.cornerRadius == nil && LiquidGlassDetector.isEnabledInMerchantApp` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/LinkUI.swift, StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/ViewModels/LinkInlineSignupViewModel.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 StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:34— `consumerPublishableKey == nil && oldValue != nil` appears character-identically in 2 files — StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowDataManager.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 StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift:41— `consumerSession == nil && oldValue != nil` appears character-identically in 2 files — StripeFinancialConnections/StripeFinancialConnections/Source/API Bindings/FinancialConnectionsAsyncAPIClient.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/NativeFlowDataManager.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 StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift:70— `dataSource.manifest.allowManualEntry && !dataSource.reduceManualEntryProminenceInErrors` appears character-identically in 3 files — StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerViewController.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/AttachLinkedPaymentAccount/AttachLinkedPaymentAccountViewController.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/Error/ErrorViewController.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 StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift:316— `elementsSession.paymentMethodRemoveLast(configuration: configuration) && loadResult.customerProvider.allowsPaymentMethodRemoval(elementsSess…` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Embedded/EmbeddedPaymentElement+Internal.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/PaymentSheetVerticalViewController.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 StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/MainLoopStateMachine.swift:103— `hasExpiryPrediction || prediction.expiryForDisplay != nil` appears character-identically in 2 files — StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/MainLoopStateMachine.swift, StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.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 Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift:40— `isConfirmingPayment || name.isEmpty || email.isEmpty` appears character-identically in 3 files — Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithContactInfoView.swift, Testers/IntegrationTester/IntegrationTester/Source/Views/PaymentMethodWithShippingInfoView.swift, Testers/IntegrationTester/IntegrationTester/Source/Views/SEPADebitView.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 Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift:27— `isConfirmingPayment || paymentMethodParams == nil` appears character-identically in 2 files — Testers/IntegrationTester/IntegrationTester/Source/Views/AUBECSDebitView.swift, Testers/IntegrationTester/IntegrationTester/Source/Views/CardView.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 StripePaymentSheet/StripePaymentSheet/Source/Categories/STPPaymentMethod+PaymentSheet.swift:147— `isLinkPaymentMethod || isLinkPassthroughMode` appears character-identically in 2 files — StripePaymentSheet/StripePaymentSheet/Source/Categories/STPPaymentMethod+PaymentSheet.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentOption+Images.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 StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:39— `localizedTypes.contains(String.Localized.driverLicense) && localizedTypes.contains(String.Localized.governmentIssuedId)` appears character-identically in 2 files — StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift, StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController+Strings.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 StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:37— `localizedTypes.contains(String.Localized.driverLicense) && localizedTypes.contains(String.Localized.passport)` appears character-identically in 2 files — StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift, StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController+Strings.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 StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift:41— `localizedTypes.contains(String.Localized.passport) && localizedTypes.contains(String.Localized.governmentIssuedId)` appears character-identically in 2 files — StripeIdentity/StripeIdentity/Source/NativeComponents/DocumentSide.swift, StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController+Strings.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 StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldValidator.swift:60— `monthState == .valid && yearState == .valid` appears character-identically in 2 files — StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardExpiryInputTextFieldValidator.swift, StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/STPPaymentCardTextFieldViewModel.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.
No direct assertions: test_encodingTopLevelEmptyStruct StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:72— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelEmptyClass StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:77— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelSingleValueEnum StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:85— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelSingleValueStruct StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:95— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelSingleValueClass StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:102— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelStructuredStruct StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:108— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelStructuredClass StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:114— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelStructuredSingleStruct StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:121— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelStructuredSingleClass StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:127— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingTopLevelDeepStructuredType StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:133— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingOutputFormattingDefault StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:140— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingOutputFormattingSortedKeys StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:256— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingOutputFormattingPrettyPrintedSortedKeys StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:272— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingDate StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:294— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingDateSecondsSince1970 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:301— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingBase64Data StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:316— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_encodingNonConformingFloatStrings StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:325— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfNil StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:465— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfInt8 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:470— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfUInt8 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:474— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfInt16 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:478— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfUInt16 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:482— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfInt32 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:486— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfUInt32 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:490— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: test_codingOfInt64 StripeCore/StripeCoreTests/External/TestJSONEncoder.swift:494— No conventional assertion call was detected, and 29 of 44 tests in `External` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 27 significant file(s) lose their only recent owner: StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/AdditionalKYCFlowCoordinator.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/ProofOfAddressView.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/View+DocumentSelection.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/DocumentPicker.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/CryptoOnrampAnalyticsEvent.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/UI/Views/SourceOfFundsDocumentView.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/DocumentCollectionConfiguration.swift, StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/AdditionalKYC/DocumentUploadModel.swift (+19 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 14 significant file(s) lose their only recent owner: StripePayments/StripePayments/Source/API Bindings/Models/Shared/STPIntentAction.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/TwoOptionSelectorView.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Currency Selector Element/CurrencySelectorElementUIView.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Elements/ExpandableDetailView.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/CustomerAdapter/CustomerPaymentOption.swift, StripePayments/StripePayments/Source/API Bindings/Models/ConfirmationTokens/STPConfirmationTokenParams.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/FlowControllerSelectionSnapshot.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Currency Selector Element/CurrencySelectorElement+Appearance.swift (+6 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 14 significant file(s) lose their only recent owner: ci_scripts/record_snapshots.rb, ci_scripts/build_documentation.rb, ci_scripts/snapshot_test_selection.rb, ci_scripts/dead_code/run_scan.rb, ci_scripts/size_report_cache.rb, ci_scripts/test.rb, StripeApplePay/StripeApplePay/Source/Extensions/BillingDetails+ApplePay.swift, ci_scripts/check_paymentsheet_test_sharding.rb (+6 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 11 significant file(s) lose their only recent owner: StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/NativeSheetContainerViewController.swift, StripePaymentSheet/StripePaymentSheet/Source/Helpers/STPCardScanner.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PaymentMethodMessagingElement.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Vertical Main Screen/RowButton+PaymentMethodMessagingSublabelView.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMMEUIView.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Views/BNPLFormHeaderView.swift, ci_scripts/changelog_utils.rb, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentMethodMessagingElement/PMME+API.swift (+3 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 5 significant file(s) lose their only recent owner: StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/DocumentCaptureViewController.swift, StripeCameraCore/StripeCameraCore/Source/Coordinators/CameraSession.swift, StripeIdentity/StripeIdentity/Source/API Bindings/SelfieUploader+API.swift, StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageUploaders/SelfieUploader.swift, StripeIdentity/StripeIdentity/Source/NativeComponents/Coordinators/ImageScanner/FaceScanner/FaceScanner.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 4 significant file(s) lose their only recent owner: REDACTED, StripePayments/StripePayments/Source/PaymentHandler/STPAnalyticsClient+STPPaymentHandler.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/CheckoutSessionPoller.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/ViewControllers/AutoComplete/String+AutoComplete.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 4 significant file(s) lose their only recent owner: StripeUICore/StripeUICore/Source/Elements/SegmentedSelectorElement.swift, StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Address/AddressAutocompleteModels.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Express Checkout Element/ExpressCheckoutElementUtilities.swift, StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/Checkout/Express Checkout Element/ExpressCheckoutElement+Configuration.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #8 — If anonymized user #8 becomes unavailable, 4 significant file(s) lose their only recent owner: StripeFinancialConnections/StripeFinancialConnections/Source/Native/Consent/ConsentLogoView.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/GenericError/GenericErrorViewController.swift, StripeFinancialConnectionsLite/StripeFinancialConnectionsLite/Source/Controllers/FCLiteAuthFlowViewController.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Common/FlowRouter.swift. Pair on, review, or document these before any departure.
P10 · Library API & versioning· Implementation type on the public API · ×5
Implementation type on the public API StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:14— 1 public type in `StripeConnect~StripeConnect~Internal` is marked as implementation by its own namespace, folder or name: `ConnectActivityIndicator` (StripeConnect/StripeConnect/Source/Internal/ConnectActivityIndicator.swift:14, `Internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/StripeCryptoOnrampBundleLocator.swift:11— 1 public type in `StripeCryptoOnramp~StripeCryptoOnramp~Internal` is marked as implementation by its own namespace, folder or name: `StripeCryptoOnrampBundleLocator` (StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/StripeCryptoOnrampBundleLocator.swift:11, `Internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/LinkPaymentMethodType.swift:13— 5 public types in `StripePaymentSheet~StripePaymentSheet~Internal` are marked as implementation by their own namespace, folder or name: `LinkPaymentMethodType` (StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/LinkPaymentMethodType.swift:13, `Internal`), `LinkRequestSurface` (StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/Link/LinkRequestSurface.swift:10, `Internal`), `STPElementsSession` (StripePaymentSheet/StripePaymentSheet/Source/Internal/API Bindings/v1-elements-sessions/STPElementsSession.swift:13, `Internal`), `VerifyKYCInfo` (StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCInfo.swift:11, `Internal`), `VerifyKYCResult` (StripePaymentSheet/StripePaymentSheet/Source/Internal/Link/Verify KYC/VerifyKYCResult.swift:11, `Internal`). 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 StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:19— 10 public types in `StripePayments~StripePayments~Internal` are marked as implementation by their own namespace, folder or name: `APIRequest` (StripePayments/StripePayments/Source/Internal/API Bindings/APIRequest.swift:19, `Internal`), `STPEmptyStripeResponse` (StripePayments/StripePayments/Source/Internal/API Bindings/STPEmptyStripeResponse.swift:13, `Internal`), `STPFormEncoder` (StripePayments/StripePayments/Source/Internal/API Bindings/STPFormEncoder.swift:11, `Internal`), `STPPaymentMethodListDeserializer` (StripePayments/StripePayments/Source/Internal/API Bindings/STPPaymentMethodListDeserializer.swift:12, `Internal`), `PaymentAnalytic` (StripePayments/StripePayments/Source/Internal/Analytics/STPAnalyticsClient+Payments.swift:310, `Internal`), `FinancialConnectionsSDKAvailability` (StripePayments/StripePayments/Source/Internal/Helpers/ConnectionsSDKAvailability.swift:13, `Internal`), `STPPaymentHandlerPollingStatus` (StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:19, `Internal`), `STPPaymentHandlerPollingResult` (StripePayments/StripePayments/Source/Internal/STPPaymentHandlerActionParams.swift:26, `Internal`), and 2 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 StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/CardBrandView.swift:16— 12 public types in `StripePaymentsUI~StripePaymentsUI~Internal` are marked as implementation by their own namespace, folder or name: `CardBrandView` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/CardBrandView.swift:16, `Internal`), `STPCardCVCInputTextField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardCVCInputTextField.swift:14, `Internal`), `STPCardNumberInputTextField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextField.swift:14, `Internal`), `InputMode` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPCardNumberInputTextField.swift:17, `Internal`), `STPPostalCodeInputTextField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/Card/STPPostalCodeInputTextField.swift:13, `Internal`), `STPCountryPickerInputField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPCountryPickerInputField.swift:12, `Internal`), `STPGenericInputPickerFieldDataSource` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPGenericInputPickerField.swift:12, `Internal`), `STPGenericInputPickerField` (StripePaymentsUI/StripePaymentsUI/Source/Internal/UI/Views/Inputs/STPGenericInputPickerField.swift:26, `Internal`), and 4 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) — 4 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 (89 single-owned of 847 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; 847 of the 1673 production source files in this repository met that bar). They are anonymized user #9 (2 file(s)), anonymized user #10 (2 file(s)), anonymized user #11 (1 file(s)), anonymized user #12 (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: StripeIdentity/StripeIdentity/Source/NativeComponents/Views/BottomSheetView.swift, StripeIdentity/StripeIdentity/Source/NativeComponents/ViewControllers/BottomSheetViewController.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Helpers/String+Localized.swift, StripeCore/StripeCore/Source/Connections Bindings/LinkBrand.swift, StripeConnect/StripeConnect/Source/Components/CheckScanningController.swift, StripePaymentSheet/StripePaymentSheet/Source/Helpers/UIImageView+Extensions.swift.
No ADRs found Testers/IntegrationTester/IntegrationTester.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 `Testers/IntegrationTester/IntegrationTester.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency· `tellUsAboutYourSourceOfFunds` spells `Us` where 15 names in the project spell it `US` · ×1
`tellUsAboutYourSourceOfFunds` spells `Us` where 15 names in the project spell it `US` StripeCryptoOnramp/StripeCryptoOnramp/Source/Internal/String+Localized.swift:90— 15 of 16 names in project Example~UI Examples~UI Examples spell the token `US` (15 of 16; unit: names in project Example~UI Examples~UI Examples containing `US`). Peers: ManualEntryValidator.isUSRoutingNumber (StripeFinancialConnections/StripeFinancialConnections/Source/Native/ManualEntry/ManualEntryValidator.swift:93); PaymentSheetFormFactory.makeUSBankAccount (StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:796); PaymentSheetFormFactory.makeUSBankAccountCopyLabel (StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/PaymentSheetFormFactory/PaymentSheetFormFactory.swift:1103); SavedPaymentMethodFormFactory.makeUSBankAccount (StripePaymentSheet/StripePaymentSheet/Source/PaymentSheet/SavedPaymentMethodFormFactory/SavedPaymentMethodFormFactory+USBankAccount.swift:13); STPCollectBankAccountParams.collectUSBankAccountParams (StripePayments/StripePayments/Source/API Bindings/Models/ACH/STPCollectBankAccountParams.swift:25). Rename to `tellUSAboutYourSourceOfFunds`. [rule N6]
D21 · Naming Consistency· `sanitizedExpirationDateFromOCRString` spells `OCR` where 34 names in the project spell it `Ocr` · ×1
`sanitizedExpirationDateFromOCRString` spells `OCR` where 34 names in the project spell it `Ocr` StripePaymentsUI/StripePaymentsUI/Source/Helpers/STPStringUtils.swift:77— 34 of 35 names in project Example~UI Examples~UI Examples spell the token `Ocr` (34 of 35; unit: names in project Example~UI Examples~UI Examples containing `Ocr`). Peers: StripeCardScan~StripeCardScan~CardScan.AppleOcr (StripeCardScan/StripeCardScan/Source/CardScan/AppleOcr/AppleOcr.swift:4); AppleOcr.performOcr (StripeCardScan/StripeCardScan/Source/CardScan/AppleOcr/AppleOcr.swift:31); StripeCardScan~StripeCardScan~CardScan.AppleCreditCardOcr (StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/AppleCreditCardOcr.swift:10); StripeCardScan~StripeCardScan~CardScan.CreditCardOcrImplementation (StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/CreditCardOcrImplementation.swift:13); UxFrameConfidenceValues.hasOcr (StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/CreditCardOcrPrediction.swift:13). Rename to `sanitizedExpirationDateFromOcrString`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 9 of 18 project(s) overshoot their size bounds, lowering Project Cohesion to 1.2/10. The most over is `StripePaymentSheet` (72517 LoC, 587 module-visible types across 62 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 190 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: StripeUICore/StripeUICore/Source/Controls/Button.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/InstitutionPicker/InstitutionTableView.swift, StripeConnect/StripeConnect/Source/Internal/Webview/ConnectWebViewController.swift, StripeConnect/StripeConnect/Source/EmbeddedComponentManager+Appearance.swift, StripeFinancialConnections/StripeFinancialConnections/Source/Native/AccountPicker/AccountPickerNoAccountEligibleErrorView.swift, StripeCardScan/StripeCardScan/Source/CardScan/CardUtils/CreditCardUtils.swift, StripeCardScan/StripeCardScan/Source/CardScan/CreditCardOcr/OcrMainLoop.swift, StripeCardScan/StripeCardScan/Source/CardVerify/CardVerifyStateMachine.swift (and 182 more) (195 orphaned of 848 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; 848 of the 1673 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift stripe3ds2-support/Pods/iOSSnapshotTestCase/README.md:57— stripe3ds2-support/Pods/iOSSnapshotTestCase/README.md links to `FBSnapshotTestCaseDemo/Scheme_FB_REFERENCE_IMAGE_DIR.png`, but `stripe3ds2-support/Pods/iOSSnapshotTestCase/FBSnapshotTestCaseDemo/Scheme_FB_REFERENCE_IMAGE_DIR.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `Stripe`.
No SAST REDACTED:3— No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 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.
X5 · Nullable reference types· Ruby's type checker does not check nil everywhere · ×1
Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 47 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Outdated: swift-custom-dump — `swift-custom-dump` is resolved at 1.3.3, but 1.7.3 is the newest release tagged on https://github.com/pointfreeco/swift-custom-dump within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-custom-dump` reaches this one with no change to Package.swift.
Outdated: xctest-dynamic-overlay — `xctest-dynamic-overlay` is resolved at 1.6.1, but 1.13.1 is the newest release tagged on https://github.com/pointfreeco/xctest-dynamic-overlay within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update xctest-dynamic-overlay` reaches this one with no change to Package.swift.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dc51-2a4b-7ee1-adf2-4dd89574514a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 35 · Warnings: 1637 · Recommendations: 280 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 23:07 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.