Public report of firebase/quickstart-android, 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.3). 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, 18:47 UTC · Survey ID cd_7dca523222f44d36905bedb5e7e2c18c
firebase/quickstart-android
Measured 13 November 2026, 18:47 UTC, at code version 153d775
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt riskUp 14 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: 21,735 lines of product code in 33 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 42
Findings by how serious they are
9 critical112 serious248 minor
17 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, 18:47 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
44of 44 dimensions measured by tools.
185of 369 findings point to an exact file and line, so you can open each one in the code. The other 184 concern the repository as a whole, such as missing documentation.
44dimensions across 7 lenses, read from 21,735 lines of product code in 33 projects.
firebase/quickstart-android is rated At risk because critical security findings are open, all of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 54 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 42, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 9 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 63.
Seven known security holes in the packages the code depends on can be used by attackers. One form field can't be read by a screen reader. Updating the vulnerable packages and labelling the form fields would close both risks. The page that doesn't say its language needs its language set.
The product code is 21,735 lines, about €22,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.
God Classes · MethodTooLong: FunctionCallingScreenKt.FunctionCallingScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt
God Classes · MethodTooLong: FunctionCallingViewModel.runTest firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt
God Classes · MethodTooLong: ThinkingModeScreenKt.ThinkingModeScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt
God Classes · MethodTooLong: HybridImagePatternScreenKt.HybridImagePatternScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/HybridImagePatternScreen.kt
God Classes · MethodTooLong: ThinkingModeViewModel.runTest firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt
Code Duplication · Near-duplicate member family (3 members, 111 shared lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt
Code Duplication · Near-duplicate member pair (41 shared lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt
Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt
Code Duplication · Edited copy of a member (26 corresponding lines) database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java
Code Duplication · Edited copy of a member (36 corresponding lines) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java
Code Duplication · Edited copy of a member (29 corresponding lines) dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/actordetail/ActorDetailScreen.kt
Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java
Code Duplication · Edited copy of a member (26 corresponding lines) database/app/src/main/java/com/google/firebase/quickstart/database/kotlin/SignInFragment.kt
Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java
Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FacebookLoginFragment.kt
Code Duplication · Edited copy of a member (24 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt
Code Duplication · Edited copy of a member (20 corresponding lines) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java
Code Duplication · Edited copy of a member (21 corresponding lines) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java
Code Duplication · Edited copy of a member (12 corresponding lines) firestore/app/src/main/java/com/google/firebase/example/fireeats/java/FilterDialogFragment.java
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java
Code Duplication · Edited copy of a member (11 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt
Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/AnonymousAuthFragment.kt
Code Duplication · Edited copy of a member (14 corresponding lines) storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java
Code Duplication · Edited copy of a member (14 corresponding lines) storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MyDownloadService.kt
Code Duplication · Edited copy of a member (13 corresponding lines) firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java
Code Duplication · Edited copy of a member (19 corresponding lines) database/app/src/main/java/com/google/firebase/quickstart/database/java/PostDetailFragment.java
Code Duplication · Edited copy of a member (13 corresponding lines) firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/MainFragment.kt
Code Duplication · Edited copy of a member (20 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.java
Code Duplication · Edited copy of a member (12 corresponding lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt
Code Duplication · Edited copy of a member (14 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/CustomAuthFragment.java
Code Duplication · Edited copy of a member (17 corresponding lines) dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/components/ActorsList.kt
Code Duplication · Edited copy of a member (11 corresponding lines) analytics/app/src/main/java/com/google/firebase/quickstart/analytics/java/MainActivity.java
Code Duplication · Edited copy of a member (10 corresponding lines) storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java
Code Duplication · Edited copy of a member (8 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PasswordlessActivity.java
Code Duplication · Edited copy of a member (6 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/BaseActivity.java
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: 13 findings
These 13 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Documentation (README) · README may be stale
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €22,000 · Estimate
Cost to rebuild
€7,400 to €37,000, for 123 to 389 hours of work, about 0.2 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.8 at a score of 54. 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: 21,735 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
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Raises the score by about 3 points · Low effort · ADR Quality
3
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 3 points · Medium effort · Forms & labels
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 €22,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 42 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
88 modules, with 34 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 48 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.
com.firebase.lint uses com.firebase.lint.HungarianNotationDetector, so a change to com.firebase.lint.HungarianNotationDetector can break com.firebase.lint, while a change to com.firebase.lint can't break com.firebase.lint.HungarianNotationDetector.
Position
Below the diagonal: com.firebase.lint uses a module listed above it, which is the healthy direction.
com.firebase.lint uses com.firebase.lint.InvalidImportDetector, so a change to com.firebase.lint.InvalidImportDetector can break com.firebase.lint, while a change to com.firebase.lint can't break com.firebase.lint.InvalidImportDetector.
Position
Below the diagonal: com.firebase.lint uses a module listed above it, which is the healthy direction.
16→22 com.google.firebase.quickstart.ai.feature.text uses com.google.firebase.quickstart.ai.uipart of a loop✕
Connections
20 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.text uses a type in com.google.firebase.quickstart.ai.ui.
com.google.firebase.quickstart.ai.feature.text uses com.google.firebase.quickstart.ai.ui, so a change to com.google.firebase.quickstart.ai.ui can break com.google.firebase.quickstart.ai.feature.text, while a change to com.google.firebase.quickstart.ai.feature.text can't break com.google.firebase.quickstart.ai.ui.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7 pairs of types, where a type in com.google.firebase.quickstart.ai.ui.navigation.Category uses a type in com.google.firebase.quickstart.ai.ui.navigation.
com.google.firebase.quickstart.ai.ui.navigation.Category uses com.google.firebase.quickstart.ai.ui.navigation, so a change to com.google.firebase.quickstart.ai.ui.navigation can break com.google.firebase.quickstart.ai.ui.navigation.Category, while a change to com.google.firebase.quickstart.ai.ui.navigation.Category can't break com.google.firebase.quickstart.ai.ui.navigation.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui.navigation.Category uses a module listed above it, which is the healthy direction.
10 pairs of types, where a type in com.google.firebase.quickstart.ai.ui.navigation.ScreenType uses a type in com.google.firebase.quickstart.ai.ui.navigation.
com.google.firebase.quickstart.ai.ui.navigation.ScreenType uses com.google.firebase.quickstart.ai.ui.navigation, so a change to com.google.firebase.quickstart.ai.ui.navigation can break com.google.firebase.quickstart.ai.ui.navigation.ScreenType, while a change to com.google.firebase.quickstart.ai.ui.navigation.ScreenType can't break com.google.firebase.quickstart.ai.ui.navigation.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui.navigation.ScreenType uses a module listed above it, which is the healthy direction.
19→23 com.google.firebase.quickstart.analytics.kotlin.MainActivity uses com.google.firebase.quickstart.analytics.kotlinpart of a loop✕
Connections
2 pairs of types, where a type in com.google.firebase.quickstart.analytics.kotlin.MainActivity uses a type in com.google.firebase.quickstart.analytics.kotlin.
com.google.firebase.quickstart.analytics.kotlin.MainActivity uses com.google.firebase.quickstart.analytics.kotlin, so a change to com.google.firebase.quickstart.analytics.kotlin can break com.google.firebase.quickstart.analytics.kotlin.MainActivity, while a change to com.google.firebase.quickstart.analytics.kotlin.MainActivity can't break com.google.firebase.quickstart.analytics.kotlin.
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 com.google.firebase.quickstart.database.java.viewholder uses a type in com.google.firebase.quickstart.database.java.models.
com.google.firebase.quickstart.database.java.viewholder uses com.google.firebase.quickstart.database.java.models, so a change to com.google.firebase.quickstart.database.java.models can break com.google.firebase.quickstart.database.java.viewholder, while a change to com.google.firebase.quickstart.database.java.viewholder can't break com.google.firebase.quickstart.database.java.models.
Position
Below the diagonal: com.google.firebase.quickstart.database.java.viewholder uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.google.firebase.quickstart.database.kotlin.viewholder uses a type in com.google.firebase.quickstart.database.kotlin.models.
com.google.firebase.quickstart.database.kotlin.viewholder uses com.google.firebase.quickstart.database.kotlin.models, so a change to com.google.firebase.quickstart.database.kotlin.models can break com.google.firebase.quickstart.database.kotlin.viewholder, while a change to com.google.firebase.quickstart.database.kotlin.viewholder can't break com.google.firebase.quickstart.database.kotlin.models.
Position
Below the diagonal: com.google.firebase.quickstart.database.kotlin.viewholder uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.ai.ui uses com.google.firebase.quickstart.ai.feature.live, so a change to com.google.firebase.quickstart.ai.feature.live can break com.google.firebase.quickstart.ai.ui, while a change to com.google.firebase.quickstart.ai.ui can't break com.google.firebase.quickstart.ai.feature.live.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.ai.ui uses com.google.firebase.quickstart.ai.feature.text, so a change to com.google.firebase.quickstart.ai.feature.text can break com.google.firebase.quickstart.ai.ui, while a change to com.google.firebase.quickstart.ai.ui can't break com.google.firebase.quickstart.ai.feature.text.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui uses a module listed above it, which is the healthy direction.
22→34 com.google.firebase.quickstart.ai.ui uses com.google.firebase.quickstart.ai.feature.hybridpart of a loop✕
Connections
7 pairs of types, where a type in com.google.firebase.quickstart.ai.ui uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.ui uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.ui, while a change to com.google.firebase.quickstart.ai.ui can't break com.google.firebase.quickstart.ai.feature.hybrid.
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 com.google.firebase.quickstart.analytics.kotlin uses a type in com.google.firebase.quickstart.analytics.kotlin.MainActivity.
com.google.firebase.quickstart.analytics.kotlin uses com.google.firebase.quickstart.analytics.kotlin.MainActivity, so a change to com.google.firebase.quickstart.analytics.kotlin.MainActivity can break com.google.firebase.quickstart.analytics.kotlin, while a change to com.google.firebase.quickstart.analytics.kotlin can't break com.google.firebase.quickstart.analytics.kotlin.MainActivity.
Position
Below the diagonal: com.google.firebase.quickstart.analytics.kotlin uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.database.java uses com.google.firebase.quickstart.database.java.models, so a change to com.google.firebase.quickstart.database.java.models can break com.google.firebase.quickstart.database.java, while a change to com.google.firebase.quickstart.database.java can't break com.google.firebase.quickstart.database.java.models.
Position
Below the diagonal: com.google.firebase.quickstart.database.java uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.database.java uses com.google.firebase.quickstart.database.java.viewholder, so a change to com.google.firebase.quickstart.database.java.viewholder can break com.google.firebase.quickstart.database.java, while a change to com.google.firebase.quickstart.database.java can't break com.google.firebase.quickstart.database.java.viewholder.
Position
Below the diagonal: com.google.firebase.quickstart.database.java uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.google.firebase.quickstart.database.java.listfragments uses a type in com.google.firebase.quickstart.database.java.models.
com.google.firebase.quickstart.database.java.listfragments uses com.google.firebase.quickstart.database.java.models, so a change to com.google.firebase.quickstart.database.java.models can break com.google.firebase.quickstart.database.java.listfragments, while a change to com.google.firebase.quickstart.database.java.listfragments can't break com.google.firebase.quickstart.database.java.models.
Position
Below the diagonal: com.google.firebase.quickstart.database.java.listfragments uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.google.firebase.quickstart.database.java.listfragments uses a type in com.google.firebase.quickstart.database.java.viewholder.
com.google.firebase.quickstart.database.java.listfragments uses com.google.firebase.quickstart.database.java.viewholder, so a change to com.google.firebase.quickstart.database.java.viewholder can break com.google.firebase.quickstart.database.java.listfragments, while a change to com.google.firebase.quickstart.database.java.listfragments can't break com.google.firebase.quickstart.database.java.viewholder.
Position
Below the diagonal: com.google.firebase.quickstart.database.java.listfragments uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.database.kotlin.PostDetailFragment uses a type in com.google.firebase.quickstart.database.kotlin.models.
com.google.firebase.quickstart.database.kotlin.PostDetailFragment uses com.google.firebase.quickstart.database.kotlin.models, so a change to com.google.firebase.quickstart.database.kotlin.models can break com.google.firebase.quickstart.database.kotlin.PostDetailFragment, while a change to com.google.firebase.quickstart.database.kotlin.PostDetailFragment can't break com.google.firebase.quickstart.database.kotlin.models.
Position
Below the diagonal: com.google.firebase.quickstart.database.kotlin.PostDetailFragment uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.database.kotlin.PostDetailFragment uses a type in com.google.firebase.quickstart.database.kotlin.viewholder.
com.google.firebase.quickstart.database.kotlin.PostDetailFragment uses com.google.firebase.quickstart.database.kotlin.viewholder, so a change to com.google.firebase.quickstart.database.kotlin.viewholder can break com.google.firebase.quickstart.database.kotlin.PostDetailFragment, while a change to com.google.firebase.quickstart.database.kotlin.PostDetailFragment can't break com.google.firebase.quickstart.database.kotlin.viewholder.
Position
Below the diagonal: com.google.firebase.quickstart.database.kotlin.PostDetailFragment uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.database.kotlin.listfragments uses a type in com.google.firebase.quickstart.database.kotlin.models.
com.google.firebase.quickstart.database.kotlin.listfragments uses com.google.firebase.quickstart.database.kotlin.models, so a change to com.google.firebase.quickstart.database.kotlin.models can break com.google.firebase.quickstart.database.kotlin.listfragments, while a change to com.google.firebase.quickstart.database.kotlin.listfragments can't break com.google.firebase.quickstart.database.kotlin.models.
Position
Below the diagonal: com.google.firebase.quickstart.database.kotlin.listfragments uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.database.kotlin.listfragments uses a type in com.google.firebase.quickstart.database.kotlin.viewholder.
com.google.firebase.quickstart.database.kotlin.listfragments uses com.google.firebase.quickstart.database.kotlin.viewholder, so a change to com.google.firebase.quickstart.database.kotlin.viewholder can break com.google.firebase.quickstart.database.kotlin.listfragments, while a change to com.google.firebase.quickstart.database.kotlin.listfragments can't break com.google.firebase.quickstart.database.kotlin.viewholder.
Position
Below the diagonal: com.google.firebase.quickstart.database.kotlin.listfragments uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel uses a type in com.google.firebase.quickstart.ai.ui.
com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel uses com.google.firebase.quickstart.ai.ui, so a change to com.google.firebase.quickstart.ai.ui can break com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel, while a change to com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel can't break com.google.firebase.quickstart.ai.ui.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.ai.ui.ChatUiState uses com.google.firebase.quickstart.ai.ui, so a change to com.google.firebase.quickstart.ai.ui can break com.google.firebase.quickstart.ai.ui.ChatUiState, while a change to com.google.firebase.quickstart.ai.ui.ChatUiState can't break com.google.firebase.quickstart.ai.ui.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui.ChatUiState uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.ai.ui.ServerPromptUiState uses com.google.firebase.quickstart.ai.ui, so a change to com.google.firebase.quickstart.ai.ui can break com.google.firebase.quickstart.ai.ui.ServerPromptUiState, while a change to com.google.firebase.quickstart.ai.ui.ServerPromptUiState can't break com.google.firebase.quickstart.ai.ui.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui.ServerPromptUiState uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.ai.ui.SvgUiState uses com.google.firebase.quickstart.ai.ui, so a change to com.google.firebase.quickstart.ai.ui can break com.google.firebase.quickstart.ai.ui.SvgUiState, while a change to com.google.firebase.quickstart.ai.ui.SvgUiState can't break com.google.firebase.quickstart.ai.ui.
Position
Below the diagonal: com.google.firebase.quickstart.ai.ui.SvgUiState uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.analytics.kotlin.ImageFragment uses a type in com.google.firebase.quickstart.analytics.kotlin.
com.google.firebase.quickstart.analytics.kotlin.ImageFragment uses com.google.firebase.quickstart.analytics.kotlin, so a change to com.google.firebase.quickstart.analytics.kotlin can break com.google.firebase.quickstart.analytics.kotlin.ImageFragment, while a change to com.google.firebase.quickstart.analytics.kotlin.ImageFragment can't break com.google.firebase.quickstart.analytics.kotlin.
Position
Below the diagonal: com.google.firebase.quickstart.analytics.kotlin.ImageFragment uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.database.kotlin uses a type in com.google.firebase.quickstart.database.kotlin.PostDetailFragment.
com.google.firebase.quickstart.database.kotlin uses com.google.firebase.quickstart.database.kotlin.PostDetailFragment, so a change to com.google.firebase.quickstart.database.kotlin.PostDetailFragment can break com.google.firebase.quickstart.database.kotlin, while a change to com.google.firebase.quickstart.database.kotlin can't break com.google.firebase.quickstart.database.kotlin.PostDetailFragment.
Position
Below the diagonal: com.google.firebase.quickstart.database.kotlin uses a module listed above it, which is the healthy direction.
com.google.firebase.quickstart.ai.feature.hybrid uses com.google.firebase.quickstart.ai.ui, so a change to com.google.firebase.quickstart.ai.ui can break com.google.firebase.quickstart.ai.feature.hybrid, while a change to com.google.firebase.quickstart.ai.feature.hybrid can't break com.google.firebase.quickstart.ai.ui.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid uses a type in com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel.
com.google.firebase.quickstart.ai.feature.hybrid uses com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel, so a change to com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel can break com.google.firebase.quickstart.ai.feature.hybrid, while a change to com.google.firebase.quickstart.ai.feature.hybrid can't break com.google.firebase.quickstart.ai.feature.hybrid.FunctionCallingViewModel.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.FunctionToolOption uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.feature.hybrid.FunctionToolOption uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.feature.hybrid.FunctionToolOption, while a change to com.google.firebase.quickstart.ai.feature.hybrid.FunctionToolOption can't break com.google.firebase.quickstart.ai.feature.hybrid.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.FunctionToolOption uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.GenerationMethod uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.feature.hybrid.GenerationMethod uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.feature.hybrid.GenerationMethod, while a change to com.google.firebase.quickstart.ai.feature.hybrid.GenerationMethod can't break com.google.firebase.quickstart.ai.feature.hybrid.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.GenerationMethod uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.InferenceModeOption uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.feature.hybrid.InferenceModeOption uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.feature.hybrid.InferenceModeOption, while a change to com.google.firebase.quickstart.ai.feature.hybrid.InferenceModeOption can't break com.google.firebase.quickstart.ai.feature.hybrid.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.InferenceModeOption uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.OnDeviceModelOptionSelection uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.feature.hybrid.OnDeviceModelOptionSelection uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.feature.hybrid.OnDeviceModelOptionSelection, while a change to com.google.firebase.quickstart.ai.feature.hybrid.OnDeviceModelOptionSelection can't break com.google.firebase.quickstart.ai.feature.hybrid.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.OnDeviceModelOptionSelection uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.SystemInstructionCase uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.feature.hybrid.SystemInstructionCase uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.feature.hybrid.SystemInstructionCase, while a change to com.google.firebase.quickstart.ai.feature.hybrid.SystemInstructionCase can't break com.google.firebase.quickstart.ai.feature.hybrid.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.SystemInstructionCase uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.google.firebase.quickstart.ai.feature.hybrid.ThinkingOption uses a type in com.google.firebase.quickstart.ai.feature.hybrid.
com.google.firebase.quickstart.ai.feature.hybrid.ThinkingOption uses com.google.firebase.quickstart.ai.feature.hybrid, so a change to com.google.firebase.quickstart.ai.feature.hybrid can break com.google.firebase.quickstart.ai.feature.hybrid.ThinkingOption, while a change to com.google.firebase.quickstart.ai.feature.hybrid.ThinkingOption can't break com.google.firebase.quickstart.ai.feature.hybrid.
Position
Below the diagonal: com.google.firebase.quickstart.ai.feature.hybrid.ThinkingOption uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
13
High / Critical
A05:2025 — Injection
3
Medium
A07:2025 — Authentication Failures
1
Medium
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — 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.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Code Duplication: Edited copy of a member (14 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 — 9
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 — 112
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 — 248
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 17
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 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 44 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, 185 of 369 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) 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 (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — 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 an ADMISSION gap, not an environment fault: it declares a published package (internal/lintchecks/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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. `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridInferenceViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/ChatViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/ServerPromptTemplateViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/SvgViewModel.kt`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX6 Interface segregation — not measured this run — 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 (admob/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: roject with invalid directory
Configuring project ':internal' without an existing directory is not allowed. The configured projectDirectory 'admo…; runtime evidence skipped (launch chosen because admob/app/build.gradle.kts applies the Android application plugin and admob/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. 'com.google.firebase.firestore' is imported (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 'com.google.firebase.firestore' is imported (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 'com.google.firebase.firestore' is imported (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 'com.google.firebase.firestore' is imported (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
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.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
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.
Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with FunctionCallingViewModel.runTest (cyclomatic 26), FunctionCallingScreenKt.FunctionCallingScreen (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.3 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.
Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with FunctionCallingViewModel.runTest (cognitive 54). — Refactoring it lifts Cognitive Complexity from 8.4 to about 9.0/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 7 MethodTooLong finding(s) in God Classes — start with FunctionCallingScreen.kt, FunctionCallingViewModel.kt, ThinkingModeScreen.kt. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
45 duplicated block group(s) detected. A further 30 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Edited copy of a member (14 corresponding lines) · ×3storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java:158
+ 48 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with AnonymousAuthFragment.kt, FunctionCallingViewModel.kt, SystemInstructionScreen.kt. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with FunctionCallingScreen.kt (3), Theme.kt. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with FirebaseUIFragment.kt, SystemInstructionViewModel.kt, MultiFactorSignInFragment.java. — One of this dimension's main actionable groups (4 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.
33 production modules (Gradle+npm), 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; 0 module(s) off the main sequence, with abstractness counted on 17 of the 33 (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 dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 559 artifact(s) resolved, 242 of them gradable against Maven Central, and 178 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
Outdated (compile): com.google.guava:guava · ×178
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Secret scan ran and found no leaked secrets. 3 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material. 1 password hash(es) are listed to check and are not counted as leaked credentials.
REDACTED
✓ On the Gold path — maintain.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 11 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 35 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. 10 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 52 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.
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt. Counted over 110 of the 285 production source files in this repository: 157 are under the ~2,400-byte size floor this dimension measures over, and the remaining 18 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
14 deducted task-comment markers across 21735 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 14 TodoComment finding(s) in Explicit Debt — start with MyFirebaseMessagingService.kt (3), MyFirebaseMessagingService.java (3), MovieDetailViewModel.kt (2). — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 17 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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).
3 finding(s): 0 critical, 0 high, 3 medium, 0 low. semgrep hit a parse error in 16 file(s) — `admob/gradlew` (line 72, line 174), `analytics/gradlew` (line 72, line 174), `appdistribution/gradlew` (line 72, line 174), `auth/gradlew` (line 72, line 174), `config/gradlew` (line 72, line 174), … (+11 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
57 of 128 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PhoneAuthFragment.java. Counted over 128 of the 285 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 57 Orphaned file finding(s) in Knowledge Freshness — start with MainActivity.java (6), MainActivity.kt (2), PhoneAuthFragment.java. — One of this dimension's main actionable groups (57 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with MainActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 17 platform declaration(s) and 117 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.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels3.5 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — REDACTED:110
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — REDACTED:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
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.
What to do
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.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/android.yml:4
`functions/functions/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — functions/functions/package.json:7
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://storage.googleapis.com/code.getmdl.io/1.0.6/material.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup. — REDACTED:8
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — functions/firebase.json:1
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
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 `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.
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.
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.
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.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 6 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: this repository stores data through 'com.google.firebase.firestore' (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'com.google.firebase.firestore' (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.google.firebase.firestore' (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
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
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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 image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's 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 JavaScript 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.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 35% of this repository's production lines — kotlin (14,086 lines), python (87 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
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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: roject with invalid directory
Configuring project ':internal' without an existing directory is not allowed. The configured projectDirectory 'admo…; runtime evidence skipped (launch chosen because admob/app/build.gradle.kts applies the Android application plugin and admob/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: this repository stores data through 'com.google.firebase.firestore' (firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/FilterDialogFragment.kt:12) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
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 — ~670 lines of test source are present (.java) 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 .java suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
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; comments in this repository's .java, .kt, .py source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
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) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not 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 (28 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's JVM, JavaScript/TypeScript source (18 module(s), 236 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — 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
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's 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.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label REDACTED:110— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
TodoComment messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin/MyFirebaseMessagingService.kt:42— // TODO(developer): Handle FCM messages here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment messaging/app/src/main/java/com/google/firebase/quickstart/fcm/java/MyFirebaseMessagingService.java:82— // TODO(developer): Handle FCM messages here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin/MyFirebaseMessagingService.kt:167— // TODO: Implement this method to send FCM registration to your app server. — 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 messaging/app/src/main/java/com/google/firebase/quickstart/fcm/java/MyFirebaseMessagingService.java:207— // TODO: Implement this method to send FCM registration to your app server. — 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 messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin/MyFirebaseMessagingService.kt:179— // TODO: Implement this method to remove FCM registration from your app server. — 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 messaging/app/src/main/java/com/google/firebase/quickstart/fcm/java/MyFirebaseMessagingService.java:219— // TODO: Implement this method to remove FCM registration from your app server. — 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 messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin/MyWorker.kt:12— // TODO(developer): add long running task here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment messaging/app/src/main/java/com/google/firebase/quickstart/fcm/java/MyWorker.java:22— // TODO(developer): add long running task here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ChatScreen.kt:259— // TODO: show a human readable version of audio, PDFs and videos — 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 dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/search/Navigation.kt:17— // TODO: Call composable — 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 dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/profile/ProfileScreen.kt:138— // TODO(thatfiredev): Handle cases where the list is too long to display — 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 dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/moviedetail/UserReviews.kt:83— // TODO(thatfiredev): Handle cases where the list is too long to display — 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 dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/moviedetail/MovieDetailViewModel.kt:65— // TODO(thatfiredev): hide the button if there's no user logged in — 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 dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/moviedetail/MovieDetailViewModel.kt:85— // TODO(thatfiredev): hide the button if there's no user logged in — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: FunctionCallingScreenKt.FunctionCallingScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:44— MethodTooLong — FunctionCallingScreen runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FunctionCallingViewModel.runTest firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:224— MethodTooLong — runTest runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ThinkingModeScreenKt.ThinkingModeScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:44— MethodTooLong — ThinkingModeScreen runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× 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: SystemInstructionScreenKt.SystemInstructionScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:44— MethodTooLong — SystemInstructionScreen runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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: HybridImagePatternScreenKt.HybridImagePatternScreen firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/HybridImagePatternScreen.kt:63— MethodTooLong — HybridImagePatternScreen runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: ChatScreenKt.ChatBubbleItem firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ChatScreen.kt:181— MethodTooLong — ChatBubbleItem runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ThinkingModeViewModel.runTest firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:113— MethodTooLong — runTest runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (20 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/AnonymousAuthFragment.kt:126— auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/AnonymousAuthFragment.kt:126-145 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt:178-197 — 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 (20 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:143— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:143-162 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:92-111 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:143` 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) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:153— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:153-172 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:154-173 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:153` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:160— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:160-179 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:227-246 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (20 lines × 2) admob/app/src/main/java/com/google/samples/quickstart/admobexample/java/MainActivity.java:1— admob/app/src/main/java/com/google/samples/quickstart/admobexample/java/MainActivity.java:1-31 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MainActivity.java:1-20 — 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 `admob/app/src/main/java/com/google/samples/quickstart/admobexample/java/MainActivity.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. Note first that the copies are not typed on the same thing: `R` names `com.google.firebase.quickstart.auth.R` in one and `com.google.samples.quickstart.admobexample.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 (16 lines × 2) dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/theme/Theme.kt:43— dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/theme/Theme.kt:43-58 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/theme/Theme.kt:42-57 — before extracting anything, compare `dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/theme/Theme.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/theme/Theme.kt` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (16 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:94— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:94-109 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:97-112 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 204 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:143— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:143-158 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:144-159 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 204 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:143` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:174— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:174-189 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:175-190 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 204 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:174` 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) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FirebaseUIFragment.kt:88— auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FirebaseUIFragment.kt:88-98 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/GoogleSignInFragment.kt:179-188 — 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FirebaseUIFragment.kt:88` 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) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:223— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:223-232 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:231-240 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:223` 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) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorSignInFragment.java:62— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorSignInFragment.java:62-71 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorUnenrollFragment.java:41-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java:273— firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java:273-282 | functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:252-261 — 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 `firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java:273` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java:158— storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java:158-171 | storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyUploadService.java:166-179 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MyDownloadService.kt:109— storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MyDownloadService.kt:109-127 | storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MyUploadService.kt:133-146 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/CustomAuthFragment.java:107— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/CustomAuthFragment.java:107-120 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PhoneAuthFragment.java:227-244 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (17 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ServerPromptScreen.kt:105— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ServerPromptScreen.kt:105-121 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SvgScreen.kt:112-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:135— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:135-151 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:136-152 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:135` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:208— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:208-224 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java:150-166 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:68— database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:68-93 | database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:95-120 — 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) database/app/src/main/java/com/google/firebase/quickstart/database/kotlin/SignInFragment.kt:57— database/app/src/main/java/com/google/firebase/quickstart/database/kotlin/SignInFragment.kt:57-82 | database/app/src/main/java/com/google/firebase/quickstart/database/kotlin/SignInFragment.kt:84-109 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×2
Edited copies of one member (4 members, 16+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:149— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:149-164 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FirebaseUIFragment.java:108-124 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GenericIdpFragment.java:174-191 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.java:210-227 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 16+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FacebookLoginFragment.kt:116— auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FacebookLoginFragment.kt:116-131 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FirebaseUIFragment.kt:82-98 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/GenericIdpFragment.kt:129-146 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/GoogleSignInFragment.kt:173-188 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:105— functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:105-125 | functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:129-148 — 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) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.java:127— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.java:127-146 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.java:186-208 — 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) firestore/app/src/main/java/com/google/firebase/example/fireeats/java/FilterDialogFragment.java:117— firestore/app/src/main/java/com/google/firebase/example/fireeats/java/FilterDialogFragment.java:117-128 | firestore/app/src/main/java/com/google/firebase/example/fireeats/java/FilterDialogFragment.java:131-142 — 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) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:167— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:167-178 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/AutoFunctionCallViewModel.kt:64-79 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt:165— auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt:165-175 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/MultiFactorFragment.kt:93-111 — 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) analytics/app/src/main/java/com/google/firebase/quickstart/analytics/java/MainActivity.java:243— analytics/app/src/main/java/com/google/firebase/quickstart/analytics/java/MainActivity.java:243-254 | analytics/app/src/main/java/com/google/firebase/quickstart/analytics/java/MainActivity.java:260-270 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java:269— firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java:269-284 | functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:250-262 — 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) firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/MainFragment.kt:236— firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/MainFragment.kt:236-249 | functions/app/src/main/java/com/google/samples/quickstart/functions/kotlin/MainActivity.kt:213-225 — 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 (6 lines × 2) admob/app/src/main/java/com/google/samples/quickstart/admobexample/kotlin/MainActivity.kt:10— admob/app/src/main/java/com/google/samples/quickstart/admobexample/kotlin/MainActivity.kt:10-15 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/MainActivity.kt:10-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: `R` names `com.google.firebase.quickstart.auth.R` in one and `com.google.samples.quickstart.admobexample.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 (6 lines × 2) firestore/app/src/main/java/com/google/firebase/example/fireeats/java/FilterDialogFragment.java:64— firestore/app/src/main/java/com/google/firebase/example/fireeats/java/FilterDialogFragment.java:64-69 | firestore/app/src/main/java/com/google/firebase/example/fireeats/java/RatingDialogFragment.java:66-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:88— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:88-96 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridInferenceViewModel.kt:89-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorSignInFragment.java:83— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorSignInFragment.java:83-91 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorUnenrollFragment.java:55-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorSignInFragment.java:83` 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.
FunctionCallingViewModel.runTest (cyclomatic 26) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:224— FunctionCallingViewModel.runTest has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
FunctionCallingScreenKt.FunctionCallingScreen (cyclomatic 17) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:44— FunctionCallingScreenKt.FunctionCallingScreen 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.
FunctionCallingViewModel.runTest (cognitive 54) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:224— FunctionCallingViewModel.runTest has cognitive complexity 54 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 6 (22 pts), boolean chains 2, error handling 2, match/switch 2 (nesting depth added 29). 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.
FunctionCallingScreenKt.FunctionCallingScreen (cognitive 28) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:44— FunctionCallingScreenKt.FunctionCallingScreen has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 6 (10 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChatScreenKt.ChatBubbleItem (cognitive 18) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ChatScreen.kt:181— ChatScreenKt.ChatBubbleItem has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Change coupling: MainActivity.kt ↔ FirebaseAISamples.kt firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/MainActivity.kt:1— `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/MainActivity.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/navigation/FirebaseAISamples.kt` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `7fdff7d7` Add hybrid function calling sample (#2855); `0f76ce25` [AI] Add Hybrid Image Pattern Finder sample (#2854); `f1a4663e` Add thinking mode view (#2848) — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (3 members, 111 shared lines) · ×1
Near-duplicate member family (3 members, 111 shared lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:46— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:46-352 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:46-287 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:46-313 — These 3 members are variants of one another: a block of 111 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 3 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 3 times.
Near-duplicate member pair (41 shared lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:104— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:104-162 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:56-111 — These two members are variants of one another: 41 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:49— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:49-86 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridInferenceViewModel.kt:51-87 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:66-111 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:151— functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:151-198 | functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:200-235 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/actordetail/ActorDetailScreen.kt:57— dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/actordetail/ActorDetailScreen.kt:57-94 | dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/feature/movies/MoviesScreen.kt:38-66 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:94— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:94-116 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/CustomAuthFragment.java:102-122 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:111-139 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:115-140 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt:137— auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt:137-163 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/MultiFactorFragment.kt:68-91 — 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:169— functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:169-195 | functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:212-232 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:99— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:99-114 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:122-137 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:123-138 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 23+ corresponding lines) · ×1
Edited copies of one member (4 members, 23+ corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/AnonymousAuthFragment.kt:60— auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/AnonymousAuthFragment.kt:60-82 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/CustomAuthFragment.kt:72-94 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/EmailPasswordFragment.kt:68-96 | auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/FacebookLoginFragment.kt:82-107 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) database/app/src/main/java/com/google/firebase/quickstart/database/java/PostDetailFragment.java:181— database/app/src/main/java/com/google/firebase/quickstart/database/java/PostDetailFragment.java:181-199 | database/app/src/main/java/com/google/firebase/quickstart/database/java/PostDetailFragment.java:202-220 — 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 (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/components/ActorsList.kt:47— dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/components/ActorsList.kt:47-63 | dataconnect/app/src/main/java/com/google/firebase/example/dataconnect/ui/components/MoviesList.kt:41-62 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java:144— storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyDownloadService.java:144-153 | storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MyUploadService.java:151-161 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PasswordlessActivity.java:190— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PasswordlessActivity.java:190-198 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PhoneAuthFragment.java:81-88 — 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 copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/BaseActivity.java:32— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/BaseActivity.java:32-37 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/BaseFragment.java:32-38 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (50 lines × 3) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:303— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:303-352 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:238-287 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:264-313 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:303` 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 (31 lines × 3) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:54— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:54-84 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:57-87 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:57-87 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:54` 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, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:51` calls `mutableStateOf` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:54` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (29–30 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:57— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:57-86 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridInferenceViewModel.kt:59-87 — 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:193— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:193-215 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:194-216 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 204 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:120— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:120-141 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:121-142 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 204 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:120` 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 (21 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/HybridImagePatternScreen.kt:149— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/HybridImagePatternScreen.kt:149-169 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/HybridInferenceScreen.kt:114-134 — 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/HybridImagePatternScreen.kt:149` 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 (32 lines × 2) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:70— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:70-101 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:68-99 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 3) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:286— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:286-301 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:221-236 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:247-262 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:286` 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) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:113— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:113-124 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:62-73 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:113` 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–10 lines × 2) firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/MainFragment.kt:239— firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/MainFragment.kt:239-247 | functions/app/src/main/java/com/google/samples/quickstart/functions/kotlin/MainActivity.kt:215-224 — 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 `firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/MainFragment.kt:239` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 3) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:129— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:129-137 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:80-88 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:78-86 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:129` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:495— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:495-500 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:257-262 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:266-271 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:495` 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 × 3) functions/app/src/main/java/com/google/samples/quickstart/functions/kotlin/MainActivity.kt:254— functions/app/src/main/java/com/google/samples/quickstart/functions/kotlin/MainActivity.kt:254-266 | messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin/MainActivity.kt:109-121 | storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MainActivity.kt:277-289 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (14 lines × 3) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:187— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:187-200 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt:189-202 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/ThinkingModeScreen.kt:188-201 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 111 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 `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/FunctionCallingScreen.kt:187` 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) firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:166— firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt:166-173 | firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt:136-143 — before extracting anything, compare `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt` and `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/ThinkingModeViewModel.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt: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.
Duplicated block (24 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:182— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:182-205 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java:124-147 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (14–20 lines × 2) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:170— functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:170-189 | functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:213-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `task` to `Task<Integer>` in one and `Task<String>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:79— database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:79-93 | database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:106-120 — 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 `database/app/src/main/java/com/google/firebase/quickstart/database/java/SignInFragment.java:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 5) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:97— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:97-110 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/CustomAuthFragment.java:105-118 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:120-133 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:150-163 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:121-134 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:113` calls `hideProgressBar` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/CustomAuthFragment.java:120` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:77— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:77-89 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java:69-81 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:77` 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 × 4) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:104— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:104-116 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:146-157 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:127-139 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:128-140 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FacebookLoginFragment.java:144` calls `getInstance`, `logOut` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:120` 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–11 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FirebaseUIFragment.java:114— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FirebaseUIFragment.java:114-124 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.java:217-225 — 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/FirebaseUIFragment.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.
Duplicated block (6–8 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:140— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java:140-145 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PhoneAuthFragment.java:225-232 — 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.java: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.
Duplicated block (12 lines × 3) functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:299— functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java:299-310 | messaging/app/src/main/java/com/google/firebase/quickstart/fcm/java/MainActivity.java:130-141 | storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MainActivity.java:296-307 — 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 (5 lines × 2) auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:249— auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:249-253 | auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java:169-173 — before extracting anything, compare `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java` and `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java:249` 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.
End-of-life runtime: Node.js 20 functions/functions/package.json:5— functions/functions/package.json declares Node.js 20 as this project's engines.node, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Third-party script without Subresource Integrity REDACTED:8— `https://storage.googleapis.com/code.getmdl.io/1.0.6/material.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup.
Orphaned file auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PhoneAuthFragment.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/PhoneAuthFragment.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 firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.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 storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MainActivity.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 functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.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 storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MainActivity.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 database/app/src/main/java/com/google/firebase/quickstart/database/java/PostDetailFragment.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 analytics/app/src/main/java/com/google/firebase/quickstart/analytics/java/MainActivity.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 messaging/app/src/main/java/com/google/firebase/quickstart/fcm/java/MyFirebaseMessagingService.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 firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/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 database/app/src/main/java/com/google/firebase/quickstart/database/kotlin/PostDetailFragment.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GoogleSignInFragment.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 crash/app/src/main/java/com/google/samples/quickstart/crash/java/CustomKeySamples.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 firestore/app/src/main/java/com/google/firebase/example/fireeats/java/RestaurantDetailFragment.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PasswordlessActivity.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 messaging/app/src/main/java/com/google/firebase/quickstart/fcm/kotlin/MyFirebaseMessagingService.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorFragment.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 crash/app/src/main/java/com/google/samples/quickstart/crash/kotlin/CustomKeySamples.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 firestore/app/src/main/java/com/google/firebase/example/fireeats/kotlin/RestaurantDetailFragment.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/PasswordlessActivity.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/GenericIdpFragment.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/MultiFactorEnrollFragment.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 auth/app/src/main/java/com/google/firebase/quickstart/auth/java/AnonymousAuthFragment.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 database/app/src/main/java/com/google/firebase/quickstart/database/java/listfragments/PostListFragment.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: firestore/app/build.gradle.kts, auth/app/build.gradle.kts, messaging/app/build.gradle.kts, crash/app/build.gradle.kts, functions/app/build.gradle.kts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (9 single-owned of 110 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; 110 of the 285 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/SystemInstructionScreen.kt, firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/SystemInstructionViewModel.kt, firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/ui/navigation/MainMenuScreen.kt, firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/SvgViewModel.kt.
No ADRs found build.gradle.kts:4— 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 `build.gradle.kts` makes this repository a deployable product (line 4).
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 57 of 128 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 128 of the 285 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: auth/app/src/main/java/com/google/firebase/quickstart/auth/java/PhoneAuthFragment.java, auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/PhoneAuthFragment.kt, firestore/app/src/main/java/com/google/firebase/example/fireeats/java/MainFragment.java, storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/java/MainActivity.java, functions/app/src/main/java/com/google/samples/quickstart/functions/java/MainActivity.java, auth/app/src/main/java/com/google/firebase/quickstart/auth/java/EmailPasswordFragment.java, storage/app/src/main/java/com/google/firebase/quickstart/firebasestorage/kotlin/MainActivity.kt, database/app/src/main/java/com/google/firebase/quickstart/database/java/PostDetailFragment.java (and 49 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST .github/workflows/android.yml:4— 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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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 dependency-update automation functions/functions/package.json:7— `functions/functions/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No security response headers detected functions/firebase.json:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `firebase.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
Duplicated predicate firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt:172— `city == null || state == null || date == null` appears character-identically in 3 files — firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/FunctionCallingViewModel.kt, firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/AutoFunctionCallViewModel.kt, firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/WeatherChatViewModel.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.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridImagePatternViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/hybrid/HybridInferenceViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/ChatViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/ServerPromptTemplateViewModel.kt`, `firebase-ai/app/src/main/java/com/google/firebase/quickstart/ai/feature/text/SvgViewModel.kt`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d63c-280e-7b6a-8b94-10f4747affe1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 112 · Recommendations: 70 · Info: 178 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 18:47 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.