Public report of kickstarter/ios-oss, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 11:00 UTC · Survey ID cd_3a43e314a3ac47d99a609f8283f4322a
kickstarter/ios-oss
Measured 26 October 2026, 10:48 UTC, at code version 5f5463c
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
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 scoreAdequate
CriticalWeakAdequateStrongExemplary
No change 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: 109,914 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Production Readiness, 33
Findings by how serious they are
22 critical502 serious359 minor
33 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 10:48 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
42of 42 dimensions measured by tools.
826of 883 findings point to an exact file and line, so you can open each one in the code. The other 57 concern the repository as a whole, such as missing documentation.
42dimensions across 6 lenses, read from 109,914 lines of product code in 9 projects.
kickstarter/ios-oss falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100 and is rated Adequate, and nine of its 22 critical findings are security problems.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 10 points. Updating or replacing each dependency with a known problem comes next, worth about 9 points. Raising Production Readiness to 70 would lift the score to about 63.
Four passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and thirteen sets of files in separate parts keep changing together, which points to hidden dependencies. Replacing each exposed password or key, pinning each tool to an exact version and making the hidden dependencies explicit would close these risks. Updating the vulnerable packages would fix the package with a known security hole.
The product code is 109,914 lines, about €180,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.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 1 finding
This critical or serious finding was in the previous survey, on 12 October 2026, and is gone from this one.
Documentation (README) · README may be stale
Rebuild cost: about €180,000 · Estimate
Cost to rebuild
€60,000 to €300,000, for 997 to 3,163 hours of work, about 1.2 person-years for 1 to 3 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 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 109,914 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: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 10 points · Low effort · REDACTED Scanning
2
Resolve the 1 Dependency not covered by the committed resolution finding(s) in Dependency Hygiene.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 9 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Production Readiness, at 33 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
11 modules, with 51 dependencies between them. One loop runs through 11 of the modules, marked above the diagonal.
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→5 GraphAPI~Operations uses KsApi~KsApipart of a loop✕
Connections
72 pairs of types, where a type in GraphAPI~Operations uses a type in KsApi~KsApi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Operations uses KsApi~KsApi, so a change to KsApi~KsApi can break GraphAPI~Operations, while a change to GraphAPI~Operations can't break KsApi~KsApi.
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→8 GraphAPI~Operations uses GraphAPI~Schemapart of a loop✕
Connections
112 pairs of types, where a type in GraphAPI~Operations uses a type in GraphAPI~Schema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Operations uses GraphAPI~Schema, so a change to GraphAPI~Schema can break GraphAPI~Operations, while a change to GraphAPI~Operations can't break GraphAPI~Schema.
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→9 GraphAPI~Operations uses GraphAPI~Fragmentspart of a loop✕
Connections
38 pairs of types, where a type in GraphAPI~Operations uses a type in GraphAPI~Fragments. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Operations uses GraphAPI~Fragments, so a change to GraphAPI~Fragments can break GraphAPI~Operations, while a change to GraphAPI~Operations can't break GraphAPI~Fragments.
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→10 GraphAPI~Operations uses Library~Librarypart of a loop✕
Connections
105 pairs of types, where a type in GraphAPI~Operations uses a type in Library~Library. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Operations uses Library~Library, so a change to Library~Library can break GraphAPI~Operations, while a change to GraphAPI~Operations can't break Library~Library.
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→4 ServerDrivenUI~ServerDrivenUI uses KDS~KDSpart of a loop✕
Connections
6 pairs of types, where a type in ServerDrivenUI~ServerDrivenUI uses a type in KDS~KDS.
ServerDrivenUI~ServerDrivenUI uses KDS~KDS, so a change to KDS~KDS can break ServerDrivenUI~ServerDrivenUI, while a change to ServerDrivenUI~ServerDrivenUI can't break KDS~KDS.
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→5 ServerDrivenUI~ServerDrivenUI uses KsApi~KsApipart of a loop✕
Connections
8 pairs of types, where a type in ServerDrivenUI~ServerDrivenUI uses a type in KsApi~KsApi.
ServerDrivenUI~ServerDrivenUI uses KsApi~KsApi, so a change to KsApi~KsApi can break ServerDrivenUI~ServerDrivenUI, while a change to ServerDrivenUI~ServerDrivenUI can't break KsApi~KsApi.
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→9 ServerDrivenUI~ServerDrivenUI uses GraphAPI~Fragmentspart of a loop✕
Connections
1 pair of types, where a type in ServerDrivenUI~ServerDrivenUI uses a type in GraphAPI~Fragments.
ServerDrivenUI~ServerDrivenUI uses GraphAPI~Fragments, so a change to GraphAPI~Fragments can break ServerDrivenUI~ServerDrivenUI, while a change to ServerDrivenUI~ServerDrivenUI can't break GraphAPI~Fragments.
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→10 ServerDrivenUI~ServerDrivenUI uses Library~Librarypart of a loop✕
Connections
23 pairs of types, where a type in ServerDrivenUI~ServerDrivenUI uses a type in Library~Library.
ServerDrivenUI~ServerDrivenUI uses Library~Library, so a change to Library~Library can break ServerDrivenUI~ServerDrivenUI, while a change to ServerDrivenUI~ServerDrivenUI can't break Library~Library.
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.
ServerDrivenUI~ServerDrivenUITestHelpers uses ServerDrivenUI~ServerDrivenUI, so a change to ServerDrivenUI~ServerDrivenUI can break ServerDrivenUI~ServerDrivenUITestHelpers, while a change to ServerDrivenUI~ServerDrivenUITestHelpers can't break ServerDrivenUI~ServerDrivenUI.
Position
Below the diagonal: ServerDrivenUI~ServerDrivenUITestHelpers uses a module listed above it, which is the healthy direction.
3→4 ServerDrivenUI~ServerDrivenUITestHelpers uses KDS~KDSpart of a loop✕
Connections
7 pairs of types, where a type in ServerDrivenUI~ServerDrivenUITestHelpers uses a type in KDS~KDS.
ServerDrivenUI~ServerDrivenUITestHelpers uses KDS~KDS, so a change to KDS~KDS can break ServerDrivenUI~ServerDrivenUITestHelpers, while a change to ServerDrivenUI~ServerDrivenUITestHelpers can't break KDS~KDS.
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→10 ServerDrivenUI~ServerDrivenUITestHelpers uses Library~Librarypart of a loop✕
Connections
2 pairs of types, where a type in ServerDrivenUI~ServerDrivenUITestHelpers uses a type in Library~Library.
ServerDrivenUI~ServerDrivenUITestHelpers uses Library~Library, so a change to Library~Library can break ServerDrivenUI~ServerDrivenUITestHelpers, while a change to ServerDrivenUI~ServerDrivenUITestHelpers can't break Library~Library.
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.
KDS~KDS uses ServerDrivenUI~ServerDrivenUI, so a change to ServerDrivenUI~ServerDrivenUI can break KDS~KDS, while a change to KDS~KDS can't break ServerDrivenUI~ServerDrivenUI.
Position
Below the diagonal: KDS~KDS uses a module listed above it, which is the healthy direction.
KDS~KDS uses ServerDrivenUI~ServerDrivenUITestHelpers, so a change to ServerDrivenUI~ServerDrivenUITestHelpers can break KDS~KDS, while a change to KDS~KDS can't break ServerDrivenUI~ServerDrivenUITestHelpers.
Position
Below the diagonal: KDS~KDS uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in KsApi~KsApi uses a type in GraphAPI~Operations. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
KsApi~KsApi uses GraphAPI~Operations, so a change to GraphAPI~Operations can break KsApi~KsApi, while a change to KsApi~KsApi can't break GraphAPI~Operations.
Position
Below the diagonal: KsApi~KsApi uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in KsApi~KsApi uses a type in KDS~KDS.
The types involved
KsApi~KsApi.Result → KDS~KDS.Success
Direction
KsApi~KsApi uses KDS~KDS, so a change to KDS~KDS can break KsApi~KsApi, while a change to KsApi~KsApi can't break KDS~KDS.
Position
Below the diagonal: KsApi~KsApi uses a module listed above it, which is the healthy direction.
5→8 KsApi~KsApi uses GraphAPI~Schemapart of a loop✕
Connections
60 pairs of types, where a type in KsApi~KsApi uses a type in GraphAPI~Schema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
KsApi~KsApi uses GraphAPI~Schema, so a change to GraphAPI~Schema can break KsApi~KsApi, while a change to KsApi~KsApi can't break GraphAPI~Schema.
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→9 KsApi~KsApi uses GraphAPI~Fragmentspart of a loop✕
Connections
29 pairs of types, where a type in KsApi~KsApi uses a type in GraphAPI~Fragments. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
KsApi~KsApi uses GraphAPI~Fragments, so a change to GraphAPI~Fragments can break KsApi~KsApi, while a change to KsApi~KsApi can't break GraphAPI~Fragments.
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→10 KsApi~KsApi uses Library~Librarypart of a loop✕
Connections
213 pairs of types, where a type in KsApi~KsApi uses a type in Library~Library. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Kickstarter-Framework~Kickstarter-Framework uses GraphAPI~Operations, so a change to GraphAPI~Operations can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break GraphAPI~Operations.
Position
Below the diagonal: Kickstarter-Framework~Kickstarter-Framework uses a module listed above it, which is the healthy direction.
71 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in ServerDrivenUI~ServerDrivenUI. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Kickstarter-Framework~Kickstarter-Framework uses ServerDrivenUI~ServerDrivenUI, so a change to ServerDrivenUI~ServerDrivenUI can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break ServerDrivenUI~ServerDrivenUI.
Position
Below the diagonal: Kickstarter-Framework~Kickstarter-Framework uses a module listed above it, which is the healthy direction.
Kickstarter-Framework~Kickstarter-Framework uses ServerDrivenUI~ServerDrivenUITestHelpers, so a change to ServerDrivenUI~ServerDrivenUITestHelpers can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break ServerDrivenUI~ServerDrivenUITestHelpers.
Position
Below the diagonal: Kickstarter-Framework~Kickstarter-Framework uses a module listed above it, which is the healthy direction.
63 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in KDS~KDS. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Kickstarter-Framework~Kickstarter-Framework uses KDS~KDS, so a change to KDS~KDS can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break KDS~KDS.
Position
Below the diagonal: Kickstarter-Framework~Kickstarter-Framework uses a module listed above it, which is the healthy direction.
137 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in KsApi~KsApi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Kickstarter-Framework~Kickstarter-Framework uses KsApi~KsApi, so a change to KsApi~KsApi can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break KsApi~KsApi.
Position
Below the diagonal: Kickstarter-Framework~Kickstarter-Framework uses a module listed above it, which is the healthy direction.
6→8 Kickstarter-Framework~Kickstarter-Framework uses GraphAPI~Schemapart of a loop✕
Connections
3 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in GraphAPI~Schema.
Kickstarter-Framework~Kickstarter-Framework uses GraphAPI~Schema, so a change to GraphAPI~Schema can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break GraphAPI~Schema.
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→9 Kickstarter-Framework~Kickstarter-Framework uses GraphAPI~Fragmentspart of a loop✕
Connections
12 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in GraphAPI~Fragments.
Kickstarter-Framework~Kickstarter-Framework uses GraphAPI~Fragments, so a change to GraphAPI~Fragments can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break GraphAPI~Fragments.
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→10 Kickstarter-Framework~Kickstarter-Framework uses Library~Librarypart of a loop✕
Connections
1336 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in Library~Library. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Kickstarter-Framework~Kickstarter-Framework uses Library~Library, so a change to Library~Library can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break Library~Library.
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→11 Kickstarter-Framework~Kickstarter-Framework uses Experimentation~Experimentationpart of a loop✕
Connections
2 pairs of types, where a type in Kickstarter-Framework~Kickstarter-Framework uses a type in Experimentation~Experimentation.
Kickstarter-Framework~Kickstarter-Framework uses Experimentation~Experimentation, so a change to Experimentation~Experimentation can break Kickstarter-Framework~Kickstarter-Framework, while a change to Kickstarter-Framework~Kickstarter-Framework can't break Experimentation~Experimentation.
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 repository uses a type in GraphAPI~Operations.
The types involved
repository.AppDelegate → GraphAPI~Operations.Data
Direction
repository uses GraphAPI~Operations, so a change to GraphAPI~Operations can break repository, while a change to repository can't break GraphAPI~Operations.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses Kickstarter-Framework~Kickstarter-Framework, so a change to Kickstarter-Framework~Kickstarter-Framework can break repository, while a change to repository can't break Kickstarter-Framework~Kickstarter-Framework.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
7→10 repository uses Library~Librarypart of a loop✕
Connections
3 pairs of types, where a type in repository uses a type in Library~Library.
repository uses Experimentation~Experimentation, so a change to Experimentation~Experimentation can break repository, while a change to repository can't break Experimentation~Experimentation.
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.
52 pairs of types, where a type in GraphAPI~Schema uses a type in KsApi~KsApi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Schema uses repository, so a change to repository can break GraphAPI~Schema, while a change to GraphAPI~Schema can't break repository.
Position
Below the diagonal: GraphAPI~Schema uses a module listed above it, which is the healthy direction.
8→10 GraphAPI~Schema uses Library~Librarypart of a loop✕
Connections
43 pairs of types, where a type in GraphAPI~Schema uses a type in Library~Library. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Schema uses Library~Library, so a change to Library~Library can break GraphAPI~Schema, while a change to GraphAPI~Schema can't break Library~Library.
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.
GraphAPI~Fragments uses ServerDrivenUI~ServerDrivenUI, so a change to ServerDrivenUI~ServerDrivenUI can break GraphAPI~Fragments, while a change to GraphAPI~Fragments can't break ServerDrivenUI~ServerDrivenUI.
Position
Below the diagonal: GraphAPI~Fragments uses a module listed above it, which is the healthy direction.
85 pairs of types, where a type in GraphAPI~Fragments uses a type in KsApi~KsApi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Fragments uses KsApi~KsApi, so a change to KsApi~KsApi can break GraphAPI~Fragments, while a change to GraphAPI~Fragments can't break KsApi~KsApi.
Position
Below the diagonal: GraphAPI~Fragments uses a module listed above it, which is the healthy direction.
122 pairs of types, where a type in GraphAPI~Fragments uses a type in GraphAPI~Schema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Fragments uses GraphAPI~Schema, so a change to GraphAPI~Schema can break GraphAPI~Fragments, while a change to GraphAPI~Fragments can't break GraphAPI~Schema.
Position
Below the diagonal: GraphAPI~Fragments uses a module listed above it, which is the healthy direction.
9→10 GraphAPI~Fragments uses Library~Librarypart of a loop✕
Connections
88 pairs of types, where a type in GraphAPI~Fragments uses a type in Library~Library. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
GraphAPI~Fragments uses Library~Library, so a change to Library~Library can break GraphAPI~Fragments, while a change to GraphAPI~Fragments can't break Library~Library.
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.
Library~Library uses GraphAPI~Operations, so a change to GraphAPI~Operations can break Library~Library, while a change to Library~Library can't break GraphAPI~Operations.
Position
Below the diagonal: Library~Library uses a module listed above it, which is the healthy direction.
Library~Library uses ServerDrivenUI~ServerDrivenUI, so a change to ServerDrivenUI~ServerDrivenUI can break Library~Library, while a change to Library~Library can't break ServerDrivenUI~ServerDrivenUI.
Position
Below the diagonal: Library~Library uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in Library~Library uses a type in ServerDrivenUI~ServerDrivenUITestHelpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Library~Library uses ServerDrivenUI~ServerDrivenUITestHelpers, so a change to ServerDrivenUI~ServerDrivenUITestHelpers can break Library~Library, while a change to Library~Library can't break ServerDrivenUI~ServerDrivenUITestHelpers.
Position
Below the diagonal: Library~Library uses a module listed above it, which is the healthy direction.
570 pairs of types, where a type in Library~Library uses a type in KsApi~KsApi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Library~Library uses Kickstarter-Framework~Kickstarter-Framework, so a change to Kickstarter-Framework~Kickstarter-Framework can break Library~Library, while a change to Library~Library can't break Kickstarter-Framework~Kickstarter-Framework.
Position
Below the diagonal: Library~Library uses a module listed above it, which is the healthy direction.
Library~Library uses GraphAPI~Schema, so a change to GraphAPI~Schema can break Library~Library, while a change to Library~Library can't break GraphAPI~Schema.
Position
Below the diagonal: Library~Library uses a module listed above it, which is the healthy direction.
Library~Library uses GraphAPI~Fragments, so a change to GraphAPI~Fragments can break Library~Library, while a change to Library~Library can't break GraphAPI~Fragments.
Position
Below the diagonal: Library~Library uses a module listed above it, which is the healthy direction.
10→11 Library~Library uses Experimentation~Experimentationpart of a loop✕
Connections
5 pairs of types, where a type in Library~Library uses a type in Experimentation~Experimentation.
Library~Library uses Experimentation~Experimentation, so a change to Experimentation~Experimentation can break Library~Library, while a change to Library~Library can't break Experimentation~Experimentation.
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.
Experimentation~Experimentation uses Library~Library, so a change to Library~Library can break Experimentation~Experimentation, while a change to Experimentation~Experimentation can't break Library~Library.
Position
Below the diagonal: Experimentation~Experimentation uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
7
High / Critical
A05:2025 — Injection
2
High / Critical
A03:2025 — Software Supply Chain Failures
1
High / Critical
Roadmap
Immediately resolve the two leaked secrets in REDACTED and address the uncovered dependency resolution to secure the codebase. Next, document significant design decisions in the docs/adr folder to establish clear architectural context. Finally, implement structured logging via os.Logger across all subsystems, prioritizing error paths that currently lack diagnostic trails to improve bug reproduction and support.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
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.
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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.
Resolve the 290 Orphaned file finding(s) in Knowledge Freshness — start with ProjectPageViewControllerDataSource.swift, UserLenses.swift, PPOProjectCardModel+Templates.swift.
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 — 22
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 — 502
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 — 359
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 33
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 42 of 42 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 42 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, 826 of 883 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in Experimentation 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (7 packages), but it was not re-run: the analyzer environment could not run it. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares 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.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Experimentation/Sources/Experimentation/Experiments/StatsigExperiment.swift`, `KDS/Sources/KDS/Controllers/ColorsView.swift`, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.swift`, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift`, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Datasource/DiscoveryProjectsDataSource.swift`, … (+45 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.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (Kickstarter.xcodeproj/project.pbxproj). 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. Watchdog then boots 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Swift 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Swift 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.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Swift 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.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Swift 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.
Repo exclusion declarations: 4 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Route.requestProperties at 51. A further 15 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 RefTag.init at 59 — they are counted neither in the figure above nor in this dimension's score. 10 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: Library/Sources/Library/Library/RefInfo.swift (RefTag.init at 59), Library/Sources/Library/Library/Tracking/KSRAnalytics.swift (CTAContext.trackingString at 46), Library/Sources/Library/Library/UserAttribute.swift (UserAttribute.keyPath at 35), KDS/Sources/KDS/Fonts/InterFont.swift (InterFont.defaultSize at 24), Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOTierTypes.swift (PPOTierType.toPledgeProjectsOverviewSort at 17), and 5 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.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Route.requestProperties (cyclomatic 51), ProjectPageViewControllerDataSource.load (cyclomatic 33). — 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 7.8 to about 8.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with ProjectPageViewControllerDataSource.load (cognitive 41), AppDelegateViewModel.swift.navigation (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.7 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.5 / 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.
TooManyMethods: Service · ×4KsApi/Sources/KsApi/Service.swift:19
What to do
Resolve the 29 MethodTooLong finding(s) in God Classes — start with AppDelegateViewModel.swift (2), DesignSystemViewController.swift (2), PledgeViewModel.swift. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 11 ClassTooLong finding(s) in God Classes — start with MockService.swift, KSRAnalytics.swift, PledgeViewModel.swift. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with KSRAnalytics.swift, MockService.swift, ProjectLenses.swift. — One of this dimension's main actionable groups (11 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
198 duplicated block group(s) detected. A further 7 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 6 of the 205 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.
+ 64 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ActivitiesViewController.swift, BackerDashboardProjectCell.swift, DiscoveryPageViewController.swift. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 15 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with PledgeRewardsSummaryViewController.swift (2), AppDelegateViewModel.swift, ActivityFriendBackingCell.swift. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 13 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CommentRepliesDataSource.swift, DiscoveryProjectCardCell.swift, PledgeViewController.swift. — One of this dimension's main actionable groups (13 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.3 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
9 production modules (SwiftPM+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 3 module(s) off the main sequence.
Off the main sequence: KsApi · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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 91 Low cohesion finding(s) in Cohesion (LCOM4) — start with ProjectPageViewModel.swift, AppDelegateViewModel.swift, DiscoveryPageViewModel.swift. — One of this dimension's main actionable groups (91 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution8.1 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
811 test methods: 692 unit, 0 integration, 0 BDD, 119 e2e.
What to do
Improve Test Distribution — currently 8.1/10. — 811 test methods: 692 unit, 0 integration, 0 BDD, 119 e2e.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.6 / 10Stronggated by 19 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 26 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 811 tests (1 harness-style project(s) excluded from the assertion penalty).
No assertions: testRecognizesURLs · ×19LibraryTests/Library/NavigationTests.swift:29
No direct assertions: testCategoryView · ×7LibraryTests/Library/ViewModels/DiscoveryProjectCategoryViewModelTests.swift:21
Test project verifies nothing: ViewModelsLibraryTests/Library/ViewModels/DiscoveryProjectCategoryViewModelTests.swift:21
What to do
Resolve the 19 No assertions finding(s) in Test Quality — start with PPOViewModelTests.swift (7), ConfirmBackingAddressMutationTests.swift (3), TextBlockTests.swift (3). — One of this dimension's main actionable groups (19 warning-level).
Resolve the 7 No direct assertions finding(s) in Test Quality — start with KSRSearchBarViewModelTests.swift (6), DiscoveryProjectCategoryViewModelTests.swift. — One of this dimension's main actionable groups (7 recommendation-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with DiscoveryProjectCategoryViewModelTests.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
44 outdated direct SwiftPM dependencies, 1 pinning defect(s). 71 of 73 direct dependencies had their releases listed (0 naming no readable repository, 2 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.
Dependency not covered by the committed resolution: statsig-kit
Outdated: abseil-cpp-binary · ×37
What to do
Resolve the 1 Dependency not covered by the committed resolution finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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.
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 of 115 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 115 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. 1 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.
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.
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.
44 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Library/Sources/Library/Library/ViewModels/RewardAddOnSelectionViewModel.swift. Counted over 448 of the 1124 production source files in this repository: 632 are under the ~2,400-byte size floor this dimension measures over, and the remaining 44 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×4
✓ On the Gold path — maintain.
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.
81 deducted task-comment markers across 109914 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 48 TodoComment finding(s) in Explicit Debt — start with CommentsViewModel.swift (3), CommentRepliesViewModel.swift (2), ProjectPageViewModel.swift (2). — One of this dimension's main actionable groups (48 warning-level).
Resolve the 32 FixmeComment finding(s) in Explicit Debt — start with ThanksViewModelTests.swift (15), String+SimpleHTMLTests.swift (3), RootViewModel.swift (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with DiscoveryPageViewModel.swift. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
3 of 7 build units (Bundler, SwiftPM) 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: 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.
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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).
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. semgrep hit a parse error in 2 file(s) — `REDACTED` (line 449, line 451), `KsApi/Sources/KsApiTests/queries/templates/FetchMySavedProjectsQuery.json` — 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
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
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.
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
293 of 492 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift. Counted over 492 of the 1124 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:1
Concentrated knowledge decay
What to do
Resolve the 290 Orphaned file finding(s) in Knowledge Freshness — start with ProjectPageViewControllerDataSource.swift, UserLenses.swift, PPOProjectCardModel+Templates.swift. — One of this dimension's main actionable groups (290 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with DiscoveryProjectCardCell.swift, CommentsViewModel.swift, Format.swift. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
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 13 Boundary-crossing change coupling finding(s) in Change Coupling — start with SearchViewController.swift (2), AppDelegateViewModel.swift (2), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
Resolve the 13 Change coupling finding(s) in Change Coupling — start with RemoteConfigFeature+Helpers.swift, MockService.swift, UpdateBackingInput+Constructor.swift. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with GraphSchema.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. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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 1 platform declaration(s) and 13 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 7 of 7 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
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.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ 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 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.
1783/2409 types (74%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Swift: leave it `internal` (the default) instead of `public`) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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 9600 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.
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 · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
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.
`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) — Library/Sources/Library/Library/Keychain.swift:104, Library/Sources/Library/Library/String+SimpleHTML.swift:125, KsApi/Sources/KsApi/PKCE.swift:53, …
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
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 — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: 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 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.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — 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 — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D21 Naming Consistency — Naming consistency is measured on C# only; Swift not measured.
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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 50 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions.
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 Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Swift code has 130,307 production line(s), 2 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
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 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
X12 Unreachable branch — 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
X13 Undrained process stream — 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
X15 Unvalidated length from an untrusted reader — 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
X16 Unfloored truncation loop — 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
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not 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
X19 Unrestored process-global state — 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
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 — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — 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
X23 Unguarded diagnostic materialisation — 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
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X25 Inert configuration knob — not 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
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. Swift's `Array`, `Dictionary` and `Set` are values: `for x in items` walks the copy taken when the loop starts, so a body that adds to or removes from `items` changes a different value, nothing is invalidated, and every original element is still visited. This repository's Swift names no Foundation mutable collection (`NSMutableArray` and kin), the one kind a Swift loop can walk by reference. Not a gap in the analyzer and not a finding about your code.
X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — not 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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
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.
Boundary-crossing change coupling: REDACTED ↔ Segment.swift REDACTED:1— `REDACTED` (context Kickstarter-iOS) and `Library/Sources/Library/Library/Tracking/Segment.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a584f699` Braze upgrade (#2599) (at that commit the file was still `Library/Tracking/Segment.swift`); `7b522b70` [MBL-1147] Track push notifications (#1943) (at that commit the file was still `Library/Tracking/Segment.swift`); `75867402` [NTV-647] Braze In-App Notification Fix (#1791) (at that commit the file was still `Library/Tracking/Segment.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: SearchViewController.swift ↔ SearchFilterPill.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/UseCases/SearchFilters/SearchFilterPill.swift` (context Library) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `036273e2` MBL-2521, MBL-2519, MBL-2514: Add filter for amount raised (at that commit the files were still `Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` and `Library/UseCases/SearchFilters/SearchFilterPill.swift`); `f3e487dc` MBL-2342: Add search filtering by project location (#2482) (at that commit the files were still `Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` and `Library/UseCases/SearchFilters/SearchFilterPill.swift`); `77367554` MBL-2351 & MBL-2346 & MBL-2350: Implement percent raised filter (#2446) (at that commit the files were still `Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` and `Library/UseCases/SearchFilters/SearchFilterPill.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: VideoFeedCell.swift ↔ VideoFeedViewModel.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Cell/VideoFeedCell.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Cell/VideoFeedCell.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/ViewModels/VideoFeedViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f19fb22e` [DISC-447] Mute Button On Video Feed Overlay (#2963); `070e2a43` [DISC-164] Video Feed Analytics (#2894); `37b9cc62` Video Feed: Fix Audio Playback and Save State (#2891) — run `git show` on any of them.
Boundary-crossing change coupling: FilterRootView.swift ↔ SearchFilterPill.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SortFilter/FilterRootView/FilterRootView.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SortFilter/FilterRootView/FilterRootView.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/UseCases/SearchFilters/SearchFilterPill.swift` (context Library) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `0e12d871` [MBL-2569, MBL-2571] Use goal filter view (#2537) (at that commit the files were still `Kickstarter-iOS/Features/SortFilter/FilterRootView/FilterRootView.swift` and `Library/UseCases/SearchFilters/SearchFilterPill.swift`); `d4cba572` MBL-2560: Hook up 'show only' search toggles (#2530) (at that commit the files were still `Kickstarter-iOS/Features/SortFilter/FilterRootView/FilterRootView.swift` and `Library/UseCases/SearchFilters/SearchFilterPill.swift`); `a5ec1319` Set raw values for enum types used in sort filters, so that applying … (at that commit the files were still `Kickstarter-iOS/Features/SortFilter/FilterRootView/FilterRootView.swift` and `Library/UseCases/SearchFilters/SearchFilterPill.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: BackingTemplates.swift ↔ ManagePledgeViewModel.swift KsApi/Sources/KsApi/models/templates/BackingTemplates.swift:1— `KsApi/Sources/KsApi/models/templates/BackingTemplates.swift` (context KsApi) and `Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `48bdd952` [MBL-2640] Support refundedAmount and REFUNDED state in GraphQL (#2546) (at that commit the files were still `KsApi/models/templates/BackingTemplates.swift` and `Library/ViewModels/ManagePledgeViewModel.swift`); `ebb2c32a` [MBL-2120] PLOT - Fixing issue when device locate is ES (#2297) (at that commit the files were still `KsApi/models/templates/BackingTemplates.swift` and `Library/ViewModels/ManagePledgeViewModel.swift`); `3e055356` [MBL-1961] Update PaymentIncrement State & StateReason GraphQL Types … (at that commit the files were still `KsApi/models/templates/BackingTemplates.swift` and `Library/ViewModels/ManagePledgeViewModel.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: PledgePaymentIncrement+GraphAPI.swift ↔ ManagePledgeViewModel.swift KsApi/Sources/KsApi/models/PledgePaymentIncrement+GraphAPI.swift:1— `KsApi/Sources/KsApi/models/PledgePaymentIncrement+GraphAPI.swift` (context KsApi) and `Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `48bdd952` [MBL-2640] Support refundedAmount and REFUNDED state in GraphQL (#2546) (at that commit the files were still `KsApi/models/PledgePaymentIncrement+GraphAPI.swift` and `Library/ViewModels/ManagePledgeViewModel.swift`); `ebb2c32a` [MBL-2120] PLOT - Fixing issue when device locate is ES (#2297) (at that commit the files were still `KsApi/models/PledgePaymentIncrement+GraphAPI.swift` and `Library/ViewModels/ManagePledgeViewModel.swift`); `3e055356` [MBL-1961] Update PaymentIncrement State & StateReason GraphQL Types … (at that commit the files were still `KsApi/models/PledgePaymentIncrement+GraphAPI.swift` and `Library/ViewModels/ManagePledgeViewModel.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: VideoFeedOverlayView.swift ↔ VideoFeedViewModel.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Overlay/VideoFeedOverlayView.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Overlay/VideoFeedOverlayView.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/ViewModels/VideoFeedViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f19fb22e` [DISC-447] Mute Button On Video Feed Overlay (#2963); `070e2a43` [DISC-164] Video Feed Analytics (#2894); `807305ee` update save count optimistically and when returning from project page… — run `git show` on any of them.
Boundary-crossing change coupling: RewardAddOnSelectionViewController.swift ↔ RewardsCollectionViewModel.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Controller/RewardAddOnSelectionViewController.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Controller/RewardAddOnSelectionViewController.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/ViewModels/RewardsCollectionViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `30a42a20` CHECK-87: Clean up navigation bar in pledge flow for consistent behav…; `389eb854` CHECK-87: Update navigation bar titles in Pledge flow (#2860); `ca534c9c` [MBL-1684] Remove Redundant No Shipping At Checkout Feature Flag Chec… (at that commit the files were still `Kickstarter-iOS/Features/RewardAddOnSelection/Controller/RewardAddOnSelectionNoShippingViewController.swift` and `Library/ViewModels/WithShippingRewardsCollectionViewModel.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: ActivitiesDataSource.swift ↔ ActivitiesViewModel.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Datasource/ActivitiesDataSource.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Datasource/ActivitiesDataSource.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/ViewModels/ActivitiesViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `e40aff92` [MBL-2385] Intersperse Tracking # Cards With Activities (#2405) (at that commit the files were still `Kickstarter-iOS/Features/Activities/Datasource/ActivitiesDataSource.swift` and `Library/ViewModels/ActivitiesViewModel.swift`); `3a9d89b7` [MBL-2360] Show Tracking Number Cards In Activity (#2397) (at that commit the files were still `Kickstarter-iOS/Features/Activities/Datasource/ActivitiesDataSource.swift` and `Library/ViewModels/ActivitiesViewModel.swift`); `7d98848e` [MBL-2274] Add RewardTrackingActivitiesCell (#2370) (at that commit the files were still `Kickstarter-iOS/Features/Activities/Datasource/ActivitiesDataSource.swift` and `Library/ViewModels/ActivitiesViewModel.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: SearchViewController.swift ↔ SearchFilters.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/UseCases/SearchFilters/SearchFilters.swift` (context Library) sit in DIFFERENT parts of the tree yet 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `eb0e946d` [MBL-2618] Add new empty state to search (#2555) (at that commit the files were still `Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` and `Library/UseCases/SearchFilters/SearchFilters.swift`); `036273e2` MBL-2521, MBL-2519, MBL-2514: Add filter for amount raised (at that commit the files were still `Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` and `Library/UseCases/SearchFilters/SearchFilters.swift`); `f3e487dc` MBL-2342: Add search filtering by project location (#2482) (at that commit the files were still `Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift` and `Library/UseCases/SearchFilters/SearchFilters.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: AppDelegateViewModel.swift ↔ KeyValueStoreType.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/KeyValueStoreType.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `1d3d8acb` [MBL-3143] Statsig Plumbing (#2796); `9d9e4711` [MBL-2422] Launch Login/Signup Flow (#2547) (at that commit the files were still `Kickstarter-iOS/AppDelegateViewModel.swift` and `Library/KeyValueStoreType.swift`); `534eadcc` [MBL-720] Configure Remote Config (#1815) (at that commit the files were still `Kickstarter-iOS/AppDelegateViewModel.swift` and `Library/KeyValueStoreType.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: AppDelegateViewModel.swift ↔ Segment.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/Tracking/Segment.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a584f699` Braze upgrade (#2599) (at that commit the files were still `Kickstarter-iOS/AppDelegateViewModel.swift` and `Library/Tracking/Segment.swift`); `75867402` [NTV-647] Braze In-App Notification Fix (#1791) (at that commit the files were still `Kickstarter-iOS/AppDelegateViewModel.swift` and `Library/Tracking/Segment.swift`); `36dffc53` [PAY-2142] Fix Deeplinks Not Routing From Braze (#1775) (at that commit the files were still `Kickstarter-iOS/AppDelegateViewModel.swift` and `Library/Tracking/Segment.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: CommentsViewController.swift ↔ CommentRepliesViewModel.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift` (context Kickstarter-Framework) and `Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift` (context Library) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6886cab4` [MBL-1024] Wire Up Block User Mutation (#1893) (at that commit the files were still `Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift` and `Library/ViewModels/CommentRepliesViewModel.swift`); `6abd404a` [MBL-1036] Block User Popup + Banner Message (#1880) (at that commit the files were still `Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift` and `Library/ViewModels/CommentRepliesViewModel.swift`); `dfdd1674` [NTV-180] Sending commentableId based on value of updateProperty in C… (at that commit the files were still `Kickstarter-iOS/Views/Controllers/CommentsViewController.swift` and `Library/ViewModels/CommentRepliesViewModel.swift`) — run `git show` on any of them.
Low cohesion: ProjectPageViewModel (LCOM4 24) Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:241— ProjectPageViewModel's methods fall into 24 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 24 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AppDelegateViewModel (LCOM4 22) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:192— AppDelegateViewModel's methods fall into 22 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 22 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: DiscoveryPageViewModel (LCOM4 19) Library/Sources/Library/Library/ViewModels/DiscoveryPageViewModel.swift:133— DiscoveryPageViewModel's methods fall into 19 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 19 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: RootViewModel (LCOM4 15) Library/Sources/Library/Library/ViewModels/RootViewModel.swift:141— RootViewModel'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: UpdateDraftViewModel (LCOM4 15) Library/Sources/Library/Library/ViewModels/UpdateDraftViewModel.swift:129— UpdateDraftViewModel'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: ActivitiesViewModel (LCOM4 14) Library/Sources/Library/Library/ViewModels/ActivitiesViewModel.swift:102— ActivitiesViewModel's methods fall into 14 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 14 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: PledgeViewModel (LCOM4 13) Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:116— PledgeViewModel'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: PostCampaignCheckoutViewModel (LCOM4 13) Library/Sources/Library/Library/ViewModels/PostCampaignCheckoutViewModel.swift:83— PostCampaignCheckoutViewModel'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: ProjectPageViewControllerDataSource (LCOM4 12) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Datasource/Datasource/ProjectPageViewControllerDataSource.swift:7— ProjectPageViewControllerDataSource'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: LoginToutViewModel (LCOM4 12) Library/Sources/Library/Library/ViewModels/LoginToutViewModel.swift:100— LoginToutViewModel'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: RewardsCollectionViewModel (LCOM4 12) Library/Sources/Library/Library/ViewModels/RewardsCollectionViewModel.swift:52— RewardsCollectionViewModel'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: BackerDashboardViewModel (LCOM4 11) Library/Sources/Library/Library/ViewModels/BackerDashboardViewModel.swift:98— BackerDashboardViewModel'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: CommentsViewModel (LCOM4 11) Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:83— CommentsViewModel'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: DiscoveryViewModel (LCOM4 11) Library/Sources/Library/Library/ViewModels/DiscoveryViewModel.swift:73— DiscoveryViewModel'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: LoginViewModel (LCOM4 11) Library/Sources/Library/Library/ViewModels/LoginViewModel.swift:79— LoginViewModel'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: ProjectPageViewController (LCOM4 10) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:27— ProjectPageViewController'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: DiscoveryPageViewController (LCOM4 9) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:15— DiscoveryPageViewController'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: CommentRepliesViewModel (LCOM4 9) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:85— CommentRepliesViewModel'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: FindFriendsViewModel (LCOM4 9) Library/Sources/Library/Library/ViewModels/FindFriendsViewModel.swift:66— FindFriendsViewModel'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: ManagePledgeViewModel (LCOM4 9) Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift:64— ManagePledgeViewModel'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: ProjectPamphletContentViewModel (LCOM4 9) Library/Sources/Library/Library/ViewModels/ProjectPamphletContentViewModel.swift:33— ProjectPamphletContentViewModel'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: VideoViewModel (LCOM4 9) Library/Sources/Library/Library/ViewModels/VideoViewModel.swift:85— VideoViewModel'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: String (LCOM4 9) Library/Sources/Library/Library/String+Attributed.swift:11— String'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: CancelPledgeViewModel (LCOM4 8) Library/Sources/Library/Library/ViewModels/CancelPledgeViewModel.swift:40— CancelPledgeViewModel'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: CreatePasswordViewModel (LCOM4 8) Library/Sources/Library/Library/ViewModels/CreatePasswordViewModel.swift:38— CreatePasswordViewModel'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.
TodoComment LibraryTests/Library/ViewModels/PledgeStatusLabelViewModelTests.swift:178— // TODO: for now we expected a nil `labelTextString`, this will be addressed when we get to the native implementation in this ticket [MBL-2012](https://kickstarter.atlassian.net/browse/MBL-2012)
TodoComment Library/Sources/Library/UIAlertController.swift:342— // Scott TODO: Use localized strings once translations can be done [mbl-1037](https://kickstarter.atlassian.net/browse/MBL-1037)
TodoComment Library/Sources/Library/Library/Navigation.swift:446— // TODO: Revisit this if `backing/details` becomes accessible or authentication rules change. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Library/Sources/Library/Library/OAuth.swift:113— // TODO: This would be neater if we can just return the V1 user from the exchange endpoint. — 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 Library/Sources/Library/Library/SettingsCellType.swift:70— // TODO: When the decision to add the Facebook friends feature back in is confirmed, refer to this PR: — 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 Library/Sources/Library/Library/ViewModels/ActivitiesViewModel.swift:188— // TODO: Remove this whole set of Signals as these live in Backings Dashboard now. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Library/Sources/Library/Library/ViewModels/CancelPledgeViewModel.swift:7— // TODO: remove once tracking is updated. — 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 Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:150— // TODO: Handle isLoading from here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:269— // TODO: Display proper error messaging from the backend — 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 Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:380— // TODO: Display proper error messaging from the backend — 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 Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:232— // TODO: Display proper error messaging from the backend — 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 Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:623— // TODO: Display proper error messaging from the backend — 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 Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:130— // TODO: ensure this does not page when cells are less than threshold. — 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 Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:496— // TODO: We may need to introduce optimizations here if this becomes problematic for projects that have — 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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift:106— // TODO: We may need to introduce optimizations here if this becomes problematic for projects that have — 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 Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift:476— // TODO: Clean up rewards fetch. — 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 KsApi/Sources/KsApi/ProjectPageFetcher.swift:64— // TODO: Clean up rewards fetch. — 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 Library/Sources/Library/Library/ViewModels/PledgeCTAContainerViewViewModel.swift:88— // TODO: these changes are temporary and will likely be removed when we get to the native implementation in this ticket [MBL-2012](https://kickstarter.atlassian.net/browse/MBL-2012)
TodoComment Library/Sources/Library/Library/ViewModels/PledgeOverTimePaymentScheduleViewModel.swift:129— // TODO: This variant isn't implemented on the backend; I believe it's a bug and should actually be danger. — 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 Library/Sources/Library/Library/ViewModels/PledgePaymentPlansOptionViewModel.swift:9— // TODO: replece with API model in [MBL-1838](https://kickstarter.atlassian.net/browse/MBL-1838)
TodoComment Library/Sources/Library/Library/ViewModels/PledgeShippingLocationViewModel.swift:30— // TODO: Clean up when a Project field for this is added (MBL-3150)
TodoComment Library/Sources/Library/Library/ViewModels/PledgeShippingLocationViewModel.swift:80— // TODO: It would make this page a bit faster if we fetched shippableLocationsExpanded earlier. — 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 Library/Sources/Library/Library/ViewModels/PledgeStatusLabelViewModel.swift:113— // TODO: These changes are temporary and will be updated to return the correct text once the native implementation for this case is complete. [MBL-2012](https://kickstarter.atlassian.net/browse/MBL-2012)
TodoComment Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:927— // TODO: We're posting this mutation more frequently than we need to. — 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 Library/Sources/Library/Library/ViewModels/RewardsCollectionViewModel.swift:74— // TODO: If we passed in ShippableCountries to the location selector, we could call this faster. — 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 LibraryTests/Library/ViewModels/PledgeAmountViewModelTests.swift:868— // FIXME: Not sure why this notification is triggered when stepper value is inside the min/max bounds. — 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 Library/Sources/Library/Library/ViewModels/DiscoveryPostcardViewModel.swift:9— // FIXME: consolidate into two parameters: project, filterParams — 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 Library/Sources/Library/Library/ViewModels/RootViewModel.swift:193— // FIXME: Look at moving the userLocalePreferencesChangedProperty signal into the currentUser signal — 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 Library/Sources/Library/Library/ViewModels/RootViewModel.swift:324— // FIXME: This signal always needs to happen when setViewControllers happens. — 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 KsApi/Sources/KsApiTests/models/graphql/adapters/CreateBackingEnvelope+CreateBackingMutation.DataTests.swift:5— // FIXME: DISABLED_SPM - This file isn't included in the old test target, and it fails to run. — 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 KsApi/Sources/KsApi/Service.swift:360— // FIXME: Should be able to convert this to Apollo as it uses /v1 but check its' use cases first. — 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.
MethodTooLong: PledgeViewModel.init Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:118— MethodTooLong — init runs 580 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 480 over it, 5.80× 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: PostCampaignCheckoutViewModel.init Library/Sources/Library/Library/ViewModels/PostCampaignCheckoutViewModel.swift:88— MethodTooLong — init runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× 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: ProjectPageViewModel.init Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:243— MethodTooLong — init runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.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: AppDelegateViewModel.init Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:194— MethodTooLong — init runs 296 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 196 over it, 2.96× 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: PledgePaymentMethodsViewModel.init Library/Sources/Library/Library/ViewModels/PledgePaymentMethodsViewModel.swift:59— MethodTooLong — init runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× 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: CommentsViewModel.init Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:88— MethodTooLong — init runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RewardsCollectionViewModel.init Library/Sources/Library/Library/ViewModels/RewardsCollectionViewModel.swift:54— MethodTooLong — init runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RewardAddOnSelectionViewModel.init Library/Sources/Library/Library/ViewModels/RewardAddOnSelectionViewModel.swift:60— MethodTooLong — init runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× 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: ManagePledgeViewModel.init Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift:66— MethodTooLong — init runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× 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: ProjectPageViewController.bindProjectPageViewModel Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:394— MethodTooLong — bindProjectPageViewModel runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: AppDelegate.application REDACTED:40— MethodTooLong — application runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: SearchViewModel.init Library/Sources/Library/Library/ViewModels/SearchViewModel.swift:90— MethodTooLong — init runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ProjectPageViewControllerDataSource.load Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Datasource/Datasource/ProjectPageViewControllerDataSource.swift:77— MethodTooLong — load runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: DiscoveryPageViewModel.init Library/Sources/Library/Library/ViewModels/DiscoveryPageViewModel.swift:135— MethodTooLong — init runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: RootViewModel.init Library/Sources/Library/Library/ViewModels/RootViewModel.swift:142— MethodTooLong — init runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× 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: CommentRepliesViewModel.init Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:88— MethodTooLong — init runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: DesignSystemViewController.bindStyles Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Controller/DesignSystemViewController.swift:283— MethodTooLong — bindStyles 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: ThanksViewModel.init Library/Sources/Library/Library/ViewModels/ThanksViewModel.swift:78— MethodTooLong — init 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: UpdateDraftViewModel.init Library/Sources/Library/Library/ViewModels/UpdateDraftViewModel.swift:131— MethodTooLong — init 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: ProjectDeepLink.projectViewControllers Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1161— MethodTooLong — projectViewControllers 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: Route.requestProperties KsApi/Sources/KsApi/lib/Route.swift:58— MethodTooLong — requestProperties runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ActivitiesViewModel.init Library/Sources/Library/Library/ViewModels/ActivitiesViewModel.swift:104— MethodTooLong — init runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ProjectPamphletMainCell.bindStyles Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectPamphletMainCell.swift:106— MethodTooLong — bindStyles 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: MessagesViewModel.init Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:83— MethodTooLong — init 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: LoginToutViewModel.init Library/Sources/Library/Library/ViewModels/LoginToutViewModel.swift:102— MethodTooLong — init runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
No assertions: testRecognizesURLs LibraryTests/Library/NavigationTests.swift:29— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testView KDS/Tests/KDSTests/ColorsViewTests.swift:7— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValues KsApi/Sources/KsApiTests/combine/CombineTestObserverTests.swift:25— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCompletion KsApi/Sources/KsApiTests/combine/CombineTestObserverTests.swift:58— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_confirmBackingAddressWithMocks_success KsApi/Sources/KsApiTests/mutations/ConfirmBackingAddressMutationTests.swift:7— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_confirmBackingAddressWithMocks_failure KsApi/Sources/KsApiTests/mutations/ConfirmBackingAddressMutationTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_confirmBackingAddressWithMocks_error KsApi/Sources/KsApiTests/mutations/ConfirmBackingAddressMutationTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testBasicText ServerDrivenUI/Tests/ServerDrivenUITests/Blocks/TextBlockTests.swift:9— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testStyles ServerDrivenUI/Tests/ServerDrivenUITests/Blocks/TextBlockTests.swift:33— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testListItemText ServerDrivenUI/Tests/ServerDrivenUITests/Blocks/TextBlockTests.swift:56— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testRichTextStylePreview_lightStyle ServerDrivenUI/Tests/ServerDrivenUITests/Styling/RichTextStyleSnapshotTests.swift:56— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testRichTextStylePreview_darkStyle ServerDrivenUI/Tests/ServerDrivenUITests/Styling/RichTextStyleSnapshotTests.swift:65— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventConfirmAddress Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:270— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventContactCreator Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:286— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventFix3DSChallenge Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:296— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventFixPaymentMethod Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:309— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventOpenSurvey Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:320— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventOpenPledgeManager Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:329— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventViewProjectDetails Kickstarter-Framework/Sources/Kickstarter-Framework-iOSTests/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModelTests.swift:338— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Duplicated block (7 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Controller/ActivitiesViewController.swift:32— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Controller/ActivitiesViewController.swift:32-38 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RootTabBar/RootTabBarViewController.swift:62-69 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Controller/ActivitiesViewController.swift:32` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:240— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:240-246 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Views/Cell/MostPopularSearchProjectCell.swift:37-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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:240` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:296— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:296-302 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:476-482 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:296` 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 (7 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Views/Cells/MessageThreadCell.swift:37— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Views/Cells/MessageThreadCell.swift:37-43 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Views/Cells/MessageCell.swift:59-65 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Views/Cells/MessageThreadCell.swift:37` 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, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Views/Cells/MessageThreadCell.swift:35` calls `uiColor` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Views/Cells/MessageCell.swift:57` 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) KsApi/Sources/KsApi/models/graphql/adapters/CommentsEnvelope+GraphCommentsEnvelope.swift:10— KsApi/Sources/KsApi/models/graphql/adapters/CommentsEnvelope+GraphCommentsEnvelope.swift:10-16 | KsApi/Sources/KsApi/models/graphql/adapters/CommentsEnvelope+GraphCommentsEnvelope.swift:30-36 — 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 `KsApi/Sources/KsApi/models/graphql/adapters/CommentsEnvelope+GraphCommentsEnvelope.swift:10` 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 (7 lines × 2) KsApi/Sources/KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.Data.swift:12— KsApi/Sources/KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.Data.swift:12-19 | KsApi/Sources/KsApi/models/graphql/adapters/UserCreditCards+UserFragment.swift:13-19 — 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 `KsApi/Sources/KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.Data.swift:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentDialogViewController.swift:122— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentDialogViewController.swift:122-128 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageDialog/Controller/MessageDialogViewController.swift:94-100 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:192— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:192-198 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift:207-213 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Datasource/DiscoveryProjectsDataSource.swift:14— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Datasource/DiscoveryProjectsDataSource.swift:14-20 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Datasource/SearchDataSource.swift:102-108 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/BadgeView.swift:25— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/BadgeView.swift:25-31 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/PledgeOverTimeBadgeView.swift:19-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Datasource/MessageThreadsDataSource.swift:13— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Datasource/MessageThreadsDataSource.swift:13-19 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SearchMessages/SearchMessagesDataSource.swift:11-17 — 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, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Datasource/MessageThreadsDataSource.swift:11` calls `String` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SearchMessages/SearchMessagesDataSource.swift:9` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgePaymentMethodAddCell.swift:29— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgePaymentMethodAddCell.swift:29-35 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgePaymentMethodCell.swift:29-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 (7 lines × 2) Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:123— Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:123-129 | Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:989-995 — 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) KsApi/Sources/KsApi/models/ClientSecretEnvelope.swift:12— KsApi/Sources/KsApi/models/ClientSecretEnvelope.swift:12-18 | KsApi/Sources/KsApi/models/PaymentIntentEnvelope.swift:12-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) KsApi/Sources/KsApi/models/graphql/adapters/CreateBackingEnvelope+CreateBackingMutation.Data.swift:6— KsApi/Sources/KsApi/models/graphql/adapters/CreateBackingEnvelope+CreateBackingMutation.Data.swift:6-12 | KsApi/Sources/KsApi/models/graphql/adapters/UpdateBackingEnvelope+UpdateBackingMutation.Data.swift:9-15 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:940— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:940-944 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:954-958 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:940` 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 × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:44— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:44-48 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityProjectStatusCell.swift:48-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.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.
Duplicated block (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityProjectStatusCell.swift:51— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityProjectStatusCell.swift:51-55 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectPamphletMainCell.swift:342-346 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityProjectStatusCell.swift:51` 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 (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:222— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:222-226 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Views/Cell/MostPopularSearchProjectCell.swift:111-115 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:293— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:293-297 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectPamphletMainCell.swift:339-343 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:293` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:217— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:217-221 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PostCampaignCheckoutViewController.swift:164-168 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PostCampaignCheckoutViewController.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:217` 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 (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Library/MFMailComposeViewController.swift:29— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Library/MFMailComposeViewController.swift:29-33 | Library/Sources/Library/Library/UIDeviceType.swift:17-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Library/MFMailComposeViewController.swift:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Controller/ActivitiesViewController.swift:93— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Controller/ActivitiesViewController.swift:93-97 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Controller/SearchViewController.swift:52-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.
Duplicated block (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.swift:419— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.swift:419-423 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryViewController.swift:200-204 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:231— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:231-235 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:211-215 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:269— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:269-273 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:248-252 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Controller/BackerDashboardProjectsViewController.swift:14— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Controller/BackerDashboardProjectsViewController.swift:14-19 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectUpdatesViewController.swift:12-16 — 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) Library/Sources/Library/Library/DataSource/UICollectionView-Extensions.swift:22— Library/Sources/Library/Library/DataSource/UICollectionView-Extensions.swift:22-26 | Library/Sources/Library/Library/DataSource/UITableView-Extensions.swift:29-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.
Duplicated block (5 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendFollowCell.swift:57— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendFollowCell.swift:57-61 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FindFriends/Views/Cells/FindFriendsFriendFollowCell.swift:82-86 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendFollowCell.swift:57` 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, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FindFriends/Views/Cells/FindFriendsFriendFollowCell.swift:80` calls `ksr_footnote` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendFollowCell.swift:55` 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 × 2) Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:126— Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:126-130 | Library/Sources/Library/Library/ViewModels/PostCampaignCheckoutViewModel.swift:99-103 — 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.
Change coupling: RemoteConfigFeature+Helpers.swift ↔ RemoteConfigFeatureFlagToolsViewModel.swift Library/Sources/Library/Library/RemoteConfig/RemoteConfigFeature+Helpers.swift:1— `Library/Sources/Library/Library/RemoteConfig/RemoteConfigFeature+Helpers.swift` and `Library/Sources/Library/Library/ViewModels/RemoteConfigFeatureFlagToolsViewModel.swift` change together 87% of the time (34 of the 39 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 34 shared commits counted here, the most recent 3 are `e9cf6bc4` Simplify RemoteConfigFeatureFlagToolsViewController (at that commit the files were still `Library/RemoteConfig/RemoteConfigFeature+Helpers.swift` and `Library/ViewModels/RemoteConfigFeatureFlagToolsViewModel.swift`); `8755ceab` MBL-2521: Add feature flag for amount raised filter (#2497) (at that commit the files were still `Library/RemoteConfig/RemoteConfigFeature+Helpers.swift` and `Library/ViewModels/RemoteConfigFeatureFlagToolsViewModel.swift`); `e3241928` add ff (#2479) (at that commit the files were still `Library/RemoteConfig/RemoteConfigFeature+Helpers.swift` and `Library/ViewModels/RemoteConfigFeatureFlagToolsViewModel.swift`) — run `git show` on any of them.
Change coupling: MockService.swift ↔ Route.swift KsApi/Sources/KsApi/MockService.swift:1— `KsApi/Sources/KsApi/MockService.swift` and `KsApi/Sources/KsApi/lib/Route.swift` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 `3d4ea98e` [MBL 2264] [1 of 3] Refactor project pamphlet cell to support a proto… (at that commit the files were still `KsApi/MockService.swift` and `KsApi/lib/Route.swift`); `a8fb8d26` MBL-1159: Refactor authenticated userSelf endpoint to put OAuth token… (at that commit the files were still `KsApi/MockService.swift` and `KsApi/lib/Route.swift`); `cfd48301` MBL-1159: Add endpoints to exchange temporary token for OAuth token, … (at that commit the files were still `KsApi/MockService.swift` and `KsApi/lib/Route.swift`) — run `git show` on any of them.
Change coupling: UpdateBackingInput+Constructor.swift ↔ PledgeViewModel.swift Library/Sources/Library/Library/UpdateBackingInput+Constructor.swift:1— `Library/Sources/Library/Library/UpdateBackingInput+Constructor.swift` and `Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 `a4c934fb` [MBL-2498] Include 'Incremental' in UpdateBackingInput (#2480) (at that commit the files were still `Library/UpdateBackingInput+Constructor.swift` and `Library/ViewModels/PledgeViewModel.swift`); `e82e6c54` [MBL-1808] Fix fix pledge flow (#2232) (at that commit the files were still `Library/UpdateBackingInput+Constructor.swift` and `Library/ViewModels/NoShippingPledgeViewModel.swift`); `3dfa5c7f` [PAY-1979] Update Backing Mutation To Use Setup Intent (#1744) (at that commit the files were still `Library/UpdateBackingInput+Constructor.swift` and `Library/ViewModels/PledgeViewModel.swift`) — run `git show` on any of them.
Change coupling: TestCase.swift ↔ XCTestCase+AppEnvironment.swift Library/Sources/LibraryTestHelpers/TestCase.swift:1— `Library/Sources/LibraryTestHelpers/TestCase.swift` and `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift` change together 66% of the time (23 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 23 shared commits counted here, the most recent 3 are `f825723f` MBL-2658: Remove ColorResolver abstraction (#2595) (at that commit the files were still `Library/TestHelpers/TestCase.swift` and `Library/TestHelpers/XCTestCase+AppEnvironment.swift`); `ca34eb9c` [Part 1]: Add LegacyColor type, with values for all legacy design sys… (at that commit the files were still `Library/TestHelpers/TestCase.swift` and `Library/TestHelpers/XCTestCase+AppEnvironment.swift`); `e629b80e` [MBL-870] Fix GraphSchema with an Update to AppTrackingTransparency (… (at that commit the files were still `Library/TestHelpers/TestCase.swift` and `Library/TestHelpers/XCTestCase+AppEnvironment.swift`) — run `git show` on any of them.
Change coupling: Environment.swift ↔ TestCase.swift Library/Sources/Library/Library/Environment.swift:1— `Library/Sources/Library/Library/Environment.swift` and `Library/Sources/LibraryTestHelpers/TestCase.swift` change together 63% of the time (26 of the 41 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 26 shared commits counted here, the most recent 3 are `f825723f` MBL-2658: Remove ColorResolver abstraction (#2595) (at that commit the files were still `Library/Environment.swift` and `Library/TestHelpers/TestCase.swift`); `ca34eb9c` [Part 1]: Add LegacyColor type, with values for all legacy design sys… (at that commit the files were still `Library/Environment.swift` and `Library/TestHelpers/TestCase.swift`); `e629b80e` [MBL-870] Fix GraphSchema with an Update to AppTrackingTransparency (… (at that commit the files were still `Library/Environment.swift` and `Library/TestHelpers/TestCase.swift`) — run `git show` on any of them.
Change coupling: Reward+RewardFragment.swift ↔ RewardLenses.swift KsApi/Sources/KsApi/models/graphql/adapters/Reward+RewardFragment.swift:1— `KsApi/Sources/KsApi/models/graphql/adapters/Reward+RewardFragment.swift` and `KsApi/Sources/KsApi/models/lenses/RewardLenses.swift` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 `19c6ba78` [MBL-2997] Added featured to GraphQL + Reward model (#2737) (at that commit the files were still `KsApi/models/graphql/adapters/Reward+RewardFragment.swift` and `KsApi/models/lenses/RewardLenses.swift`); `c229ea7e` [MBL-2452] Add AudienceData.secret to reward fragment (#2454) (at that commit the files were still `KsApi/models/graphql/adapters/Reward+RewardFragment.swift` and `KsApi/models/lenses/RewardLenses.swift`); `4f3fbdbd` Adding image field to the Reward fragment (#2312) (at that commit the files were still `KsApi/models/graphql/adapters/Reward+RewardFragment.swift` and `KsApi/models/lenses/RewardLenses.swift`) — run `git show` on any of them.
Change coupling: Backing+BackingFragment.swift ↔ BackingLenses.swift KsApi/Sources/KsApi/models/graphql/adapters/Backing+BackingFragment.swift:1— `KsApi/Sources/KsApi/models/graphql/adapters/Backing+BackingFragment.swift` and `KsApi/Sources/KsApi/models/lenses/BackingLenses.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 — 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 `c0b8831b` [MBL-2316] Replace Native View Pledge Screen with WebView for PM Back… (at that commit the files were still `KsApi/models/graphql/adapters/Backing+BackingFragment.swift` and `KsApi/models/lenses/BackingLenses.swift`); `6ade3dc5` [NO TICKET] Expose The Backing.Order Object (#2371) (at that commit the files were still `KsApi/models/graphql/adapters/Backing+BackingFragment.swift` and `KsApi/models/lenses/BackingLenses.swift`); `e82e6c54` [MBL-1808] Fix fix pledge flow (#2232) (at that commit the files were still `KsApi/models/graphql/adapters/Backing+BackingFragment.swift` and `KsApi/models/lenses/BackingLenses.swift`) — run `git show` on any of them.
Change coupling: MessagesViewModel.swift ↔ ProjectPageViewModel.swift Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:1— `Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift` and `Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 7 shared commits counted here, the most recent 3 are `312555a0` Use a smaller fragment when you fetch the backer attached to a Backin… (at that commit the files were still `Library/ViewModels/MessagesViewModel.swift` and `Library/ViewModels/ProjectPageViewModel.swift`); `5b1275f7` [MBL-2597][a] Delete PledgeManagementDetailsWebViewController (#2532) (at that commit the files were still `Library/ViewModels/MessagesViewModel.swift` and `Library/ViewModels/ProjectPageViewModel.swift`); `c0b8831b` [MBL-2316] Replace Native View Pledge Screen with WebView for PM Back… (at that commit the files were still `Library/ViewModels/MessagesViewModel.swift` and `Library/ViewModels/ProjectPageViewModel.swift`) — run `git show` on any of them.
Change coupling: SearchViewModel+GraphQL.swift ↔ SearchViewModel.swift Library/Sources/Library/Library/ViewModels/SearchViewModel+GraphQL.swift:1— `Library/Sources/Library/Library/ViewModels/SearchViewModel+GraphQL.swift` and `Library/Sources/Library/Library/ViewModels/SearchViewModel.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 — 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 `0286291e` [MBL-2573] Make goal filter functional (#2538) (at that commit the files were still `Library/ViewModels/SearchViewModel+GraphQL.swift` and `Library/ViewModels/SearchViewModel.swift`); `d4cba572` MBL-2560: Hook up 'show only' search toggles (#2530) (at that commit the files were still `Library/ViewModels/SearchViewModel+GraphQL.swift` and `Library/ViewModels/SearchViewModel.swift`); `036273e2` MBL-2521, MBL-2519, MBL-2514: Add filter for amount raised (at that commit the files were still `Library/ViewModels/SearchViewModel+GraphQL.swift` and `Library/ViewModels/SearchViewModel.swift`) — run `git show` on any of them.
Change coupling: RewardCardContainerViewModel.swift ↔ RewardsCollectionViewModel.swift Library/Sources/Library/Library/ViewModels/RewardCardContainerViewModel.swift:1— `Library/Sources/Library/Library/ViewModels/RewardCardContainerViewModel.swift` and `Library/Sources/Library/Library/ViewModels/RewardsCollectionViewModel.swift` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 7 shared commits counted here, the most recent 3 are `5c1e7752` [MBL-1712] No Reward Option Not Shown in Edit Reward Flow (#2150) (at that commit the files were still `Library/ViewModels/RewardCardContainerViewModel.swift` and `Library/ViewModels/WithShippingRewardsCollectionViewModel.swift`); `fd1a221c` [MBL-1317] Show Rewards Based on Reward.isAvailable (#2014) (at that commit the files were still `Library/ViewModels/RewardCardContainerViewModel.swift` and `Library/ViewModels/RewardsCollectionViewModel.swift`); `7b1f2c80` [NT-1565] Backers Can Edit an Expired Reward with Add-Ons (#1313) (at that commit the files were still `Library/ViewModels/RewardCardContainerViewModel.swift` and `Library/ViewModels/RewardsCollectionViewModel.swift`) — run `git show` on any of them.
Change coupling: SharedFunctions.swift ↔ RewardCardContainerViewModel.swift Library/Sources/Library/Library/SharedFunctions.swift:1— `Library/Sources/Library/Library/SharedFunctions.swift` and `Library/Sources/Library/Library/ViewModels/RewardCardContainerViewModel.swift` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 `5c1e7752` [MBL-1712] No Reward Option Not Shown in Edit Reward Flow (#2150) (at that commit the files were still `Library/SharedFunctions.swift` and `Library/ViewModels/RewardCardContainerViewModel.swift`); `fd1a221c` [MBL-1317] Show Rewards Based on Reward.isAvailable (#2014) (at that commit the files were still `Library/SharedFunctions.swift` and `Library/ViewModels/RewardCardContainerViewModel.swift`); `519c3991` [MBL-1207] Pledge Button on Project Page (#1951) (at that commit the files were still `Library/SharedFunctions.swift` and `Library/ViewModels/RewardCardContainerViewModel.swift`) — run `git show` on any of them.
Change coupling: PPOProjectCardModel.swift ↔ PPOContainerViewController.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel.swift:1— `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 `4184f253` [MBL-2093] Add manage pledge action to PPO (#2491) (at that commit the files were still `Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel.swift` and `Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift`); `bb3ddea2` [MBL-1493] Handle confirm address action (#2250) (at that commit the files were still `Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel.swift` and `Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift`); `e73aa2fa` [MBL-1490] Handle fix pledge action (#2235) (at that commit the files were still `Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel.swift` and `Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift`) — run `git show` on any of them.
Change coupling: ManagePledgeViewModel.swift ↔ MockPledgeOverTimePlanIncrements.swift Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift:1— `Library/Sources/Library/Library/ViewModels/ManagePledgeViewModel.swift` and `Library/Sources/LibraryTestHelpers/MockPledgeOverTimePlanIncrements.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 — 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 `48bdd952` [MBL-2640] Support refundedAmount and REFUNDED state in GraphQL (#2546) (at that commit the files were still `Library/ViewModels/ManagePledgeViewModel.swift` and `Library/TestHelpers/MockPledgeOverTimePlanIntervals.swift`); `ebb2c32a` [MBL-2120] PLOT - Fixing issue when device locate is ES (#2297) (at that commit the files were still `Library/ViewModels/ManagePledgeViewModel.swift` and `Library/TestHelpers/MockPledgeOverTimePlanIntervals.swift`); `3e055356` [MBL-1961] Update PaymentIncrement State & StateReason GraphQL Types … (at that commit the files were still `Library/ViewModels/ManagePledgeViewModel.swift` and `Library/TestHelpers/MockPledgeOverTimePlanIntervals.swift`) — run `git show` on any of them.
Duplicated block (8 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift:59— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift:59-66 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentsDataSource.swift:63-70 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift:59` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:502— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:502-509 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:513-520 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:337— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:337-344 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SurveyResponse/Controller/PledgeManagerWebViewController.swift:58-65 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:337` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedViewController.swift:232— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedViewController.swift:232-239 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedViewController.swift:403-410 — 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) KsApi/Sources/KsApi/MockService.swift:1229— KsApi/Sources/KsApi/MockService.swift:1229-1236 | KsApi/Sources/KsApi/MockService.swift:1249-1256 — 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 `KsApi/Sources/KsApi/MockService.swift:1229` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.swift:376— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.swift:376-383 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryViewController.swift:167-174 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BetaTools/Controller/BetaToolsViewController.swift:457— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BetaTools/Controller/BetaToolsViewController.swift:457-464 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Help/Controller/HelpViewController.swift:98-106 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentPostFailedCell.swift:28— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentPostFailedCell.swift:28-35 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:46-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Controller/PledgePaymentPlansViewController.swift:33— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Controller/PledgePaymentPlansViewController.swift:33-40 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgePaymentMethodsViewController.swift:38-45 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift:69— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift:69-76 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksDisclaimerCell.swift:81-88 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsAccount/Controller/SettingsAccountViewController.swift:132— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsAccount/Controller/SettingsAccountViewController.swift:132-139 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsNotifications/Controller/SettingsNotificationsViewController.swift:184-192 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:127— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:127-134 | Library/Sources/Library/Library/VideoFeedAudioController.swift:77-84 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift` and `Library/Sources/Library/Library/VideoFeedAudioController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:6— Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:6-13 | Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:21-28 — 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 `Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:6` 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 (9 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/CuratedProjects/Controller/CuratedProjectsViewController.swift:161— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/CuratedProjects/Controller/CuratedProjectsViewController.swift:161-169 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ThanksProjects/Controller/ThanksViewController.swift:224-232 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:375— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:375-383 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Controller/MessagesViewController.swift:179-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.
Duplicated block (9 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FindFriends/Views/Cells/FindFriendsFriendFollowCell.swift:95— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FindFriends/Views/Cells/FindFriendsFriendFollowCell.swift:95-103 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FindFriends/Views/Cells/FindFriendsStatsCell.swift:76-84 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FindFriends/Views/Cells/FindFriendsFriendFollowCell.swift:95` 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 lines × 2) Library/Sources/Library/Library/ViewModels/BackerDashboardProjectsViewModel.swift:106— Library/Sources/Library/Library/ViewModels/BackerDashboardProjectsViewModel.swift:106-114 | Library/Sources/Library/Library/ViewModels/BackerDashboardProjectsViewModel.swift:139-147 — 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 `Library/Sources/Library/Library/ViewModels/BackerDashboardProjectsViewModel.swift:106` 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) Library/Sources/Library/Library/ViewModels/SettingsPrivacyViewModel.swift:70— Library/Sources/Library/Library/ViewModels/SettingsPrivacyViewModel.swift:70-78 | Library/Sources/Library/Library/ViewModels/SettingsRecommendationsCellViewModel.swift:58-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift:79— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift:79-87 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentsDataSource.swift:80-88 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:47— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:47-55 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:38-46 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:202— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:202-210 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:187-195 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:669— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:669-677 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PostCampaignCheckoutViewController.swift:529-537 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PostCampaignCheckoutViewController.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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) KsApi/Sources/KsApi/models/PaymentIntentEnvelope.swift:23— KsApi/Sources/KsApi/models/PaymentIntentEnvelope.swift:23-31 | KsApi/Sources/KsApi/models/graphql/adapters/ClientSecretEnvelope+CreateSetupIntentMutation.Data.swift:9-17 — 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) KsApi/Sources/KsApi/models/graphql/adapters/Project+FastFetchProjectQuery.swift:52— KsApi/Sources/KsApi/models/graphql/adapters/Project+FastFetchProjectQuery.swift:52-60 | KsApi/Sources/KsApi/models/graphql/adapters/Project+FetchAddOnsQueryData.swift:6-14 — 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) Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:40— Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:40-48 | Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:55-63 — 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 `Library/Sources/LibraryTestHelpers/DispatchTimeInterval-Extensions.swift:40` 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 (6 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:48— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:48-53 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:297-302 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:48` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:516— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:516-521 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:821-826 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryPageViewController.swift:516` 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) KsApi/Sources/KsApi/MockService.swift:2053— KsApi/Sources/KsApi/MockService.swift:2053-2058 | KsApi/Sources/KsApi/extensions/MockGraphQLClient.swift:85-90 — 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) REDACTED:35— REDACTED:35-40 | REDACTED:74-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 `REDACTED:35` 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) Library/Sources/Library/Library/ViewModels/DiscoveryPostcardViewModel.swift:160— Library/Sources/Library/Library/ViewModels/DiscoveryPostcardViewModel.swift:160-165 | Library/Sources/Library/Library/ViewModels/ProjectPamphletMainCellViewModel.swift:215-220 — 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 `Library/Sources/Library/Library/ViewModels/DiscoveryPostcardViewModel.swift:160` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoCTAContainerView.swift:123— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoCTAContainerView.swift:123-128 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeViewCTAContainerView.swift:222-227 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:275— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:275-280 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:254-259 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:143— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:143-148 | Library/Sources/Library/Library/VideoFeedAudioController.swift:93-98 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift` and `Library/Sources/Library/Library/VideoFeedAudioController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (6 lines × 2) Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:145— Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:145-150 | Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:1032-1037 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsFollowCell.swift:33— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsFollowCell.swift:33-38 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsPrivacyRecommendationCell.swift:25-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) Library/Sources/Library/Kickstarter-iOS/Features/DesignSystem/Colors/DesignSystemColors.swift:75— Library/Sources/Library/Kickstarter-iOS/Features/DesignSystem/Colors/DesignSystemColors.swift:75-80 | Library/Sources/Library/Library/Styles/SettingsStyles.swift:104-109 — 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) Library/Sources/Library/Kickstarter-iOS/Features/DesignSystem/Colors/DesignSystemColors.swift:92— Library/Sources/Library/Kickstarter-iOS/Features/DesignSystem/Colors/DesignSystemColors.swift:92-97 | Library/Sources/Library/Library/Styles/BaseStyles.swift:54-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.
ClassTooLong: MockService KsApi/Sources/KsApi/MockService.swift:9— ClassTooLong — 1260 significant lines (blank, comment-only and punctuation-only lines excluded), 117 methods. The bar is 400 significant lines; this is 860 over it, 3.15× 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: KSRAnalytics Library/Sources/Library/Library/Tracking/KSRAnalytics.swift:8— ClassTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 736 over it, 2.84× 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: PledgeViewModel Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:116— ClassTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 271 over it, 1.68× 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: Service KsApi/Sources/KsApi/Service.swift:19— ClassTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded), 122 methods. The bar is 400 significant lines; this is 261 over it, 1.65× 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: ProjectPageViewController Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:27— ClassTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 223 over it, 1.56× 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: PostCampaignCheckoutViewModel Library/Sources/Library/Library/ViewModels/PostCampaignCheckoutViewModel.swift:83— ClassTooLong — 467 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 67 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.
ClassTooLong: ProjectPageViewModel Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:241— ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 51 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.
ClassTooLong: ProjectPageViewControllerDataSource Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Datasource/Datasource/ProjectPageViewControllerDataSource.swift:7— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 16 over it, 1.04× 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: AppDelegateViewModel Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:192— ClassTooLong — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 14 over it, 1.04× 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: Colors KDS/Sources/KDS/Colors/Colors.swift:3— ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 12 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: DiscoveryProjectCardCell Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:13— ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 2 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.
FileTooLong: Tracking/KSRAnalytics.swift Library/Sources/Library/Library/Tracking/KSRAnalytics.swift— FileTooLong — 1407 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: KSRAnalytics (8-1841). The bar is 500 significant lines; this is 907 over it, 2.81× 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: KsApi/MockService.swift KsApi/Sources/KsApi/MockService.swift— FileTooLong — 1372 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: MockService (9-1960). The bar is 500 significant lines; this is 872 over it, 2.74× 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: lenses/ProjectLenses.swift KsApi/Sources/KsApi/models/lenses/ProjectLenses.swift— FileTooLong — 1106 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 606 over it, 2.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Kickstarter-iOS/AppDelegateViewModel.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift— FileTooLong — 864 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 364 over it, 1.73× 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: Controller/ProjectPageViewController.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift— FileTooLong — 844 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: ProjectPageViewController (27-1010). The bar is 500 significant lines; this is 344 over it, 1.69× 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: ViewModels/PledgeViewModel.swift Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift— FileTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: PledgeViewModel (116-1106). The bar is 500 significant lines; this is 314 over it, 1.63× 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: KsApi/Service.swift KsApi/Sources/KsApi/Service.swift— FileTooLong — 672 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Service (19-1043). The bar is 500 significant lines; this is 172 over it, 1.34× 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: lenses/RewardLenses.swift KsApi/Sources/KsApi/models/lenses/RewardLenses.swift— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 132 over it, 1.26× 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: ViewModels/ProjectPageViewModel.swift Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: ProjectPageViewModel (241-921). The bar is 500 significant lines; this is 99 over it, 1.20× 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: ViewModels/PostCampaignCheckoutViewModel.swift Library/Sources/Library/Library/ViewModels/PostCampaignCheckoutViewModel.swift— FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: PostCampaignCheckoutViewModel (83-785). The bar is 500 significant lines; this is 36 over it, 1.07× 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: Cells/DiscoveryProjectCardCell.swift Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: DiscoveryProjectCardCell (13-606). The bar is 500 significant lines; this is 27 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (10 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:33— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:33-42 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendFollowCell.swift:25-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.
Duplicated block (10 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:52— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityFriendBackingCell.swift:52-61 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityProjectStatusCell.swift:37-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 (10 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Help/Views/Cells/SettingsTableViewCell.swift:31— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Help/Views/Cells/SettingsTableViewCell.swift:31-40 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsAccount/Views/Cells/SettingsAccountWarningCell.swift:42-51 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:179— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:179-188 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:166-175 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Library/Sources/Library/Library/ViewModels/ActivityFriendBackingViewModel.swift:148— Library/Sources/Library/Library/ViewModels/ActivityFriendBackingViewModel.swift:148-157 | Library/Sources/Library/Library/ViewModels/ActivityProjectStatusViewModel.swift:133-142 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Controller/BackerDashboardProjectsViewController.swift:125— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Controller/BackerDashboardProjectsViewController.swift:125-134 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageThreads/Controller/MessageThreadsViewController.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.
Duplicated block (10 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoShimmerLoadingView.swift:34— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoShimmerLoadingView.swift:34-43 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeShippingLocationShimmerLoadingView.swift:34-43 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoShimmerLoadingView.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeShippingLocationShimmerLoadingView.swift` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:162— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:162-171 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:146-155 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/CreatePassword/Views/SettingsGroupedHeaderView.swift:15— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/CreatePassword/Views/SettingsGroupedHeaderView.swift:15-24 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/SettingsGroupedFooterView.swift:17-26 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/CreatePassword/Views/SettingsGroupedHeaderView.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/SettingsGroupedFooterView.swift` as WHOLE FILES: 87% 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:248— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:248-259 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Search/Views/Cell/MostPopularSearchProjectCell.swift:60-71 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:58— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:58-69 | Library/Sources/Library/Library/VideoFeedAudioController.swift:43-54 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift` and `Library/Sources/Library/Library/VideoFeedAudioController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:58` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:150— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift:150-161 | Library/Sources/Library/Library/VideoFeedAudioController.swift:100-111 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedAudioController.swift` and `Library/Sources/Library/Library/VideoFeedAudioController.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift:43— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift:43-54 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareSheetView.swift:384-395 — 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 (12 lines × 2) KsApi/Sources/KsApi/AsyncApolloClient.swift:47— KsApi/Sources/KsApi/AsyncApolloClient.swift:47-58 | KsApi/Sources/KsApi/AsyncApolloClient.swift:68-79 — 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 `KsApi/Sources/KsApi/AsyncApolloClient.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.
Duplicated block (12 lines × 2) KsApi/Sources/KsApi/MockService.swift:1139— KsApi/Sources/KsApi/MockService.swift:1139-1150 | KsApi/Sources/KsApi/MockService.swift:1922-1933 — 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 `KsApi/Sources/KsApi/MockService.swift:1139` 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) KsApi/Sources/KsApi/models/ProjectAndBackingEnvelope.swift:23— KsApi/Sources/KsApi/models/ProjectAndBackingEnvelope.swift:23-34 | KsApi/Sources/KsApi/models/graphql/adapters/Backing+BackingFragment.swift:83-94 — 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 `KsApi/Sources/KsApi/models/ProjectAndBackingEnvelope.swift:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) Library/Sources/Library/Library/CreditCard+Utils.swift:18— Library/Sources/Library/Library/CreditCard+Utils.swift:18-29 | Library/Sources/Library/Library/ViewModels/ManagePledgePaymentMethodViewModel.swift:160-171 — 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 (15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Datasource/BackerDashboardPagesDataSource.swift:38— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Datasource/BackerDashboardPagesDataSource.swift:38-52 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Datasource/DiscoveryPagesDataSource.swift:37-51 — 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 (15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Datasource/BackerDashboardPagesDataSource.swift:54— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Datasource/BackerDashboardPagesDataSource.swift:54-68 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Datasource/DiscoveryPagesDataSource.swift:53-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.
Duplicated block (15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ChangePassword/Controller/ChangePasswordViewController.swift:116— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ChangePassword/Controller/ChangePasswordViewController.swift:116-130 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SelectCurrency/Controller/SelectCurrencyViewController.swift:90-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.
Duplicated block (15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Controller/MessagesViewController.swift:125— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Controller/MessagesViewController.swift:125-139 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:664-678 — 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 (15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:115— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:115-129 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:99-113 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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 (15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift:52— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift:52-66 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCheckmarkListCell.swift:84-98 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCheckmarkListCell.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. 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 (15 lines × 2) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:266— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:266-280 | Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:620-634 — 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 `Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:266` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivitySurveyResponseCell.swift:41— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivitySurveyResponseCell.swift:41-53 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/FindFriendsFacebookConnectCell.swift:77-89 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivitySurveyResponseCell.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.
Duplicated block (13 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BetaTools/Controller/BetaToolsViewController.swift:254— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BetaTools/Controller/BetaToolsViewController.swift:254-266 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BetaTools/Controller/BetaToolsViewController.swift:284-296 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FeatureFlagTools/Controller/FeatureFlagToolsViewController.swift:18— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FeatureFlagTools/Controller/FeatureFlagToolsViewController.swift:18-30 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RemoteConfigFeatureFlagTools/Controller/RemoteConfigFeatureFlagToolsViewController.swift:21-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:534— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:534-546 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:555-567 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:534` 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 (13 lines × 2) KsApi/Sources/KsApi/MockService.swift:1624— KsApi/Sources/KsApi/MockService.swift:1624-1636 | KsApi/Sources/KsApi/MockService.swift:1639-1651 — 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 (13 lines × 2) Library/Sources/Library/Library/ViewModels/SettingsNotificationsViewModel.swift:50— Library/Sources/Library/Library/ViewModels/SettingsNotificationsViewModel.swift:50-62 | Library/Sources/Library/Library/ViewModels/SettingsRecommendationsCellViewModel.swift:36-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/ViewModels/SettingsNotificationsViewModel.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 (13 lines × 2) ServerDrivenUI/Sources/ServerDrivenUI/RichTextGQLConversions.swift:11— ServerDrivenUI/Sources/ServerDrivenUI/RichTextGQLConversions.swift:11-23 | ServerDrivenUI/Sources/ServerDrivenUI/RichTextGQLConversions.swift:27-39 — 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 (11 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/FindFriendsFacebookConnectCell.swift:118— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/FindFriendsFacebookConnectCell.swift:118-128 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/LoginTout/Controller/LoginToutViewController.swift:452-462 — 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 (11 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:180— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:180-190 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift:195-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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:180` 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, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:178` calls `commentRepliesViewControllerDidBlockUser` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift:194` 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 (11 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:212— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:212-222 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:197-207 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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 (11 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.swift:52— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.swift:52-62 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PostCampaignPledgeRewardsSummaryCell.swift:76-86 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.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 (11 lines × 2) KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.swift:20— KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.swift:20-30 | KsApi/Sources/KsApi/models/UpdatePledgeEnvelope.swift:20-30 — before extracting anything, compare `KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.swift` and `KsApi/Sources/KsApi/models/UpdatePledgeEnvelope.swift` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.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.
Duplicated block (11 lines × 2) KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+UnwatchProjectMutation.Data.swift:9— KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+UnwatchProjectMutation.Data.swift:9-20 | KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+WatchProjectMutation.Data.swift:10-20 — before extracting anything, compare `KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+UnwatchProjectMutation.Data.swift` and `KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+WatchProjectMutation.Data.swift` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (11 lines × 2) Library/Sources/Library/Library/AppEnvironment.swift:440— Library/Sources/Library/Library/AppEnvironment.swift:440-450 | Library/Sources/Library/Library/AppEnvironment.swift:459-469 — 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 `Library/Sources/Library/Library/AppEnvironment.swift:440` 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 (20 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:94— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:94-113 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:356-375 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:94` 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, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:376` calls `constraint` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:114` 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 (20 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:57— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:57-76 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:48-67 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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 (20 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnCardView.swift:171— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnCardView.swift:171-190 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardView.swift:185-204 — 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 (20 lines × 2) Library/Sources/Library/Library/AppEnvironment.swift:214— Library/Sources/Library/Library/AppEnvironment.swift:214-233 | Library/Sources/Library/Library/AppEnvironment.swift:291-310 — 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 `Library/Sources/Library/Library/AppEnvironment.swift:214` 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) KsApi/Sources/KsApi/mutations/CreateCheckoutMutation.swift:6— KsApi/Sources/KsApi/mutations/CreateCheckoutMutation.swift:6-25 | KsApi/Sources/KsApi/mutations/UpdateBackingMutation.swift:6-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryExpandedSelectableRow.swift:40— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryExpandedSelectableRow.swift:40-53 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryFiltersStaticRowCell.swift:16-29 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryExpandedSelectableRow.swift:40` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Datasource/PledgeExpandableRewardsHeaderDataSource.swift:13— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Datasource/PledgeExpandableRewardsHeaderDataSource.swift:13-26 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Datasource/PostCampaignPledgeRewardsSummaryDataSource.swift:13-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. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Datasource/PledgeExpandableRewardsHeaderDataSource.swift:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Library/Sources/Library/Library/Format.swift:312— Library/Sources/Library/Library/Format.swift:312-325 | Library/Sources/Library/Library/ViewModels/ErroredBackingViewViewModel.swift:91-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. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/Format.swift:312` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:214— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:214-227 | Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:303-316 — 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 `Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:214` 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) Library/Sources/Library/Library/ViewModels/PledgeAmountSummaryViewModel.swift:112— Library/Sources/Library/Library/ViewModels/PledgeAmountSummaryViewModel.swift:112-125 | Library/Sources/Library/Library/ViewModels/PledgeAmountSummaryViewModel.swift:131-144 — 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 `Library/Sources/Library/Library/ViewModels/PledgeAmountSummaryViewModel.swift:112` 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 × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/ActivitySampleProjectCell.swift:85— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/ActivitySampleProjectCell.swift:85-94 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:301-310 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/VideoViewController.swift:143-152 — 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeExpandableRewardsHeaderViewController.swift:79— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeExpandableRewardsHeaderViewController.swift:79-88 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:84-93 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:75-84 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeExpandableRewardsHeaderViewController.swift:79` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewControllerHelpers.swift:27— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewControllerHelpers.swift:27-36 | Library/Sources/Library/Library/Styles/CheckoutStyles.swift:173-182 | Library/Sources/Library/Library/Styles/LoginStyles.swift:162-171 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewControllerHelpers.swift:27` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsAskAQuestionCell.swift:40— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsAskAQuestionCell.swift:40-49 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksDisclaimerCell.swift:58-67 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabDisclaimerCell.swift:67-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsAskAQuestionCell.swift:40` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksDisclaimerCell.swift:71` calls `attributedTextForFootnoteLabel` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsAskAQuestionCell.swift:54` 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 × 3) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:257— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:257-266 | Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:368-377 | Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:220-229 — 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 (7 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:171— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:171-177 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabDisclaimerCell.swift:188-194 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeDisclaimerView.swift:125-131 — 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 (7 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/PersonalizationCell.swift:43— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/PersonalizationCell.swift:43-49 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PostCampaignPledgeRewardsSummaryHeaderCell.swift:20-26 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardTracking/Views/RewardTrackingActivitiesCell.swift:38-44 — 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 (7 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:215— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:215-222 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeSummaryViewController.swift:117-123 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeViewCTAContainerView.swift:250-256 — 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 (7 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/ManagePledgePaymentMethodView.swift:35— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/ManagePledgePaymentMethodView.swift:35-41 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:41-48 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardView.swift:45-51 — 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 (7 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeLocalPickupView.swift:17— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeLocalPickupView.swift:17-23 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeShippingSummaryView.swift:19-25 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/Cells/PillCell.swift:19-25 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeLocalPickupView.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeShippingSummaryView.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. 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.
Swallowed exception (caught, then discarded) Library/Sources/Library/Library/Keychain.swift:104— `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) Library/Sources/Library/Library/String+SimpleHTML.swift:125— `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) KsApi/Sources/KsApi/PKCE.swift:53— `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) KsApi/Sources/KsApi/models/ProjectStatsEnvelope.swift:214— `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) KsApi/Sources/KsApi/models/ProjectStatsEnvelope.swift:284— `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.
TooManyMethods: Service KsApi/Sources/KsApi/Service.swift:19— TooManyMethods — 122 methods, declared across 3 files: KsApi/Service.swift (116), KsApi/Service+DecodeHelpers.swift (3), KsApi/Service+RequestHelpers.swift (3). The bar is 30 methods; this is 92 over it, 4.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. Most of these members implement KsApi~KsApi.ServiceType (101 of 106 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: MockService KsApi/Sources/KsApi/MockService.swift:9— TooManyMethods — 117 methods. The bar is 30 methods; this is 87 over it, 3.90× the bar. Most of these members implement KsApi~KsApi.ServiceType (101 of 101 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: ProjectPageViewController Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:27— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.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: KSRAnalytics Library/Sources/Library/Library/Tracking/KSRAnalytics.swift:8— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (17 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:459— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:459-475 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PostCampaignCheckoutViewController.swift:374-390 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PostCampaignCheckoutViewController.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 (17 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnSelectionContinueCTAView.swift:55— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnSelectionContinueCTAView.swift:55-71 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeCTAContainerView.swift:120-136 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnSelectionContinueCTAView.swift:55` 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) KsApi/Sources/KsApi/MockService.swift:421— KsApi/Sources/KsApi/MockService.swift:421-440 | KsApi/Sources/KsApi/MockService.swift:483-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `KsApi/Sources/KsApi/MockService.swift:421` 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) KsApi/Sources/KsApi/models/graphql/adapters/CategoryEnvelope+FetchCategoryQueryData.swift:53— KsApi/Sources/KsApi/models/graphql/adapters/CategoryEnvelope+FetchCategoryQueryData.swift:53-69 | KsApi/Sources/KsApi/models/graphql/adapters/RootCategoriesEnvelope+FetchRootCategoriesQueryData.swift:51-67 — 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 `KsApi/Sources/KsApi/models/graphql/adapters/CategoryEnvelope+FetchCategoryQueryData.swift:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardEmptyStateCell.swift:102— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardEmptyStateCell.swift:102-122 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Views/Cells/MessagesEmptyStateCell.swift:18-33 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsFollowCell.swift:40-61 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsPrivacyDeleteOrRequestCell.swift:50-67 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsPrivacyRecommendationCell.swift:32-51 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:111— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:111-138 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ExternalSourceViewElementCell.swift:81-99 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ImageViewElementCell.swift:100-129 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectHeaderCell.swift:36-58 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/TextViewElementCell.swift:44-65 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsCell.swift:106— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsCell.swift:106-143 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift:45-61 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabAIGenerationCell.swift:41-57 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift:51-73 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCheckmarkListCell.swift:83-105 — 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.
Duplicated block (18 lines × 2) Library/Sources/Library/Library/AppEnvironment.swift:253— Library/Sources/Library/Library/AppEnvironment.swift:253-270 | Library/Sources/Library/Library/AppEnvironment.swift:333-350 — 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 `Library/Sources/Library/Library/AppEnvironment.swift:253` 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 (18 lines × 2) Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:33— Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:33-50 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:117-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.
Duplicated block (18 lines × 2) Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:73— Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:73-90 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:157-174 — 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 `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:73` 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 × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:148— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:148-159 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabDisclaimerCell.swift:164-175 | Library/Sources/Library/Library/ViewModels/PledgeStatusLabelViewModel.swift:268-279 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:148` 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 (12 lines × 3) Library/Sources/Library/Library/Environment.swift:164— Library/Sources/Library/Library/Environment.swift:164-175 | Library/Sources/Library/Library/UseCases/SimilarProjects/ProjectCardProperties.swift:48-59 | Library/Sources/Library/Library/ViewModels/ProjectPamphletMainCellProperties.swift:74-85 — 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 `Library/Sources/Library/Library/Environment.swift:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:263— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:263-274 | Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:226-237 | Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:617-628 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:263` 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 × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:871— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:871-878 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectUpdatesViewController.swift:90-97 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Update/Controller/UpdateViewController.swift:90-97 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:871` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift:28— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift:28-35 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift:42-49 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareSheetView.swift:383-390 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoShimmerLoadingView.swift:14— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoShimmerLoadingView.swift:14-21 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/SimilarProjects/Cells/SimilarProjectsLoadingCollectionViewCell.swift:20-27 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeShippingLocationShimmerLoadingView.swift:14-21 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoShimmerLoadingView.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeShippingLocationShimmerLoadingView.swift` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentPostFailedCell.swift:61— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentPostFailedCell.swift:61-65 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentRemovedCell.swift:81-85 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/RootCommentCell.swift:77-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 all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentPostFailedCell.swift:54` calls `uiColor`, `bindStyles` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/RootCommentCell.swift:72` 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 × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:679— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:679-683 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Controllers/PledgeViewController.swift:685-689 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/HeaderFooterViews/RewardsCollectionViewHeaderView.swift:66-70 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 3) KsApi/Sources/KsApi/models/CommentsEnvelope.swift:15— KsApi/Sources/KsApi/models/CommentsEnvelope.swift:15-19 | KsApi/Sources/KsApi/models/CommentsEnvelope.swift:21-25 | KsApi/Sources/KsApi/models/graphql/adapters/CommentRepliesEnvelope+GraphCommentRepliesEnvelope.swift:35-42 — 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.
Off the main sequence: KsApi — KsApi: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: KDS — KDS: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: Experimentation — Experimentation: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) KsApi/Sources/KsApi/MockService.swift:247— KsApi/Sources/KsApi/MockService.swift:247-602 | Library/Sources/Library/Library/Environment.swift:127-201 | Library/Sources/Library/Library/UseCases/SimilarProjects/ProjectCardProperties.swift:30-66 | Library/Sources/Library/Library/ViewModels/ProjectPamphletMainCellProperties.swift:46-102 — 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) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:88— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:88-300 | Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:88-411 | Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:83-256 | Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:243-716 — 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.
Duplicated block (26 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:111— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:111-136 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/LoginTout/Controller/LoginToutViewController.swift:233-258 — 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 (26 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:133— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:133-158 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:117-142 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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 (21 lines × 2) Library/Sources/Library/Library/ViewModels/PledgeExpandableRewardsHeaderViewModel.swift:199— Library/Sources/Library/Library/ViewModels/PledgeExpandableRewardsHeaderViewModel.swift:199-219 | Library/Sources/Library/Library/ViewModels/PostCampaignPledgeRewardsSummaryViewModel.swift:247-267 — 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 (21 lines × 2) KsApi/Sources/KsApi/mutations/CreateBackingMutation.swift:6— KsApi/Sources/KsApi/mutations/CreateBackingMutation.swift:6-26 | KsApi/Sources/KsApi/mutations/CreatePaymentsSourceMutation.swift:6-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. 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:81— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:81-99 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:480-498 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) KsApi/Sources/KsApi/mutations/UnwatchProjectMutation.swift:6— KsApi/Sources/KsApi/mutations/UnwatchProjectMutation.swift:6-24 | KsApi/Sources/KsApi/mutations/WatchProjectMutation.swift:6-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. 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 (18 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.swift:94— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.swift:94-111 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardHeaderCell.swift:110-127 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PostCampaignPledgeRewardsSummaryHeaderCell.swift:133-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.swift:94` 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 (18 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SortFilter/AmountRaisedView/AmountRaisedView.swift:10— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SortFilter/AmountRaisedView/AmountRaisedView.swift:10-27 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SortFilter/GoalView/GoalView.swift:10-27 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SortFilter/PercentRaisedView/PercentRaisedView.swift:10-27 — 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 (16 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift:274— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift:274-289 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift:296-311 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOContainerViewController.swift:274` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Library/Sources/Library/Library/ViewModels/HelpViewModel.swift:117— Library/Sources/Library/Library/ViewModels/HelpViewModel.swift:117-132 | Library/Sources/Library/Library/ViewModels/ProjectUpdatesViewModel.swift:276-291 — 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 (15–16 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsNotifications/Views/Cells/SettingsNotificationCell.swift:77— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsNotifications/Views/Cells/SettingsNotificationCell.swift:77-91 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsNotifications/Views/Cells/SettingsNotificationCell.swift:94-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:53— Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:53-68 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:138-152 — 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 `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.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 (11–12 lines × 2) KDS/Sources/KDS/Fonts/InterFont.swift:47— KDS/Sources/KDS/Fonts/InterFont.swift:47-58 | KDS/Sources/KDS/Fonts/SystemFont.swift:36-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 `KDS/Sources/KDS/Fonts/InterFont.swift:47` 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–12 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:97— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:97-107 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PostCampaignPledgeRewardsSummaryHeaderCell.swift:94-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. 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:113— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:113-122 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryExpandedSelectableRow.swift:49-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. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:113` 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 (10–11 lines × 2) Library/Sources/Library/Library/Styles/CheckoutStyles.swift:173— Library/Sources/Library/Library/Styles/CheckoutStyles.swift:173-182 | Library/Sources/Library/Library/Styles/LoginStyles.swift:161-171 — 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 `Library/Sources/Library/Library/Styles/CheckoutStyles.swift:173` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaymentMethods/Controller/PaymentMethodSettingsViewController.swift:194— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaymentMethods/Controller/PaymentMethodSettingsViewController.swift:194-203 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgePaymentMethodsViewController.swift:183-191 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaymentMethods/Controller/PaymentMethodSettingsViewController.swift:194` 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, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaymentMethods/Controller/PaymentMethodSettingsViewController.swift:205` calls `shouldCancelPaymentSheetAppearance` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgePaymentMethodsViewController.swift:193` 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 (9–10 lines × 2) Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift:359— Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift:359-367 | Library/Sources/Library/Library/ViewModels/RewardCardViewModel.swift:328-337 — 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 `Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift:359` 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–9 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectUpdatesViewController.swift:88— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectUpdatesViewController.swift:88-95 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Update/Controller/UpdateViewController.swift:87-95 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectUpdatesViewController.swift:88` 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–9 lines × 2) KsApi/Sources/KsApi/MockService.swift:759— KsApi/Sources/KsApi/MockService.swift:759-767 | KsApi/Sources/KsApi/Service.swift:214-221 — 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 `KsApi/Sources/KsApi/MockService.swift:759` 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 (5 lines × 4) Library/Sources/Library/Library/AppEnvironment.swift:227— Library/Sources/Library/Library/AppEnvironment.swift:227-231 | Library/Sources/Library/Library/AppEnvironment.swift:304-308 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:45-49 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:129-133 — before extracting anything, compare `Library/Sources/Library/Library/AppEnvironment.swift` and `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 (5 lines × 4) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/PledgeOverTimePaymentScheduleItemView.swift:87— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/PledgeOverTimePaymentScheduleItemView.swift:87-91 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:261-265 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:267-271 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.swift:273-277 — 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.
Route.requestProperties (cyclomatic 51) KsApi/Sources/KsApi/lib/Route.swift:58— Route.requestProperties has cyclomatic complexity 51 (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.
ProjectPageViewControllerDataSource.load (cyclomatic 33) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Datasource/Datasource/ProjectPageViewControllerDataSource.swift:77— ProjectPageViewControllerDataSource.load 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.
AppDelegateViewModel.swift.navigation (cyclomatic 24) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:896— AppDelegateViewModel.swift.navigation has cyclomatic complexity 24 (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.
ProjectPageViewController.bindProjectPageViewModel (cyclomatic 23) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:394— ProjectPageViewController.bindProjectPageViewModel has cyclomatic complexity 23 (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.
AppDelegateViewModel.init (cyclomatic 21) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:194— AppDelegateViewModel.init has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsNotificationCellViewModel.notificationFor (cyclomatic 21) Library/Sources/Library/Library/ViewModels/SettingsNotificationCellViewModel.swift:196— SettingsNotificationCellViewModel.notificationFor 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.
PledgeViewModel.init (cyclomatic 19) Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:118— PledgeViewModel.init has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryParams.validForAPIV1 (cyclomatic 18) KsApi/Sources/KsApi/models/DiscoveryParams.swift:227— DiscoveryParams.validForAPIV1 has cyclomatic complexity 18 (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.
ProjectUpdatesViewModel.init (cyclomatic 17) Library/Sources/Library/Library/ViewModels/ProjectUpdatesViewModel.swift:64— ProjectUpdatesViewModel.init 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.
SearchViewModel.init (cyclomatic 17) Library/Sources/Library/Library/ViewModels/SearchViewModel.swift:90— SearchViewModel.init 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.
TextViewElementCellViewModel.swift.attributedText (cyclomatic 17) Library/Sources/Library/Library/ViewModels/HTML Parser/TextViewElementCellViewModel.swift:45— TextViewElementCellViewModel.swift.attributedText 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.
Format.relative (cyclomatic 16) Library/Sources/Library/Library/Format.swift:346— Format.relative 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.
D12 · Dependency Hygiene· Dependency not covered by the committed resolution · ×1
Dependency not covered by the committed resolution: statsig-kit — `statsig-kit` is declared in Kickstarter-Framework/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
HackComment Library/Sources/Library/Library/ViewModels/DiscoveryPageViewModel.swift:75— /// Hack to emit when we should asynchronously reload the table view's data to properly display postcards. — 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.
ProjectPageViewControllerDataSource.load (cognitive 41) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Datasource/Datasource/ProjectPageViewControllerDataSource.swift:77— ProjectPageViewControllerDataSource.load has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 6, match/switch 3 (6 pts), ternaries 1 (3 pts) (nesting depth added 17). 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.
AppDelegateViewModel.swift.navigation (cognitive 32) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:896— AppDelegateViewModel.swift.navigation has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextViewElementCellViewModel.swift.attributedText (cognitive 25) Library/Sources/Library/Library/ViewModels/HTML Parser/TextViewElementCellViewModel.swift:45— TextViewElementCellViewModel.swift.attributedText has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectPageViewController.bindProjectPageViewModel (cognitive 22) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Controller/ProjectPageViewController.swift:394— ProjectPageViewController.bindProjectPageViewModel has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15, boolean chains 6, ternaries 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.
Format.relative (cognitive 22) Library/Sources/Library/Library/Format.swift:346— Format.relative has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 10 (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.
SettingsNotificationCellViewModel.notificationFor (cognitive 22) Library/Sources/Library/Library/ViewModels/SettingsNotificationCellViewModel.swift:196— SettingsNotificationCellViewModel.notificationFor has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 1, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AppDelegateViewModel.init (cognitive 20) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:194— AppDelegateViewModel.init has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, boolean chains 6, ternaries 2. 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.
MessageBannerViewController.showViewAndAnimate (cognitive 20) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/MessageBanner/Controller/MessageBannerViewController.swift:130— MessageBannerViewController.showViewAndAnimate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PledgeViewModel.init (cognitive 19) Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:118— PledgeViewModel.init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 7. 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.
ProjectPageViewModel.init (cognitive 18) Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:243— ProjectPageViewModel.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 4, boolean chains 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.
RichTextExampleProjectsViewModel.extractSlug (cognitive 16) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RichTextExample/RichTextExampleProjectsViewModel.swift:21— RichTextExampleProjectsViewModel.extractSlug has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7 (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.
PPOProjectCardModel.init (cognitive 16) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel+Parsing.swift:13— PPOProjectCardModel.init has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 6. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ProjectUpdatesViewModel.init (cognitive 16) Library/Sources/Library/Library/ViewModels/ProjectUpdatesViewModel.swift:64— ProjectUpdatesViewModel.init has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 15, ternaries 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.
SearchViewModel.init (cognitive 16) Library/Sources/Library/Library/ViewModels/SearchViewModel.swift:90— SearchViewModel.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 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.
RewardAddOnSelectionViewModel.swift.filteredAddOns (cognitive 16) Library/Sources/Library/Library/ViewModels/RewardAddOnSelectionViewModel.swift:519— RewardAddOnSelectionViewModel.swift.filteredAddOns has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 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.
Change-coupling hub: GraphSchema.swift → MockService.swift, Service.swift, ServiceType.swift KsApi/Sources/KsApi/GraphSchema.swift— `KsApi/Sources/KsApi/GraphSchema.swift` changes together with 3 other files — `KsApi/Sources/KsApi/MockService.swift`, `KsApi/Sources/KsApi/Service.swift`, `KsApi/Sources/KsApi/ServiceType.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.
D4 · Code Duplication· Near-duplicate member family (4 members, 39 shared lines) · ×1
Near-duplicate member family (4 members, 39 shared lines) Library/Sources/Library/Library/AppEnvironment.swift:200— Library/Sources/Library/Library/AppEnvironment.swift:200-270 | Library/Sources/Library/Library/AppEnvironment.swift:274-350 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:18-90 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:102-174 — These 4 members are variants of one another: a block of 39 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.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:58— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.swift:58-102 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:476-499 — 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.
Duplicated block (29–36 lines × 2) KsApi/Sources/KsApi/MockService.swift:459— KsApi/Sources/KsApi/MockService.swift:459-487 | KsApi/Sources/KsApi/MockService.swift:532-567 — 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 (25 lines × 2) Library/Sources/Library/Library/DataSource/UIView-Extensions.swift:7— Library/Sources/Library/Library/DataSource/UIView-Extensions.swift:7-31 | Library/Sources/Library/Library/UIViewController-Preparation.swift:11-35 — 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 `Library/Sources/Library/Library/DataSource/UIView-Extensions.swift:7` 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 (24 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:154— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:154-177 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/LoginTout/Controller/LoginToutViewController.swift:425-448 — 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 (18–21 lines × 3) Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:442— Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:442-462 | Library/Sources/Library/Library/ViewModels/RewardsCollectionViewModel.swift:331-351 | Library/Sources/Library/Library/ViewModels/ThanksViewModel.swift:231-248 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:442` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–20 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaginationExample/PaginationExampleViewModel.swift:53— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaginationExample/PaginationExampleViewModel.swift:53-71 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PaginationExample/PaginationExampleViewModel.swift:73-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–19 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:241— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:241-259 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift:221-238 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PostCampaignPledgeRewardsSummaryViewController.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 155 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Controller/PledgeRewardsSummaryViewController.swift:241` 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 (18 lines × 4) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:111— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:111-128 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ExternalSourceViewElementCell.swift:81-98 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ImageViewElementCell.swift:100-117 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/TextViewElementCell.swift:44-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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.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 (17–18 lines × 2) KsApi/Sources/KsApi/extensions/ApolloClient+RAC.swift:19— KsApi/Sources/KsApi/extensions/ApolloClient+RAC.swift:19-36 | KsApi/Sources/KsApi/extensions/ApolloClient+RAC.swift:87-103 — 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 `KsApi/Sources/KsApi/extensions/ApolloClient+RAC.swift:19` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Controller/DesignSystemViewController.swift:480— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Controller/DesignSystemViewController.swift:480-496 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoCTAContainerView.swift:191-207 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeView/Views/PledgeViewCTAContainerView.swift:309-325 — 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 (14–16 lines × 5) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:112— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:112-125 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ExternalSourceViewElementCell.swift:82-95 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ImageViewElementCell.swift:101-114 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectHeaderCell.swift:36-51 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/TextViewElementCell.swift:45-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/AudioVideoViewElementCell.swift:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–16 lines × 2) Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:57— Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:57-70 | Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:437-452 — 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 `Library/Sources/Library/Library/ViewModels/ApplePayTokenUseCase.swift:57` 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 × 4) Library/Sources/Library/Library/AppEnvironment.swift:235— Library/Sources/Library/Library/AppEnvironment.swift:235-249 | Library/Sources/Library/Library/AppEnvironment.swift:312-326 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:54-68 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:138-152 — before extracting anything, compare `Library/Sources/Library/Library/AppEnvironment.swift` and `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 `Library/Sources/Library/Library/AppEnvironment.swift:235` 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–15 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Onboarding/Views/OnboardingCTAView.swift:93— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Onboarding/Views/OnboardingCTAView.swift:93-103 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Onboarding/Views/OnboardingCTAView.swift:107-117 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Onboarding/Views/OnboardingItemView.swift:62-76 — 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 (14–15 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1232— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1232-1246 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1304-1317 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/AppDelegateViewModel.swift:1232` 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 (14 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:204— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:204-217 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentsViewController.swift:277-290 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Controller/MessagesViewController.swift:241-254 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Controllers/CommentRepliesViewController.swift:204` 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 × 4) Library/Sources/Library/Library/AppEnvironment.swift:201— Library/Sources/Library/Library/AppEnvironment.swift:201-213 | Library/Sources/Library/Library/AppEnvironment.swift:275-287 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:19-31 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:103-115 — before extracting anything, compare `Library/Sources/Library/Library/AppEnvironment.swift` and `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 × 3) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:282— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:282-294 | Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:393-405 | Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:637-649 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:282` 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–13 lines × 2) KDS/Sources/KDS/Fonts/InterFont.swift:16— KDS/Sources/KDS/Fonts/InterFont.swift:16-28 | KDS/Sources/KDS/Fonts/SystemFont.swift:21-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `KDS/Sources/KDS/Fonts/InterFont.swift:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 4) KsApi/Sources/KsApi/MockService.swift:581— KsApi/Sources/KsApi/MockService.swift:581-602 | Library/Sources/Library/Library/Environment.swift:190-201 | Library/Sources/Library/Library/UseCases/SimilarProjects/ProjectCardProperties.swift:55-66 | Library/Sources/Library/Library/ViewModels/ProjectPamphletMainCellProperties.swift:91-102 — 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 `KsApi/Sources/KsApi/MockService.swift:581` 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–12 lines × 2) Library/Sources/Library/Library/ViewModels/ActivityFriendFollowCellViewModel.swift:38— Library/Sources/Library/Library/ViewModels/ActivityFriendFollowCellViewModel.swift:38-46 | Library/Sources/Library/Library/ViewModels/ActivitySurveyResponseCellViewModel.swift:55-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/ViewModels/ActivityFriendFollowCellViewModel.swift:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:126— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FacebookConfirmation/Controller/FacebookConfirmationViewController.swift:126-136 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Help/Controller/HelpViewController.swift:54-64 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/LoginTout/Controller/LoginToutViewController.swift:248-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 × 5) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsCell.swift:106— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsCell.swift:106-115 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift:45-54 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabAIGenerationCell.swift:41-50 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift:51-63 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCheckmarkListCell.swift:83-95 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsCell.swift:106` 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) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:110— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:110-118 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryExpandedSelectableRow.swift:46-55 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DiscoveryFilters/Views/Cells/DiscoveryFiltersStaticRowCell.swift:22-31 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:110` 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 × 4) Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:259— Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:259-267 | Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:370-378 | Library/Sources/Library/Library/ViewModels/MessagesViewModel.swift:222-230 | Library/Sources/Library/Library/ViewModels/ProjectPageViewModel.swift:613-621 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:259` 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 (7 lines × 5) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardEmptyStateCell.swift:102— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardEmptyStateCell.swift:102-109 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Messages/Views/Cells/MessagesEmptyStateCell.swift:18-25 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsFollowCell.swift:40-47 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsPrivacyDeleteOrRequestCell.swift:50-57 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/SettingsPrivacy/Views/Cells/SettingsPrivacyRecommendationCell.swift:32-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardEmptyStateCell.swift:102` 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 × 4) Library/Sources/Library/Library/AppEnvironment.swift:220— Library/Sources/Library/Library/AppEnvironment.swift:220-225 | Library/Sources/Library/Library/AppEnvironment.swift:297-302 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:39-44 | Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift:123-128 — before extracting anything, compare `Library/Sources/Library/Library/AppEnvironment.swift` and `Library/Sources/LibraryTestHelpers/XCTestCase+AppEnvironment.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 (5–6 lines × 2) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:158— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:158-162 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:171-176 — 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 `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:158` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:162` calls `constraint` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardContainerView.swift:176` 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 (7 lines × 6) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityErroredBackingsCell.swift:30— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Activities/Views/Cells/ActivityErroredBackingsCell.swift:30-36 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift:24-30 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabAIGenerationCell.swift:26-32 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift:29-35 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCheckmarkListCell.swift:29-35 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabDisclaimerCell.swift:32-38 — before extracting anything, compare `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectRisksCell.swift` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectTabCategoryDescriptionCell.swift` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 × 5) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:70— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.swift:70-75 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ManagePledge/Views/Cells/RewardTableViewCell.swift:13-18 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardCell.swift:18-23 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgePaymentMethods/Views/Cells/PledgeExpandableHeaderRewardHeaderCell.swift:20-25 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectPamphletCreatorHeaderCell.swift:16-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (6 lines × 7) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentViewMoreRepliesFailedCell.swift:30— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentViewMoreRepliesFailedCell.swift:30-35 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentsErrorCell.swift:16-21 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/EmptyCommentsCell.swift:17-22 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/ViewMoreRepliesCell.swift:18-23 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsAskAQuestionCell.swift:26-31 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectFAQsEmptyStateCell.swift:16-21 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectHeaderCell.swift:22-27 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/ViewMoreRepliesCell.swift:14` calls `UILabel` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Views/Cells/CommentViewMoreRepliesFailedCell.swift:26` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 5) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoCTAContainerView.swift:52— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoCTAContainerView.swift:52-58 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/ProjectNavigationSelectorView.swift:49-55 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnSelectionContinueCTAView.swift:40-46 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/KSRSearchBar.swift:47-52 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeCTAContainerView.swift:101-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/DesignSystem/Views/DemoCTAContainerView.swift:48` calls `PledgeViewCTAContainerViewModel` and `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/ProjectNavigationSelectorView.swift:45` 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 (9 lines × 3) Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/ActivitySampleBackingCell.swift:24— Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/ActivitySampleBackingCell.swift:24-32 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/ActivitySampleFollowCell.swift:24-32 | Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/ActivitySampleProjectCell.swift:26-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 all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.swift:33— KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.swift:33-38 | KsApi/Sources/KsApi/models/ProjectStatsEnvelope.swift:266-271 | KsApi/Sources/KsApi/models/UpdatePledgeEnvelope.swift:33-38 — before extracting anything, compare `KsApi/Sources/KsApi/models/ChangePaymentMethodEnvelope.swift` and `KsApi/Sources/KsApi/models/UpdatePledgeEnvelope.swift` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 × 8) KsApi/Sources/KsApi/models/graphql/adapters/ClearUserUnseenActivityEnvelope+ClearUserUnseenActivityMutation.Data.swift:20— KsApi/Sources/KsApi/models/graphql/adapters/ClearUserUnseenActivityEnvelope+ClearUserUnseenActivityMutation.Data.swift:20-29 | KsApi/Sources/KsApi/models/graphql/adapters/CreateBackingEnvelope+CreateBackingMutation.Data.swift:14-23 | KsApi/Sources/KsApi/models/graphql/adapters/CreatePaymentSourceEnvelope+CreatePaymentSourceMutation.Data.swift:30-39 | KsApi/Sources/KsApi/models/graphql/adapters/DeletePaymentSourceEnvelope+DeletePaymentSourceMutation.Data.swift:26-35 | KsApi/Sources/KsApi/models/graphql/adapters/SignInWithAppleEnvelope+SignInWithAppleMutation.Data.swift:25-34 | KsApi/Sources/KsApi/models/graphql/adapters/UpdateBackingEnvelope+UpdateBackingMutation.Data.swift:20-29 | KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+UnwatchProjectMutation.Data.swift:25-34 | KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+WatchProjectMutation.Data.swift:25-34 — before extracting anything, compare `KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+UnwatchProjectMutation.Data.swift` and `KsApi/Sources/KsApi/models/graphql/adapters/WatchProjectResponseEnvelope+WatchProjectMutation.Data.swift` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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–8 lines × 2) Library/Sources/LibraryTestHelpers/Combos.swift:67— Library/Sources/LibraryTestHelpers/Combos.swift:67-74 | Library/Sources/LibraryTestHelpers/Combos.swift:90-96 — 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 `Library/Sources/LibraryTestHelpers/Combos.swift:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Orphaned file Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Datasource/Datasource/ProjectPageViewControllerDataSource.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 KsApi/Sources/KsApi/models/lenses/UserLenses.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel+Templates.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 KsApi/Sources/KsApi/models/Project.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 Library/Sources/Library/Library/ViewModels/UpdateDraftViewModel.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ProjectPamphletMainCell.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardsCollection/Views/RewardCardView.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryPostcardCell.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RewardAddOnSelection/Views/RewardAddOnCardView.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 Library/Sources/Library/Library/ViewModels/DiscoveryPostcardViewModel.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.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 Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeOverTime/Views/PledgePaymentPlanOptionView.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 Library/Sources/Library/Library/ViewModels/DiscoveryNavigationHeaderViewModel.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/SharedViews/PledgeCTAContainerView.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Controller/DiscoveryNavigationHeaderViewController.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 KsApi/Sources/KsApi/models/lenses/User.NotificationsLenses.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 Library/Sources/Library/Library/DataSource/ValueCellDataSource.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 KsApi/Sources/KsApi/models/User.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 Library/Sources/Library/Library/ViewModels/DiscoveryFiltersViewModel.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 Library/Sources/Library/UIAlertController.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 KsApi/Sources/KsApi/models/graphql/adapters/User+UserFragment.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 Library/Sources/Library/Library/ViewModels/WatchProjectViewModel.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardProjects/Views/Cells/BackerDashboardProjectCell.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/ProjectNavigationSelectorView.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.
No direct assertions: testCategoryView LibraryTests/Library/ViewModels/DiscoveryProjectCategoryViewModelTests.swift:21— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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: testSearchFieldFocus_OnBeginEditing LibraryTests/Library/ViewModels/KSRSearchBarViewModelTests.swift:21— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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: testSearchFieldFocus_OnEditingDidEnd LibraryTests/Library/ViewModels/KSRSearchBarViewModelTests.swift:26— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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: testSearchTextChanged LibraryTests/Library/ViewModels/KSRSearchBarViewModelTests.swift:31— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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: testClearSearchText LibraryTests/Library/ViewModels/KSRSearchBarViewModelTests.swift:36— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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: testCancelButtonPressed LibraryTests/Library/ViewModels/KSRSearchBarViewModelTests.swift:43— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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: testSearchTextEditingDidEnd_ResignsFirstResponder LibraryTests/Library/ViewModels/KSRSearchBarViewModelTests.swift:50— No conventional assertion call was detected, and 7 of 7 tests in `ViewModels` 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.
Duplicated predicate Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift:124— `!project.memberData.permissions.isEmpty && !isBacker` appears character-identically in 2 files — Library/Sources/Library/Library/ViewModels/CommentRepliesViewModel.swift, Library/Sources/Library/Library/ViewModels/CommentsViewModel.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 Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift:342— `$0.id == backing.rewardId || $0.id == backing.reward?.id` appears character-identically in 2 files — Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift, Library/Sources/Library/Library/ViewModels/RewardCardViewModel.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 Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Update/ViewModel/UpdateViewModel.swift:91— `action.navigationType == .other || action.targetFrame?.mainFrame == .some(false)` appears character-identically in 2 files — Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Update/ViewModel/UpdateViewModel.swift, Library/Sources/Library/Library/ViewModels/ProjectUpdatesViewModel.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 Library/Sources/Library/Library/ViewModels/DiscoveryPageViewModel.swift:348— `featureVideoFeedEnabled() && Reachability.current != .none` appears character-identically in 2 files — Library/Sources/Library/Library/ViewModels/DiscoveryPageViewModel.swift, Library/Sources/Library/Library/ViewModels/SearchViewModel.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 Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift:406— `reward.shipping.enabled == false || estimatedShipping == nil` appears character-identically in 2 files — Library/Sources/Library/Library/ViewModels/PledgeViewModel.swift, Library/Sources/Library/Library/ViewModels/PostCampaignCheckoutViewModel.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 Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift:132— `reward.shipping.enabled == false || text == nil` appears character-identically in 2 files — Library/Sources/Library/Library/ViewModels/RewardAddOnCardViewModel.swift, Library/Sources/Library/Library/ViewModels/RewardCardViewModel.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 24 significant file(s) lose their only recent owner: Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Controller/VideoFeedViewController.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareSheetView.swift, Library/Sources/Library/Library/ViewModels/VideoFeedViewModel.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Overlay/VideoFeedOverlayView.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Cell/VideoFeedCell.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/FloatingTabBar/FloatingTabBar.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/VideoPlayer/VideoFeedVideoPlayer.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/VideoFeed/Social Sharing/VideoFeedShareDestination.swift (+16 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: ServerDrivenUI/Sources/ServerDrivenUI/RichTextGQLConversions.swift, ServerDrivenUI/Sources/ServerDrivenUI/Blocks/OEmbedBlock.swift, ServerDrivenUI/Sources/ServerDrivenUI/RichTextElement.swift, ServerDrivenUI/Sources/ServerDrivenUI/Blocks/TextBlock.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/RichTextExample/RichTextExampleProjectsViewModel.swift, ServerDrivenUI/Sources/ServerDrivenUI/RichTextElement+Normalizing.swift, ServerDrivenUI/Sources/ServerDrivenUI/Blocks/AudioVideoBlock.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 7 significant file(s) lose their only recent owner: Library/Sources/Library/Library/ViewModels/RewardAddOnSelectionViewModel.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgeShippingLocation/PledgeShippingLocationViewController.swift, KsApi/Sources/KsApi/models/graphql/adapters/Project+FetchProjectRewardsByIdQueryData.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ShippingRules/ShippingLocationsView.swift, Experimentation/Sources/Experimentation/StatsigClient.swift, KsApi/Sources/KsApi/models/graphql/adapters/Project+FastFetchProjectQuery.swift, Library/Sources/Library/Library/OAuthError.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 6 significant file(s) lose their only recent owner: Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOViewModel.swift, Library/Sources/Library/Library/ViewModels/BackerDashboardViewModel.swift, Library/Sources/Library/Library/ViewModels/BackerDashboardProjectsViewModel.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardModel.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/ProjectPage/Views/Cells/ExternalSourceViewElementCell.swift, Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/PledgedProjectsOverview/PPOTierTypes.swift. Pair on, review, or document these before any departure.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Views/Cells/DiscoveryProjectCardCell.swift:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Library/Sources/Library/Library/ViewModels/CommentsViewModel.swift:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Library/Sources/Library/Library/Format.swift:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: ViewModels LibraryTests/Library/ViewModels/DiscoveryProjectCategoryViewModelTests.swift:21— No conventional assertion call was detected in 7 of 7 tests in `ViewModels` — 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.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 7 project(s) overshoot their size bounds, lowering Project Cohesion to 1.4/10. The most over is `Kickstarter-Framework` (44354 LoC, 636 module-visible types across 169 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
Concentrated knowledge decay — 293 of 492 significant files have no living knowledge, while the repository is still being changed at a low rate (49 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 293 separate risks. Counted over 492 of the 1124 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 1783/2409 types (74%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
No SAST — 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 9600 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Outdated: abseil-cpp-binary — `abseil-cpp-binary` is resolved at 1.2024072200.0, but 1.2025051202.0 is the newest release tagged on https://github.com/google/abseil-cpp-binary.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update abseil-cpp-binary` reaches this one with no change to Package.swift.
Outdated: alamofire — `alamofire` is resolved at 5.10.2, but 5.12.2 is the newest release tagged on https://github.com/Alamofire/Alamofire.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update alamofire` reaches this one with no change to Package.swift.
Outdated: alamofireimage — `alamofireimage` is resolved at 4.3.0, but 4.4.0 is the newest release tagged on https://github.com/Alamofire/AlamofireImage within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update alamofireimage` reaches this one with no change to Package.swift.
Outdated: analytics-swift — `analytics-swift` is resolved at 1.8.0, but 1.10.3 is the newest release tagged on https://github.com/segmentio/analytics-swift within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update analytics-swift` reaches this one with no change to Package.swift.
Outdated: apollo-ios — `apollo-ios` is resolved at 1.25.3, but 1.25.7 is the newest release tagged on https://github.com/apollographql/apollo-ios.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update apollo-ios` reaches this one with no change to Package.swift.
Outdated: apollo-ios — `apollo-ios` is resolved at 1.9.3, but 1.25.7 is the newest release tagged on https://github.com/apollographql/apollo-ios.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update apollo-ios` reaches this one with no change to Package.swift.
Outdated: app-check — `app-check` is resolved at 11.2.0, but 11.3.2 is the newest release tagged on https://github.com/google/app-check.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update app-check` reaches this one with no change to Package.swift.
Outdated: googledatatransport — `googledatatransport` is resolved at 10.1.0, but 10.1.1 is the newest release tagged on https://github.com/google/GoogleDataTransport.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update googledatatransport` reaches this one with no change to Package.swift.
Outdated: googleutilities — `googleutilities` is resolved at 8.1.0, but 8.1.5 is the newest release tagged on https://github.com/google/GoogleUtilities.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update googleutilities` reaches this one with no change to Package.swift.
Outdated: grpc-binary — `grpc-binary` is resolved at 1.69.1, but 1.83.1 is the newest release tagged on https://github.com/google/grpc-binary.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update grpc-binary` reaches this one with no change to Package.swift.
Outdated: gtm-session-fetcher — `gtm-session-fetcher` is resolved at 4.1.0, but 4.5.0 is the newest release tagged on https://github.com/google/gtm-session-fetcher.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update gtm-session-fetcher` reaches this one with no change to Package.swift.
Outdated: kingfisher — `kingfisher` is resolved at 8.6.2, but 8.14.0 is the newest release tagged on https://github.com/onevcat/Kingfisher within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update kingfisher` reaches this one with no change to Package.swift.
Outdated: kingfisher — `kingfisher` is resolved at 8.5.0, but 8.14.0 is the newest release tagged on https://github.com/onevcat/Kingfisher within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update kingfisher` reaches this one with no change to Package.swift.
Outdated: kingfisher — `kingfisher` is resolved at 8.8.1, but 8.14.0 is the newest release tagged on https://github.com/onevcat/Kingfisher within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update kingfisher` reaches this one with no change to Package.swift.
Outdated: kingfisherwebp — `kingfisherwebp` is resolved at 1.7.2, but 1.7.3 is the newest release tagged on https://github.com/yeatse/KingfisherWebP.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update kingfisherwebp` reaches this one with no change to Package.swift.
Outdated: kingfisherwebp — `kingfisherwebp` is resolved at 1.7.0, but 1.7.3 is the newest release tagged on https://github.com/yeatse/KingfisherWebP.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update kingfisherwebp` reaches this one with no change to Package.swift.
Outdated: leveldb — `leveldb` is resolved at 1.22.2, but 1.22.5 is the newest release tagged on https://github.com/firebase/leveldb.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update leveldb` reaches this one with no change to Package.swift.
Outdated: libwebp-xcode — `libwebp-xcode` is resolved at 1.3.2, but 1.6.0 is the newest release tagged on https://github.com/SDWebImage/libwebp-Xcode within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update libwebp-xcode` reaches this one with no change to Package.swift.
Outdated: lottie-ios — `lottie-ios` is resolved at 4.6.0, but 4.6.1 is the newest release tagged on https://github.com/airbnb/lottie-ios.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update lottie-ios` reaches this one with no change to Package.swift.
Outdated: lottie-ios — `lottie-ios` is resolved at 4.5.1, but 4.6.1 is the newest release tagged on https://github.com/airbnb/lottie-ios.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update lottie-ios` reaches this one with no change to Package.swift.
Outdated: nanopb — `nanopb` is resolved at 2.30910.0, but 2.30910.1 is the newest release tagged on https://github.com/firebase/nanopb.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update nanopb` reaches this one with no change to Package.swift.
Outdated: promises — `promises` is resolved at 2.4.0, but 2.4.1 is the newest release tagged on https://github.com/google/promises.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update promises` reaches this one with no change to Package.swift.
Outdated: reactiveswift — `reactiveswift` is resolved at 7.1.1, but 7.2.1 is the newest release tagged on https://github.com/ReactiveCocoa/ReactiveSwift within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update reactiveswift` reaches this one with no change to Package.swift.
Outdated: sdwebimage — `sdwebimage` is resolved at 5.21.2, but 5.21.7 is the newest release tagged on https://github.com/SDWebImage/SDWebImage.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sdwebimage` reaches this one with no change to Package.swift.
Outdated: sqlite.swift — `sqlite.swift` is resolved at 0.15.4, but 0.17.0 is the newest release tagged on https://github.com/stephencelis/SQLite.swift.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sqlite.swift` reaches this one with no change to Package.swift.
+ 12 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 50 file(s) — `Experimentation/Sources/Experimentation/Experiments/StatsigExperiment.swift`, `KDS/Sources/KDS/Controllers/ColorsView.swift`, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/BackerDashboardPages/Controller/BackerDashboardViewController.swift`, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Comments/Datasource/CommentRepliesDataSource.swift`, `Kickstarter-Framework/Sources/Kickstarter-Framework/Kickstarter-iOS/Features/Discovery/Datasource/DiscoveryProjectsDataSource.swift`, … (+45 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a177d3-bd24-7bd1-b75a-2262e045034b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 22 · Warnings: 502 · Recommendations: 322 · Info: 37 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 10:48 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.