Executive summary
firebase/FirebaseUI-Android falls short of our standard for production because its Dependencies dimensions are rated Weak. It scores 72 out of 100, which alone would earn Strong, but it is rated Adequate: a rating can't sit more than one step above its weakest group.
Production Readiness, at 65, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 74.
Two passwords or keys are open to anyone who can read the repository. One pipeline step installs packages that can change without warning, and one set of files in separate parts keeps changing together, which points to a hidden dependency. Replacing each exposed password or key, pinning what the pipeline installs and making the hidden dependencies explicit would close these risks.
The product code is 30,264 lines, about €97,000 to rebuild.
If Production Readiness rose from 65 to 70, the lowest score rated Strong, the score would rise from 72 to about 74.
New since the last survey: 62 findings
- God Classes · ClassTooLong: AuthException auth/src/main/java/com/firebase/ui/auth/AuthException.kt
- God Classes · MethodTooLong: EmailEntryStepKt.EmailEntryStep app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/EmailEntryStep.kt
- God Classes · ClassTooLong: DefaultAuthUIStringProvider auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt
- Code Duplication · Near-duplicate member pair (56 shared lines) app/src/main/java/com/firebaseui/android/demo/MainActivity.kt
- Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/common/AuthPage.kt
- Code Duplication · Edited copy of a member (121 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/ResetPasswordUI.kt
- Code Duplication · Edited copy of a member (81 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt
- Code Duplication · Edited copy of a member (74 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/mfa/MfaChallengeUI.kt
- Code Duplication · Edited copy of a member (71 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt
- Code Duplication · Edited copy of a member (67 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt
- Code Duplication · Edited copy of a member (48 corresponding lines) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Edited copy of a member (44 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt
- Code Duplication · Edited copy of a member (39 corresponding lines) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Edited copy of a member (35 corresponding lines) auth/src/main/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt
- Code Duplication · Edited copy of a member (33 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt
- Code Duplication · Edited copy of a member (28 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/AuthChooserActivity.kt
- Code Duplication · Edited copy of a member (43 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt
- Code Duplication · Edited copy of a member (19 corresponding lines) database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java
- Code Duplication · Edited copy of a member (29 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/ResetPasswordUI.kt
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Edited copy of a member (28 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/EnterPhoneNumberUI.kt
- Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) auth/src/main/java/com/firebase/ui/auth/configuration/validators/EmailValidator.kt
- Code Duplication · Edited copy of a member (7 corresponding lines) database/src/main/java/com/firebase/ui/database/paging/DatabasePagingKey.java
- Code Duplication · Edited copy of a member (17 corresponding lines) database/src/main/java/com/firebase/ui/database/paging/FirebaseRecyclerPagingAdapter.java
- Code Duplication · Edited copy of a member (7 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt
- Code Duplication · Edited copy of a member (11 corresponding lines) firestore/src/main/java/com/firebase/ui/firestore/paging/FirestorePagingOptions.java
- Code Duplication · Edited copy of a member (9 corresponding lines) database/src/main/java/com/firebase/ui/database/paging/FirebaseRecyclerPagingAdapter.java
- Code Duplication · Edited copy of a member (4 corresponding lines) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Duplicated block (37 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Duplicated block (28 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt
- Code Duplication · Duplicated block (27 lines × 2) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (20 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Duplicated block (19 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/AuthenticatedUI.kt
- Code Duplication · Duplicated block (19 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/CustomMethodPickerDemoActivity.kt
- Code Duplication · Duplicated block (19 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt
- Code Duplication · Duplicated block (18 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt
- Code Duplication · Duplicated block (15–16 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/CustomMethodPickerDemoActivity.kt
- Code Duplication · Duplicated block (13–15 lines × 11) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (13–15 lines × 6) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/common/AuthPage.kt
- Code Duplication · Duplicated block (15 lines × 2) auth/src/main/java/com/firebase/ui/auth/FirebaseAuthUI.kt
- Code Duplication · Duplicated block (14 lines × 2) app/src/main/java/com/firebaseui/android/demo/storage/StorageDemoActivity.kt
- Code Duplication · Duplicated block (14 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt
- Code Duplication · Duplicated block (14 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt
- Code Duplication · Duplicated block (13 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt
- Code Duplication · Duplicated block (11–12 lines × 3) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (11 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/mfa/MfaChallengeUI.kt
- Code Duplication · Duplicated block (11 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt
- Code Duplication · Duplicated block (9 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Duplicated block (17 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/AuthChooserActivity.kt
- Code Duplication · Duplicated block (13 lines × 6) app/src/main/java/com/firebaseui/android/demo/MainActivity.kt
- Code Duplication · Duplicated block (11 lines × 8) app/src/main/java/com/firebaseui/android/demo/MainActivity.kt
- Code Duplication · Duplicated block (13 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/mfa/pages/ConfigureSmsStep.kt
- Code Duplication · Duplicated block (9 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/LoginStep.kt
- Code Duplication · Duplicated block (10 lines × 12) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (12 lines × 4) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/LoginStep.kt
- Code Duplication · Duplicated block (11 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/EmailEntryStep.kt
- Code Duplication · Duplicated block (9 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/phone/pages/PhoneEntryStep.kt
- Churn × Complexity Hotspots · Hotspot: auth/src/main/java/com/firebase/ui/auth/AuthException.kt auth/src/main/java/com/firebase/ui/auth/AuthException.kt
- Churn × Complexity Hotspots · Repeated repair: auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/GoogleAuthProvider+FirebaseAuthUI.kt auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/GoogleAuthProvider+FirebaseAuthUI.kt
- Churn × Complexity Hotspots · Repeated repair: auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt
- Churn × Complexity Hotspots · Repeated repair: auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/AuthUIStringProvider.kt auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/AuthUIStringProvider.kt
- Churn × Complexity Hotspots · Repeated repair: auth/src/main/java/com/firebase/ui/auth/ui/components/TopLevelDialogController.kt auth/src/main/java/com/firebase/ui/auth/ui/components/TopLevelDialogController.kt
Fixed since the last survey: 18 findings
- Cognitive Complexity · BaseStringScript.ProcessFile (cognitive 19) scripts/translations/base_string_script.py
- Code Duplication · Duplicated block (37 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Duplicated block (28 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt
- Code Duplication · Duplicated block (27 lines × 2) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (20 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt
- Code Duplication · Duplicated block (19 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt
- Code Duplication · Duplicated block (18 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt
- Code Duplication · Duplicated block (14–16 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/method_picker/AuthMethodPicker.kt
- Code Duplication · Duplicated block (13–15 lines × 8) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (15 lines × 2) auth/src/main/java/com/firebase/ui/auth/FirebaseAuthUI.kt
- Code Duplication · Duplicated block (14 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt
- Code Duplication · Duplicated block (14 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt
- Code Duplication · Duplicated block (13 lines × 3) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (13 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt
- Code Duplication · Duplicated block (11–12 lines × 3) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
- Code Duplication · Duplicated block (11 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt
- Code Duplication · Duplicated block (16 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/AuthChooserActivity.kt
- Code Duplication · Duplicated block (10 lines × 12) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt
Rebuild cost: about €97,000 · Estimate
| Cost to rebuild | €32,000 to €160,000, for 535 to 1,696 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 72. 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: 30,264 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook | 2 com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google | 3 com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone | 4 com.firebase.ui.auth.data | 5 com.firebase.ui.auth.util.SignInPreferenceManager | 6 com.firebase.ui.common | 7 scripts.translations.base_string_script | 8 com.firebase.ui.auth.AuthState | 9 com.firebase.ui.auth.configuration.string_provider | 10 com.firebase.ui.auth.configuration.theme.AuthUITheme | 11 com.firebase.ui.auth.ui.screens.AuthRoute.Email | 12 com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment | 13 com.firebase.ui.auth.ui.screens.AuthRoute.Phone | 14 com.firebase.ui.auth.util.EmailLinkPersistenceManager | 15 com.firebase.ui.database | 16 com.firebase.ui.firestore | 17 com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector | 18 com.firebase.ui.auth.AuthException | 19 com.firebase.ui.auth.AuthState.Reauthentication | 20 com.firebase.ui.auth.configuration.theme | 21 com.firebase.ui.auth.util | 22 com.firebaseui.lint | 23 com.firebase.ui.auth.configuration.auth_provider.AuthProvider | 24 com.firebase.ui.auth.configuration.auth_provider | 25 com.firebase.ui.auth.configuration | 26 com.firebase.ui.auth.ui.method_picker | 27 com.firebase.ui.auth | 28 com.firebase.ui.auth.configuration.PasswordRule | 29 com.firebase.ui.auth.configuration.validators | 30 com.firebase.ui.auth.mfa | 31 com.firebase.ui.auth.FirebaseAuthActivity | 32 com.firebase.ui.auth.FirebaseAuthUI | 33 com.firebase.ui.auth.ui.components | 34 com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState | 35 com.firebase.ui.auth.ui.screens.email | 36 com.firebase.ui.auth.ui.screens.phone | 37 com.firebase.ui.auth.ui.screens.AuthRoute | 38 com.firebase.ui.auth.ui.screens.reauth | 39 com.firebase.ui.auth.ui.screens | 40 com.firebase.ui.auth.ui.screens.mfa |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook | ||||||||||||||||||||||||||||||||||||||||
| 2 com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google | ||||||||||||||||||||||||||||||||||||||||
| 3 com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone | ||||||||||||||||||||||||||||||||||||||||
| 4 com.firebase.ui.auth.data | ||||||||||||||||||||||||||||||||||||||||
| 5 com.firebase.ui.auth.util.SignInPreferenceManager | ||||||||||||||||||||||||||||||||||||||||
| 6 com.firebase.ui.common | ||||||||||||||||||||||||||||||||||||||||
| 7 scripts.translations.base_string_script | ||||||||||||||||||||||||||||||||||||||||
| 8 com.firebase.ui.auth.AuthState | 1 | 14 | ||||||||||||||||||||||||||||||||||||||
| 9 com.firebase.ui.auth.configuration.string_provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 com.firebase.ui.auth.configuration.theme.AuthUITheme | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 com.firebase.ui.auth.ui.screens.AuthRoute.Email | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 com.firebase.ui.auth.ui.screens.AuthRoute.Phone | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 com.firebase.ui.auth.util.EmailLinkPersistenceManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 com.firebase.ui.database | 8 | |||||||||||||||||||||||||||||||||||||||
| 16 com.firebase.ui.firestore | 6 | |||||||||||||||||||||||||||||||||||||||
| 17 com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 com.firebase.ui.auth.AuthException | 1 | 22 | ||||||||||||||||||||||||||||||||||||||
| 19 com.firebase.ui.auth.AuthState.Reauthentication | 10 | |||||||||||||||||||||||||||||||||||||||
| 20 com.firebase.ui.auth.configuration.theme | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 com.firebase.ui.auth.util | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 com.firebaseui.lint | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 com.firebase.ui.auth.configuration.auth_provider.AuthProvider | 1 | 2 | 1 | 1 | 4 | 2 | ||||||||||||||||||||||||||||||||||
| 24 com.firebase.ui.auth.configuration.auth_provider | 1 | 2 | 2 | 1 | 1 | 5 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 25 com.firebase.ui.auth.configuration | 3 | 4 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 com.firebase.ui.auth.ui.method_picker | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 com.firebase.ui.auth | 2 | 2 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 28 com.firebase.ui.auth.configuration.PasswordRule | 6 | 6 | ||||||||||||||||||||||||||||||||||||||
| 29 com.firebase.ui.auth.configuration.validators | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 com.firebase.ui.auth.mfa | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 31 com.firebase.ui.auth.FirebaseAuthActivity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 com.firebase.ui.auth.FirebaseAuthUI | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 com.firebase.ui.auth.ui.components | 1 | 1 | 5 | 1 | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||
| 34 com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 com.firebase.ui.auth.ui.screens.email | 1 | 6 | 4 | |||||||||||||||||||||||||||||||||||||
| 36 com.firebase.ui.auth.ui.screens.phone | 3 | 1 | 4 | 4 | ||||||||||||||||||||||||||||||||||||
| 37 com.firebase.ui.auth.ui.screens.AuthRoute | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 38 com.firebase.ui.auth.ui.screens.reauth | 2 | 1 | 3 | 2 | 2 | 3 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||
| 39 com.firebase.ui.auth.ui.screens | 2 | 1 | 3 | 1 | 4 | 3 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||
| 40 com.firebase.ui.auth.ui.screens.mfa | 2 | 1 | 1 | 7 | 1 | 10 | 1 |
8→19 com.firebase.ui.auth.AuthState uses com.firebase.ui.auth.AuthState.Reauthentication part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.AuthState uses a type in com.firebase.ui.auth.AuthState.Reauthentication.
- The types involved
com.firebase.ui.auth.AuthState.Reauthentication→com.firebase.ui.auth.AuthState.Reauthentication.Request
- Direction
- com.firebase.ui.auth.AuthState uses com.firebase.ui.auth.AuthState.Reauthentication, so a change to com.firebase.ui.auth.AuthState.Reauthentication can break com.firebase.ui.auth.AuthState, while a change to com.firebase.ui.auth.AuthState can't break com.firebase.ui.auth.AuthState.Reauthentication.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→27 com.firebase.ui.auth.AuthState uses com.firebase.ui.auth part of a loop✕
- Connections
- 14 pairs of types, where a type in com.firebase.ui.auth.AuthState uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.AuthState.Aborted→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.Cancelled→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.EmailSignInLinkSent→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.Error→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.Idle→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.Loading→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.PasswordResetLinkSent→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.PhoneNumberVerificationRequired→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.Reauthentication→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.RequiresEmailVerification→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.RequiresMfa→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.RequiresProfileCompletion→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.SMSAutoVerified→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.AuthState.Success→com.firebase.ui.auth.AuthState
- Direction
- com.firebase.ui.auth.AuthState uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.AuthState, while a change to com.firebase.ui.auth.AuthState can't break com.firebase.ui.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→25 com.firebase.ui.auth.configuration.string_provider uses com.firebase.ui.auth.configuration part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.string_provider uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.configuration.string_provider.AuthUIStringProviderSample→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth.configuration.string_provider uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.configuration.string_provider, while a change to com.firebase.ui.auth.configuration.string_provider can't break com.firebase.ui.auth.configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 com.firebase.ui.auth.configuration.theme.AuthUITheme uses com.firebase.ui.auth.configuration.theme part of a loop✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.configuration.theme.AuthUITheme uses a type in com.firebase.ui.auth.configuration.theme.
- The types involved
com.firebase.ui.auth.configuration.theme.AuthUITheme.Companion→com.firebase.ui.auth.configuration.theme.AuthUIThemecom.firebase.ui.auth.configuration.theme.AuthUITheme.ProviderStyle→com.firebase.ui.auth.configuration.theme.AuthUIAsset
- Direction
- com.firebase.ui.auth.configuration.theme.AuthUITheme uses com.firebase.ui.auth.configuration.theme, so a change to com.firebase.ui.auth.configuration.theme can break com.firebase.ui.auth.configuration.theme.AuthUITheme, while a change to com.firebase.ui.auth.configuration.theme.AuthUITheme can't break com.firebase.ui.auth.configuration.theme.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→37 com.firebase.ui.auth.ui.screens.AuthRoute.Email uses com.firebase.ui.auth.ui.screens.AuthRoute part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute.Email uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Email.Step→com.firebase.ui.auth.ui.screens.AuthRoute.Destination
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute.Email uses com.firebase.ui.auth.ui.screens.AuthRoute, so a change to com.firebase.ui.auth.ui.screens.AuthRoute can break com.firebase.ui.auth.ui.screens.AuthRoute.Email, while a change to com.firebase.ui.auth.ui.screens.AuthRoute.Email can't break com.firebase.ui.auth.ui.screens.AuthRoute.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→37 com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment uses com.firebase.ui.auth.ui.screens.AuthRoute part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.Step→com.firebase.ui.auth.ui.screens.AuthRoute.Destination
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment uses com.firebase.ui.auth.ui.screens.AuthRoute, so a change to com.firebase.ui.auth.ui.screens.AuthRoute can break com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment, while a change to com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment can't break com.firebase.ui.auth.ui.screens.AuthRoute.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→37 com.firebase.ui.auth.ui.screens.AuthRoute.Phone uses com.firebase.ui.auth.ui.screens.AuthRoute part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute.Phone uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Phone.Step→com.firebase.ui.auth.ui.screens.AuthRoute.Destination
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute.Phone uses com.firebase.ui.auth.ui.screens.AuthRoute, so a change to com.firebase.ui.auth.ui.screens.AuthRoute can break com.firebase.ui.auth.ui.screens.AuthRoute.Phone, while a change to com.firebase.ui.auth.ui.screens.AuthRoute.Phone can't break com.firebase.ui.auth.ui.screens.AuthRoute.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 com.firebase.ui.auth.util.EmailLinkPersistenceManager uses com.firebase.ui.auth.util part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.util.EmailLinkPersistenceManager uses a type in com.firebase.ui.auth.util.
- The types involved
com.firebase.ui.auth.util.EmailLinkPersistenceManager.DefaultPersistenceManager→com.firebase.ui.auth.util.PersistenceManager
- Direction
- com.firebase.ui.auth.util.EmailLinkPersistenceManager uses com.firebase.ui.auth.util, so a change to com.firebase.ui.auth.util can break com.firebase.ui.auth.util.EmailLinkPersistenceManager, while a change to com.firebase.ui.auth.util.EmailLinkPersistenceManager can't break com.firebase.ui.auth.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→6 com.firebase.ui.database uses com.firebase.ui.common✕
- Connections
- 8 pairs of types, where a type in com.firebase.ui.database uses a type in com.firebase.ui.common.
- The types involved
com.firebase.ui.database.CachingSnapshotParser→com.firebase.ui.common.BaseCachingSnapshotParsercom.firebase.ui.database.CachingSnapshotParser→com.firebase.ui.common.BaseSnapshotParsercom.firebase.ui.database.ChangeEventListener→com.firebase.ui.common.BaseChangeEventListenercom.firebase.ui.database.FirebaseIndexArray→com.firebase.ui.common.ChangeEventTypecom.firebase.ui.database.FirebaseListAdapter→com.firebase.ui.common.ChangeEventTypecom.firebase.ui.database.FirebaseRecyclerAdapter→com.firebase.ui.common.ChangeEventTypecom.firebase.ui.database.ObservableSnapshotArray→com.firebase.ui.common.BaseObservableSnapshotArraycom.firebase.ui.database.SnapshotParser→com.firebase.ui.common.BaseSnapshotParser
- Direction
- com.firebase.ui.database uses com.firebase.ui.common, so a change to com.firebase.ui.common can break com.firebase.ui.database, while a change to com.firebase.ui.database can't break com.firebase.ui.common.
- Position
- Below the diagonal: com.firebase.ui.database uses a module listed above it, which is the healthy direction.
16→6 com.firebase.ui.firestore uses com.firebase.ui.common✕
- Connections
- 6 pairs of types, where a type in com.firebase.ui.firestore uses a type in com.firebase.ui.common.
- The types involved
com.firebase.ui.firestore.CachingSnapshotParser→com.firebase.ui.common.BaseCachingSnapshotParsercom.firebase.ui.firestore.CachingSnapshotParser→com.firebase.ui.common.BaseSnapshotParsercom.firebase.ui.firestore.ChangeEventListener→com.firebase.ui.common.BaseChangeEventListenercom.firebase.ui.firestore.FirestoreRecyclerAdapter→com.firebase.ui.common.ChangeEventTypecom.firebase.ui.firestore.ObservableSnapshotArray→com.firebase.ui.common.BaseObservableSnapshotArraycom.firebase.ui.firestore.SnapshotParser→com.firebase.ui.common.BaseSnapshotParser
- Direction
- com.firebase.ui.firestore uses com.firebase.ui.common, so a change to com.firebase.ui.common can break com.firebase.ui.firestore, while a change to com.firebase.ui.firestore can't break com.firebase.ui.common.
- Position
- Below the diagonal: com.firebase.ui.firestore uses a module listed above it, which is the healthy direction.
17→22 com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector uses com.firebaseui.lint part of a loop✕
- Connections
- 2 pairs of types, where a type in com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector uses a type in com.firebaseui.lint.
- The types involved
com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector.AdapterStartListeningMethodVisitor→com.firebaseui.lint.AdapterReferencecom.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector.AdapterStopListeningMethodVisitor→com.firebaseui.lint.AdapterReference
- Direction
- com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector uses com.firebaseui.lint, so a change to com.firebaseui.lint can break com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector, while a change to com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector can't break com.firebaseui.lint.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→9 com.firebase.ui.auth.AuthException uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.AuthException uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.AuthException.Companion→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.AuthException uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.AuthException, while a change to com.firebase.ui.auth.AuthException can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.AuthException uses a module listed above it, which is the healthy direction.
18→27 com.firebase.ui.auth.AuthException uses com.firebase.ui.auth part of a loop✕
- Connections
- 22 pairs of types, where a type in com.firebase.ui.auth.AuthException uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.AuthException.AccountLinkingRequiredException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.AuthCancelledException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.Companion→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.DifferentSignInMethodRequiredException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.EmailAlreadyInUseException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.EmailLinkCrossDeviceLinkingException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.EmailLinkDifferentAnonymousUserException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.EmailLinkPromptForEmailException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.EmailLinkWrongDeviceException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.EmailMismatchException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.InvalidCredentialsException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.InvalidEmailLinkException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.MfaRequiredException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.MisconfigurationException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.NetworkException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.PasswordPolicyViolationException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.PhoneVerificationCooldownException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.SignInMethodUnavailableException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.TooManyRequestsException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.UnknownException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.UserNotFoundException→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.AuthException.WeakPasswordException→com.firebase.ui.auth.AuthException
- Direction
- com.firebase.ui.auth.AuthException uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.AuthException, while a change to com.firebase.ui.auth.AuthException can't break com.firebase.ui.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→8 com.firebase.ui.auth.AuthState.Reauthentication uses com.firebase.ui.auth.AuthState✕
- Connections
- 10 pairs of types, where a type in com.firebase.ui.auth.AuthState.Reauthentication uses a type in com.firebase.ui.auth.AuthState.
- The types involved
com.firebase.ui.auth.AuthState.Reauthentication.AttemptFailed→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.Authenticating→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.EmailSignInLinkSent→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.PasswordResetLinkSent→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.PhoneNumberVerificationRequired→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.Required→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.RequiresMfa→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.SmsAutoVerified→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.Succeeded→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.AuthState.Reauthentication.Succeeded→com.firebase.ui.auth.AuthState.Success
- Direction
- com.firebase.ui.auth.AuthState.Reauthentication uses com.firebase.ui.auth.AuthState, so a change to com.firebase.ui.auth.AuthState can break com.firebase.ui.auth.AuthState.Reauthentication, while a change to com.firebase.ui.auth.AuthState.Reauthentication can't break com.firebase.ui.auth.AuthState.
- Position
- Below the diagonal: com.firebase.ui.auth.AuthState.Reauthentication uses a module listed above it, which is the healthy direction.
20→10 com.firebase.ui.auth.configuration.theme uses com.firebase.ui.auth.configuration.theme.AuthUITheme✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.configuration.theme uses a type in com.firebase.ui.auth.configuration.theme.AuthUITheme.
- The types involved
com.firebase.ui.auth.configuration.theme.AuthUITheme→com.firebase.ui.auth.configuration.theme.AuthUITheme.ProviderStylecom.firebase.ui.auth.configuration.theme.ProviderStyleDefaults→com.firebase.ui.auth.configuration.theme.AuthUITheme.ProviderStyle
- Direction
- com.firebase.ui.auth.configuration.theme uses com.firebase.ui.auth.configuration.theme.AuthUITheme, so a change to com.firebase.ui.auth.configuration.theme.AuthUITheme can break com.firebase.ui.auth.configuration.theme, while a change to com.firebase.ui.auth.configuration.theme can't break com.firebase.ui.auth.configuration.theme.AuthUITheme.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.theme uses a module listed above it, which is the healthy direction.
21→4 com.firebase.ui.auth.util uses com.firebase.ui.auth.data✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.util uses a type in com.firebase.ui.auth.data.
- The types involved
com.firebase.ui.auth.util.CountryUtils→com.firebase.ui.auth.data.CountryData
- Direction
- com.firebase.ui.auth.util uses com.firebase.ui.auth.data, so a change to com.firebase.ui.auth.data can break com.firebase.ui.auth.util, while a change to com.firebase.ui.auth.util can't break com.firebase.ui.auth.data.
- Position
- Below the diagonal: com.firebase.ui.auth.util uses a module listed above it, which is the healthy direction.
21→5 com.firebase.ui.auth.util uses com.firebase.ui.auth.util.SignInPreferenceManager✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.util uses a type in com.firebase.ui.auth.util.SignInPreferenceManager.
- The types involved
com.firebase.ui.auth.util.SignInPreferenceManager→com.firebase.ui.auth.util.SignInPreferenceManager.SignInPreference
- Direction
- com.firebase.ui.auth.util uses com.firebase.ui.auth.util.SignInPreferenceManager, so a change to com.firebase.ui.auth.util.SignInPreferenceManager can break com.firebase.ui.auth.util, while a change to com.firebase.ui.auth.util can't break com.firebase.ui.auth.util.SignInPreferenceManager.
- Position
- Below the diagonal: com.firebase.ui.auth.util uses a module listed above it, which is the healthy direction.
21→14 com.firebase.ui.auth.util uses com.firebase.ui.auth.util.EmailLinkPersistenceManager✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.util uses a type in com.firebase.ui.auth.util.EmailLinkPersistenceManager.
- The types involved
com.firebase.ui.auth.util.PersistenceManager→com.firebase.ui.auth.util.EmailLinkPersistenceManager.SessionRecord
- Direction
- com.firebase.ui.auth.util uses com.firebase.ui.auth.util.EmailLinkPersistenceManager, so a change to com.firebase.ui.auth.util.EmailLinkPersistenceManager can break com.firebase.ui.auth.util, while a change to com.firebase.ui.auth.util can't break com.firebase.ui.auth.util.EmailLinkPersistenceManager.
- Position
- Below the diagonal: com.firebase.ui.auth.util uses a module listed above it, which is the healthy direction.
22→17 com.firebaseui.lint uses com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector✕
- Connections
- 1 pair of types, where a type in com.firebaseui.lint uses a type in com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector.
- The types involved
com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector→com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector.MissingLifecycleMethodsVisitor
- Direction
- com.firebaseui.lint uses com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector, so a change to com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector can break com.firebaseui.lint, while a change to com.firebaseui.lint can't break com.firebaseui.lint.FirestoreRecyclerAdapterLifecycleDetector.
- Position
- Below the diagonal: com.firebaseui.lint uses a module listed above it, which is the healthy direction.
23→1 com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.FacebookProfileData
- Direction
- com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook can break com.firebase.ui.auth.configuration.auth_provider.AuthProvider, while a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a module listed above it, which is the healthy direction.
23→3 com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.Verifiercom.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.VerifyPhoneNumberResult
- Direction
- com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone can break com.firebase.ui.auth.configuration.auth_provider.AuthProvider, while a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a module listed above it, which is the healthy direction.
23→20 com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.theme✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a type in com.firebase.ui.auth.configuration.theme.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AuthProvider.GenericOAuth→com.firebase.ui.auth.configuration.theme.AuthUIAsset
- Direction
- com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.theme, so a change to com.firebase.ui.auth.configuration.theme can break com.firebase.ui.auth.configuration.auth_provider.AuthProvider, while a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can't break com.firebase.ui.auth.configuration.theme.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a module listed above it, which is the healthy direction.
23→21 com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.util✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a type in com.firebase.ui.auth.util.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Email→com.firebase.ui.auth.util.ContinueUrlBuilder
- Direction
- com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.util, so a change to com.firebase.ui.auth.util can break com.firebase.ui.auth.configuration.auth_provider.AuthProvider, while a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can't break com.firebase.ui.auth.util.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a module listed above it, which is the healthy direction.
23→24 com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.auth_provider part of a loop✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a type in com.firebase.ui.auth.configuration.auth_provider.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Anonymous→com.firebase.ui.auth.configuration.auth_provider.AuthProvidercom.firebase.ui.auth.configuration.auth_provider.AuthProvider.Email→com.firebase.ui.auth.configuration.auth_provider.AuthProvidercom.firebase.ui.auth.configuration.auth_provider.AuthProvider.OAuth→com.firebase.ui.auth.configuration.auth_provider.AuthProvidercom.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone→com.firebase.ui.auth.configuration.auth_provider.AuthProvider
- Direction
- com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration.auth_provider, so a change to com.firebase.ui.auth.configuration.auth_provider can break com.firebase.ui.auth.configuration.auth_provider.AuthProvider, while a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can't break com.firebase.ui.auth.configuration.auth_provider.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→25 com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration part of a loop✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Companion→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.configuration.auth_provider.AuthProvider.Email→com.firebase.ui.auth.configuration.PasswordRule
- Direction
- com.firebase.ui.auth.configuration.auth_provider.AuthProvider uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.configuration.auth_provider.AuthProvider, while a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can't break com.firebase.ui.auth.configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.FacebookAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.LoginManagerProvider
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider uses a module listed above it, which is the healthy direction.
24→2 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.GoogleAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.AuthorizationProvidercom.firebase.ui.auth.configuration.auth_provider.GoogleAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.CredentialManagerProvider
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider uses a module listed above it, which is the healthy direction.
24→3 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.PhoneAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.CredentialProvidercom.firebase.ui.auth.configuration.auth_provider.PhoneAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.Verifier
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider uses a module listed above it, which is the healthy direction.
24→18 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.AuthException✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.AuthException.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.EmailAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.AuthException.DifferentSignInMethodRequiredException
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.AuthException, so a change to com.firebase.ui.auth.AuthException can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.AuthException.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider uses a module listed above it, which is the healthy direction.
24→21 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.util✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.util.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.EmailAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.util.PersistenceManager
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.util, so a change to com.firebase.ui.auth.util can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.util.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider uses a module listed above it, which is the healthy direction.
24→23 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider✕
- Connections
- 5 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.EmailAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Emailcom.firebase.ui.auth.configuration.auth_provider.FacebookAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebookcom.firebase.ui.auth.configuration.auth_provider.GoogleAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Googlecom.firebase.ui.auth.configuration.auth_provider.OAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.OAuthcom.firebase.ui.auth.configuration.auth_provider.PhoneAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.auth_provider uses a module listed above it, which is the healthy direction.
24→25 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration part of a loop✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.EmailAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→27 com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth part of a loop✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.configuration.auth_provider uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.configuration.auth_provider.AnonymousAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.configuration.auth_provider.FacebookAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.configuration.auth_provider.GoogleAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.configuration.auth_provider.OAuthProvider+FirebaseAuthUIKt→com.firebase.ui.auth.AuthException
- Direction
- com.firebase.ui.auth.configuration.auth_provider uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.configuration.auth_provider, while a change to com.firebase.ui.auth.configuration.auth_provider can't break com.firebase.ui.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→9 com.firebase.ui.auth.configuration uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.configuration uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.configuration.AuthUIConfiguration→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.AuthUIConfigurationBuilder→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.PasswordRule→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.configuration uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.configuration, while a change to com.firebase.ui.auth.configuration can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration uses a module listed above it, which is the healthy direction.
25→20 com.firebase.ui.auth.configuration uses com.firebase.ui.auth.configuration.theme✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.configuration uses a type in com.firebase.ui.auth.configuration.theme.
- The types involved
com.firebase.ui.auth.configuration.AuthUIConfiguration→com.firebase.ui.auth.configuration.theme.AuthUIAssetcom.firebase.ui.auth.configuration.AuthUIConfiguration→com.firebase.ui.auth.configuration.theme.AuthUIThemecom.firebase.ui.auth.configuration.AuthUIConfigurationBuilder→com.firebase.ui.auth.configuration.theme.AuthUIAssetcom.firebase.ui.auth.configuration.AuthUIConfigurationBuilder→com.firebase.ui.auth.configuration.theme.AuthUITheme
- Direction
- com.firebase.ui.auth.configuration uses com.firebase.ui.auth.configuration.theme, so a change to com.firebase.ui.auth.configuration.theme can break com.firebase.ui.auth.configuration, while a change to com.firebase.ui.auth.configuration can't break com.firebase.ui.auth.configuration.theme.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration uses a module listed above it, which is the healthy direction.
25→24 com.firebase.ui.auth.configuration uses com.firebase.ui.auth.configuration.auth_provider✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.configuration uses a type in com.firebase.ui.auth.configuration.auth_provider.
- The types involved
com.firebase.ui.auth.configuration.AuthUIConfiguration→com.firebase.ui.auth.configuration.auth_provider.AuthProvidercom.firebase.ui.auth.configuration.AuthUIConfigurationBuilder→com.firebase.ui.auth.configuration.auth_provider.AuthProvidercom.firebase.ui.auth.configuration.AuthUIConfigurationBuilder→com.firebase.ui.auth.configuration.auth_provider.AuthProvidersBuilder
- Direction
- com.firebase.ui.auth.configuration uses com.firebase.ui.auth.configuration.auth_provider, so a change to com.firebase.ui.auth.configuration.auth_provider can break com.firebase.ui.auth.configuration, while a change to com.firebase.ui.auth.configuration can't break com.firebase.ui.auth.configuration.auth_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration uses a module listed above it, which is the healthy direction.
26→5 com.firebase.ui.auth.ui.method_picker uses com.firebase.ui.auth.util.SignInPreferenceManager✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.method_picker uses a type in com.firebase.ui.auth.util.SignInPreferenceManager.
- The types involved
com.firebase.ui.auth.ui.method_picker.AuthMethodPickerKt→com.firebase.ui.auth.util.SignInPreferenceManager.SignInPreference
- Direction
- com.firebase.ui.auth.ui.method_picker uses com.firebase.ui.auth.util.SignInPreferenceManager, so a change to com.firebase.ui.auth.util.SignInPreferenceManager can break com.firebase.ui.auth.ui.method_picker, while a change to com.firebase.ui.auth.ui.method_picker can't break com.firebase.ui.auth.util.SignInPreferenceManager.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.method_picker uses a module listed above it, which is the healthy direction.
26→20 com.firebase.ui.auth.ui.method_picker uses com.firebase.ui.auth.configuration.theme✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.method_picker uses a type in com.firebase.ui.auth.configuration.theme.
- The types involved
com.firebase.ui.auth.ui.method_picker.AuthMethodPickerKt→com.firebase.ui.auth.configuration.theme.AuthUIAsset
- Direction
- com.firebase.ui.auth.ui.method_picker uses com.firebase.ui.auth.configuration.theme, so a change to com.firebase.ui.auth.configuration.theme can break com.firebase.ui.auth.ui.method_picker, while a change to com.firebase.ui.auth.ui.method_picker can't break com.firebase.ui.auth.configuration.theme.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.method_picker uses a module listed above it, which is the healthy direction.
26→24 com.firebase.ui.auth.ui.method_picker uses com.firebase.ui.auth.configuration.auth_provider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.method_picker uses a type in com.firebase.ui.auth.configuration.auth_provider.
- The types involved
com.firebase.ui.auth.ui.method_picker.AuthMethodPickerKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider
- Direction
- com.firebase.ui.auth.ui.method_picker uses com.firebase.ui.auth.configuration.auth_provider, so a change to com.firebase.ui.auth.configuration.auth_provider can break com.firebase.ui.auth.ui.method_picker, while a change to com.firebase.ui.auth.ui.method_picker can't break com.firebase.ui.auth.configuration.auth_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.method_picker uses a module listed above it, which is the healthy direction.
27→1 com.firebase.ui.auth uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.
- The types involved
com.firebase.ui.auth.AuthFlowScope→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.LoginManagerProvidercom.firebase.ui.auth.FirebaseAuthUI→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.LoginManagerProvider
- Direction
- com.firebase.ui.auth uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook can break com.firebase.ui.auth, while a change to com.firebase.ui.auth can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Facebook.
- Position
- Below the diagonal: com.firebase.ui.auth uses a module listed above it, which is the healthy direction.
27→2 com.firebase.ui.auth uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.
- The types involved
com.firebase.ui.auth.AuthFlowScope→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.CredentialManagerProvidercom.firebase.ui.auth.FirebaseAuthUI→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.CredentialManagerProvider
- Direction
- com.firebase.ui.auth uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google can break com.firebase.ui.auth, while a change to com.firebase.ui.auth can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Google.
- Position
- Below the diagonal: com.firebase.ui.auth uses a module listed above it, which is the healthy direction.
27→19 com.firebase.ui.auth uses com.firebase.ui.auth.AuthState.Reauthentication✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth uses a type in com.firebase.ui.auth.AuthState.Reauthentication.
- The types involved
com.firebase.ui.auth.FirebaseAuthUI→com.firebase.ui.auth.AuthState.Reauthentication.Required
- Direction
- com.firebase.ui.auth uses com.firebase.ui.auth.AuthState.Reauthentication, so a change to com.firebase.ui.auth.AuthState.Reauthentication can break com.firebase.ui.auth, while a change to com.firebase.ui.auth can't break com.firebase.ui.auth.AuthState.Reauthentication.
- Position
- Below the diagonal: com.firebase.ui.auth uses a module listed above it, which is the healthy direction.
27→25 com.firebase.ui.auth uses com.firebase.ui.auth.configuration✕
- Connections
- 5 pairs of types, where a type in com.firebase.ui.auth uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.AuthFlowController→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.AuthFlowScope→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.AuthFlowScopeKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.FirebaseAuthActivity→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.FirebaseAuthUI→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth, while a change to com.firebase.ui.auth can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth uses a module listed above it, which is the healthy direction.
28→9 com.firebase.ui.auth.configuration.PasswordRule uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 6 pairs of types, where a type in com.firebase.ui.auth.configuration.PasswordRule uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.configuration.PasswordRule.Custom→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.PasswordRule.MinimumLength→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.PasswordRule.RequireDigit→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.PasswordRule.RequireLowercase→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.PasswordRule.RequireSpecialCharacter→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.PasswordRule.RequireUppercase→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.configuration.PasswordRule uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.configuration.PasswordRule, while a change to com.firebase.ui.auth.configuration.PasswordRule can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.PasswordRule uses a module listed above it, which is the healthy direction.
28→25 com.firebase.ui.auth.configuration.PasswordRule uses com.firebase.ui.auth.configuration✕
- Connections
- 6 pairs of types, where a type in com.firebase.ui.auth.configuration.PasswordRule uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.configuration.PasswordRule.Custom→com.firebase.ui.auth.configuration.PasswordRulecom.firebase.ui.auth.configuration.PasswordRule.MinimumLength→com.firebase.ui.auth.configuration.PasswordRulecom.firebase.ui.auth.configuration.PasswordRule.RequireDigit→com.firebase.ui.auth.configuration.PasswordRulecom.firebase.ui.auth.configuration.PasswordRule.RequireLowercase→com.firebase.ui.auth.configuration.PasswordRulecom.firebase.ui.auth.configuration.PasswordRule.RequireSpecialCharacter→com.firebase.ui.auth.configuration.PasswordRulecom.firebase.ui.auth.configuration.PasswordRule.RequireUppercase→com.firebase.ui.auth.configuration.PasswordRule
- Direction
- com.firebase.ui.auth.configuration.PasswordRule uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.configuration.PasswordRule, while a change to com.firebase.ui.auth.configuration.PasswordRule can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.PasswordRule uses a module listed above it, which is the healthy direction.
29→4 com.firebase.ui.auth.configuration.validators uses com.firebase.ui.auth.data✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.validators uses a type in com.firebase.ui.auth.data.
- The types involved
com.firebase.ui.auth.configuration.validators.PhoneNumberValidator→com.firebase.ui.auth.data.CountryData
- Direction
- com.firebase.ui.auth.configuration.validators uses com.firebase.ui.auth.data, so a change to com.firebase.ui.auth.data can break com.firebase.ui.auth.configuration.validators, while a change to com.firebase.ui.auth.configuration.validators can't break com.firebase.ui.auth.data.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.validators uses a module listed above it, which is the healthy direction.
29→9 com.firebase.ui.auth.configuration.validators uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 6 pairs of types, where a type in com.firebase.ui.auth.configuration.validators uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.configuration.validators.EmailValidator→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.validators.FieldValidator→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.validators.GeneralFieldValidator→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.validators.PasswordValidator→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.validators.PhoneNumberValidator→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.configuration.validators.VerificationCodeValidator→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.configuration.validators uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.configuration.validators, while a change to com.firebase.ui.auth.configuration.validators can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.validators uses a module listed above it, which is the healthy direction.
29→25 com.firebase.ui.auth.configuration.validators uses com.firebase.ui.auth.configuration✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.configuration.validators uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.configuration.validators.PasswordValidator→com.firebase.ui.auth.configuration.PasswordRule
- Direction
- com.firebase.ui.auth.configuration.validators uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.configuration.validators, while a change to com.firebase.ui.auth.configuration.validators can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.configuration.validators uses a module listed above it, which is the healthy direction.
30→4 com.firebase.ui.auth.mfa uses com.firebase.ui.auth.data✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.mfa uses a type in com.firebase.ui.auth.data.
- The types involved
com.firebase.ui.auth.mfa.MfaEnrollmentContentState→com.firebase.ui.auth.data.CountryData
- Direction
- com.firebase.ui.auth.mfa uses com.firebase.ui.auth.data, so a change to com.firebase.ui.auth.data can break com.firebase.ui.auth.mfa, while a change to com.firebase.ui.auth.mfa can't break com.firebase.ui.auth.data.
- Position
- Below the diagonal: com.firebase.ui.auth.mfa uses a module listed above it, which is the healthy direction.
30→9 com.firebase.ui.auth.mfa uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.mfa uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.mfa.MfaEnrollmentStepKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.mfa.MfaErrorMapperKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.mfa uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.mfa, while a change to com.firebase.ui.auth.mfa can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.mfa uses a module listed above it, which is the healthy direction.
30→23 com.firebase.ui.auth.mfa uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.mfa uses a type in com.firebase.ui.auth.configuration.auth_provider.AuthProvider.
- The types involved
com.firebase.ui.auth.mfa.SmsEnrollmentHandler→com.firebase.ui.auth.configuration.auth_provider.AuthProvider.Phone
- Direction
- com.firebase.ui.auth.mfa uses com.firebase.ui.auth.configuration.auth_provider.AuthProvider, so a change to com.firebase.ui.auth.configuration.auth_provider.AuthProvider can break com.firebase.ui.auth.mfa, while a change to com.firebase.ui.auth.mfa can't break com.firebase.ui.auth.configuration.auth_provider.AuthProvider.
- Position
- Below the diagonal: com.firebase.ui.auth.mfa uses a module listed above it, which is the healthy direction.
30→25 com.firebase.ui.auth.mfa uses com.firebase.ui.auth.configuration✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.mfa uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.mfa.MfaChallengeContentState→com.firebase.ui.auth.configuration.MfaFactorcom.firebase.ui.auth.mfa.MfaEnrollmentContentState→com.firebase.ui.auth.configuration.MfaFactorcom.firebase.ui.auth.mfa.MfaEnrollmentStepKt→com.firebase.ui.auth.configuration.MfaFactor
- Direction
- com.firebase.ui.auth.mfa uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.mfa, while a change to com.firebase.ui.auth.mfa can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.mfa uses a module listed above it, which is the healthy direction.
31→25 com.firebase.ui.auth.FirebaseAuthActivity uses com.firebase.ui.auth.configuration✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.FirebaseAuthActivity uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.FirebaseAuthActivity.Companion→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth.FirebaseAuthActivity uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.FirebaseAuthActivity, while a change to com.firebase.ui.auth.FirebaseAuthActivity can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.FirebaseAuthActivity uses a module listed above it, which is the healthy direction.
31→27 com.firebase.ui.auth.FirebaseAuthActivity uses com.firebase.ui.auth✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.FirebaseAuthActivity uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.FirebaseAuthActivity.Companion→com.firebase.ui.auth.FirebaseAuthUI
- Direction
- com.firebase.ui.auth.FirebaseAuthActivity uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.FirebaseAuthActivity, while a change to com.firebase.ui.auth.FirebaseAuthActivity can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.FirebaseAuthActivity uses a module listed above it, which is the healthy direction.
32→27 com.firebase.ui.auth.FirebaseAuthUI uses com.firebase.ui.auth✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.FirebaseAuthUI uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.FirebaseAuthUI.Companion→com.firebase.ui.auth.FirebaseAuthUI
- Direction
- com.firebase.ui.auth.FirebaseAuthUI uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.FirebaseAuthUI, while a change to com.firebase.ui.auth.FirebaseAuthUI can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.FirebaseAuthUI uses a module listed above it, which is the healthy direction.
33→4 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.data✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.data.
- The types involved
com.firebase.ui.auth.ui.components.CountrySelectorKt→com.firebase.ui.auth.data.CountryData
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.data, so a change to com.firebase.ui.auth.data can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.data.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
33→8 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.AuthState✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.AuthState.
- The types involved
com.firebase.ui.auth.ui.components.TopLevelDialogController→com.firebase.ui.auth.AuthState.Error
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.AuthState, so a change to com.firebase.ui.auth.AuthState can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.AuthState.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
33→9 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 5 pairs of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.ui.components.AuthProviderButtonKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.ui.components.ErrorRecoveryDialogKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.ui.components.ReauthenticationDialogKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.ui.components.TopLevelDialogController→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.ui.components.TopLevelDialogControllerKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
33→10 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.theme.AuthUITheme✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.configuration.theme.AuthUITheme.
- The types involved
com.firebase.ui.auth.ui.components.AuthProviderButtonKt→com.firebase.ui.auth.configuration.theme.AuthUITheme.ProviderStyle
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.theme.AuthUITheme, so a change to com.firebase.ui.auth.configuration.theme.AuthUITheme can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.configuration.theme.AuthUITheme.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
33→24 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.auth_provider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.configuration.auth_provider.
- The types involved
com.firebase.ui.auth.ui.components.AuthProviderButtonKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.auth_provider, so a change to com.firebase.ui.auth.configuration.auth_provider can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.configuration.auth_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
33→27 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.components.ErrorRecoveryDialogKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.components.TopLevelDialogController→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.components.TopLevelDialogController→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.ui.components.TopLevelDialogControllerKt→com.firebase.ui.auth.AuthState
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
33→29 com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.validators✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.components uses a type in com.firebase.ui.auth.configuration.validators.
- The types involved
com.firebase.ui.auth.ui.components.AuthTextFieldKt→com.firebase.ui.auth.configuration.validators.FieldValidatorcom.firebase.ui.auth.ui.components.VerificationCodeInputFieldKt→com.firebase.ui.auth.configuration.validators.FieldValidator
- Direction
- com.firebase.ui.auth.ui.components uses com.firebase.ui.auth.configuration.validators, so a change to com.firebase.ui.auth.configuration.validators can break com.firebase.ui.auth.ui.components, while a change to com.firebase.ui.auth.ui.components can't break com.firebase.ui.auth.configuration.validators.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components uses a module listed above it, which is the healthy direction.
34→27 com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState uses com.firebase.ui.auth✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState.ErrorDialog→com.firebase.ui.auth.AuthException
- Direction
- com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState, while a change to com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.components.TopLevelDialogController.DialogState uses a module listed above it, which is the healthy direction.
35→11 com.firebase.ui.auth.ui.screens.email uses com.firebase.ui.auth.ui.screens.AuthRoute.Email✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.email uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.Email.
- The types involved
com.firebase.ui.auth.ui.screens.email.EmailAuthDestinationsKt→com.firebase.ui.auth.ui.screens.AuthRoute.Email.Step
- Direction
- com.firebase.ui.auth.ui.screens.email uses com.firebase.ui.auth.ui.screens.AuthRoute.Email, so a change to com.firebase.ui.auth.ui.screens.AuthRoute.Email can break com.firebase.ui.auth.ui.screens.email, while a change to com.firebase.ui.auth.ui.screens.email can't break com.firebase.ui.auth.ui.screens.AuthRoute.Email.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.email uses a module listed above it, which is the healthy direction.
35→25 com.firebase.ui.auth.ui.screens.email uses com.firebase.ui.auth.configuration✕
- Connections
- 6 pairs of types, where a type in com.firebase.ui.auth.ui.screens.email uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.ui.screens.email.EmailAuthDestinationsKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.email.EmailAuthScreenKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.email.ResetPasswordUIKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.email.SignInEmailLinkUIKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.email.SignInUIKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.email.SignUpUIKt→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth.ui.screens.email uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.ui.screens.email, while a change to com.firebase.ui.auth.ui.screens.email can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.email uses a module listed above it, which is the healthy direction.
35→27 com.firebase.ui.auth.ui.screens.email uses com.firebase.ui.auth✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.ui.screens.email uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.screens.email.EmailAuthDestinationsKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.screens.email.EmailAuthDestinationsKt→com.firebase.ui.auth.FirebaseAuthUIcom.firebase.ui.auth.ui.screens.email.EmailAuthScreenKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.screens.email.EmailAuthScreenKt→com.firebase.ui.auth.FirebaseAuthUI
- Direction
- com.firebase.ui.auth.ui.screens.email uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.screens.email, while a change to com.firebase.ui.auth.ui.screens.email can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.email uses a module listed above it, which is the healthy direction.
36→4 com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth.data✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.ui.screens.phone uses a type in com.firebase.ui.auth.data.
- The types involved
com.firebase.ui.auth.ui.screens.phone.EnterPhoneNumberUIKt→com.firebase.ui.auth.data.CountryDatacom.firebase.ui.auth.ui.screens.phone.PhoneAuthContentState→com.firebase.ui.auth.data.CountryDatacom.firebase.ui.auth.ui.screens.phone.PhoneAuthFlowState→com.firebase.ui.auth.data.CountryData
- Direction
- com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth.data, so a change to com.firebase.ui.auth.data can break com.firebase.ui.auth.ui.screens.phone, while a change to com.firebase.ui.auth.ui.screens.phone can't break com.firebase.ui.auth.data.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.phone uses a module listed above it, which is the healthy direction.
36→13 com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth.ui.screens.AuthRoute.Phone✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.phone uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.Phone.
- The types involved
com.firebase.ui.auth.ui.screens.phone.PhoneAuthDestinationsKt→com.firebase.ui.auth.ui.screens.AuthRoute.Phone.Step
- Direction
- com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth.ui.screens.AuthRoute.Phone, so a change to com.firebase.ui.auth.ui.screens.AuthRoute.Phone can break com.firebase.ui.auth.ui.screens.phone, while a change to com.firebase.ui.auth.ui.screens.phone can't break com.firebase.ui.auth.ui.screens.AuthRoute.Phone.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.phone uses a module listed above it, which is the healthy direction.
36→25 com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth.configuration✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.ui.screens.phone uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.ui.screens.phone.EnterPhoneNumberUIKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.phone.EnterVerificationCodeUIKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.phone.PhoneAuthDestinationsKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.phone.PhoneAuthScreenKt→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.ui.screens.phone, while a change to com.firebase.ui.auth.ui.screens.phone can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.phone uses a module listed above it, which is the healthy direction.
36→27 com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.ui.screens.phone uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.screens.phone.PhoneAuthDestinationsKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.screens.phone.PhoneAuthDestinationsKt→com.firebase.ui.auth.FirebaseAuthUIcom.firebase.ui.auth.ui.screens.phone.PhoneAuthScreenKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.screens.phone.PhoneAuthScreenKt→com.firebase.ui.auth.FirebaseAuthUI
- Direction
- com.firebase.ui.auth.ui.screens.phone uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.screens.phone, while a change to com.firebase.ui.auth.ui.screens.phone can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.phone uses a module listed above it, which is the healthy direction.
37→11 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.AuthRoute.Email✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.Email.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Email→com.firebase.ui.auth.ui.screens.AuthRoute.Email.Step
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.AuthRoute.Email, so a change to com.firebase.ui.auth.ui.screens.AuthRoute.Email can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.ui.screens.AuthRoute.Email.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.AuthRoute uses a module listed above it, which is the healthy direction.
37→12 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment→com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.Step
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment, so a change to com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.AuthRoute uses a module listed above it, which is the healthy direction.
37→13 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.AuthRoute.Phone✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.Phone.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Phone→com.firebase.ui.auth.ui.screens.AuthRoute.Phone.Step
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.AuthRoute.Phone, so a change to com.firebase.ui.auth.ui.screens.AuthRoute.Phone can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.ui.screens.AuthRoute.Phone.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.AuthRoute uses a module listed above it, which is the healthy direction.
37→30 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.mfa✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.mfa.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment→com.firebase.ui.auth.mfa.MfaEnrollmentStep
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.mfa, so a change to com.firebase.ui.auth.mfa can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.mfa.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.AuthRoute uses a module listed above it, which is the healthy direction.
37→35 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.email✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.ui.screens.email.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Email→com.firebase.ui.auth.ui.screens.email.EmailAuthMode
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.email, so a change to com.firebase.ui.auth.ui.screens.email can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.ui.screens.email.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.AuthRoute uses a module listed above it, which is the healthy direction.
37→36 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.phone✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.ui.screens.phone.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Phone→com.firebase.ui.auth.ui.screens.phone.PhoneAuthStep
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens.phone, so a change to com.firebase.ui.auth.ui.screens.phone can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.ui.screens.phone.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.AuthRoute uses a module listed above it, which is the healthy direction.
37→39 com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens part of a loop✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.AuthRoute uses a type in com.firebase.ui.auth.ui.screens.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRoute.Destination→com.firebase.ui.auth.ui.screens.AuthRoutecom.firebase.ui.auth.ui.screens.AuthRoute.FlowEntry→com.firebase.ui.auth.ui.screens.AuthRoute
- Direction
- com.firebase.ui.auth.ui.screens.AuthRoute uses com.firebase.ui.auth.ui.screens, so a change to com.firebase.ui.auth.ui.screens can break com.firebase.ui.auth.ui.screens.AuthRoute, while a change to com.firebase.ui.auth.ui.screens.AuthRoute can't break com.firebase.ui.auth.ui.screens.
- 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.
38→8 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.AuthState✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.AuthState.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthFlowState→com.firebase.ui.auth.AuthState.Reauthenticationcom.firebase.ui.auth.ui.screens.reauth.ReauthSurface→com.firebase.ui.auth.AuthState.Reauthentication
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.AuthState, so a change to com.firebase.ui.auth.AuthState can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.AuthState.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→9 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→19 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.AuthState.Reauthentication✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.AuthState.Reauthentication.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthFlowState→com.firebase.ui.auth.AuthState.Reauthentication.Requestcom.firebase.ui.auth.ui.screens.reauth.ReauthFlowState→com.firebase.ui.auth.AuthState.Reauthentication.Requiredcom.firebase.ui.auth.ui.screens.reauth.ReauthSurface→com.firebase.ui.auth.AuthState.Reauthentication.Request
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.AuthState.Reauthentication, so a change to com.firebase.ui.auth.AuthState.Reauthentication can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.AuthState.Reauthentication.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→24 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.configuration.auth_provider✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.configuration.auth_provider.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthContentState→com.firebase.ui.auth.configuration.auth_provider.AuthProvidercom.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.configuration.auth_provider, so a change to com.firebase.ui.auth.configuration.auth_provider can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.configuration.auth_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→25 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.configuration✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.reauth.ReauthSurface→com.firebase.ui.auth.configuration.AuthUIConfiguration
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→27 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.FirebaseAuthUIcom.firebase.ui.auth.ui.screens.reauth.ReauthFlowState→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.ui.screens.reauth.ReauthFlowState→com.firebase.ui.auth.AuthStateSink
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→30 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.mfa✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.mfa.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.mfa.MfaChallengeContentState
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.mfa, so a change to com.firebase.ui.auth.mfa can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.mfa.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→35 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.ui.screens.email✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.ui.screens.email.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.ui.screens.email.EmailAuthContentState
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.ui.screens.email, so a change to com.firebase.ui.auth.ui.screens.email can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.ui.screens.email.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→36 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.ui.screens.phone✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.ui.screens.phone.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.ui.screens.phone.PhoneAuthContentStatecom.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.ui.screens.phone.PhoneAuthFlowState
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.ui.screens.phone, so a change to com.firebase.ui.auth.ui.screens.phone can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.ui.screens.phone.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
38→37 com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.ui.screens.AuthRoute✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.reauth uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.
- The types involved
com.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.ui.screens.AuthRoute.Destinationcom.firebase.ui.auth.ui.screens.reauth.ReauthDestinationsKt→com.firebase.ui.auth.ui.screens.AuthRoute.Reauth
- Direction
- com.firebase.ui.auth.ui.screens.reauth uses com.firebase.ui.auth.ui.screens.AuthRoute, so a change to com.firebase.ui.auth.ui.screens.AuthRoute can break com.firebase.ui.auth.ui.screens.reauth, while a change to com.firebase.ui.auth.ui.screens.reauth can't break com.firebase.ui.auth.ui.screens.AuthRoute.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.reauth uses a module listed above it, which is the healthy direction.
39→9 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.ui.screens.AuthSuccessUiContext→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvidercom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→24 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.configuration.auth_provider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.configuration.auth_provider.
- The types involved
com.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.configuration.auth_provider.AuthProvider
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.configuration.auth_provider, so a change to com.firebase.ui.auth.configuration.auth_provider can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.configuration.auth_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→25 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.configuration✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.ui.screens.AuthSuccessUiContext→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.configuration.MfaConfiguration
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→26 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.method_picker✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.ui.method_picker.
- The types involved
com.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.ui.method_picker.MethodPickerTermsConfiguration
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.method_picker, so a change to com.firebase.ui.auth.ui.method_picker can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.ui.method_picker.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→27 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth✕
- Connections
- 4 pairs of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.screens.AuthSuccessUiContext→com.firebase.ui.auth.FirebaseAuthUIcom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.AuthExceptioncom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.AuthStatecom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.FirebaseAuthUI
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→30 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.mfa✕
- Connections
- 3 pairs of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.mfa.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRouteKt→com.firebase.ui.auth.mfa.MfaEnrollmentStepcom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.mfa.MfaChallengeContentStatecom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.mfa.MfaEnrollmentContentState
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.mfa, so a change to com.firebase.ui.auth.mfa can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.mfa.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→35 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.email✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.ui.screens.email.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRouteKt→com.firebase.ui.auth.ui.screens.email.EmailAuthModecom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.ui.screens.email.EmailAuthContentState
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.email, so a change to com.firebase.ui.auth.ui.screens.email can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.ui.screens.email.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→36 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.phone✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.ui.screens.phone.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRouteKt→com.firebase.ui.auth.ui.screens.phone.PhoneAuthStepcom.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.ui.screens.phone.PhoneAuthContentState
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.phone, so a change to com.firebase.ui.auth.ui.screens.phone can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.ui.screens.phone.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→37 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.AuthRoute✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.
- The types involved
com.firebase.ui.auth.ui.screens.AuthRouteKt→com.firebase.ui.auth.ui.screens.AuthRoute.Destination
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.AuthRoute, so a change to com.firebase.ui.auth.ui.screens.AuthRoute can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.ui.screens.AuthRoute.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
39→38 com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.reauth✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens uses a type in com.firebase.ui.auth.ui.screens.reauth.
- The types involved
com.firebase.ui.auth.ui.screens.FirebaseAuthScreenKt→com.firebase.ui.auth.ui.screens.reauth.ReauthContentState
- Direction
- com.firebase.ui.auth.ui.screens uses com.firebase.ui.auth.ui.screens.reauth, so a change to com.firebase.ui.auth.ui.screens.reauth can break com.firebase.ui.auth.ui.screens, while a change to com.firebase.ui.auth.ui.screens can't break com.firebase.ui.auth.ui.screens.reauth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens uses a module listed above it, which is the healthy direction.
40→4 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.data✕
- Connections
- 2 pairs of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.data.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.data.CountryDatacom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentFlowState→com.firebase.ui.auth.data.CountryData
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.data, so a change to com.firebase.ui.auth.data can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.data.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
40→9 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.configuration.string_provider✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.configuration.string_provider.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDefaultsKt→com.firebase.ui.auth.configuration.string_provider.AuthUIStringProvider
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.configuration.string_provider, so a change to com.firebase.ui.auth.configuration.string_provider can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.configuration.string_provider.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
40→12 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.Step
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment, so a change to com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.ui.screens.AuthRoute.MfaEnrollment.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
40→25 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.configuration✕
- Connections
- 7 pairs of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.configuration.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDefaultsKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDefaultsKt→com.firebase.ui.auth.configuration.MfaFactorcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.configuration.MfaConfigurationcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentFlowState→com.firebase.ui.auth.configuration.MfaFactorcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentScreenKt→com.firebase.ui.auth.configuration.AuthUIConfigurationcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentScreenKt→com.firebase.ui.auth.configuration.MfaConfiguration
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.configuration, so a change to com.firebase.ui.auth.configuration can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.configuration.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
40→27 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.FirebaseAuthUI
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth, so a change to com.firebase.ui.auth can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
40→30 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.mfa✕
- Connections
- 10 pairs of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.mfa.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaChallengeDefaultsKt→com.firebase.ui.auth.mfa.MfaChallengeContentStatecom.firebase.ui.auth.ui.screens.mfa.MfaChallengeScreenKt→com.firebase.ui.auth.mfa.MfaChallengeContentStatecom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDefaultsKt→com.firebase.ui.auth.mfa.MfaEnrollmentContentStatecom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.mfa.MfaEnrollmentContentStatecom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentFlowState→com.firebase.ui.auth.mfa.SmsEnrollmentSessioncom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentFlowState→com.firebase.ui.auth.mfa.TotpSecretcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentScreenKt→com.firebase.ui.auth.mfa.MfaEnrollmentContentStatecom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentScreenKt→com.firebase.ui.auth.mfa.MfaEnrollmentStepcom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentScreenKt→com.firebase.ui.auth.mfa.SmsEnrollmentHandlercom.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentScreenKt→com.firebase.ui.auth.mfa.TotpEnrollmentHandler
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.mfa, so a change to com.firebase.ui.auth.mfa can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.mfa.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
40→39 com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.ui.screens✕
- Connections
- 1 pair of types, where a type in com.firebase.ui.auth.ui.screens.mfa uses a type in com.firebase.ui.auth.ui.screens.
- The types involved
com.firebase.ui.auth.ui.screens.mfa.MfaEnrollmentDestinationsKt→com.firebase.ui.auth.ui.screens.AuthRoute
- Direction
- com.firebase.ui.auth.ui.screens.mfa uses com.firebase.ui.auth.ui.screens, so a change to com.firebase.ui.auth.ui.screens can break com.firebase.ui.auth.ui.screens.mfa, while a change to com.firebase.ui.auth.ui.screens.mfa can't break com.firebase.ui.auth.ui.screens.
- Position
- Below the diagonal: com.firebase.ui.auth.ui.screens.mfa uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A05:2025 — Injection | 3 | High / Critical |
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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +4.0 pts | Low | ADR Quality |
| 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. | +5.4 pts | Medium | Security & performance tooling |
| Resolve the 1 `AuthSuccessUiContext` spells `Ui` where 64 names in the project spell… finding(s) in Naming Consistency — start with FirebaseAuthScreen.kt. | +1.3 pts | Low | Naming Consistency |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +2.5 pts | Low | Bus Factor |
| 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. | +3.6 pts | Medium | Architecture documentation |
| Resolve the 20 Orphaned file finding(s) in Knowledge Freshness — start with MfaChallengeScreen.kt, FirebaseIndexArray.java, BaseObservableSnapshotArray.java. | +1.3 pts | Medium | Knowledge Freshness |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +0.5 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +0.5 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/firebaseui/android/demo/MainActivity.kt | 5.4 | Mixed | Change Coupling: Boundary-crossing change coupling: MainActivity.kt ↔ FirebaseAuthScreen.kt |
| auth/src/main/java/com/firebase/ui/auth/ui/components/VerificationCodeInputField.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt | 6.7 | Mixed | Cyclomatic Complexity: FirebaseAuthScreenKt.FirebaseAuthScreen (cyclomatic 89) |
| auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 7.0 | Mixed | Cyclomatic Complexity: EmailAuthProvider+FirebaseAuthUIKt.createOrLinkUserWithEmailAndPassword (cyclomatic 22) |
| app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (81 corresponding lines) |
| app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt | 7.1 | Mixed | Code Duplication: Edited copy of a member (48 corresponding lines) |
| auth/src/main/java/com/firebase/ui/auth/AuthException.kt | 7.2 | Mixed | Cyclomatic Complexity: AuthException.from (cyclomatic 87) |
| auth/src/main/java/com/firebase/ui/auth/ui/components/AuthProviderButton.kt | 7.2 | Mixed | Cyclomatic Complexity: AuthProviderButtonKt.resolveProviderLabel (cyclomatic 26) |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt | 7.2 | Mixed | Cyclomatic Complexity: MfaChallengeScreenKt.MfaChallengeScreen (cyclomatic 17) |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt | 7.2 | Mixed | Cyclomatic Complexity: ReauthDestinationsKt.reauthDestinations (cyclomatic 16) |
| database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java | 7.2 | Mixed | Code Duplication: Edited copy of a member (19 corresponding lines) |
| auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt | 7.2 | Mixed | Code Duplication: Edited copies of one member (3 members, 17+ corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt | 7.4 | Mixed | God Classes: MethodTooLong: SignInUIKt.SignInUI |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt | 7.4 | Mixed | God Classes: MethodTooLong: MfaEnrollmentDefaultsKt.DefaultMfaEnrollmentContent |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt | 7.4 | Mixed | God Classes: MethodTooLong: SignInEmailLinkUIKt.SignInEmailLinkUI |
| app/src/main/java/com/firebaseui/android/demo/auth/CustomMethodPickerDemoActivity.kt | 7.4 | Mixed | Code Duplication: Duplicated block (19 lines × 2) |
| auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/PhoneAuthScreen.kt | 7.8 | Mixed | Cyclomatic Complexity: PhoneAuthScreenKt.PhoneAuthScreen (cyclomatic 37) |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 43 dimensions across the health lenses
- 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, 171 of 344 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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 (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the Java/Kotlin suite (repository root, Gradle) did not finish re-running within its budget: the JVM suite did not finish re-running within its tier budget.
- 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.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `auth/src/main/java/com/firebase/ui/auth/AuthFlowScope.kt`, `auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt`, `auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt` 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 (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: -iso-3a8ecdb10120456d9ece9a6d6ab14c8b/app/src/debug/google-services.json, app/src/google-services.json, /tmp/codehealth-iso-3a8ecdb10120456d9ece9a6…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5), 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5), 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5), 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5), 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin 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.
- 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.
- 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.
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
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FirebaseAuthScreenKt.FirebaseAuthScreen at 89. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ErrorRecoveryDialogKt.getRecoveryMessage at 22 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: auth/src/main/java/com/firebase/ui/auth/ui/components/ErrorRecoveryDialog.kt (ErrorRecoveryDialogKt.getRecoveryMessage at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with FirebaseAuthScreenKt.FirebaseAuthScreen (cyclomatic 89), AuthException.from (cyclomatic 87), PhoneAuthScreenKt.PhoneAuthScreen (cyclomatic 37). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 7.1 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
27 method(s) exceeded the cognitive complexity threshold of 15; the worst was FirebaseAuthScreenKt.FirebaseAuthScreen at 127.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with FirebaseAuthScreenKt.FirebaseAuthScreen (cognitive 127). — Refactoring it lifts Cognitive Complexity from 4.7 to about 5.8/10.
D3 · God Classes
21 god class(es) detected.
What to do
- Resolve the 15 MethodTooLong finding(s) in God Classes — start with HighLevelApiDemoActivity.kt (2), FirebaseAuthScreen.kt, AuthException.kt. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with FirebaseAuthScreen.kt, AuthProvider.kt, EmailAuthProvider+FirebaseAuthUI.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with AuthException.kt, AuthProvider.kt, DefaultAuthUIStringProvider.kt. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
39 duplicated block group(s) detected. 8.9 % of the production lines (2,679 of 30,264) are in a reported copy. A further 25 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with SignInEmailLinkUI.kt (2), StorageDemoActivity.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (28 corresponding lines) finding(s) in Code Duplication — start with AuthChooserActivity.kt, EnterPhoneNumberUI.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with DatabasePagingKey.java, ReauthDestinations.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
13 production modules (Gradle), 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; 2 module(s) off the main sequence, with abstractness counted on 10 of the 13 (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 to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 27 classes have LCOM4 above 3.
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 453 artifact(s) resolved, 226 of them gradable against Maven Central, and 166 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.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 16 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 15 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. 12 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 34 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.
D15 · Churn × Complexity Hotspots
Top hotspots: auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt (33×89=2937); auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/PhoneAuthScreen.kt (17×37=629); auth/src/main/java/com/firebase/ui/auth/AuthException.kt (5×87=435) Repeated repair below the complexity floor: auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/GoogleAuthProvider+FirebaseAuthUI.kt (6 of 10 changes were fixes); auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt (5 of 8 changes were fixes); auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/AuthUIStringProvider.kt (4 of 7 changes were fixes)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with FirebaseAuthScreen.kt, PhoneAuthScreen.kt, AuthException.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Repeated repair finding(s) in Churn × Complexity Hotspots — start with GoogleAuthProvider+FirebaseAuthUI.kt, DefaultAuthUIStringProvider.kt, AuthUIStringProvider.kt. — One of this dimension's main actionable groups (6 warning-level).
D16 · Bus Factor
37 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt. Counted over 118 of the 203 production source files in this repository: 72 are under the ~2,400-byte size floor this dimension measures over, and the remaining 13 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 30264 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with VerificationCodeInputField.kt. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 11 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- 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).
D21 · Naming Consistency
1 naming inconsistencies among 65 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `AuthSuccessUiContext` spells `Ui` where 64 names in the project spell… finding(s) in Naming Consistency — start with FirebaseAuthScreen.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 11 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 1 high, 2 medium, 0 low. semgrep hit a parse error in 2 file(s) — `auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt` (line 703), `gradlew` (line 74, line 178) — 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
20 of 131 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt. Counted over 131 of the 203 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 20 Orphaned file finding(s) in Knowledge Freshness — start with MfaChallengeScreen.kt, FirebaseIndexArray.java, BaseObservableSnapshotArray.java. — One of this dimension's main actionable groups (20 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).
D35 · Change Coupling
Strongest change-coupling: MainActivity.kt↔FirebaseAuthScreen.kt 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with MainActivity.kt. — One of this dimension's main actionable groups (1 issue-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 50 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- 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 5 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
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- 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.) — e2eTest/firebase.json:1
What to do
- 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.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/src/main/java/com/firebaseui/android/demo/auth/HighLevelApiDemoActivity.kt:591
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 89% | Strong | Solid. |
| Maturity | 70% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate — gated by D12, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 82% | Checked 4 of 9 | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.google.firebase.firestore' (firestore/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5) 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5) 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5) 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
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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.
- 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 12% of this repository's production lines — kotlin (27,028 lines), python (244 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: -iso-3a8ecdb10120456d9ece9a6d6ab14c8b/app/src/debug/google-services.json, app/src/google-services.json, /tmp/codehealth-iso-3a8ecdb10120456d9ece9a6…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and 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/src/main/java/com/firebase/ui/firestore/CachingSnapshotParser.java:5) 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 — ~39979 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Java, Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 3 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).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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 source (10 module(s), 182 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 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.
- 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
- 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)
Critical — 4 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: MainActivity.kt ↔ FirebaseAuthScreen.kt app/src/main/java/com/firebaseui/android/demo/MainActivity.kt:1
Serious — 144 finding(s)
- MethodTooLong: FirebaseAuthScreenKt.FirebaseAuthScreen auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt:158
- MethodTooLong: Companion.from auth/src/main/java/com/firebase/ui/auth/AuthException.kt:488
- MethodTooLong: SignInUIKt.SignInUI auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt:80
- MethodTooLong: ReauthDestinationsKt.reauthDestinations auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt:148
- MethodTooLong: HighLevelApiDemoActivity.onCreate app/src/main/java/com/firebaseui/android/demo/auth/HighLevelApiDemoActivity.kt:79
- MethodTooLong: SignUpUIKt.SignUpUI auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignUpUI.kt:58
- MethodTooLong: AuthFlowControllerDemoActivityKt.AuthFlowDemo app/src/main/java/com/firebaseui/android/demo/auth/AuthFlowControllerDemoActivity.kt:150
- MethodTooLong: HighLevelApiDemoActivityKt.AppAuthenticatedContent app/src/main/java/com/firebaseui/android/demo/auth/HighLevelApiDemoActivity.kt:262
- MethodTooLong: MfaEnrollmentDefaultsKt.DefaultMfaEnrollmentContent auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt:75
- MethodTooLong: EmailEntryStepKt.EmailEntryStep app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/EmailEntryStep.kt:48
- MethodTooLong: SignInEmailLinkUIKt.SignInEmailLinkUI auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt:66
- MethodTooLong: EnterVerificationCodeUIKt.EnterVerificationCodeUI auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/EnterVerificationCodeUI.kt:63
- MethodTooLong: AuthProviderButtonKt.PreviewAuthProviderButton auth/src/main/java/com/firebase/ui/auth/ui/components/AuthProviderButton.kt:250
- MethodTooLong: CountrySelectorKt.CountrySelector auth/src/main/java/com/firebase/ui/auth/ui/components/CountrySelector.kt:77
- MethodTooLong: EmailAuthProvider+FirebaseAuthUIKt.signInWithEmailAndPassword auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:209
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-auth/1.2.0_to_2.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-auth/2.3.0_to_3.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-auth/3.3.1_to_4.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-database/1.2.0_to_2.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-database/2.3.0_to_3.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-database/3.3.1_to_4.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-firestore/3.3.1_to_4.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-storage/1.2.0_to_2.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-storage/2.3.0_to_3.0.0/compat_report.html:292
- compat_report.html.initTabs (cognitive 25) docs/compat_reports/firebase-ui-storage/3.3.1_to_4.0.0/compat_report.html:292
- Hotspot: auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt:158
- Hotspot: auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/PhoneAuthScreen.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/PhoneAuthScreen.kt:137
- Hotspot: auth/src/main/java/com/firebase/ui/auth/AuthException.kt auth/src/main/java/com/firebase/ui/auth/AuthException.kt:488
- Hotspot: auth/src/main/java/com/firebase/ui/auth/ui/screens/email/EmailAuthScreen.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/email/EmailAuthScreen.kt:191
- Hotspot: auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentScreen.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentScreen.kt:127
- Hotspot: auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:79
- Hotspot: auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt:148
- Repeated repair: auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/GoogleAuthProvider+FirebaseAuthUI.kt auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/GoogleAuthProvider+FirebaseAuthUI.kt:58
- Repeated repair: auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt:56
- Repeated repair: auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/AuthUIStringProvider.kt auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/AuthUIStringProvider.kt:423
- Repeated repair: auth/src/main/java/com/firebase/ui/auth/ui/components/TopLevelDialogController.kt auth/src/main/java/com/firebase/ui/auth/ui/components/TopLevelDialogController.kt:112
- Repeated repair: auth/src/main/java/com/firebase/ui/auth/ui/method_picker/AuthMethodPicker.kt auth/src/main/java/com/firebase/ui/auth/ui/method_picker/AuthMethodPicker.kt:100
- Repeated repair: auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDestinations.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDestinations.kt:276
- FileTooLong: screens/FirebaseAuthScreen.kt auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt
- FileTooLong: auth_provider/AuthProvider.kt auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AuthProvider.kt
- FileTooLong: auth_provider/EmailAuthProvider+FirebaseAuthUI.kt auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt
- ClassTooLong: AuthException auth/src/main/java/com/firebase/ui/auth/AuthException.kt:66
- ClassTooLong: AuthProvider auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AuthProvider.kt:106
- ClassTooLong: DefaultAuthUIStringProvider auth/src/main/java/com/firebase/ui/auth/configuration/string_provider/DefaultAuthUIStringProvider.kt:22
- Duplicated block (14 lines × 2) app/src/main/java/com/firebaseui/android/demo/storage/StorageDemoActivity.kt:94
- Duplicated block (14 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt:126
- Duplicated block (14 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInEmailLinkUI.kt:177
- Edited copy of a member (28 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/AuthChooserActivity.kt:31
- Edited copy of a member (28 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/EnterPhoneNumberUI.kt:189
- Edited copy of a member (7 corresponding lines) database/src/main/java/com/firebase/ui/database/paging/DatabasePagingKey.java:27
- Edited copy of a member (7 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt:123
- Duplicated block (19 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/CustomMethodPickerDemoActivity.kt:65
- Duplicated block (19 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt:139
- Duplicated block (18 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:295
- Duplicated block (18 lines × 2) database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java:71
- Duplicated block (15 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/CustomMethodPickerDemoActivity.kt:93
- Duplicated block (15 lines × 2) auth/src/main/java/com/firebase/ui/auth/FirebaseAuthUI.kt:482
- Duplicated block (13 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt:192
- Duplicated block (13 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:175
- Duplicated block (11 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt:450
- Duplicated block (11 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/EmailEntryStep.kt:122
- Duplicated block (9 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt:87
- Duplicated block (9 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/phone/pages/PhoneEntryStep.kt:66
- Off the main sequence: :storage
- Off the main sequence: :auth
- FirebaseAuthScreenKt.FirebaseAuthScreen (cyclomatic 89) auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt:158
- AuthException.from (cyclomatic 87) auth/src/main/java/com/firebase/ui/auth/AuthException.kt:488
- PhoneAuthScreenKt.PhoneAuthScreen (cyclomatic 37) auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/PhoneAuthScreen.kt:137
- MfaEnrollmentScreenKt.MfaEnrollmentScreenInternal (cyclomatic 29) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentScreen.kt:127
- AuthProviderButtonKt.resolveProviderLabel (cyclomatic 26) auth/src/main/java/com/firebase/ui/auth/ui/components/AuthProviderButton.kt:215
- EmailAuthProvider+FirebaseAuthUIKt.createOrLinkUserWithEmailAndPassword (cyclomatic 22) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:79
- EmailAuthScreenKt.EmailAuthScreen (cyclomatic 22) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/EmailAuthScreen.kt:191
- EmailAuthProvider+FirebaseAuthUIKt.signInWithEmailLink (cyclomatic 17) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:591
- VerificationCodeInputFieldKt.VerificationCodeInputField (cyclomatic 17) auth/src/main/java/com/firebase/ui/auth/ui/components/VerificationCodeInputField.kt:86
- MfaChallengeScreenKt.MfaChallengeScreen (cyclomatic 17) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt:68
- EmailAuthProvider+FirebaseAuthUIKt.signInWithEmailAndPassword (cyclomatic 16) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:209
- ReauthDestinationsKt.reauthDestinations (cyclomatic 16) auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt:148
- ReauthFlowState.fold (cyclomatic 16) auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthFlowState.kt:83
- TodoComment auth/src/main/java/com/firebase/ui/auth/ui/components/VerificationCodeInputField.kt:170
- FirebaseAuthScreenKt.FirebaseAuthScreen (cognitive 127) auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt:158
- AuthProviderButtonKt.resolveProviderLabel (cognitive 51) auth/src/main/java/com/firebase/ui/auth/ui/components/AuthProviderButton.kt:215
- PhoneAuthScreenKt.PhoneAuthScreen (cognitive 50) auth/src/main/java/com/firebase/ui/auth/ui/screens/phone/PhoneAuthScreen.kt:137
- MfaEnrollmentScreenKt.MfaEnrollmentScreenInternal (cognitive 40) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentScreen.kt:127
- DatabasePagingSource.loadSingle (cognitive 29) database/src/main/java/com/firebase/ui/database/paging/DatabasePagingSource.java:47
- EmailAuthProvider+FirebaseAuthUIKt.createOrLinkUserWithEmailAndPassword (cognitive 28) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:79
- AuthException.from (cognitive 27) auth/src/main/java/com/firebase/ui/auth/AuthException.kt:488
- EmailAuthProvider+FirebaseAuthUIKt.signInWithEmailAndPassword (cognitive 23) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:209
- ReauthDestinationsKt.reauthDestinations (cognitive 23) auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt:148
- MfaChallengeScreenKt.MfaChallengeScreen (cognitive 22) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt:68
- EmailAuthProvider+FirebaseAuthUIKt.signInWithEmailLink (cognitive 21) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:591
- EmailAuthScreenKt.EmailAuthScreen (cognitive 20) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/EmailAuthScreen.kt:191
- OAuthProvider+FirebaseAuthUIKt.signInWithProvider (cognitive 19) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/OAuthProvider+FirebaseAuthUI.kt:69
- AuthTextFieldKt.AuthTextField (cognitive 19) auth/src/main/java/com/firebase/ui/auth/ui/components/AuthTextField.kt:98
- VerificationCodeInputFieldKt.VerificationCodeInputField (cognitive 18) auth/src/main/java/com/firebase/ui/auth/ui/components/VerificationCodeInputField.kt:86
- GoogleAuthProvider+FirebaseAuthUIKt.signInWithGoogle (cognitive 17) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/GoogleAuthProvider+FirebaseAuthUI.kt:58
- VerificationCodeInputFieldKt.SingleDigitField (cognitive 17) auth/src/main/java/com/firebase/ui/auth/ui/components/VerificationCodeInputField.kt:278
- REDACTED
- REDACTED
- Near-duplicate member pair (56 shared lines) app/src/main/java/com/firebaseui/android/demo/MainActivity.kt:144
- Members sharing a duplicated core (6 members, 50+ identical tokens) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/common/AuthPage.kt:52
- Edited copy of a member (121 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/ResetPasswordUI.kt:72
- Edited copy of a member (81 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:159
- Edited copy of a member (74 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/mfa/MfaChallengeUI.kt:28
- Edited copy of a member (71 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaEnrollmentDefaults.kt:449
- Edited copy of a member (67 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:290
- Edited copy of a member (48 corresponding lines) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt:137
- Edited copy of a member (44 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:242
- Edited copy of a member (39 corresponding lines) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt:47
- Edited copy of a member (35 corresponding lines) auth/src/main/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt:96
- Edited copy of a member (33 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/SignInUI.kt:328
- Edited copy of a member (43 corresponding lines) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:88
- Edited copy of a member (19 corresponding lines) database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java:126
- Edited copy of a member (29 corresponding lines) auth/src/main/java/com/firebase/ui/auth/ui/screens/email/ResetPasswordUI.kt:196
- Edited copies of one member (3 members, 17+ corresponding lines) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt:24
- Edited copies of one member (3 members, 20+ corresponding lines) auth/src/main/java/com/firebase/ui/auth/configuration/validators/EmailValidator.kt:28
- Edited copy of a member (17 corresponding lines) database/src/main/java/com/firebase/ui/database/paging/FirebaseRecyclerPagingAdapter.java:70
- Edited copy of a member (11 corresponding lines) firestore/src/main/java/com/firebase/ui/firestore/paging/FirestorePagingOptions.java:204
- Edited copy of a member (9 corresponding lines) database/src/main/java/com/firebase/ui/database/paging/FirebaseRecyclerPagingAdapter.java:56
- Edited copy of a member (4 corresponding lines) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt:125
- Duplicated block (37 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt:148
- Duplicated block (28 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt:111
- Duplicated block (27 lines × 2) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt:139
- Duplicated block (22 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:258
- Duplicated block (20 lines × 2) app/src/main/java/com/firebaseui/android/demo/database/DatabaseDemoActivity.kt:56
- Duplicated block (19 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/AuthenticatedUI.kt:113
- Duplicated block (15–16 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/CustomMethodPickerDemoActivity.kt:206
- Duplicated block (16 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/EmailAuthSlotDemoActivity.kt:191
- Duplicated block (13–15 lines × 11) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt:57
- Duplicated block (13–15 lines × 6) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/common/AuthPage.kt:62
- Duplicated block (12–15 lines × 2) app/src/main/java/com/firebaseui/android/demo/auth/AuthFlowControllerDemoActivity.kt:194
- Duplicated block (11–12 lines × 3) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt:30
- Duplicated block (11 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/mfa/MfaChallengeUI.kt:62
- Duplicated block (17 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/AuthChooserActivity.kt:146
- Duplicated block (13 lines × 6) app/src/main/java/com/firebaseui/android/demo/MainActivity.kt:176
- Duplicated block (11 lines × 8) app/src/main/java/com/firebaseui/android/demo/MainActivity.kt:162
- Duplicated block (13 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/mfa/pages/ConfigureSmsStep.kt:105
- Duplicated block (9 lines × 3) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/LoginStep.kt:73
- Duplicated block (10 lines × 12) auth/src/main/java/com/firebase/ui/auth/configuration/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt:55
- Duplicated block (12 lines × 4) app/src/main/java/com/firebaseui/android/demo/auth/fullcustomization/screens/email/pages/LoginStep.kt:83
- Duplicated block (12 lines × 2) auth/src/main/java/com/firebase/ui/auth/ui/components/AuthProviderButton.kt:329
- Duplicated block (17 lines × 2) database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java:128
- Duplicated block (8 lines × 2) database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java:39
- Duplicated block (6 lines × 2) database/src/main/java/com/firebase/ui/database/paging/DefaultSnapshotDiffCallback.java:33
- Swallowed exception (caught, then discarded) app/src/main/java/com/firebaseui/android/demo/auth/HighLevelApiDemoActivity.kt:591
Minor — 30 finding(s)
- Orphaned file auth/src/main/java/com/firebase/ui/auth/ui/screens/mfa/MfaChallengeScreen.kt:1
- Orphaned file database/src/main/java/com/firebase/ui/database/FirebaseIndexArray.java:1
- Orphaned file common/src/main/java/com/firebase/ui/common/BaseObservableSnapshotArray.java:1
- Orphaned file auth/src/main/java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt:1
- Orphaned file database/src/main/java/com/firebase/ui/database/FirebaseListOptions.java:1
- Orphaned file database/src/main/java/com/firebase/ui/database/FirebaseRecyclerOptions.java:1
- Orphaned file firestore/src/main/java/com/firebase/ui/firestore/FirestoreRecyclerAdapter.java:1
- Orphaned file database/src/main/java/com/firebase/ui/database/FirebaseRecyclerAdapter.java:1
- Orphaned file auth/src/main/java/com/firebase/ui/auth/mfa/MfaChallengeContentState.kt:1
- Orphaned file auth/src/main/java/com/firebase/ui/auth/ui/components/QrCodeImage.kt:1
- Orphaned file firestore/src/main/java/com/firebase/ui/firestore/FirestoreRecyclerOptions.java:1
- Orphaned file database/src/main/java/com/firebase/ui/database/FirebaseListAdapter.java:1
- Orphaned file lint/src/main/java/com/firebaseui/lint/FirestoreRecyclerAdapterLifecycleDetector.kt:1
- Orphaned file firestore/src/main/java/com/firebase/ui/firestore/FirestoreArray.java:1
- Orphaned file database/src/main/java/com/firebase/ui/database/FirebaseArray.java:1
- Orphaned file auth/src/main/java/com/firebase/ui/auth/util/Preconditions.java:1
- Orphaned file auth/src/main/java/com/firebase/ui/auth/mfa/TotpSecret.kt:1
- Orphaned file firestore/src/main/java/com/firebase/ui/firestore/paging/FirestorePagingAdapter.java:1
- Orphaned file auth/src/main/java/com/firebase/ui/auth/mfa/MfaEnrollmentStep.kt:1
- Orphaned file scripts/translations/base_string_script.py:1
- Off-boarding risk: anonymized user #1
- No ADRs found build.gradle.kts:8
- `AuthSuccessUiContext` spells `Ui` where 64 names in the project spell it `UI` auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt:1010
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- No ADRs
- No SAST .github/workflows/android.yml:4
- No security response headers detected e2eTest/firebase.json:1
- Duplicated predicate auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt:981
Minor — 166 finding(s)
- Outdated (compile): com.squareup:javapoet
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-compat-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): org.codehaus.mojo:animal-sniffer-annotations
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): net.java.dev.jna:jna-platform
- Outdated (compile): net.java.dev.jna:jna
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): com.google.jimfs:jimfs
- Outdated (compile): org.apache.commons:commons-compress
- Outdated (compile): commons-codec:commons-codec
- Outdated (compile): commons-io:commons-io
- Outdated (compile): org.apache.commons:commons-lang3
- Outdated (compile): org.glassfish.jaxb:jaxb-runtime
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-70dfed2691c045449e4a1a68597ea19c/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-70dfed2691c045449e4a1a68597ea19c/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `auth/src/main/java/com/firebase/ui/auth/AuthFlowScope.kt`, `auth/src/main/java/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt`, `auth/src/main/java/com/firebase/ui/auth/ui/screens/reauth/ReauthDestinations.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — 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). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |