Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 17 extensions are included in analyses: xml, java, swift, h, md, json, m, gitignore, xib, gradle, storyboard, properties, pro, txt, plist, bat, yml
- 5 criteria are used to exclude files from analysis:
- exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (10 files).
- exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (1 file).
- exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
- 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).
- The source code folder contains 248 files:
- 162 files are included in analyses.
- 86 files are excluded from analyses:
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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*".
- 135 files match defined criteria (9,701 lines of code, 100.0% vs. main code):
- 5 *.m files (3,257 lines of code)
- 79 *.xml files (2,142 lines of code)
- 19 *.java files (1,907 lines of code)
- 18 *.swift files (1,352 lines of code)
- 14 *.h files (1,043 lines of code)
- " *.m" is biggest, containing 33.57% of code.
- " *.h" is smallest, containing 10.75% of code.
Build and Deployment Code
Source code used to configure or support build and deployment process.
- The following criteria are used to filter files:
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]gradle".
- files with paths like ".*/AndroidManifest[.]xml".
- files with paths like ".*[.]bat".
- 5 files match defined criteria (229 lines of code, 2.4% vs. main code):
- 3 *.gradle files (113 lines of code)
- 1 *.bat files (66 lines of code)
- 1 *.xml files (50 lines of code)
- " *.gradle" is biggest, containing 49.34% of code.
- " *.xml" is smallest, containing 21.83% of code.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]md".
- files with paths like ".*[.]json".
- files with paths like ".*/README[.][a-z0-9]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]xib".
- files with paths like ".*[.]storyboard".
- files with paths like ".*[.]plist".
- files with paths like ".*[.]properties".
- files with paths like ".*[.]txt".
- 22 files match defined criteria (1,513 lines of code, 15.6% vs. main code):
- 10 *.json files (693 lines of code)
- 5 *.md files (346 lines of code)
- 2 *.storyboard files (216 lines of code)
- 3 *.xib files (188 lines of code)
- 1 *.plist files (55 lines of code)
- 1 *.properties files (15 lines of code)
- " *.json" is biggest, containing 45.8% of code.
- " *.properties" is smallest, containing 0.99% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.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
- *.xml files are analyzed with XmlAnalyzer:
- 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
- *.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)
- *.swift files are analyzed with SwiftAnalyzer:
- 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
- *.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
2022-04-16 06:52