Optimized UI components for Firebase
This report presents the forensic synthetic code analysis of firebase/FirebaseUI-Android, a Kotlin project with 4,795 GitHub stars. SynthScan v2.0 examined 83,931 lines of code across 421 source files, recording 145 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 3.9 places this repository in the Likely human-written band.
The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).
Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.
Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.
This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.
The scanner identified 145 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | …/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt | 84 | * // Step 1: Sign in anonymously | COMMENT |
| LOW⚡ | …/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt | 87 | * // Step 2: Later, upgrade to permanent account | COMMENT |
| LOW⚡ | …tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt | 43 | * // Step 1: Start verification | COMMENT |
| LOW⚡ | …tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt | 49 | * // Step 2: Observe AuthState | COMMENT |
| LOW | …tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt | 75 | * // Step 3: When user enters code | COMMENT |
| LOW⚡ | …java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt | 36 | * // Step 1: Generate a TOTP secret | COMMENT |
| LOW⚡ | …java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt | 39 | * // Step 2: Display QR code to user | COMMENT |
| LOW⚡ | …java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt | 42 | * // Step 3: Verify the code entered by the user | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 43 | * // Step 1: Send verification code | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 46 | * // Step 2: Display masked phone number and wait for user input | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 49 | * // Step 3: If needed, resend code after timer expires | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 52 | * // Step 4: Verify the code entered by the user | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 286 | // Step 1: Create an email/password account first | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 291 | // Step 2: Sign out | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 297 | // Step 3: Sign in anonymously | COMMENT |
| LOW | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 343 | // Step 4: Try to upgrade with existing email | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 385 | // Step 5: Wait for error state (AccountLinkingRequiredException) | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 393 | // Step 6: Verify ErrorRecoveryDialog is displayed | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 201 | // Step 3: Navigate to phone auth from the authenticated content slot | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 209 | // Step 4: Enter phone number and request verification code | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 263 | // Step 7: Wait for success | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 271 | // Step 8: Verify the UID is preserved (linking happened, not a new account) | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 363 | // Step 4: Click "Link Google" from authenticated content | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 371 | // Step 5: Click the Google sign-in button on the method picker | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 384 | // Step 6: Wait for linking to complete | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 392 | // Step 7: Verify the UID is preserved and Google provider is added | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 151 | // Step 1: Create an email/password user, verify their email, and sign in | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 167 | // Step 2: Set up auth screen with isCredentialLinkingEnabled + phone provider | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 223 | // Step 5: Fetch verification code from emulator | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 247 | // Step 6: Enter verification code | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 292 | // Step 1: Create an email/password user, verify their email, and sign in | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 308 | // Step 2: Configure mock Google credential | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 331 | // Step 3: Set up auth screen with isCredentialLinkingEnabled + Google provider | COMMENT |
| LOW | …java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt | 157 | // Step 1: Complete initial sign-in via the main screen form. | COMMENT |
| LOW | …java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt | 180 | // Step 2: Emit ReauthenticationRequired to simulate a sensitive operation requiring reauth. | COMMENT |
| LOW | …java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt | 198 | // Step 3: Enter credentials in the reauth bottom sheet. | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 421 | // Step 1: establish a pre-existing session - the "returning user". | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 432 | // Step 2: mount PhoneAuthScreen standalone, exactly like the reporter's app - | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 461 | // Step 3: enter phone number and request a verification code. | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 474 | // Step 4: fetch verification code from emulator | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 498 | // Step 5: enter verification code | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 514 | // Step 6: onSuccess must fire - this is what issue #2352 reports as broken. | COMMENT |
| LOW | …om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt | 220 | // Step 1: Sign in anonymously | COMMENT |
| LOW⚡ | …om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt | 245 | // Step 2: Click "Upgrade with Google" button | COMMENT |
| LOW⚡ | …om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt | 253 | // Step 3: Click the Google sign-in button on the method picker | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 61 | // Step 1: Send verification email to generate an OOB code | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 68 | // Step 2: Retrieve the VERIFY_EMAIL OOB code for this user from the emulator | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 92 | // Step 3: Apply the action code to verify the email | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 96 | // Step 4: Reload the user to refresh their email verification status | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 38 | ### Step 1: Update Dependencies | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 62 | ### Step 2: Migrate to Compose | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 136 | ### Step 3: Update Provider Configuration | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 169 | ### Step 4: Update Theming | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 210 | ### Step 5: Update Sign Out | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 229 | ### Step 6: Update Account Deletion | COMMENT |
| LOW | docs/upgrade-to-10.0.md | 256 | ### Step 7: Auth State Observation | COMMENT |
| LOW⚡ | .github/ISSUE_TEMPLATE.md | 12 | ### Step 1: Are you in the right place? | COMMENT |
| LOW⚡ | .github/ISSUE_TEMPLATE.md | 19 | ### Step 2: Describe your environment | COMMENT |
| LOW⚡ | .github/ISSUE_TEMPLATE.md | 27 | ### Step 3: Describe the problem: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | …/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt | 84 | * // Step 1: Sign in anonymously | COMMENT |
| LOW⚡ | …/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt | 87 | * // Step 2: Later, upgrade to permanent account | COMMENT |
| LOW⚡ | …tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt | 43 | * // Step 1: Start verification | COMMENT |
| LOW⚡ | …tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt | 49 | * // Step 2: Observe AuthState | COMMENT |
| LOW | …tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt | 75 | * // Step 3: When user enters code | COMMENT |
| LOW⚡ | …java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt | 36 | * // Step 1: Generate a TOTP secret | COMMENT |
| LOW⚡ | …java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt | 39 | * // Step 2: Display QR code to user | COMMENT |
| LOW⚡ | …java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt | 42 | * // Step 3: Verify the code entered by the user | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 43 | * // Step 1: Send verification code | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 46 | * // Step 2: Display masked phone number and wait for user input | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 49 | * // Step 3: If needed, resend code after timer expires | COMMENT |
| LOW⚡ | …/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt | 52 | * // Step 4: Verify the code entered by the user | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 286 | // Step 1: Create an email/password account first | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 291 | // Step 2: Sign out | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 297 | // Step 3: Sign in anonymously | COMMENT |
| LOW | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 343 | // Step 4: Try to upgrade with existing email | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 385 | // Step 5: Wait for error state (AccountLinkingRequiredException) | COMMENT |
| LOW⚡ | …firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt | 393 | // Step 6: Verify ErrorRecoveryDialog is displayed | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 201 | // Step 3: Navigate to phone auth from the authenticated content slot | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 209 | // Step 4: Enter phone number and request verification code | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 263 | // Step 7: Wait for success | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 271 | // Step 8: Verify the UID is preserved (linking happened, not a new account) | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 363 | // Step 4: Click "Link Google" from authenticated content | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 371 | // Step 5: Click the Google sign-in button on the method picker | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 384 | // Step 6: Wait for linking to complete | COMMENT |
| LOW⚡ | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 392 | // Step 7: Verify the UID is preserved and Google provider is added | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 151 | // Step 1: Create an email/password user, verify their email, and sign in | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 167 | // Step 2: Set up auth screen with isCredentialLinkingEnabled + phone provider | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 223 | // Step 5: Fetch verification code from emulator | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 247 | // Step 6: Enter verification code | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 292 | // Step 1: Create an email/password user, verify their email, and sign in | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 308 | // Step 2: Configure mock Google credential | COMMENT |
| LOW | …base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt | 331 | // Step 3: Set up auth screen with isCredentialLinkingEnabled + Google provider | COMMENT |
| LOW | …java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt | 157 | // Step 1: Complete initial sign-in via the main screen form. | COMMENT |
| LOW | …java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt | 180 | // Step 2: Emit ReauthenticationRequired to simulate a sensitive operation requiring reauth. | COMMENT |
| LOW | …java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt | 198 | // Step 3: Enter credentials in the reauth bottom sheet. | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 421 | // Step 1: establish a pre-existing session - the "returning user". | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 432 | // Step 2: mount PhoneAuthScreen standalone, exactly like the reporter's app - | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 461 | // Step 3: enter phone number and request a verification code. | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 474 | // Step 4: fetch verification code from emulator | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 498 | // Step 5: enter verification code | COMMENT |
| LOW | …com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt | 514 | // Step 6: onSuccess must fire - this is what issue #2352 reports as broken. | COMMENT |
| LOW | …om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt | 220 | // Step 1: Sign in anonymously | COMMENT |
| LOW⚡ | …om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt | 245 | // Step 2: Click "Upgrade with Google" button | COMMENT |
| LOW⚡ | …om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt | 253 | // Step 3: Click the Google sign-in button on the method picker | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 61 | // Step 1: Send verification email to generate an OOB code | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 68 | // Step 2: Retrieve the VERIFY_EMAIL OOB code for this user from the emulator | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 92 | // Step 3: Apply the action code to verify the email | COMMENT |
| LOW⚡ | …test/java/com/firebase/ui/auth/testutil/TestHelpers.kt | 96 | // Step 4: Reload the user to refresh their email verification status | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | …om/firebaseui/android/demo/HighLevelApiDemoActivity.kt | 445 | com.firebase.ui.auth.ui.components.AuthTextField( | CODE |
| CRITICAL | …om/firebaseui/android/demo/HighLevelApiDemoActivity.kt | 515 | com.firebase.ui.auth.configuration.validators.PasswordValidator( | CODE |
| CRITICAL | …om/firebaseui/android/demo/HighLevelApiDemoActivity.kt | 521 | com.firebase.ui.auth.configuration.validators.PasswordValidator( | CODE |
| CRITICAL | …om/firebaseui/android/demo/HighLevelApiDemoActivity.kt | 536 | com.firebase.ui.auth.ui.components.AuthTextField( | CODE |
| CRITICAL | …om/firebaseui/android/demo/HighLevelApiDemoActivity.kt | 546 | com.firebase.ui.auth.ui.components.AuthTextField( | CODE |
| CRITICAL | …main/java/com/firebase/ui/auth/FirebaseAuthActivity.kt | 178 | * Use [com.google.firebase.auth.FirebaseAuth.getInstance().currentUser] to get the full user object. | COMMENT |
| CRITICAL | …/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt | 942 | com.firebase.ui.auth.ui.screens.email.EmailAuthScreen( | CODE |
| CRITICAL | …/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt | 956 | com.firebase.ui.auth.ui.screens.phone.PhoneAuthScreen( | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | CONTRIBUTING.md | 254 | * email = "user@example.com", | COMMENT |
| LOW | …/auth_provider/GoogleAuthProviderFirebaseAuthUITest.kt | 267 | val expectedDisplayName = "John Doe" | CODE |
| LOW | …uth/credentialmanager/PasswordCredentialHandlerTest.kt | 103 | handler.savePassword("user@example.com", "") | CODE |
| LOW | …uth/credentialmanager/PasswordCredentialHandlerTest.kt | 123 | handler.savePassword("user@example.com", " ") | CODE |
| LOW | …c/test/java/com/firebase/ui/auth/mfa/TotpSecretTest.kt | 60 | val accountName = "user@example.com" | CODE |
| LOW⚡ | …/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt | 93 | * name = "John Doe", | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 109 | * name = "John Doe", | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 294 | * email = "user@example.com", | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 313 | * email = "user@example.com", | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 586 | * val displayName = "John Doe" // From Google profile | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 629 | * email = "user@example.com", | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 760 | * email = "user@example.com" | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 771 | * email = "user@example.com", | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 785 | * email = "user@example.com" | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 1226 | * email = "user@example.com" | COMMENT |
| LOW | …tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt | 1249 | * email = "user@example.com", | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/translations/add_string_prefix.py | 3 | CODE | |
| LOW | scripts/translations/add_string_prefix.py | 4 | CODE | |
| LOW | scripts/translations/remove_string.py | 10 | CODE | |
| LOW | scripts/translations/remove_string.py | 11 | CODE | |
| LOW | scripts/translations/base_string_script.py | 3 | CODE | |
| LOW | scripts/translations/base_string_script.py | 4 | CODE | |
| LOW | scripts/translations/base_string_script.py | 5 | CODE | |
| LOW | scripts/translations/remove_non_translatable.py | 3 | CODE | |
| LOW | scripts/translations/remove_non_translatable.py | 4 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/compare.sh | 1 | # Usage: | COMMENT |
| LOW | scripts/translations/remove_string.py | 6 | # Usage: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …ava/com/firebase/ui/auth/FirebaseUIComposeRegistrar.kt | 1 | // Copyright 2025 Google LLC | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/translations/base_string_script.py | 36 | CODE |