Repository Analysis

firebase/FirebaseUI-Android

Optimized UI components for Firebase

3.9 Likely human-written View on GitHub

Analysis Overview

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).

3.9
Adjusted Score
3.9
Raw Score
100%
Time Factor
2026-07-14
Last Push
4.8K
Stars
Kotlin
Language
83.9K
Lines of Code
421
Files
145
Pattern Hits
2026-07-14
Scan Date
0.02
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

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.

No multi-scan history yet — run the scanner again to build trend data.

Severity Breakdown

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.

CRITICAL 8HIGH 0MEDIUM 0LOW 137

Directory Score Breakdown

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.

Pattern Findings

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.

Structural Annotation Overuse59 hits · 110 pts
SeverityFileLineSnippetContext
LOW…/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt84 * // Step 1: Sign in anonymouslyCOMMENT
LOW…/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt87 * // Step 2: Later, upgrade to permanent accountCOMMENT
LOW…tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt43 * // Step 1: Start verificationCOMMENT
LOW…tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt49 * // Step 2: Observe AuthStateCOMMENT
LOW…tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt75 * // Step 3: When user enters codeCOMMENT
LOW…java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt36 * // Step 1: Generate a TOTP secretCOMMENT
LOW…java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt39 * // Step 2: Display QR code to userCOMMENT
LOW…java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt42 * // Step 3: Verify the code entered by the userCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt43 * // Step 1: Send verification codeCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt46 * // Step 2: Display masked phone number and wait for user inputCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt49 * // Step 3: If needed, resend code after timer expiresCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt52 * // Step 4: Verify the code entered by the userCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt286 // Step 1: Create an email/password account firstCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt291 // Step 2: Sign outCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt297 // Step 3: Sign in anonymouslyCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt343 // Step 4: Try to upgrade with existing emailCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt385 // Step 5: Wait for error state (AccountLinkingRequiredException)COMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt393 // Step 6: Verify ErrorRecoveryDialog is displayedCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt201 // Step 3: Navigate to phone auth from the authenticated content slotCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt209 // Step 4: Enter phone number and request verification codeCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt263 // Step 7: Wait for successCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt271 // Step 8: Verify the UID is preserved (linking happened, not a new account)COMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt363 // Step 4: Click "Link Google" from authenticated contentCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt371 // Step 5: Click the Google sign-in button on the method pickerCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt384 // Step 6: Wait for linking to completeCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt392 // Step 7: Verify the UID is preserved and Google provider is addedCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt151 // Step 1: Create an email/password user, verify their email, and sign inCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt167 // Step 2: Set up auth screen with isCredentialLinkingEnabled + phone providerCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt223 // Step 5: Fetch verification code from emulatorCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt247 // Step 6: Enter verification codeCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt292 // Step 1: Create an email/password user, verify their email, and sign inCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt308 // Step 2: Configure mock Google credentialCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt331 // Step 3: Set up auth screen with isCredentialLinkingEnabled + Google providerCOMMENT
LOW…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt157 // Step 1: Complete initial sign-in via the main screen form.COMMENT
LOW…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt180 // Step 2: Emit ReauthenticationRequired to simulate a sensitive operation requiring reauth.COMMENT
LOW…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt198 // Step 3: Enter credentials in the reauth bottom sheet.COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt421 // Step 1: establish a pre-existing session - the "returning user".COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt432 // Step 2: mount PhoneAuthScreen standalone, exactly like the reporter's app -COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt461 // Step 3: enter phone number and request a verification code.COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt474 // Step 4: fetch verification code from emulatorCOMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt498 // Step 5: enter verification codeCOMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt514 // Step 6: onSuccess must fire - this is what issue #2352 reports as broken.COMMENT
LOW…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt220 // Step 1: Sign in anonymouslyCOMMENT
LOW…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt245 // Step 2: Click "Upgrade with Google" buttonCOMMENT
LOW…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt253 // Step 3: Click the Google sign-in button on the method pickerCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt61 // Step 1: Send verification email to generate an OOB codeCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt68 // Step 2: Retrieve the VERIFY_EMAIL OOB code for this user from the emulatorCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt92 // Step 3: Apply the action code to verify the emailCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt96 // Step 4: Reload the user to refresh their email verification statusCOMMENT
LOWdocs/upgrade-to-10.0.md38### Step 1: Update DependenciesCOMMENT
LOWdocs/upgrade-to-10.0.md62### Step 2: Migrate to ComposeCOMMENT
LOWdocs/upgrade-to-10.0.md136### Step 3: Update Provider ConfigurationCOMMENT
LOWdocs/upgrade-to-10.0.md169### Step 4: Update ThemingCOMMENT
LOWdocs/upgrade-to-10.0.md210### Step 5: Update Sign OutCOMMENT
LOWdocs/upgrade-to-10.0.md229### Step 6: Update Account DeletionCOMMENT
LOWdocs/upgrade-to-10.0.md256### Step 7: Auth State ObservationCOMMENT
LOW.github/ISSUE_TEMPLATE.md12### Step 1: Are you in the right place?COMMENT
LOW.github/ISSUE_TEMPLATE.md19### Step 2: Describe your environmentCOMMENT
LOW.github/ISSUE_TEMPLATE.md27### Step 3: Describe the problem:COMMENT
Verbosity Indicators49 hits · 92 pts
SeverityFileLineSnippetContext
LOW…/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt84 * // Step 1: Sign in anonymouslyCOMMENT
LOW…/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt87 * // Step 2: Later, upgrade to permanent accountCOMMENT
LOW…tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt43 * // Step 1: Start verificationCOMMENT
LOW…tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt49 * // Step 2: Observe AuthStateCOMMENT
LOW…tion/auth_provider/PhoneAuthProvider+FirebaseAuthUI.kt75 * // Step 3: When user enters codeCOMMENT
LOW…java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt36 * // Step 1: Generate a TOTP secretCOMMENT
LOW…java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt39 * // Step 2: Display QR code to userCOMMENT
LOW…java/com/firebase/ui/auth/mfa/TotpEnrollmentHandler.kt42 * // Step 3: Verify the code entered by the userCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt43 * // Step 1: Send verification codeCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt46 * // Step 2: Display masked phone number and wait for user inputCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt49 * // Step 3: If needed, resend code after timer expiresCOMMENT
LOW…/java/com/firebase/ui/auth/mfa/SmsEnrollmentHandler.kt52 * // Step 4: Verify the code entered by the userCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt286 // Step 1: Create an email/password account firstCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt291 // Step 2: Sign outCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt297 // Step 3: Sign in anonymouslyCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt343 // Step 4: Try to upgrade with existing emailCOMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt385 // Step 5: Wait for error state (AccountLinkingRequiredException)COMMENT
LOW…firebase/ui/auth/ui/screens/AnonymousAuthScreenTest.kt393 // Step 6: Verify ErrorRecoveryDialog is displayedCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt201 // Step 3: Navigate to phone auth from the authenticated content slotCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt209 // Step 4: Enter phone number and request verification codeCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt263 // Step 7: Wait for successCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt271 // Step 8: Verify the UID is preserved (linking happened, not a new account)COMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt363 // Step 4: Click "Link Google" from authenticated contentCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt371 // Step 5: Click the Google sign-in button on the method pickerCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt384 // Step 6: Wait for linking to completeCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt392 // Step 7: Verify the UID is preserved and Google provider is addedCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt151 // Step 1: Create an email/password user, verify their email, and sign inCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt167 // Step 2: Set up auth screen with isCredentialLinkingEnabled + phone providerCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt223 // Step 5: Fetch verification code from emulatorCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt247 // Step 6: Enter verification codeCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt292 // Step 1: Create an email/password user, verify their email, and sign inCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt308 // Step 2: Configure mock Google credentialCOMMENT
LOW…base/ui/auth/ui/screens/CredentialLinkingScreenTest.kt331 // Step 3: Set up auth screen with isCredentialLinkingEnabled + Google providerCOMMENT
LOW…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt157 // Step 1: Complete initial sign-in via the main screen form.COMMENT
LOW…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt180 // Step 2: Emit ReauthenticationRequired to simulate a sensitive operation requiring reauth.COMMENT
LOW…java/com/firebase/ui/auth/ui/screens/ReauthFlowTest.kt198 // Step 3: Enter credentials in the reauth bottom sheet.COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt421 // Step 1: establish a pre-existing session - the "returning user".COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt432 // Step 2: mount PhoneAuthScreen standalone, exactly like the reporter's app -COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt461 // Step 3: enter phone number and request a verification code.COMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt474 // Step 4: fetch verification code from emulatorCOMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt498 // Step 5: enter verification codeCOMMENT
LOW…com/firebase/ui/auth/ui/screens/PhoneAuthScreenTest.kt514 // Step 6: onSuccess must fire - this is what issue #2352 reports as broken.COMMENT
LOW…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt220 // Step 1: Sign in anonymouslyCOMMENT
LOW…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt245 // Step 2: Click "Upgrade with Google" buttonCOMMENT
LOW…om/firebase/ui/auth/ui/screens/GoogleAuthScreenTest.kt253 // Step 3: Click the Google sign-in button on the method pickerCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt61 // Step 1: Send verification email to generate an OOB codeCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt68 // Step 2: Retrieve the VERIFY_EMAIL OOB code for this user from the emulatorCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt92 // Step 3: Apply the action code to verify the emailCOMMENT
LOW…test/java/com/firebase/ui/auth/testutil/TestHelpers.kt96 // Step 4: Reload the user to refresh their email verification statusCOMMENT
Hallucination Indicators8 hits · 85 pts
SeverityFileLineSnippetContext
CRITICAL…om/firebaseui/android/demo/HighLevelApiDemoActivity.kt445 com.firebase.ui.auth.ui.components.AuthTextField(CODE
CRITICAL…om/firebaseui/android/demo/HighLevelApiDemoActivity.kt515 com.firebase.ui.auth.configuration.validators.PasswordValidator(CODE
CRITICAL…om/firebaseui/android/demo/HighLevelApiDemoActivity.kt521 com.firebase.ui.auth.configuration.validators.PasswordValidator(CODE
CRITICAL…om/firebaseui/android/demo/HighLevelApiDemoActivity.kt536 com.firebase.ui.auth.ui.components.AuthTextField(CODE
CRITICAL…om/firebaseui/android/demo/HighLevelApiDemoActivity.kt546 com.firebase.ui.auth.ui.components.AuthTextField(CODE
CRITICAL…main/java/com/firebase/ui/auth/FirebaseAuthActivity.kt178 * Use [com.google.firebase.auth.FirebaseAuth.getInstance().currentUser] to get the full user object.COMMENT
CRITICAL…/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt942 com.firebase.ui.auth.ui.screens.email.EmailAuthScreen(CODE
CRITICAL…/com/firebase/ui/auth/ui/screens/FirebaseAuthScreen.kt956 com.firebase.ui.auth.ui.screens.phone.PhoneAuthScreen(CODE
Fake / Example Data16 hits · 23 pts
SeverityFileLineSnippetContext
LOWCONTRIBUTING.md254 * email = "user@example.com",COMMENT
LOW…/auth_provider/GoogleAuthProviderFirebaseAuthUITest.kt267 val expectedDisplayName = "John Doe"CODE
LOW…uth/credentialmanager/PasswordCredentialHandlerTest.kt103 handler.savePassword("user@example.com", "")CODE
LOW…uth/credentialmanager/PasswordCredentialHandlerTest.kt123 handler.savePassword("user@example.com", " ")CODE
LOW…c/test/java/com/firebase/ui/auth/mfa/TotpSecretTest.kt60 val accountName = "user@example.com"CODE
LOW…/auth_provider/AnonymousAuthProvider+FirebaseAuthUI.kt93 * name = "John Doe",COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt109 * name = "John Doe",COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt294 * email = "user@example.com",COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt313 * email = "user@example.com",COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt586 * val displayName = "John Doe" // From Google profileCOMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt629 * email = "user@example.com",COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt760 * email = "user@example.com"COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt771 * email = "user@example.com",COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt785 * email = "user@example.com"COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt1226 * email = "user@example.com"COMMENT
LOW…tion/auth_provider/EmailAuthProvider+FirebaseAuthUI.kt1249 * email = "user@example.com",COMMENT
Unused Imports9 hits · 9 pts
SeverityFileLineSnippetContext
LOWscripts/translations/add_string_prefix.py3CODE
LOWscripts/translations/add_string_prefix.py4CODE
LOWscripts/translations/remove_string.py10CODE
LOWscripts/translations/remove_string.py11CODE
LOWscripts/translations/base_string_script.py3CODE
LOWscripts/translations/base_string_script.py4CODE
LOWscripts/translations/base_string_script.py5CODE
LOWscripts/translations/remove_non_translatable.py3CODE
LOWscripts/translations/remove_non_translatable.py4CODE
Example Usage Blocks2 hits · 3 pts
SeverityFileLineSnippetContext
LOWscripts/compare.sh1# Usage:COMMENT
LOWscripts/translations/remove_string.py6# Usage:COMMENT
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…ava/com/firebase/ui/auth/FirebaseUIComposeRegistrar.kt1// Copyright 2025 Google LLCCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/translations/base_string_script.py36CODE