microsoft / appcenter-sdk-android-breakpad
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
gyp
m4
plist
gypi
in
mk
txt
i
proto
gitmodules
S
s
  • 31 extensions are included in analyses: h, cc, gyp, md, mm, c, m4, sh, m, plist, gypi, in, py, mk, txt, xib, json, go, i, bat, xml, cpp, rb, proto, gitmodules, S, yml, svg, gitignore, s, PL
  • 9 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*[.]m4" (stuff autogenerated by autoconf - still C deps) (13 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (12 files).
    • exclude files with path like ".*/testdata/.*" (Test data) (5 files).
    • exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (60 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 ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (2 files).
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.

main105387 LOC (85%) 522 files
test5735 LOC (4%) 36 files
generated0 LOC (0%) 0 files
build and deployment7556 LOC (6%) 12 files
other5233 LOC (4%) 14 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
in
gypi
gyp
s
proto
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 522 files match defined criteria (105,387 lines of code, 100.0% vs. main code):
    • 209 *.cc files (70,313 lines of code)
    • 258 *.h files (18,419 lines of code)
    • 4 *.in files (8,257 lines of code)
    • 14 *.mm files (3,320 lines of code)
    • 8 *.m files (1,801 lines of code)
    • 5 *.gypi files (937 lines of code)
    • 15 *.gyp files (804 lines of code)
    • 2 *.s files (488 lines of code)
    • 1 *.c files (363 lines of code)
    • 2 *.go files (315 lines of code)
    • 2 *.py files (170 lines of code)
    • 1 *.proto files (170 lines of code)
    • 1 *.yml files (30 lines of code)
  • " *.cc" is biggest, containing 66.72% of code.
  • " *.yml" is smallest, containing 0.03% of code.


*.cc70313 LOC (66%) 209 files
*.h18419 LOC (17%) 258 files
*.in8257 LOC (7%) 4 files
*.mm3320 LOC (3%) 14 files
*.m1801 LOC (1%) 8 files
*.gypi937 LOC (<1%) 5 files
*.gyp804 LOC (<1%) 15 files
*.s488 LOC (<1%) 2 files
*.c363 LOC (<1%) 1 files
*.go315 LOC (<1%) 2 files
*.py170 LOC (<1%) 2 files
*.proto170 LOC (<1%) 1 files
*.yml30 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
gyp
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/test_.*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*_tests[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 36 files match defined criteria (5,735 lines of code, 5.4% vs. main code):
    • 19 *.cc files (5,010 lines of code)
    • 12 *.h files (455 lines of code)
    • 1 *.mm files (127 lines of code)
    • 2 *.gyp files (88 lines of code)
    • 1 *.py files (33 lines of code)
    • 1 *.cpp files (22 lines of code)
  • " *.cc" is biggest, containing 87.36% of code.
  • " *.cpp" is smallest, containing 0.38% of code.


*.cc5010 LOC (87%) 19 files
*.h455 LOC (7%) 12 files
*.mm127 LOC (2%) 1 files
*.gyp88 LOC (1%) 2 files
*.py33 LOC (<1%) 1 files
*.cpp22 LOC (<1%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
mk
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitmodules".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]mk".
    • files with paths like ".*[.]bat".
  • 12 files match defined criteria (7,556 lines of code, 7.2% vs. main code):
    • 8 *.sh files (7,372 lines of code)
    • 3 *.mk files (162 lines of code)
    • 1 *.bat files (22 lines of code)
  • " *.sh" is biggest, containing 97.56% of code.
  • " *.bat" is smallest, containing 0.29% of code.


*.sh7372 LOC (97%) 8 files
*.mk162 LOC (2%) 3 files
*.bat22 LOC (<1%) 1 files
Other Code
plist
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]plist".
    • files with paths like ".*[.]xib".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 14 files match defined criteria (5,233 lines of code, 5.0% vs. main code):
    • 2 *.xib files (4,888 lines of code)
    • 7 *.plist files (195 lines of code)
    • 3 *.md files (76 lines of code)
    • 1 *.json files (41 lines of code)
    • 1 *.xml files (33 lines of code)
  • " *.xib" is biggest, containing 93.41% of code.
  • " *.xml" is smallest, containing 0.63% of code.


*.xib4888 LOC (93%) 2 files
*.plist195 LOC (3%) 7 files
*.md76 LOC (1%) 3 files
*.json41 LOC (<1%) 1 files
*.xml33 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
  • *.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
  • *.in files are analyzed with RustAnalyzer:
    • 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
  • *.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
  • *.m 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
  • *.gypi 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
  • *.gyp 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
  • *.s 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
  • *.c files are analyzed with CStyleAnalyzer:
    • 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
  • *.go files are analyzed with GoLangAnalyzer:
    • 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
  • *.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
  • *.proto 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
  • *.yml files are analyzed with YamlAnalyzer:
    • 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)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-01-30 15:27