Public report of googlesamples/mlkit, published 13 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 13 November 2026, 20:01 UTC · Survey ID cd_ef5b9bc5d5db48ec8d3d71125e8740b0
googlesamples/mlkit
Measured 13 November 2026, 20:00 UTC, at code version 8cb8b87
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 44,215 lines of product code in 49 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 17
Findings by how serious they are
2 critical302 serious87 minor
21 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 20:00 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
43of 43 dimensions measured by tools.
382of 391 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
43dimensions across 6 lenses, read from 44,215 lines of product code in 49 projects.
googlesamples/mlkit falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 45 out of 100 and is rated Weak, and neither of its two critical findings concerns security.
Production Readiness, at 17, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 66.
Two parts of the code are no longer understood by anyone working on it. Having someone learn the forgotten files would close this risk.
The product code is 44,215 lines, about €39,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 17 to 70, the lowest score rated Strong, the score would rise from 45 to about 66.
Code composition: what the lines of code are
Product code 100%Tests 0%
New since the last survey: 117 findings
These 117 critical or serious findings weren't in the previous survey, on 24 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · MethodTooLong: AgentScreenKt.AgentScreen android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt
God Classes · FileTooLong: kotlin/AgentScreen.kt android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt
God Classes · MethodTooLong: AgentScreenKt.AgentTimelineCard android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt
God Classes · MethodTooLong: AgentViewModel.sendPrompt android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/viewmodel/AgentViewModel.kt
God Classes · MethodTooLong: AgentScreenKt.AgentConfigDialog android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt
God Classes · TooManyMethods: GenerationConfigUtils android/genai/app/src/main/java/com/google/mlkit/genai/demo/GenerationConfigUtils.kt
God Classes · TooManyMethods: OpenPromptActivity android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt
God Classes · ClassTooLong: AgentViewModel android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/viewmodel/AgentViewModel.kt
Code Duplication · Edited copy of a member (153 corresponding lines) ios/quickstarts/vision/VisionExample/CameraViewController.swift
Code Duplication · Edited copy of a member (57 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt
Code Duplication · Edited copy of a member (55 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt
Code Duplication · Edited copy of a member (48 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java
Code Duplication · Edited copy of a member (46 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt
Code Duplication · Edited copy of a member (53 corresponding lines) ios/quickstarts/vision/VisionExample/CameraViewController.swift
Code Duplication · Edited copy of a member (34 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java
Code Duplication · Edited copy of a member (50 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java
Code Duplication · Edited copy of a member (46 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java
Code Duplication · Edited copy of a member (31 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt
Code Duplication · Edited copy of a member (41 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt
Code Duplication · Edited copy of a member (34 corresponding lines) ios/quickstarts/automl/AutoMLExample/ViewController.swift
Code Duplication · Edited copy of a member (33 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java
Code Duplication · Edited copy of a member (35 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt
Code Duplication · Edited copy of a member (50 corresponding lines) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt
Code Duplication · Edited copy of a member (25 corresponding lines) ios/quickstarts/automl/AutoMLExample/ViewController.swift
Code Duplication · Edited copy of a member (24 corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift
Code Duplication · Edited copy of a member (23 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java
Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java
Code Duplication · Edited copy of a member (25 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java
Code Duplication · Edited copy of a member (26 corresponding lines) android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java
Code Duplication · Edited copy of a member (16 corresponding lines) ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift
Code Duplication · Edited copy of a member (32 corresponding lines) android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java
Code Duplication · Edited copy of a member (19 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java
Code Duplication · Edited copy of a member (27 corresponding lines) android/documentscanner/app/src/main/java/com/google/mlkit/samples/documentscanner/kotlin/MainActivity.kt
Code Duplication · Edited copy of a member (24 corresponding lines) android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift
Code Duplication · Edited copy of a member (20 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/barcodescanner/BarcodeGraphic.kt
Code Duplication · Edited copy of a member (26 corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift
Code Duplication · Edited copy of a member (31 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java
Code Duplication · Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java
Code Duplication · Edited copy of a member (24 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java
Code Duplication · Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java
Code Duplication · Edited copy of a member (20 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java
Code Duplication · Edited copy of a member (26 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt
Code Duplication · Edited copy of a member (23 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java
Code Duplication · Edited copy of a member (16 corresponding lines) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift
Code Duplication · Edited copy of a member (26 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt
Code Duplication · Edited copy of a member (27 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java
Code Duplication · Edited copies of one member (4 members, 26+ corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift
Code Duplication · Edited copy of a member (24 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java
Code Duplication · Edited copy of a member (22 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java
Code Duplication · Edited copy of a member (18 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/InferenceInfoGraphic.java
Code Duplication · Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java
Code Duplication · Edited copy of a member (12 corresponding lines) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java
Code Duplication · Edited copy of a member (19 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java
Code Duplication · Edited copy of a member (18 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt
Code Duplication · Edited copy of a member (18 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java
Code Duplication · Edited copy of a member (16 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt
Code Duplication · Edited copy of a member (15 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt
Code Duplication · Edited copy of a member (13 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java
Code Duplication · Edited copy of a member (13 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/segmenter/SegmentationGraphic.java
Code Duplication · Edited copy of a member (12 corresponding lines) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/kotlin/chat/ChatFragment.kt
Code Duplication · Edited copy of a member (15 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt
Code Duplication · Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java
Code Duplication · Edited copy of a member (13 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt
Code Duplication · Edited copy of a member (13 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt
Code Duplication · Edited copy of a member (8 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift
Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift
Code Duplication · Edited copy of a member (11 corresponding lines) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechTranslationActivity.kt
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java
Code Duplication · Edited copy of a member (11 corresponding lines) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/MainActivityJava.java
Code Duplication · Edited copy of a member (13 corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift
Code Duplication · Edited copy of a member (4 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java
Code Duplication · Edited copy of a member (5 corresponding lines) android/internal/chooserx/src/main/java/com/mlkit/example/internal/ChoiceAdapter.java
Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) ios/quickstarts/entityextraction/EntityExtractionExample/EntityViewController.swift
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 25 findings
These 25 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one.
€13,000 to €65,000, for 217 to 688 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 44,215 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Raises the score by about 9 points · Low effort · ADR Quality
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 7 points · Medium effort · CI/CD gates
3
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 7 points · Medium effort · Observability
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 €39,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 17 (Critical). 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 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 7,093 lines over the last 90 days, which is about 28,766 lines a year. At that pace, the extra work comes to an estimated 1.5 to 9.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
46 modules, with 38 dependencies between them. 3 loops run through 12 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 6 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
google.mlkit.md.MainActivity.ModeItemAdapter uses google.mlkit.md.MainActivity, so a change to google.mlkit.md.MainActivity can break google.mlkit.md.MainActivity.ModeItemAdapter, while a change to google.mlkit.md.MainActivity.ModeItemAdapter can't break google.mlkit.md.MainActivity.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→39 google.mlkit.md.barcodedetection.BarcodeFieldAdapter uses google.mlkit.md.barcodedetectionpart of a loop✕
Connections
1 pair of types, where a type in google.mlkit.md.barcodedetection.BarcodeFieldAdapter uses a type in google.mlkit.md.barcodedetection.
google.mlkit.md.barcodedetection.BarcodeFieldAdapter uses google.mlkit.md.barcodedetection, so a change to google.mlkit.md.barcodedetection can break google.mlkit.md.barcodedetection.BarcodeFieldAdapter, while a change to google.mlkit.md.barcodedetection.BarcodeFieldAdapter can't break google.mlkit.md.barcodedetection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→36 google.mlkit.md.camera.CameraSource uses google.mlkit.md.camerapart of a loop✕
Connections
1 pair of types, where a type in google.mlkit.md.camera.CameraSource uses a type in google.mlkit.md.camera.
google.mlkit.md.camera.CameraSource uses google.mlkit.md.camera, so a change to google.mlkit.md.camera can break google.mlkit.md.camera.CameraSource, while a change to google.mlkit.md.camera.CameraSource can't break google.mlkit.md.camera.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→36 google.mlkit.md.camera.GraphicOverlay uses google.mlkit.md.camerapart of a loop✕
Connections
1 pair of types, where a type in google.mlkit.md.camera.GraphicOverlay uses a type in google.mlkit.md.camera.
google.mlkit.md.camera.GraphicOverlay uses google.mlkit.md.camera, so a change to google.mlkit.md.camera can break google.mlkit.md.camera.GraphicOverlay, while a change to google.mlkit.md.camera.GraphicOverlay can't break google.mlkit.md.camera.
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.
google.mlkit.md.camera.WorkflowModel.WorkflowState uses google.mlkit.md.camera.WorkflowModel, so a change to google.mlkit.md.camera.WorkflowModel can break google.mlkit.md.camera.WorkflowModel.WorkflowState, while a change to google.mlkit.md.camera.WorkflowModel.WorkflowState can't break google.mlkit.md.camera.WorkflowModel.
Position
Below the diagonal: google.mlkit.md.camera.WorkflowModel.WorkflowState uses a module listed above it, which is the healthy direction.
24→34 google.mlkit.md.productsearch.PreviewCardAdapter uses google.mlkit.md.productsearchpart of a loop✕
Connections
1 pair of types, where a type in google.mlkit.md.productsearch.PreviewCardAdapter uses a type in google.mlkit.md.productsearch.
google.mlkit.md.productsearch.PreviewCardAdapter uses google.mlkit.md.productsearch, so a change to google.mlkit.md.productsearch can break google.mlkit.md.productsearch.PreviewCardAdapter, while a change to google.mlkit.md.productsearch.PreviewCardAdapter can't break google.mlkit.md.productsearch.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→34 google.mlkit.md.productsearch.ProductAdapter uses google.mlkit.md.productsearchpart of a loop✕
Connections
1 pair of types, where a type in google.mlkit.md.productsearch.ProductAdapter uses a type in google.mlkit.md.productsearch.
google.mlkit.md.productsearch.ProductAdapter uses google.mlkit.md.productsearch, so a change to google.mlkit.md.productsearch can break google.mlkit.md.productsearch.ProductAdapter, while a change to google.mlkit.md.productsearch.ProductAdapter can't break google.mlkit.md.productsearch.
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.
google.mlkit.showcase.translate.main uses google.mlkit.showcase.translate.util, so a change to google.mlkit.showcase.translate.util can break google.mlkit.showcase.translate.main, while a change to google.mlkit.showcase.translate.main can't break google.mlkit.showcase.translate.util.
Position
Below the diagonal: google.mlkit.showcase.translate.main uses a module listed above it, which is the healthy direction.
mlkit.lint uses mlkit.lint.HungarianNotationDetector, so a change to mlkit.lint.HungarianNotationDetector can break mlkit.lint, while a change to mlkit.lint can't break mlkit.lint.HungarianNotationDetector.
Position
Below the diagonal: mlkit.lint uses a module listed above it, which is the healthy direction.
mlkit.lint uses mlkit.lint.InvalidImportDetector, so a change to mlkit.lint.InvalidImportDetector can break mlkit.lint, while a change to mlkit.lint can't break mlkit.lint.InvalidImportDetector.
Position
Below the diagonal: mlkit.lint uses a module listed above it, which is the healthy direction.
google.mlkit.md.MainActivity uses google.mlkit.md.MainActivity.ModeItemAdapter, so a change to google.mlkit.md.MainActivity.ModeItemAdapter can break google.mlkit.md.MainActivity, while a change to google.mlkit.md.MainActivity can't break google.mlkit.md.MainActivity.ModeItemAdapter.
Position
Below the diagonal: google.mlkit.md.MainActivity uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in google.mlkit.md.barcodedetection.BarcodeFieldAdapter.BarcodeFieldViewHolder uses a type in google.mlkit.md.barcodedetection.BarcodeFieldAdapter.
google.mlkit.md.barcodedetection.BarcodeFieldAdapter.BarcodeFieldViewHolder uses google.mlkit.md.barcodedetection.BarcodeFieldAdapter, so a change to google.mlkit.md.barcodedetection.BarcodeFieldAdapter can break google.mlkit.md.barcodedetection.BarcodeFieldAdapter.BarcodeFieldViewHolder, while a change to google.mlkit.md.barcodedetection.BarcodeFieldAdapter.BarcodeFieldViewHolder can't break google.mlkit.md.barcodedetection.BarcodeFieldAdapter.
Position
Below the diagonal: google.mlkit.md.barcodedetection.BarcodeFieldAdapter.BarcodeFieldViewHolder uses a module listed above it, which is the healthy direction.
google.mlkit.md.objectdetection uses google.mlkit.md.camera.GraphicOverlay, so a change to google.mlkit.md.camera.GraphicOverlay can break google.mlkit.md.objectdetection, while a change to google.mlkit.md.objectdetection can't break google.mlkit.md.camera.GraphicOverlay.
Position
Below the diagonal: google.mlkit.md.objectdetection uses a module listed above it, which is the healthy direction.
30→36 google.mlkit.md.objectdetection uses google.mlkit.md.camerapart of a loop✕
Connections
16 pairs of types, where a type in google.mlkit.md.objectdetection uses a type in google.mlkit.md.camera.
google.mlkit.md.objectdetection uses google.mlkit.md.camera, so a change to google.mlkit.md.camera can break google.mlkit.md.objectdetection, while a change to google.mlkit.md.objectdetection can't break google.mlkit.md.camera.
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.
30→37 google.mlkit.md.objectdetection uses google.mlkit.mdpart of a loop✕
Connections
3 pairs of types, where a type in google.mlkit.md.objectdetection uses a type in google.mlkit.md.
google.mlkit.md.objectdetection uses google.mlkit.md, so a change to google.mlkit.md can break google.mlkit.md.objectdetection, while a change to google.mlkit.md.objectdetection can't break google.mlkit.md.
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 google.mlkit.md.productsearch.ProductAdapter.ProductViewHolder uses a type in google.mlkit.md.productsearch.ProductAdapter.
google.mlkit.md.productsearch.ProductAdapter.ProductViewHolder uses google.mlkit.md.productsearch.ProductAdapter, so a change to google.mlkit.md.productsearch.ProductAdapter can break google.mlkit.md.productsearch.ProductAdapter.ProductViewHolder, while a change to google.mlkit.md.productsearch.ProductAdapter.ProductViewHolder can't break google.mlkit.md.productsearch.ProductAdapter.
Position
Below the diagonal: google.mlkit.md.productsearch.ProductAdapter.ProductViewHolder uses a module listed above it, which is the healthy direction.
google.mlkit.showcase.translate.main.MainFragment uses google.mlkit.showcase.translate.main, so a change to google.mlkit.showcase.translate.main can break google.mlkit.showcase.translate.main.MainFragment, while a change to google.mlkit.showcase.translate.main.MainFragment can't break google.mlkit.showcase.translate.main.
Position
Below the diagonal: google.mlkit.showcase.translate.main.MainFragment uses a module listed above it, which is the healthy direction.
google.mlkit.md.MainActivity.DetectionMode uses google.mlkit.md.MainActivity, so a change to google.mlkit.md.MainActivity can break google.mlkit.md.MainActivity.DetectionMode, while a change to google.mlkit.md.MainActivity.DetectionMode can't break google.mlkit.md.MainActivity.
Position
Below the diagonal: google.mlkit.md.MainActivity.DetectionMode uses a module listed above it, which is the healthy direction.
google.mlkit.md.productsearch uses google.mlkit.md.productsearch.PreviewCardAdapter, so a change to google.mlkit.md.productsearch.PreviewCardAdapter can break google.mlkit.md.productsearch, while a change to google.mlkit.md.productsearch can't break google.mlkit.md.productsearch.PreviewCardAdapter.
Position
Below the diagonal: google.mlkit.md.productsearch uses a module listed above it, which is the healthy direction.
google.mlkit.md.productsearch uses google.mlkit.md.productsearch.ProductAdapter, so a change to google.mlkit.md.productsearch.ProductAdapter can break google.mlkit.md.productsearch, while a change to google.mlkit.md.productsearch can't break google.mlkit.md.productsearch.ProductAdapter.
Position
Below the diagonal: google.mlkit.md.productsearch uses a module listed above it, which is the healthy direction.
google.mlkit.md.productsearch uses google.mlkit.md.objectdetection, so a change to google.mlkit.md.objectdetection can break google.mlkit.md.productsearch, while a change to google.mlkit.md.productsearch can't break google.mlkit.md.objectdetection.
Position
Below the diagonal: google.mlkit.md.productsearch uses a module listed above it, which is the healthy direction.
google.mlkit.md.productsearch.SearchEngine uses google.mlkit.md.objectdetection, so a change to google.mlkit.md.objectdetection can break google.mlkit.md.productsearch.SearchEngine, while a change to google.mlkit.md.productsearch.SearchEngine can't break google.mlkit.md.objectdetection.
Position
Below the diagonal: google.mlkit.md.productsearch.SearchEngine uses a module listed above it, which is the healthy direction.
google.mlkit.md.camera uses google.mlkit.md.camera.WorkflowModel, so a change to google.mlkit.md.camera.WorkflowModel can break google.mlkit.md.camera, while a change to google.mlkit.md.camera can't break google.mlkit.md.camera.WorkflowModel.
Position
Below the diagonal: google.mlkit.md.camera uses a module listed above it, which is the healthy direction.
google.mlkit.md.camera uses google.mlkit.md.camera.CameraSource, so a change to google.mlkit.md.camera.CameraSource can break google.mlkit.md.camera, while a change to google.mlkit.md.camera can't break google.mlkit.md.camera.CameraSource.
Position
Below the diagonal: google.mlkit.md.camera uses a module listed above it, which is the healthy direction.
google.mlkit.md.camera uses google.mlkit.md.camera.GraphicOverlay, so a change to google.mlkit.md.camera.GraphicOverlay can break google.mlkit.md.camera, while a change to google.mlkit.md.camera can't break google.mlkit.md.camera.GraphicOverlay.
Position
Below the diagonal: google.mlkit.md.camera uses a module listed above it, which is the healthy direction.
google.mlkit.md.camera uses google.mlkit.md.objectdetection, so a change to google.mlkit.md.objectdetection can break google.mlkit.md.camera, while a change to google.mlkit.md.camera can't break google.mlkit.md.objectdetection.
Position
Below the diagonal: google.mlkit.md.camera uses a module listed above it, which is the healthy direction.
google.mlkit.md.camera uses google.mlkit.md.productsearch, so a change to google.mlkit.md.productsearch can break google.mlkit.md.camera, while a change to google.mlkit.md.camera can't break google.mlkit.md.productsearch.
Position
Below the diagonal: google.mlkit.md.camera uses a module listed above it, which is the healthy direction.
36→37 google.mlkit.md.camera uses google.mlkit.mdpart of a loop✕
Connections
2 pairs of types, where a type in google.mlkit.md.camera uses a type in google.mlkit.md.
google.mlkit.md.camera uses google.mlkit.md, so a change to google.mlkit.md can break google.mlkit.md.camera, while a change to google.mlkit.md.camera can't break google.mlkit.md.
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.
google.mlkit.md uses google.mlkit.md.camera.WorkflowModel, so a change to google.mlkit.md.camera.WorkflowModel can break google.mlkit.md, while a change to google.mlkit.md can't break google.mlkit.md.camera.WorkflowModel.
Position
Below the diagonal: google.mlkit.md uses a module listed above it, which is the healthy direction.
google.mlkit.md uses google.mlkit.md.objectdetection, so a change to google.mlkit.md.objectdetection can break google.mlkit.md, while a change to google.mlkit.md can't break google.mlkit.md.objectdetection.
Position
Below the diagonal: google.mlkit.md uses a module listed above it, which is the healthy direction.
google.mlkit.md uses google.mlkit.md.productsearch, so a change to google.mlkit.md.productsearch can break google.mlkit.md, while a change to google.mlkit.md can't break google.mlkit.md.productsearch.
Position
Below the diagonal: google.mlkit.md uses a module listed above it, which is the healthy direction.
google.mlkit.md uses google.mlkit.md.camera, so a change to google.mlkit.md.camera can break google.mlkit.md, while a change to google.mlkit.md can't break google.mlkit.md.camera.
Position
Below the diagonal: google.mlkit.md uses a module listed above it, which is the healthy direction.
google.mlkit.md.settings uses google.mlkit.md.camera, so a change to google.mlkit.md.camera can break google.mlkit.md.settings, while a change to google.mlkit.md.settings can't break google.mlkit.md.camera.
Position
Below the diagonal: google.mlkit.md.settings uses a module listed above it, which is the healthy direction.
google.mlkit.md.barcodedetection uses google.mlkit.md.barcodedetection.BarcodeFieldAdapter, so a change to google.mlkit.md.barcodedetection.BarcodeFieldAdapter can break google.mlkit.md.barcodedetection, while a change to google.mlkit.md.barcodedetection can't break google.mlkit.md.barcodedetection.BarcodeFieldAdapter.
Position
Below the diagonal: google.mlkit.md.barcodedetection uses a module listed above it, which is the healthy direction.
google.mlkit.md.barcodedetection uses google.mlkit.md.camera.GraphicOverlay, so a change to google.mlkit.md.camera.GraphicOverlay can break google.mlkit.md.barcodedetection, while a change to google.mlkit.md.barcodedetection can't break google.mlkit.md.camera.GraphicOverlay.
Position
Below the diagonal: google.mlkit.md.barcodedetection uses a module listed above it, which is the healthy direction.
google.mlkit.md.barcodedetection uses google.mlkit.md.camera, so a change to google.mlkit.md.camera can break google.mlkit.md.barcodedetection, while a change to google.mlkit.md.barcodedetection can't break google.mlkit.md.camera.
Position
Below the diagonal: google.mlkit.md.barcodedetection uses a module listed above it, which is the healthy direction.
google.mlkit.md.barcodedetection uses google.mlkit.md, so a change to google.mlkit.md can break google.mlkit.md.barcodedetection, while a change to google.mlkit.md.barcodedetection can't break google.mlkit.md.
Position
Below the diagonal: google.mlkit.md.barcodedetection uses a module listed above it, which is the healthy direction.
google.mlkit.md.barcodedetection.BarcodeResultFragment uses google.mlkit.md.barcodedetection, so a change to google.mlkit.md.barcodedetection can break google.mlkit.md.barcodedetection.BarcodeResultFragment, while a change to google.mlkit.md.barcodedetection.BarcodeResultFragment can't break google.mlkit.md.barcodedetection.
Position
Below the diagonal: google.mlkit.md.barcodedetection.BarcodeResultFragment uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 78% · Adequate · gated by D4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
11
Medium
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj; Add a CI workflow that builds and runs the test suite on every push/PR; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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.
Code Duplication: Edited copy of a member (15 corresponding lines)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 2
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 — 302
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 — 87
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 21
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 43 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, 382 of 391 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 164 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .m (10,415 lines, 19% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.swift, .kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift, .kt) and this repository declares a JVM test suite (android/internal/lint, Gradle), 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.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 31 Maven/Gradle manifest(s) were read, stating a version for 165 dependency(ies) and leaving 11 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (android/internal/lintchecks/build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D26 Project Cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Project size and spread are measured over build units whose source a code model reads. This repository's .m source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `ios/quickstarts/translate/TranslateExample/ViewController.swift` 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (android/android-snippets/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: tools.build:apkzlib:7.2.1
> Could not resolve com.google.code.findbugs:jsr305:3.0.2.
> Could not get resource 'https://jcenter.bintray.com/com/google/code/findbugs/jsr305/3.0.2/jsr305-3…; runtime evidence skipped (launch chosen because android/android-snippets/app/build.gradle applies the Android application plugin and android/android-snippets/gradlew builds it).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin, Swift, c, objectivec is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X25 Inert configuration knob — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X26 Unsynchronised callback handoff — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X28 Index access outside its own emptiness guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X30 Support guard that admits what it rejects — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BaseActivity.runInference at 29. A further 4 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 DetectorPickerRow.description at 21 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java (LivePreviewActivity.createCameraSource at 20), android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt (LivePreviewActivity.createCameraSource at 20), android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt (StillImageActivity.createImageProcessor at 20). 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.
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BaseActivity.runInference (cyclomatic 29), CameraXLivePreviewActivity.bindAnalysisUseCase (cyclomatic 27), CameraXLivePreviewActivity.bindAnalysisUseCase (cyclomatic 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cyclomatic Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 16 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with BaseActivity.runInference (cognitive 65), CameraViewController.addContours (cognitive 39), ViewController.addContours (cognitive 39). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.8 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.4 / 10Stronggated by 13 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 7 MethodTooLong finding(s) in God Classes — start with AgentScreen.kt (3), BaseActivity.kt (2), AgentViewModel.kt. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 ClassTooLong finding(s) in God Classes — start with OpenPromptActivity.kt, AgentViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 FileTooLong finding(s) in God Classes — start with OpenPromptActivity.kt, AgentScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication3.5 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
164 duplicated block group(s) detected. 16.3 % of the production lines (7,222 of 44,215) are in a reported copy. A further 70 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .m (19% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 97 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with CameraViewController.swift (4), CameraSource.java (2), SpeechRecognitionActivity.kt. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with CameraViewController.swift (2), ImageDescriptionActivity.kt, SegmentationGraphic.kt. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with GraphicOverlay.java (2), ViewController.swift (2), FaceGraphic.kt. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
49 production modules (Gradle+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; a workspace's implicit (product-name) dependency is not visible there; 0 module(s) off the main sequence, with abstractness counted on 25 of the 49 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What 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.
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.
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 19 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 31 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 11 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 109 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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.
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt. Counted over 145 of the 340 production source files in this repository: 127 are under the ~2,400-byte size floor this dimension measures over, and the remaining 68 have no attributable history left to measure.
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.
3 deducted task-comment markers across 44215 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 3 TodoComment finding(s) in Explicit Debt — start with CameraSource.java, MLKitVisionImage.java, MLKitVisionImage.kt. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundios/showcase/vision-showcase/ShowcaseApp.xcodeproj/project.pbxproj:1
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 25 build units (Gradle, Xcode) flagged as possibly oversized/incoherent. This repository's .m source was read by no build unit, so this covers part of the tree, not all of it.
Projects may be oversized for their cohesion
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
11 finding(s): 0 critical, 0 high, 11 medium, 0 low. semgrep hit a parse error in 10 file(s) — `android/android-snippets/gradlew` (lines 160–161, line 162, line 163, …), `android/automl/gradlew` (lines 144–145, line 146, line 147, …), `android/codescanner/gradlew` (line 177), `android/digitalink/gradlew` (lines 144–145, line 146, line 147, …), `android/documentscanner/gradlew` (line 72, line 177), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
What to do
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d29_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.
68 of 213 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ios/quickstarts/vision/VisionExample/ViewController.swift. Counted over 213 of the 340 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 66 Orphaned file finding(s) in Knowledge Freshness — start with ViewController.swift (3), UIUtilities.swift (2), LiveObjectDetectionActivity.kt. — One of this dimension's main actionable groups (66 recommendation-level).
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with ViewController.swift, CameraSource.kt. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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 14 platform declaration(s) and 166 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.
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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 41 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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 repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
tutorials/README.md links to `CONTRIBUTING.md`, but `tutorials/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tutorials/README.md:8
What to do
Reconcile the README with reality: tutorials/README.md links to `CONTRIBUTING.md`, but `tutorials/CONTRIBUTING.md` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
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: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. 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 spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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 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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
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?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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 (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:74, android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:92
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — android/material-showcase/app/src/main/java/com/google/mlkit/md/settings/PreferenceUtils.kt:100, android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/EmbeddingScreen.kt:351
`catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:998
`catch (RuntimeException)` 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. (×2) — android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:66, android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:84
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~7.4 `!!` not-null assertions per 1k Kotlin product lines — 186 across the 25033 line(s) of the 151 Kotlin file(s) read (generated, test and sample code not counted). Densest: android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXSourceDemoActivity.kt (24), android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt (19), android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt (15). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Replace `!!` rather than adding to it: each is a run-time null check the compiler could not prove. Narrow the value with a null check, an early return or `?: return`, use `?.` / `?:` where absence is legitimate, `requireNotNull(x) { "why" }` / `checkNotNull` where a missing value is a contract breach worth a message, make the property non-nullable and set it in the constructor (or `by lazy`) instead of `lateinit` plus `!!`, or change the API so the null cannot arrive.
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 — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No 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 — AX6 reached only 27% of this repository's production lines — kotlin (22,488 lines), objectivec (9,161 lines), swift (7,156 lines), c (1,254 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: tools.build:apkzlib:7.2.1
> Could not resolve com.google.code.findbugs:jsr305:3.0.2.
> Could not get resource 'https://jcenter.bintray.com/com/google/code/findbugs/jsr305/3.0.2/jsr305-3…; runtime evidence skipped (launch chosen because android/android-snippets/app/build.gradle applies the Android application plugin and android/android-snippets/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
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.
D10 Test Quality — ~82 lines of test source are present (.swift, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
D12 Dependency Hygiene — Not scored — 31 Maven/Gradle manifest(s) were read, stating a version for 165 dependency(ies) and leaving 11 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 31 folder(s) declared by build.gradle were not judged for an overview, an example or the map.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, .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 reads resolved call sites in the languages it reads only — this repository's production source is .java, .m, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (53 value object(s))
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
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — X1 reached only 41% of this repository's production lines — java (14,571 lines), objectivec (9,161 lines), swift (7,156 lines), c (1,254 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 41% of this repository's production lines — java (14,571 lines), objectivec (9,161 lines), swift (7,156 lines), c (1,254 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Orphaned knowledge ios/quickstarts/vision/VisionExample/ViewController.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge android/material-showcase/app/src/main/java/com/google/mlkit/md/camera/CameraSource.kt:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Duplicated block (10 lines × 2) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt:211— android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt:211-220 | android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechTranslationActivity.kt:145-154 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/TextToSpeechActivity.kt:268— android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/TextToSpeechActivity.kt:268-277 | android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/TextToSpeechActivity.kt:421-430 — 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 `android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/TextToSpeechActivity.kt:268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:273— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:273-282 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:302-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 `android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:97— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:97-106 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:131-140 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:248— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:248-257 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:319-328 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:79— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:79-88 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectDetectorProcessor.java:77-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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:79` 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 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:74— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:74-83 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:82-91 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `R` names `com.google.mlkit.vision.automl.demo.R` in one and `com.google.mlkit.vision.demo.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:135— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:135-144 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:128-137 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:347— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:347-356 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:376-385 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:42— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:42-51 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java:42-51 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:449— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:449-458 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:627-636 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) ios/quickstarts/vision/VisionExample/CameraViewController.swift:725— ios/quickstarts/vision/VisionExample/CameraViewController.swift:725-734 | ios/showcase/translate-showcase/TranslateDemo/CameraViewController.swift:379-388 — 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) ios/quickstarts/vision/VisionExample/CameraViewController.swift:798— ios/quickstarts/vision/VisionExample/CameraViewController.swift:798-807 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:809-818 — 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 `ios/quickstarts/vision/VisionExample/CameraViewController.swift:798` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) ios/quickstarts/vision/VisionExample/ViewController.swift:563— ios/quickstarts/vision/VisionExample/ViewController.swift:563-572 | ios/quickstarts/vision/VisionExample/ViewController.swift:763-773 — 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 (10 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:204— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:204-213 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:527-536 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ios/quickstarts/vision/VisionExample/CameraViewController.swift:537` calls `rotate` and `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:214` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ImageDescriptionActivity.kt:100— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ImageDescriptionActivity.kt:100-108 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/SummarizationActivity.kt:87-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ImageDescriptionActivity.kt:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt:42— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt:42-50 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/subjectsegmenter/SubjectSegmentationGraphic.kt:54-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt:52` calls `rewind` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/subjectsegmenter/SubjectSegmentationGraphic.kt:64` 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 × 2) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/kotlin/MainActivityKotlin.kt:27— android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/kotlin/MainActivityKotlin.kt:27-37 | android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/MainActivity.kt:26-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) android/android-snippets/app/src/main/java/com/google/example/mlkit/ObjectDetectionActivity.java:94— android/android-snippets/app/src/main/java/com/google/example/mlkit/ObjectDetectionActivity.java:94-102 | android/android-snippets/app/src/main/java/com/google/example/mlkit/ObjectDetectionActivity.java:151-159 — 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 `android/android-snippets/app/src/main/java/com/google/example/mlkit/ObjectDetectionActivity.java: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.
Duplicated block (9 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:581— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:581-589 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:607-615 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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 (9 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:105— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:105-113 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:151-159 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 96 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 (9 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:121— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:121-129 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/VisionProcessorBase.java:157-165 — 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 after the matched lines, `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/VisionProcessorBase.java:169` calls `elapsedRealtime` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:135` 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 × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:460— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:460-468 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:638-646 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 (9 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:62— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:62-70 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:87-95 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 (11 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/facedetector/FaceGraphic.kt:178— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/facedetector/FaceGraphic.kt:178-188 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/facedetector/FaceGraphic.kt:206-216 — 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 `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/facedetector/FaceGraphic.kt:178` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:73— android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:73-83 | android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:133-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:77— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:77-87 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:74-84 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:167— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:167-178 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:213-223 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:167` 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) android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/java/TranslateFragment.java:137— android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/java/TranslateFragment.java:137-147 | android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/java/TranslateFragment.java:150-160 — 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 `android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/java/TranslateFragment.java:137` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:179— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:179-189 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java:251-261 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (11 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:230— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:230-240 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java:302-312 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (11 lines × 2) ios/quickstarts/automl/AutoMLExample/ViewController.swift:230— ios/quickstarts/automl/AutoMLExample/ViewController.swift:230-240 | ios/quickstarts/vision/VisionExample/ViewController.swift:237-247 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `ios/quickstarts/automl/AutoMLExample/ViewController.swift:230` 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) ios/quickstarts/automl/AutoMLExample/ViewController.swift:158— ios/quickstarts/automl/AutoMLExample/ViewController.swift:158-168 | ios/quickstarts/vision/VisionExample/ViewController.swift:181-191 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:177— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:177-189 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:177-189 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:164— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:164-176 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/ChooserActivity.java:115-127 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/ChooserActivity.java` 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. 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:172— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:172-184 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:309-321 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 96 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:172` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:225— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:225-237 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:296-308 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:342— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:342-354 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:331-343 — 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:342` 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) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:29— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:29-41 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:28-40 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift` and `ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:29` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) ios/quickstarts/vision/VisionExample/CameraViewController.swift:162— ios/quickstarts/vision/VisionExample/CameraViewController.swift:162-174 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:383-395 — 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 `ios/quickstarts/vision/VisionExample/CameraViewController.swift:162` 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) ios/quickstarts/vision/VisionExample/CameraViewController.swift:711— ios/quickstarts/vision/VisionExample/CameraViewController.swift:711-723 | ios/showcase/translate-showcase/TranslateDemo/CameraViewController.swift:365-377 — 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.
MethodTooLong: AgentScreenKt.AgentScreen android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:129— MethodTooLong — AgentScreen runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: AgentScreenKt.AgentTimelineCard android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:495— MethodTooLong — AgentTimelineCard 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: AgentViewModel.sendPrompt android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/viewmodel/AgentViewModel.kt:338— MethodTooLong — sendPrompt 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: AgentScreenKt.AgentConfigDialog android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:803— MethodTooLong — AgentConfigDialog runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: BaseActivity.downloadFeature android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/BaseActivity.kt:277— MethodTooLong — downloadFeature runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BaseActivity.runInference android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/BaseActivity.kt:279— MethodTooLong — runInference runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TranslateFragment.onViewCreated android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/java/TranslateFragment.java:68— MethodTooLong — onViewCreated runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (17 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/posedetector/PoseDetectorProcessor.kt:65— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/posedetector/PoseDetectorProcessor.kt:65-81 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/posedetector/PoseDetectorProcessor.kt:84-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:205— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:205-221 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:195-211 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:205` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:551— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:551-567 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:577-593 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:101— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:101-117 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:71-87 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:222— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:222-238 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:272-288 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 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. Note first that the copies are not typed on the same thing: `PreferenceUtils` names `com.google.mlkit.vision.automl.demo.preference.PreferenceUtils` in one and `com.google.mlkit.vision.demo.preference.PreferenceUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:114— android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:114-130 | android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:156-172 — 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 `android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) ios/quickstarts/automl/AutoMLExample/ViewController.swift:211— ios/quickstarts/automl/AutoMLExample/ViewController.swift:211-227 | ios/quickstarts/vision/VisionExample/ViewController.swift:218-234 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:878— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:878-893 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:898-913 — 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 `android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:878` 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) android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:107— android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:107-122 | android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:142-157 — 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 `android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:92— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:92-107 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:89-104 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (16 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:130— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:130-145 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java:130-145 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:192— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:192-207 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:329-344 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 96 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. 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 (16 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/posedetector/PoseDetectorProcessor.java:99— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/posedetector/PoseDetectorProcessor.java:99-114 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/posedetector/PoseDetectorProcessor.java:118-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `image` to `InputImage` in one and `MlImage` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:376— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:376-391 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:545-560 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:376` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/util/Language.kt:31— android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/util/Language.kt:31-42 | android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/kotlin/TranslateViewModel.kt:186-197 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:256— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:256-267 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:338-349 — 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java:43— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java:43-54 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/labeldetector/LabelGraphic.java:41-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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. Note first that the copies are not typed on the same thing: `GraphicOverlay` names `com.google.mlkit.vision.automl.demo.GraphicOverlay` in one and `com.google.mlkit.vision.demo.GraphicOverlay` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java:43— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java:43-54 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/CameraXLivePreviewPreferenceFragment.java:43-54 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/CameraXLivePreviewPreferenceFragment.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 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. 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. Note first that the copies are not typed on the same thing: `R` names `com.google.mlkit.vision.automl.demo.R` in one and `com.google.mlkit.vision.demo.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:166— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:166-177 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java:164-175 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:121— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:121-132 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:167-178 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 96 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) ios/quickstarts/entityextraction/EntityExtractionExample/EntityViewController.swift:94— ios/quickstarts/entityextraction/EntityExtractionExample/EntityViewController.swift:94-105 | ios/quickstarts/translate/TranslateExample/ViewController.swift:82-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ios/quickstarts/translate/TranslateExample/ViewController.swift:95` calls `textViewDidChange`, `translate` and `ios/quickstarts/entityextraction/EntityExtractionExample/EntityViewController.swift:109` 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.
Swallowed exception (caught, then discarded) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:74— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:92— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) android/material-showcase/app/src/main/java/com/google/mlkit/md/settings/PreferenceUtils.kt:100— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:998— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/EmbeddingScreen.kt:351— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:66— `catch (RuntimeException)` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:84— `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×6
Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:90— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:90-104 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectDetectorProcessor.java:88-102 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:223— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:223-237 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:294-308 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:73— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:73-87 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:81-95 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:444— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:444-458 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:460-474 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt:39— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/segmenter/SegmentationGraphic.kt:39-53 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/subjectsegmenter/SubjectSegmentationGraphic.kt:48-64 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:84— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:84-98 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/VisionProcessorBase.java:104-118 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:84— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:84-91 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:88-95 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:84` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:98— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:98-105 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXSourceDemoActivity.kt:67-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `R.layout.activity_vision_camerax_live_preview) previewView = findViewById(R.id.preview_view) if (previewView ==` in one and `R.layout.activity_vision_cameraxsource_demo) previewView = findViewById(R.id.preview_view) if (previewView ==` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/MultiObjectProcessor.kt:86— android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/MultiObjectProcessor.kt:86-93 | android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/ProminentObjectProcessor.kt:79-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.
Duplicated block (8 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:97— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:97-104 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectDetectorProcessor.java:95-102 — 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/segmenter/SegmentationGraphic.java:61— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/segmenter/SegmentationGraphic.java:61-68 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/subjectsegmenter/SubjectSegmentationGraphic.java:81-89 — 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 after the matched lines, `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/segmenter/SegmentationGraphic.java:70` calls `rewind` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/subjectsegmenter/SubjectSegmentationGraphic.java:90` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:110— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:110-117 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java:110-117 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:191— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:191-197 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:191-197 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:197— android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:197-203 | android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:213-219 — 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 `android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:197` 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, `android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:210` calls `add`, `Message`, `getTimeInMillis` and `android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:196` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:73— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:73-79 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java:73-79 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:151— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:151-157 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:198-204 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:147` calls `putInt` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:194` 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 × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:113— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:113-119 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java:125-131 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:113— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:113-119 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/VisionProcessorBase.java:149-155 — 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:113` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:76— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:76-88 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectDetectorProcessor.java:74-86 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/segmenter/SegmentationGraphic.java:57— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/segmenter/SegmentationGraphic.java:57-71 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/subjectsegmenter/SubjectSegmentationGraphic.java:78-90 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:53— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:53-65 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/RewritingActivity.kt:53-65 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:185— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:185-197 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:210-222 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:90— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:90-102 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:113-125 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (25 lines × 2) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:584— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:584-608 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:613-637 — 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 `android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:584` 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 (25 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:309— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:309-333 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:196-220 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (25 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:370— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:370-394 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:257-281 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (25 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:82— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java:82-106 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java:82-106 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSourcePreview.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSourcePreview.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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. Note first that the copies are not typed on the same thing: `PreferenceUtils` names `com.google.mlkit.vision.automl.demo.preference.PreferenceUtils` in one and `com.google.mlkit.vision.demo.preference.PreferenceUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (25 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:131— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:131-155 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:488-512 — 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) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:339— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:339-357 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:347-365 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:339` 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 (19 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:181— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:181-199 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:157-175 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (19 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXViewModel.java:47— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXViewModel.java:47-65 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraXViewModel.java:47-65 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXViewModel.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraXViewModel.java` as WHOLE FILES: 96% 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. 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 (19 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:84— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:84-102 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:130-148 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 96 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `SettingsActivity` names `com.google.mlkit.vision.automl.demo.preference.SettingsActivity` in one and `com.google.mlkit.vision.demo.preference.SettingsActivity` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:52— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:52-70 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:49-67 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (5 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXSourceDemoActivity.kt:75— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXSourceDemoActivity.kt:75-79 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt:112-117 — 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 `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXSourceDemoActivity.kt:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java:59— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java:59-63 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/labeldetector/LabelGraphic.java:57-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:89— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:89-93 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:363-367 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `R` names `com.google.mlkit.vision.automl.demo.R` in one and `com.google.mlkit.vision.demo.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) ios/quickstarts/automl/AutoMLExample/ViewController.swift:170— ios/quickstarts/automl/AutoMLExample/ViewController.swift:170-174 | ios/quickstarts/vision/VisionExample/ViewController.swift:193-197 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 × 2) ios/quickstarts/automl/AutoMLExample/ViewController.swift:608— ios/quickstarts/automl/AutoMLExample/ViewController.swift:608-612 | ios/quickstarts/vision/VisionExample/ViewController.swift:1200-1204 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×4
Edited copy of a member (24 corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:482— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:482-505 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:660-684 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:99— android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:99-122 | android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/kotlin/MainActivityKotlin.kt:129-157 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:233— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:233-256 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:258-281 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:469— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:469-492 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:494-518 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×4
Edited copy of a member (26 corresponding lines) android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:105— android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:105-130 | android/langid/app/src/main/java/com/google/mlkit/samples/nl/languageid/java/MainActivityJava.java:137-172 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:376— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:376-401 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:545-571 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:104— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:104-129 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/RewritingActivity.kt:104-132 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:988— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:988-1013 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/EmbeddingScreen.kt:341-367 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (22 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:153— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:153-174 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:153-174 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:153` 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 (22 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:311— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:311-332 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:387-408 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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. 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 (22 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/SettingsActivity.java:53— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/SettingsActivity.java:53-74 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/SettingsActivity.java:55-76 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/SettingsActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/SettingsActivity.java` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. Note first that the copies are not typed on the same thing: `R` names `com.google.mlkit.vision.automl.demo.R` in one and `com.google.mlkit.vision.demo.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 2) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:102— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:102-123 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:99-120 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift` and `ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:89— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:89-102 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/RewritingActivity.kt:89-102 — 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 `android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:89` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:182— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:182-195 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:214-227 — 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 `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:182` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:269— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:269-282 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:156-169 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:295— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:295-308 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:371-384 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:295` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:372— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:372-391 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:401-420 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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. 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 (20 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:626— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:626-645 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:652-671 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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. 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 (20 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java:99— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java:99-118 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/CameraXLivePreviewPreferenceFragment.java:99-118 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/CameraXLivePreviewPreferenceFragment.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 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. 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 (20 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/facedetector/FaceGraphic.java:197— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/facedetector/FaceGraphic.java:197-216 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/facedetector/FaceGraphic.java:222-241 — 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 `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/facedetector/FaceGraphic.java:197` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:239— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:239-244 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:227-232 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:140— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:140-145 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java:212-217 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:239— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:239-244 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:310-315 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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) ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift:227— ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift:227-232 | ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift:244-249 — 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.
TodoComment android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:108— // TODO(b/74400062) Re-enable the annotaion — 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 android/android-snippets/app/src/main/java/com/google/example/mlkit/MLKitVisionImage.java:62— // TODO How do we document the FrameMetadata developers need to implement? — 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 android/android-snippets/app/src/main/java/com/google/example/mlkit/kotlin/MLKitVisionImage.kt:55— // TODO How do we document the FrameMetadata developers need to implement? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift:226— ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift:226-241 | ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift:243-264 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:26— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:26-41 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:25-40 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:109— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:109-130 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:114-129 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/InferenceInfoGraphic.java:50— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/InferenceInfoGraphic.java:50-67 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/InferenceInfoGraphic.java:63-88 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java:43— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java:43-60 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/textdetector/TextGraphic.java:64-86 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:49— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/AutoMLImageLabelerProcessor.java:49-67 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectDetectorProcessor.java:48-65 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentActivity.kt:39— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentActivity.kt:39-53 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/EmbeddingActivity.kt:41-56 — 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 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:89— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:89-103 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/ChooserActivity.java:77-91 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/ChooserActivity.java` 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. 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/LivePreviewPreferenceFragment.java:45— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/LivePreviewPreferenceFragment.java:45-59 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/LivePreviewPreferenceFragment.java:47-61 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/LivePreviewPreferenceFragment.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/LivePreviewPreferenceFragment.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. 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. Note first that the copies are not typed on the same thing: `CameraSource` names `com.google.mlkit.vision.automl.demo.CameraSource` in one and `com.google.mlkit.vision.demo.CameraSource` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (24 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:337— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:337-360 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:224-247 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (24 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:380— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:380-403 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:487-510 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:379` calls `i` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:486` 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 (24 lines × 2) ios/quickstarts/automl/AutoMLExample/ViewController.swift:256— ios/quickstarts/automl/AutoMLExample/ViewController.swift:256-279 | ios/quickstarts/vision/VisionExample/ViewController.swift:265-288 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:168— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:168-185 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:239-256 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:168` 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:260— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:260-277 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:331-348 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:260` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:48— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:48-65 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:56-73 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `CameraSource` names `com.google.mlkit.vision.automl.demo.CameraSource` in one and `com.google.mlkit.vision.demo.CameraSource` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
CameraXLivePreviewActivity.bindAnalysisUseCase (cyclomatic 27) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:247— CameraXLivePreviewActivity.bindAnalysisUseCase has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CameraXLivePreviewActivity.bindAnalysisUseCase (cyclomatic 27) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:293— CameraXLivePreviewActivity.bindAnalysisUseCase has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ClassTooLong: OpenPromptActivity android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:85— ClassTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 274 over it, 1.69× 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: AgentViewModel android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/viewmodel/AgentViewModel.kt:101— ClassTooLong — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 21 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: kotlin/OpenPromptActivity.kt android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt— FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: OpenPromptActivity (85-1012). The bar is 500 significant lines; this is 249 over it, 1.50× 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: kotlin/AgentScreen.kt android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 225 over it, 1.45× 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.
TooManyMethods: GenerationConfigUtils android/genai/app/src/main/java/com/google/mlkit/genai/demo/GenerationConfigUtils.kt:23— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OpenPromptActivity android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:85— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×2
Edited copy of a member (46 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:335— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:335-380 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:342-389 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (46 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:134— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:134-184 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:334-379 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java:57— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/automl/LabelGraphic.java:57-90 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/labeldetector/LabelGraphic.java:55-95 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) ios/quickstarts/automl/AutoMLExample/ViewController.swift:57— ios/quickstarts/automl/AutoMLExample/ViewController.swift:57-93 | ios/quickstarts/vision/VisionExample/ViewController.swift:64-97 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×2
Edited copy of a member (50 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:259— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:259-308 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:330-384 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt:470— android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt:470-519 | android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechTranslationActivity.kt:300-355 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:77— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:77-107 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:79-112 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:204— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:204-236 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:194-224 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) ios/quickstarts/automl/AutoMLExample/ViewController.swift:230— ios/quickstarts/automl/AutoMLExample/ViewController.swift:230-254 | ios/quickstarts/vision/VisionExample/ViewController.swift:237-263 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:78— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ChooserActivity.java:78-108 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/ChooserActivity.java:68-92 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:47— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:47-69 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:55-77 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:177— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:177-199 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:153-175 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java:66— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java:66-93 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/textdetector/TextGraphic.java:148-166 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:123— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:123-141 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/PreferenceUtils.java:168-186 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) android/documentscanner/app/src/main/java/com/google/mlkit/samples/documentscanner/kotlin/MainActivity.kt:116— android/documentscanner/app/src/main/java/com/google/mlkit/samples/documentscanner/kotlin/MainActivity.kt:116-142 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:206-235 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:165— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:165-192 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:212-238 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/barcodescanner/BarcodeGraphic.kt:51— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/barcodescanner/BarcodeGraphic.kt:51-75 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/textdetector/TextGraphic.kt:118-137 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:221— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:221-240 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:271-291 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:192— android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:192-203 | android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ChatFragment.java:205-219 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/kotlin/chat/ChatFragment.kt:185— android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/kotlin/chat/ChatFragment.kt:185-196 | android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/kotlin/chat/ChatFragment.kt:198-212 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechTranslationActivity.kt:407— android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechTranslationActivity.kt:407-421 | android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt:598-608 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/MainActivityJava.java:28— android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/MainActivityJava.java:28-38 | android/translate/app/src/main/java/com/google/mlkit/samples/nl/translate/java/MainActivity.java:26-36 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:358— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:358-380 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:367-389 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:358` 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 (23 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectGraphic.java:57— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectGraphic.java:57-79 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/objectdetector/ObjectGraphic.java:57-79 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectGraphic.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/objectdetector/ObjectGraphic.java` as WHOLE FILES: 96% 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. 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. Note first that the copies are not typed on the same thing: `GraphicOverlay` names `com.google.mlkit.vision.automl.demo.GraphicOverlay` in one and `com.google.mlkit.vision.demo.GraphicOverlay` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 3) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:107— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:107-123 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt:85-101 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:160-176 — 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 after the matched lines, `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/StillImageActivity.kt:178` calls `add` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:126` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 3) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:141— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:141-157 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:109-125 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:215-231 — before extracting anything, compare `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:233` calls `add` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:160` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/barcodescanner/BarcodeGraphic.kt:56— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/barcodescanner/BarcodeGraphic.kt:56-61 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/objectdetector/ObjectGraphic.kt:88-93 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/textdetector/TextGraphic.kt:120-125 — 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 (6 lines × 3) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java:74— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/barcodescanner/BarcodeGraphic.java:74-79 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/facemeshdetector/FaceMeshGraphic.java:99-104 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/textdetector/TextGraphic.java:150-155 — 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) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:168— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:168-177 | android/documentscanner/app/src/main/java/com/google/mlkit/samples/documentscanner/java/MainActivity.java:138-147 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:239-248 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `R` names `com.google.mlkit.samples.documentscanner.R` in one and `com.google.mlkit.vision.demo.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:178` calls `createImageProcessor`, `tryReloadAndDetectInImage` and `android/documentscanner/app/src/main/java/com/google/mlkit/samples/documentscanner/java/MainActivity.java:148` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:26— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:26-35 | ios/quickstarts/vision/VisionExample/UIUtilities.swift:27-36 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:25-34 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift` and `ios/quickstarts/vision/VisionExample/UIUtilities.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:26` 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, `ios/quickstarts/vision/VisionExample/UIUtilities.swift:37` calls `isValid` and `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:36` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:99— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:99-107 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:69-77 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:133-141 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:101-109 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:99` 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 × 4) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:112— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:112-120 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:82-90 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:160-168 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:128-136 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:97— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:97-104 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:131-138 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXSourceDemoActivity.java:77-84 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 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 × 3) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:317— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:317-325 | ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:344-351 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:333-340 — 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:317` 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 (31 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:403— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:403-433 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:573-603 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 (31 lines × 2) ios/quickstarts/automl/AutoMLExample/ViewController.swift:63— ios/quickstarts/automl/AutoMLExample/ViewController.swift:63-93 | ios/quickstarts/vision/VisionExample/ViewController.swift:67-97 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `ios/quickstarts/automl/AutoMLExample/ViewController.swift:63` 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, `ios/quickstarts/automl/AutoMLExample/ViewController.swift:61` calls `isModelDownloaded`, `remoteModel` and `ios/quickstarts/vision/VisionExample/ViewController.swift:65` 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.
BaseActivity.runInference (cyclomatic 29) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/BaseActivity.kt:279— BaseActivity.runInference has cyclomatic complexity 29 (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.
CameraViewController.addContours (cyclomatic 27) ios/quickstarts/vision/VisionExample/CameraViewController.swift:736— CameraViewController.addContours has cyclomatic complexity 27 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ViewController.addContours (cyclomatic 27) ios/quickstarts/vision/VisionExample/ViewController.swift:294— ViewController.addContours has cyclomatic complexity 27 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
StillImageActivity.createImageProcessor (cyclomatic 26) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:410— StillImageActivity.createImageProcessor has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OpenPromptActivity.createGenerateContentRequest (cyclomatic 18) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:685— OpenPromptActivity.createGenerateContentRequest has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ViewController.detect (cyclomatic 18) ios/quickstarts/vision/VisionExample/ViewController.swift:113— ViewController.detect 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. This is NOT this file's highest cyclomatic complexity: DetectorPickerRow.description (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Date.timeAgo (cyclomatic 17) ios/quickstarts/smartreply/SmartReplyExample/DateExtension.swift:21— Date.timeAgo 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.
AgentScreenKt.AgentTimelineCard (cyclomatic 16) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:495— AgentScreenKt.AgentTimelineCard 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.
AgentViewModel.sendPrompt (cyclomatic 16) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/viewmodel/AgentViewModel.kt:338— AgentViewModel.sendPrompt 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.
BaseActivity.runInference (cognitive 65) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/BaseActivity.kt:279— BaseActivity.runInference has cognitive complexity 65 (threshold 15). Drivers by points: if/else 30 (54 pts), error handling 5 (7 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraViewController.addContours (cognitive 39) ios/quickstarts/vision/VisionExample/CameraViewController.swift:736— CameraViewController.addContours has cognitive complexity 39 (threshold 15). Drivers by points: loops 13 (26 pts), if/else 13 (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ViewController.addContours (cognitive 39) ios/quickstarts/vision/VisionExample/ViewController.swift:294— ViewController.addContours has cognitive complexity 39 (threshold 15). Drivers by points: loops 13 (26 pts), if/else 13 (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TextGraphic.draw (cognitive 27) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/textdetector/TextGraphic.java:90— TextGraphic.draw has cognitive complexity 27 (threshold 15). Drivers by points: loops 4 (13 pts), ternaries 3 (11 pts), if/else 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentScreenKt.AgentTimelineCard (cognitive 24) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentScreen.kt:495— AgentScreenKt.AgentTimelineCard has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 2, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
OpenPromptActivity.runInferenceStreamImpl (cognitive 24) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:573— OpenPromptActivity.runInferenceStreamImpl has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenPromptActivity.createGenerateContentRequest (cognitive 23) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:685— OpenPromptActivity.createGenerateContentRequest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 2 (5 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenPromptActivity.onConfigUpdated (cognitive 22) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:361— OpenPromptActivity.onConfigUpdated has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 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.
AgentViewModel.sendPrompt (cognitive 22) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/viewmodel/AgentViewModel.kt:338— AgentViewModel.sendPrompt has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, error handling 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenPromptActivity.onOptionsItemSelected (cognitive 21) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:950— OpenPromptActivity.onOptionsItemSelected has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Date.timeAgo (cognitive 21) ios/quickstarts/smartreply/SmartReplyExample/DateExtension.swift:21— Date.timeAgo has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 7, boolean chains 6 (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.
OpenPromptActivity.onCreate (cognitive 20) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:203— OpenPromptActivity.onCreate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiObjectProcessor.onSuccess (cognitive 20) android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/MultiObjectProcessor.kt:100— MultiObjectProcessor.onSuccess has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProminentObjectProcessor.onSuccess (cognitive 18) android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/ProminentObjectProcessor.kt:93— ProminentObjectProcessor.onSuccess has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3 (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.
SpeechRecognitionActivity.startSpeechRecognition (cognitive 18) android/speech/app/src/main/java/com/google/mlkit/genai/speech/demo/SpeechRecognitionActivity.kt:272— SpeechRecognitionActivity.startSpeechRecognition has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 3 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BitmapUtils.encodeToNv21 (cognitive 18) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:220— BitmapUtils.encodeToNv21 has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (11 pts), if/else 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewController.computeAllLanguageTags (cognitive 18) ios/quickstarts/digitalinkrecognition/DigitalInkRecognitionExample/ViewController.swift:258— ViewController.computeAllLanguageTags has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraSource.selectSizePair (cognitive 17) android/material-showcase/app/src/main/java/com/google/mlkit/md/camera/CameraSource.kt:453— CameraSource.selectSizePair has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenPromptActivity.resultToContentItems (cognitive 16) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/OpenPromptActivity.kt:790— OpenPromptActivity.resultToContentItems has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FaceGraphic.draw (cognitive 16) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/facedetector/FaceGraphic.kt:61— FaceGraphic.draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, loops 2 (3 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TextGraphic.draw (cognitive 16) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/textdetector/TextGraphic.kt:63— TextGraphic.draw has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (13 pts), if/else 2 (3 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D4 · Code Duplication· Near-duplicate member family (4 members, 18 shared lines) · ×1
Near-duplicate member family (4 members, 18 shared lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:86— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:86-141 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:61-102 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:121-189 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:93-148 — These 4 members are variants of one another: a block of 18 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) ios/quickstarts/automl/AutoMLExample/ViewController.swift:418— ios/quickstarts/automl/AutoMLExample/ViewController.swift:418-476 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:484-547 | ios/quickstarts/vision/VisionExample/ViewController.swift:671-748 | ios/quickstarts/vision/VisionExample/ViewController.swift:845-896 | ios/quickstarts/vision/VisionExample/ViewController.swift:902-958 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (153 corresponding lines) · ×1
Edited copy of a member (153 corresponding lines) ios/quickstarts/vision/VisionExample/CameraViewController.swift:736— ios/quickstarts/vision/VisionExample/CameraViewController.swift:736-889 | ios/quickstarts/vision/VisionExample/ViewController.swift:294-446 — These two members are one piece of code written twice and then edited apart: 153 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:199— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:199-255 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:199-255 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:90— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:90-151 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt:69-123 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:184— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/VisionProcessorBase.java:184-231 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/VisionProcessorBase.java:285-362 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) ios/quickstarts/vision/VisionExample/CameraViewController.swift:129— ios/quickstarts/vision/VisionExample/CameraViewController.swift:129-181 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:479-541 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:257— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:257-297 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:257-300 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:425— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:425-459 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:452-484 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:299— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:299-333 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:302-340 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:187— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:187-214 | android/documentscanner/app/src/main/java/com/google/mlkit/samples/documentscanner/java/MainActivity.java:127-153 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:258-285 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:69— android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:69-100 | android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:131-165 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:76— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:76-98 | ios/quickstarts/vision/VisionExample/UIUtilities.swift:101-125 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:74-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 26+ corresponding lines) · ×1
Edited copies of one member (4 members, 26+ corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:315— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:315-340 | ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:342-367 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:302-329 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:331-357 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:106— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/PreferenceUtils.java:106-127 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/LivePreviewPreferenceFragment.java:125-147 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:87— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/ProofreadingActivity.kt:87-102 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/RewritingActivity.kt:87-102 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/SummarizationActivity.kt:85-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:458— android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:458-465 | android/genai/app/src/main/java/com/google/mlkit/genai/demo/kotlin/AgentDemoAppFunctions.kt:483-490 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:72— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:72-88 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:95-111 | ios/quickstarts/entityextraction/EntityExtractionExample/ModelManagementViewController.swift:28-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:43— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:43-50 | ios/quickstarts/vision/VisionExample/UIUtilities.swift:66-75 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:42-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:153— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:153-168 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:178-193 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:146-160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:405— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:405-408 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:432-435 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) android/internal/chooserx/src/main/java/com/mlkit/example/internal/ChoiceAdapter.java:41— android/internal/chooserx/src/main/java/com/mlkit/example/internal/ChoiceAdapter.java:41-45 | android/smartreply/app/src/main/java/com/google/mlkit/samples/nl/smartreply/java/chat/ReplyChipAdapter.java:48-52 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) ios/quickstarts/entityextraction/EntityExtractionExample/EntityViewController.swift:109— ios/quickstarts/entityextraction/EntityExtractionExample/EntityViewController.swift:109-112 | ios/quickstarts/languageid/LanguageIDExample/ViewController.swift:73-76 | ios/quickstarts/translate/TranslateExample/ViewController.swift:101-104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (44 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:200— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:200-243 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:200-243 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 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 (34–38 lines × 2) android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:100— android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:100-133 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt:76-113 — 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 `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt:100` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `R.layout.activity_vision_camerax_live_preview) previewView = findViewById(R.id.preview_view) if (previewView ==` in one and `R.layout.activity_vision_live_preview) preview = findViewById(R.id.preview_view) if (preview ==` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (30 lines × 2) android/material-showcase/app/src/main/java/com/google/mlkit/md/TaskExt.kt:31— android/material-showcase/app/src/main/java/com/google/mlkit/md/TaskExt.kt:31-60 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/TaskExt.kt:33-68 — 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 `android/material-showcase/app/src/main/java/com/google/mlkit/md/TaskExt.kt:31` 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 × 3) android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:144— android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:144-150 | android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:144-150 | android/material-showcase/app/src/main/java/com/google/mlkit/md/StaticObjectDetectionActivity.kt:145-151 — before extracting anything, compare `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt:141` calls `shutdown` and `android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:141` 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 (74 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:266— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:266-339 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:295-368 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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. 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. Note first that the copies are not typed on the same thing: `PreferenceUtils` names `com.google.mlkit.vision.automl.demo.preference.PreferenceUtils` in one and `com.google.mlkit.vision.demo.preference.PreferenceUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (56–60 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:90— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:90-145 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:124-183 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:90` 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. Note first that the copies are not typed on the same thing: `SettingsActivity` names `com.google.mlkit.vision.automl.demo.preference.SettingsActivity` in one and `com.google.mlkit.vision.demo.preference.SettingsActivity` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (56 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectGraphic.java:84— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectGraphic.java:84-139 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/objectdetector/ObjectGraphic.java:84-139 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/object/ObjectGraphic.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/objectdetector/ObjectGraphic.java` as WHOLE FILES: 96% 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. 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 (52 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:664— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:664-715 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:690-741 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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. 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 (59–60 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/LivePreviewPreferenceFragment.java:63— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/LivePreviewPreferenceFragment.java:63-122 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/LivePreviewPreferenceFragment.java:65-123 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/LivePreviewPreferenceFragment.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/LivePreviewPreferenceFragment.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. 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. Note first that the copies are not typed on the same thing: `CameraSource` names `com.google.mlkit.vision.automl.demo.CameraSource` in one and `com.google.mlkit.vision.demo.CameraSource` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (45 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:290— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:290-334 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:430-474 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:290` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `PreferenceUtils` names `com.google.mlkit.vision.automl.demo.preference.PreferenceUtils` in one and `com.google.mlkit.vision.demo.preference.PreferenceUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (43 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:133— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java:133-175 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java:109-151 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/BitmapUtils.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/BitmapUtils.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 182 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. 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 (40 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:502— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:502-541 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:528-567 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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. 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 (37 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java:58— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java:58-94 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/CameraXLivePreviewPreferenceFragment.java:58-94 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/preference/CameraXLivePreviewPreferenceFragment.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/preference/CameraXLivePreviewPreferenceFragment.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 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. 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 (28 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:114— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:114-141 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java:162-189 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXLivePreviewActivity.java` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 145 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:114` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `SettingsActivity` names `com.google.mlkit.vision.automl.demo.preference.SettingsActivity` in one and `com.google.mlkit.vision.demo.preference.SettingsActivity` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (27 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:200— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java:200-226 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java:272-298 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/GraphicOverlay.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/GraphicOverlay.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 (15–16 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:430— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java:430-445 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java:456-470 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraSource.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/CameraSource.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 291 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 (14–15 lines × 2) android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:86— android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:86-100 | android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:152-165 — 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 `android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java:86` 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 × 4) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:166— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:166-176 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:195-205 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:237-247 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java:267-277 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/StillImageActivity.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 182 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:166` 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, `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:190` calls `add` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:161` 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–11 lines × 3) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:107— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java:107-116 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:77-86 | android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:161-171 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/CameraXLivePreviewActivity.java` and `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/StillImageActivity.java:161` 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 (8–9 lines × 3) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:89— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:89-96 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/CameraXSourceDemoActivity.java:86-94 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java:135-142 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/java/LivePreviewActivity.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 96 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 `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/LivePreviewActivity.java:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. Note first that the copies are not typed on the same thing: `SettingsActivity` names `com.google.mlkit.vision.automl.demo.preference.SettingsActivity` in one and `com.google.mlkit.vision.demo.preference.SettingsActivity` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (68 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/FrameMetadata.java:1— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/FrameMetadata.java:1-68 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/FrameMetadata.java:1-68 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/FrameMetadata.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/FrameMetadata.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/FrameMetadata.java:1` 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 (29 lines × 2) android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ScopedExecutor.java:32— android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ScopedExecutor.java:32-60 | android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/ScopedExecutor.java:32-60 — before extracting anything, compare `android/automl/app/src/main/java/com/google/mlkit/vision/automl/demo/ScopedExecutor.java` and `android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/ScopedExecutor.java` as WHOLE FILES: 97% 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 (22–26 lines × 2) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:224— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:224-245 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:420-445 — 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 (21–22 lines × 3) ios/quickstarts/vision/VisionExample/CameraViewController.swift:137— ios/quickstarts/vision/VisionExample/CameraViewController.swift:137-158 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:193-213 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:238-258 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ios/quickstarts/vision/VisionExample/CameraViewController.swift:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15–18 lines × 5) ios/quickstarts/automl/AutoMLExample/ViewController.swift:449— ios/quickstarts/automl/AutoMLExample/ViewController.swift:449-466 | ios/quickstarts/automl/AutoMLExample/ViewController.swift:518-532 | ios/quickstarts/vision/VisionExample/ViewController.swift:688-705 | ios/quickstarts/vision/VisionExample/ViewController.swift:860-877 | ios/quickstarts/vision/VisionExample/ViewController.swift:931-948 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/ViewController.swift` and `ios/quickstarts/vision/VisionExample/ViewController.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `ios/quickstarts/automl/AutoMLExample/ViewController.swift:449` 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 (23 lines × 3) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:52— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:52-74 | ios/quickstarts/vision/VisionExample/UIUtilities.swift:77-99 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:50-72 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift` and `ios/quickstarts/vision/VisionExample/UIUtilities.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (17–18 lines × 3) ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:79— ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:79-96 | ios/quickstarts/vision/VisionExample/UIUtilities.swift:104-121 | ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift:77-93 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift` and `ios/quickstarts/vision/VisionExample/UIUtilities.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `ios/quickstarts/automl/AutoMLExample/UIUtilities.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ios/quickstarts/vision/VisionExample/UIUtilities.swift:123` calls `fatalError` and `ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:97` 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 (4–17 lines × 3) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:191— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:191-207 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:514-530 | ios/quickstarts/vision/VisionExample/ViewController.swift:1046-1049 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:191` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 5) ios/quickstarts/vision/VisionExample/CameraViewController.swift:140— ios/quickstarts/vision/VisionExample/CameraViewController.swift:140-154 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:196-209 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:241-254 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:340-353 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:439-452 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ios/quickstarts/vision/VisionExample/CameraViewController.swift:140` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ios/quickstarts/vision/VisionExample/CameraViewController.swift:437` calls `joined` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift:139` 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 (13–14 lines × 3) ios/quickstarts/vision/VisionExample/CameraViewController.swift:151— ios/quickstarts/vision/VisionExample/CameraViewController.swift:151-163 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:206-219 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:501-514 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ios/quickstarts/vision/VisionExample/CameraViewController.swift:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:190— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:190-201 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:218-229 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:513-524 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:190` 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–11 lines × 4) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:184— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:184-193 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:156-165 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:211-221 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:507-516 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:470— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:470-480 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:648-658 | ios/showcase/translate-showcase/TranslateDemo/CameraViewController.swift:353-363 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:470` 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 lines × 4) ios/quickstarts/vision/VisionExample/CameraViewController.swift:752— ios/quickstarts/vision/VisionExample/CameraViewController.swift:752-761 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:763-772 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:774-783 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:785-794 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ios/quickstarts/vision/VisionExample/CameraViewController.swift:752` 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–10 lines × 6) ios/quickstarts/vision/VisionExample/CameraViewController.swift:822— ios/quickstarts/vision/VisionExample/CameraViewController.swift:822-831 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:833-842 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:844-853 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:855-864 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:867-873 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:878-884 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ios/quickstarts/vision/VisionExample/CameraViewController.swift:822` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–9 lines × 5) ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:188— ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:188-195 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:160-168 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:216-223 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:381-389 | ios/quickstarts/vision/VisionExample/CameraViewController.swift:511-518 — before extracting anything, compare `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift` and `ios/quickstarts/vision/VisionExample/CameraViewController.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 145 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 `ios/quickstarts/automl/AutoMLExample/CameraViewController.swift:188` 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.
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 android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt: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 ios/showcase/translate-showcase/TranslateDemo/CameraViewController.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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt: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 android/material-showcase/app/src/main/java/com/google/mlkit/md/StaticObjectDetectionActivity.kt: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 ios/quickstarts/smartreply/SmartReplyExample/MainViewController.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 ios/quickstarts/digitalinkrecognition/DigitalInkRecognitionExample/ViewController.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 android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/main/MainFragment.kt: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 android/material-showcase/app/src/main/java/com/google/mlkit/md/Utils.kt: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 ios/quickstarts/translate/TranslateExample/ViewController.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 ios/quickstarts/digitalinkrecognition/DigitalInkRecognitionExample/StrokeManager.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 android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/MultiObjectProcessor.kt: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 android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveBarcodeScanningActivity.kt: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 android/material-showcase/app/src/main/java/com/google/mlkit/md/objectdetection/ProminentObjectProcessor.kt: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/FaceDetectionActivity.java: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 ios/showcase/translate-showcase/TranslateDemo/SearchViewController.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 android/android-snippets/app/src/main/java/com/google/example/mlkit/ObjectDetectionActivity.java: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 android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/main/MainViewModel.kt: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 android/material-showcase/app/src/main/java/com/google/mlkit/md/productsearch/BottomSheetScrimView.kt: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/ImageLabelingActivity.java: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/kotlin/FaceDetectionActivity.kt: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 android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/analyzer/TextAnalyzer.kt: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/kotlin/ObjectDetectionActivity.kt: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/kotlin/MLKitVisionImage.kt: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/MLKitVisionImage.java: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 android/android-snippets/app/src/main/java/com/google/example/mlkit/TextRecognitionActivity.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:221— `searchedObject == null || java.lang.Float.isNaN(slideOffset)` appears character-identically in 2 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:373— `shouldPlayPromptChipEnteringAnimation && !it.isRunning` appears character-identically in 3 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveBarcodeScanningActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:330— `shouldPlayPromptChipEnteringAnimation && promptChipAnimator?.isRunning == false` appears character-identically in 2 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:378— `shouldPlaySearchButtonEnteringAnimation && !it.isRunning` appears character-identically in 2 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:329— `wasPromptChipGone && promptChip?.visibility == View.VISIBLE` appears character-identically in 3 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveBarcodeScanningActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:376— `wasSearchButtonGone && searchButton?.visibility == View.VISIBLE` appears character-identically in 2 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt:263— `workflowState == null || Objects.equal(currentWorkflowState, workflowState)` appears character-identically in 3 files — android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveBarcodeScanningActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt. 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 ios/quickstarts/automl/AutoMLExample/ViewController.swift:160— `UIImagePickerController.isCameraDeviceAvailable(.front) || UIImagePickerController .isCameraDeviceAvailable(.rear)` appears character-identically in 2 files — ios/quickstarts/automl/AutoMLExample/ViewController.swift, ios/quickstarts/vision/VisionExample/ViewController.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 ios/quickstarts/automl/AutoMLExample/ViewController.swift:79— `UIImagePickerController.isCameraDeviceAvailable(.front) || UIImagePickerController.isCameraDeviceAvailable(.rear)` appears character-identically in 2 files — ios/quickstarts/automl/AutoMLExample/ViewController.swift, ios/quickstarts/vision/VisionExample/ViewController.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 ios/quickstarts/automl/AutoMLExample/UIUtilities.swift:80— `deviceOrientation == .faceDown || deviceOrientation == .faceUp || deviceOrientation == .unknown` appears character-identically in 3 files — ios/quickstarts/automl/AutoMLExample/UIUtilities.swift, ios/quickstarts/vision/VisionExample/UIUtilities.swift, ios/showcase/translate-showcase/TranslateDemo/UIUtilities.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
No ADRs found ios/showcase/vision-showcase/ShowcaseApp.xcodeproj/project.pbxproj:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `ios/showcase/vision-showcase/ShowcaseApp.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 25 project(s) overshoot their size bounds, lowering Project Cohesion to 9.2/10. The most over is `android/vision-quickstart/app` (11261 LoC, 104 module-visible types across 23 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.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 66 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: android/material-showcase/app/src/main/java/com/google/mlkit/md/LiveObjectDetectionActivity.kt, ios/showcase/translate-showcase/TranslateDemo/CameraViewController.swift, android/material-showcase/app/src/main/java/com/google/mlkit/md/CustomModelObjectDetectionActivity.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/StaticObjectDetectionActivity.kt, ios/quickstarts/smartreply/SmartReplyExample/MainViewController.swift, ios/quickstarts/digitalinkrecognition/DigitalInkRecognitionExample/ViewController.swift, android/translate-showcase/app/src/main/java/com/google/mlkit/showcase/translate/main/MainFragment.kt, android/material-showcase/app/src/main/java/com/google/mlkit/md/Utils.kt (and 58 more) (68 orphaned of 213 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 213 of the 340 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Thin README README.md:1— The root README is 41 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
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.
README/code drift tutorials/README.md:8— tutorials/README.md links to `CONTRIBUTING.md`, but `tutorials/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.)
Not-null assertions (`!!`) override null safety — ~7.4 `!!` not-null assertions per 1k Kotlin product lines — 186 across the 25033 line(s) of the 151 Kotlin file(s) read (generated, test and sample code not counted). Densest: android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXSourceDemoActivity.kt (24), android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/LivePreviewActivity.kt (19), android/vision-quickstart/app/src/main/java/com/google/mlkit/vision/demo/kotlin/CameraXLivePreviewActivity.kt (15). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default in catch android/material-showcase/app/src/main/java/com/google/mlkit/md/Utils.kt:86— `getRequiredPermissions` swallows every exception into `arrayOf()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
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 1 file(s) — `ios/quickstarts/translate/TranslateExample/ViewController.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a1d67f-bba4-79e5-8d54-c9220c3e4c04 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 2 · Warnings: 302 · Recommendations: 87 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 20:00 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.