firebase / FirebaseUI-Android
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
properties
pro
txt
  • 17 extensions are included in analyses: java, xml, md, kts, html, properties, kt, py, sh, pro, json, gitignore, gradle, txt, svg, bat, yml
  • 8 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (2 files).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (9 files).
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/docs/.*" (Documentation) (21 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*[.]txt" (Text files) (1 file).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main14504 LOC (45%) 189 files
test4470 LOC (14%) 44 files
generated0 LOC (0%) 0 files
build and deployment141 LOC (<1%) 7 files
other12644 LOC (39%) 187 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
pro
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 189 files match defined criteria (14,504 lines of code, 100.0% vs. main code):
    • 165 *.java files (13,607 lines of code)
    • 12 *.kts files (481 lines of code)
    • 5 *.kt files (251 lines of code)
    • 6 *.py files (145 lines of code)
    • 1 *.pro files (20 lines of code)
  • " *.java" is biggest, containing 93.82% of code.
  • " *.pro" is smallest, containing 0.14% of code.


*.java13607 LOC (93%) 165 files
*.kts481 LOC (3%) 12 files
*.kt251 LOC (1%) 5 files
*.py145 LOC (<1%) 6 files
*.pro20 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/src/androidTest/.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*[-]tests/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 44 files match defined criteria (4,470 lines of code, 30.8% vs. main code):
    • 41 *.java files (4,294 lines of code)
    • 2 *.kt files (118 lines of code)
    • 1 *.kts files (58 lines of code)
  • " *.java" is biggest, containing 96.06% of code.
  • " *.kts" is smallest, containing 1.3% of code.


*.java4294 LOC (96%) 41 files
*.kt118 LOC (2%) 2 files
*.kts58 LOC (1%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*[.]bat".
  • 7 files match defined criteria (141 lines of code, 1.0% vs. main code):
    • 1 *.bat files (68 lines of code)
    • 4 *.sh files (49 lines of code)
    • 2 *.gradle files (24 lines of code)
  • " *.bat" is biggest, containing 48.23% of code.
  • " *.gradle" is smallest, containing 17.02% of code.


*.bat68 LOC (48%) 1 files
*.sh49 LOC (34%) 4 files
*.gradle24 LOC (17%) 2 files
Other Code
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]json".
    • files with paths like ".*/checkstyle[.]xml".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 187 files match defined criteria (12,644 lines of code, 87.2% vs. main code):
    • 172 *.xml files (10,851 lines of code)
    • 6 *.md files (1,713 lines of code)
    • 1 *.json files (50 lines of code)
    • 8 *.properties files (30 lines of code)
  • " *.xml" is biggest, containing 85.82% of code.
  • " *.properties" is smallest, containing 0.24% of code.


*.xml10851 LOC (85%) 172 files
*.md1713 LOC (13%) 6 files
*.json50 LOC (<1%) 1 files
*.properties30 LOC (<1%) 8 files
Analyzers
Info about analyzers used for source code examinations.
  • *.java files are analyzed with JavaAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on package names)
  • *.kts files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.kt files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.py files are analyzed with PythonAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis
  • *.pro files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-02-03 05:34