firebase / quickstart-cpp
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
txt
properties
pro
storyboard
plist
clang-format
  • 18 extensions are included in analyses: cc, xml, json, gradle, md, java, txt, properties, mm, h, pro, storyboard, plist, bat, clang-format, js, yml, yaml
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (10 files).
    • exclude files with path like ".*/proguard[.]pro" (ProGuard) (10 files).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 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) (10 files).
    • 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.

main7696 LOC (25%) 63 files
test0 LOC (0%) 0 files
generated8246 LOC (27%) 1 files
build and deployment1451 LOC (4%) 30 files
other12445 LOC (41%) 85 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 63 files match defined criteria (7,696 lines of code, 100.0% vs. main code):
    • 30 *.cc files (6,008 lines of code)
    • 10 *.mm files (897 lines of code)
    • 12 *.java files (464 lines of code)
    • 10 *.h files (308 lines of code)
    • 1 *.js files (19 lines of code)
  • " *.cc" is biggest, containing 78.07% of code.
  • " *.js" is smallest, containing 0.25% of code.


*.cc6008 LOC (78%) 30 files
*.mm897 LOC (11%) 10 files
*.java464 LOC (6%) 12 files
*.h308 LOC (4%) 10 files
*.js19 LOC (<1%) 1 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/package[-]lock[.]json".
  • 1 file matches defined criteria (8,246 lines of code, 107.1% vs. main code). All matches are in *.json files.


*.json8246 LOC (100%) 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 ".*[.]gradle".
    • files with paths like ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]bat".
    • files with paths like ".*/package[-]lock[.]json".
    • files with paths like ".*/package[.]json".
  • 30 files match defined criteria (1,451 lines of code, 18.9% vs. main code):
    • 20 *.gradle files (791 lines of code)
    • 10 *.bat files (660 lines of code)
  • " *.gradle" is biggest, containing 54.51% of code.
  • " *.bat" is smallest, containing 45.49% of code.


*.gradle791 LOC (54%) 20 files
*.bat660 LOC (45%) 10 files
Other Code
plist
storyboard
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]plist".
    • files with paths like ".*[.]storyboard".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 85 files match defined criteria (12,445 lines of code, 161.7% vs. main code):
    • 22 *.json files (9,385 lines of code)
    • 12 *.md files (2,144 lines of code)
    • 30 *.xml files (420 lines of code)
    • 10 *.plist files (411 lines of code)
    • 10 *.storyboard files (70 lines of code)
    • 1 *.properties files (15 lines of code)
  • " *.json" is biggest, containing 75.41% of code.
  • " *.properties" is smallest, containing 0.12% of code.


*.json9385 LOC (75%) 22 files
*.md2144 LOC (17%) 12 files
*.xml420 LOC (3%) 30 files
*.plist411 LOC (3%) 10 files
*.storyboard70 LOC (<1%) 10 files
*.properties15 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.cc files are analyzed with CppAnalyzer:
    • 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
  • *.mm files are analyzed with CppAnalyzer:
    • 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
  • *.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)
  • *.h files are analyzed with CppAnalyzer:
    • 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
  • *.js files are analyzed with JavaScriptAnalyzer:
    • 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
    • No dependency analysis


2022-02-03 05:35