2.7

Adjusted Signal

2.7

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

4.8K

Stars

Kotlin

Language

120.1K

Lines of Code

536

Files

167

Pattern Hits

2026-10-31

Scan Date

0.01

HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 8.1/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 123 finding(s).

Hallucinated Dependency & Supply Chain Risk 4.9/100 · LOW

Are imports declared and package/API names verified? 44 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 9.5/100 · LOW

Which changes need focused human review? 167 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 8HIGH 0MEDIUM 0LOW 159

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 167 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Structural Annotation Overuse65 hits · 109 pts

Severity	File	Line	Snippet	Context
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	45	* // Step 1: Send verification code	COMMENT
LOW⚡	…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt	48	* // Step 2: Display masked phone number and wait for user input	COMMENT
LOW⚡	…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt	51	* // Step 3: If needed, resend code after timer expires	COMMENT
LOW⚡	…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt	54	* // Step 4: Verify the code entered by the user	COMMENT
LOW⚡	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	273	// Step 1: Create an email/password account first	COMMENT
LOW⚡	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	278	// Step 2: Sign out	COMMENT
LOW⚡	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	284	// Step 3: Sign in anonymously	COMMENT
LOW	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	334	// Step 4: Try to upgrade with existing email	COMMENT
LOW	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	376	// Step 5: Wait for onSignInFailure to fire with AccountLinkingRequiredException.	COMMENT
LOW	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	390	// Step 6: Verify ErrorRecoveryDialog is displayed	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	188	// Step 3: Navigate to phone auth from the authenticated content slot	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	196	// Step 4: Enter phone number and request verification code	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	357	// Step 4: Click "Link Google" from authenticated content	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	365	// Step 5: Click the Google sign-in button on the method picker	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	138	// Step 1: Create an email/password user, verify their email, and sign in	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	154	// Step 2: Set up auth screen with isCredentialLinkingEnabled + phone provider	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	210	// Step 5: Fetch verification code from emulator	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	234	// Step 6: Enter verification code	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	252	// Step 7: Wait for success	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	265	// Step 8: Verify the UID is preserved (linking happened, not a new account)	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	286	// Step 1: Create an email/password user, verify their email, and sign in	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	302	// Step 2: Configure mock Google credential	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	325	// Step 3: Set up auth screen with isCredentialLinkingEnabled + Google provider	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	378	// Step 6: Wait for linking to complete	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	391	// Step 7: Verify the UID is preserved and Google provider is added	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	162	// Step 1: Complete initial sign-in via the main screen form.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	185	// Step 2: the first attempt fails the way Firebase fails one, so `withReauth` raises it.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	527	// Step 1: complete initial sign-in via the main screen form (correct password).	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	548	// Step 2: emit Reauthentication.Required with a retryOperation.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	667	// Step 1: initial sign-in through the main screen.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	687	// Step 2: an operation that signs the user out, as delete() does.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	710	// Step 3: reauthenticate, which runs the signing-out operation.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	807	// Step 1: initial sign-in through the main screen.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	825	// Step 2: the first attempt fails the way Firebase fails one, so `withReauth` raises it.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	849	// Step 3: reauthenticate, which runs the password change.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	942	// Step 1: initial sign-in through the main screen.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	960	// Step 2: the first attempt fails the way Firebase fails one, so `withReauth` raises it.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	980	// Step 3: reauthenticate, which runs the deletion.	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	434	// Step 1: establish a pre-existing session - the "returning user".	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	445	// Step 2: mount PhoneAuthScreen standalone, exactly like the reporter's app -	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	474	// Step 3: enter phone number and request a verification code.	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	487	// Step 4: fetch verification code from emulator	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	511	// Step 5: enter verification code	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	529	// Step 6: onSuccess must fire - this is what issue #2352 reports as broken.	COMMENT
LOW	…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt	208	// Step 1: Sign in anonymously	COMMENT
LOW⚡	…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt	233	// Step 2: Click "Upgrade with Google" button	COMMENT
LOW⚡	…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt	241	// Step 3: Click the Google sign-in button on the method picker	COMMENT
LOW⚡	…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt	69	// Step 1: Send verification email to generate an OOB code	COMMENT
LOW⚡	…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt	76	// 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	100	// Step 3: Apply the action code to verify the email	COMMENT
LOW⚡	…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt	104	// 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	140	### Step 3: Update Provider Configuration	COMMENT
LOW	docs/upgrade-to-10.0.md	176	### Step 4: Update Theming	COMMENT
LOW	docs/upgrade-to-10.0.md	223	### Step 5: Update Sign Out	COMMENT
LOW	docs/upgrade-to-10.0.md	242	### Step 6: Update Account Deletion	COMMENT
5 more matches not shown…

Verbosity Indicators54 hits · 90 pts

Severity	File	Line	Snippet	Context
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	45	* // Step 1: Send verification code	COMMENT
LOW⚡	…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt	48	* // Step 2: Display masked phone number and wait for user input	COMMENT
LOW⚡	…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt	51	* // Step 3: If needed, resend code after timer expires	COMMENT
LOW⚡	…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt	54	* // Step 4: Verify the code entered by the user	COMMENT
LOW⚡	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	273	// Step 1: Create an email/password account first	COMMENT
LOW⚡	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	278	// Step 2: Sign out	COMMENT
LOW⚡	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	284	// Step 3: Sign in anonymously	COMMENT
LOW	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	334	// Step 4: Try to upgrade with existing email	COMMENT
LOW	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	376	// Step 5: Wait for onSignInFailure to fire with AccountLinkingRequiredException.	COMMENT
LOW	…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt	390	// Step 6: Verify ErrorRecoveryDialog is displayed	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	188	// Step 3: Navigate to phone auth from the authenticated content slot	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	196	// Step 4: Enter phone number and request verification code	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	357	// Step 4: Click "Link Google" from authenticated content	COMMENT
LOW⚡	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	365	// Step 5: Click the Google sign-in button on the method picker	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	138	// Step 1: Create an email/password user, verify their email, and sign in	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	154	// Step 2: Set up auth screen with isCredentialLinkingEnabled + phone provider	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	210	// Step 5: Fetch verification code from emulator	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	234	// Step 6: Enter verification code	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	252	// Step 7: Wait for success	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	265	// Step 8: Verify the UID is preserved (linking happened, not a new account)	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	286	// Step 1: Create an email/password user, verify their email, and sign in	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	302	// Step 2: Configure mock Google credential	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	325	// Step 3: Set up auth screen with isCredentialLinkingEnabled + Google provider	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	378	// Step 6: Wait for linking to complete	COMMENT
LOW	…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt	391	// Step 7: Verify the UID is preserved and Google provider is added	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	162	// Step 1: Complete initial sign-in via the main screen form.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	185	// Step 2: the first attempt fails the way Firebase fails one, so `withReauth` raises it.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	527	// Step 1: complete initial sign-in via the main screen form (correct password).	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	548	// Step 2: emit Reauthentication.Required with a retryOperation.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	667	// Step 1: initial sign-in through the main screen.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	687	// Step 2: an operation that signs the user out, as delete() does.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	710	// Step 3: reauthenticate, which runs the signing-out operation.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	807	// Step 1: initial sign-in through the main screen.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	825	// Step 2: the first attempt fails the way Firebase fails one, so `withReauth` raises it.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	849	// Step 3: reauthenticate, which runs the password change.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	942	// Step 1: initial sign-in through the main screen.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	960	// Step 2: the first attempt fails the way Firebase fails one, so `withReauth` raises it.	COMMENT
LOW	…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt	980	// Step 3: reauthenticate, which runs the deletion.	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	434	// Step 1: establish a pre-existing session - the "returning user".	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	445	// Step 2: mount PhoneAuthScreen standalone, exactly like the reporter's app -	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	474	// Step 3: enter phone number and request a verification code.	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	487	// Step 4: fetch verification code from emulator	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	511	// Step 5: enter verification code	COMMENT
LOW	…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt	529	// Step 6: onSuccess must fire - this is what issue #2352 reports as broken.	COMMENT
LOW	…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt	208	// Step 1: Sign in anonymously	COMMENT
LOW⚡	…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt	233	// Step 2: Click "Upgrade with Google" button	COMMENT
LOW⚡	…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt	241	// Step 3: Click the Google sign-in button on the method picker	COMMENT
LOW⚡	…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt	69	// Step 1: Send verification email to generate an OOB code	COMMENT
LOW⚡	…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt	76	// 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	100	// Step 3: Apply the action code to verify the email	COMMENT
LOW⚡	…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt	104	// Step 4: Reload the user to refresh their email verification status	COMMENT

Hallucination Indicators8 hits · 85 pts

Severity	File	Line	Snippet	Context
CRITICAL	…rebaseui/android/demo/database/DatabaseDemoActivity.kt	90	com.google.android.gms.tasks.Tasks.forResult(null)	CODE
CRITICAL	…baseui/android/demo/firestore/FirestoreDemoActivity.kt	94	com.google.android.gms.tasks.Tasks.forResult(null)	CODE
CRITICAL	…rebaseui/android/demo/auth/HighLevelApiDemoActivity.kt	512	com.firebase.ui.auth.configuration.validators.PasswordValidator(	CODE
CRITICAL	…rebaseui/android/demo/auth/HighLevelApiDemoActivity.kt	518	com.firebase.ui.auth.configuration.validators.PasswordValidator(	CODE
CRITICAL	…rebaseui/android/demo/auth/HighLevelApiDemoActivity.kt	533	com.firebase.ui.auth.ui.components.AuthTextField(	CODE
CRITICAL	…rebaseui/android/demo/auth/HighLevelApiDemoActivity.kt	543	com.firebase.ui.auth.ui.components.AuthTextField(	CODE
CRITICAL	…th/ui/screens/mfa/MfaEnrollmentTotpRegenerationTest.kt	367	com.firebase.ui.auth.mfa.TotpSecret.from(firstSecret)	CODE
CRITICAL	…main/java/com/firebase/ui/auth/FirebaseAuthActivity.kt	185	* Use [com.google.firebase.auth.FirebaseAuth.getInstance().currentUser] to get the full user object.	COMMENT

Fake / Example Data25 hits · 26 pts

Severity	File	Line	Snippet	Context
LOW	CONTRIBUTING.md	256	* email = "user@example.com",	COMMENT
LOW	…a/com/firebase/ui/auth/ui/TestTagsAsResourceIdsTest.kt	619	identifier = "user@example.com",	CODE
LOW	…a/com/firebase/ui/auth/ui/TestTagsAsResourceIdsTest.kt	642	email = "user@example.com",	CODE
LOW	…a/com/firebase/ui/auth/ui/TestTagsAsResourceIdsTest.kt	659	email = "user@example.com",	CODE
LOW	…a/com/firebase/ui/auth/ui/TestTagsAsResourceIdsTest.kt	672	whenever(user.email).thenReturn("user@example.com")	CODE
LOW	…/ui/screens/FirebaseAuthScreenMfaEnrollmentExitTest.kt	108	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…ui/auth/ui/screens/FirebaseAuthScreenMfaSuccessTest.kt	145	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…th/ui/screens/mfa/MfaEnrollmentTotpRegenerationTest.kt	118	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…uth/ui/screens/mfa/MfaEnrollmentRouteNavigationTest.kt	116	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…/ui/auth/ui/screens/mfa/MfaEnrollmentEntryResetTest.kt	142	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…ase/ui/auth/ui/screens/mfa/MfaEnrollmentSmsStepTest.kt	109	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…th/ui/screens/mfa/MfaEnrollmentHostDestinationsTest.kt	119	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…/screens/mfa/MfaEnrollmentCountryReconciliationTest.kt	103	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…i/screens/mfa/MfaEnrollmentFlowStateRestorationTest.kt	126	`when`(mockUser.email).thenReturn("user@example.com")	CODE
LOW	…/com/firebase/ui/auth/ui/screens/email/SignInUITest.kt	188	val prefillEmail = "user@example.com"	CODE
LOW	…/com/firebase/ui/auth/ui/screens/email/SignInUITest.kt	252	composeTestRule.onNodeWithText("user@example.com").assertDoesNotExist()	CODE
LOW	…ebase/ui/auth/ui/method_picker/AuthMethodPickerTest.kt	486	identifier = "user@example.com",	CODE
LOW	…ebase/ui/auth/ui/method_picker/AuthMethodPickerTest.kt	525	identifier = "user@example.com",	CODE
LOW	…ebase/ui/auth/ui/method_picker/AuthMethodPickerTest.kt	552	identifier = "user@example.com",	CODE
LOW	…ebase/ui/auth/ui/method_picker/AuthMethodPickerTest.kt	575	Truth.assertThat(continueAsIdentifier).isEqualTo("user@example.com")	CODE
LOW	…ebase/ui/auth/ui/method_picker/AuthMethodPickerTest.kt	587	identifier = "user@example.com",	CODE
LOW	…/auth_provider/GoogleAuthProviderFirebaseAuthUITest.kt	280	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

Unused Imports11 hits · 11 pts

Severity	File	Line	Context
LOW	scripts/translations/add_string_prefix.py	3	CODE
LOW	scripts/translations/add_string_prefix.py	4	CODE
LOW	scripts/translations/export_translations.py	4	CODE
LOW	scripts/translations/export_translations.py	6	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

Example Usage Blocks2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	scripts/compare.sh	1	# Usage:	COMMENT
LOW	scripts/translations/remove_string.py	6	# Usage:	COMMENT

Over-Commented Block1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	…ava/com/firebase/ui/auth/FirebaseUIComposeRegistrar.kt	1	// Copyright 2025 Google LLC	COMMENT

Deep Nesting1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	scripts/translations/base_string_script.py	36		CODE

firebase/FirebaseUI-Android

Open-Source Code Quality, Security and Technical Debt Review