Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 20 extensions are included in analyses: bzl, json, plist, sh, swift, m, py, storyboard, md, h, txt, xib, cc, xml, d, metal, yml, yaml, gitignore, bash
- 6 criteria are used to exclude files from analysis:
- 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 ".*/testdata/.*" (Test data) (46 files).
- exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
- exclude files with path like ".*[.]txt" (Text files) (10 files).
- The source code folder contains 705 files:
- 500 files are included in analyses.
- 205 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 ".*".
- 132 files match defined criteria (30,674 lines of code, 100.0% vs. main code):
- 112 *.bzl files (25,527 lines of code)
- 20 *.py files (5,147 lines of code)
- " *.bzl" is biggest, containing 83.22% of code.
- " *.py" is smallest, containing 16.78% of code.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*_test[.].*".
- files with paths like ".*/[Tt]ests/.*".
- files with paths like ".*/[Tt]est/.*".
- files with paths like ".*/test_.*".
- files with paths like ".*_tests[.].*".
- files with any line of content like ".*/simpletest/.*".
- 130 files match defined criteria (17,612 lines of code, 57.4% vs. main code):
- 48 *.sh files (9,167 lines of code)
- 56 *.bzl files (7,478 lines of code)
- 1 *.bash files (451 lines of code)
- 3 *.py files (303 lines of code)
- 8 *.swift files (101 lines of code)
- 4 *.m files (44 lines of code)
- 3 *.cc files (39 lines of code)
- 3 *.h files (19 lines of code)
- 2 *.d files (6 lines of code)
- 2 *.metal files (4 lines of code)
- " *.sh" is biggest, containing 52.05% of code.
- " *.metal" is smallest, containing 0.02% of code.
Build and Deployment Code
Source code used to configure or support build and deployment process.
Other Code
- 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 ".*[.]json".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]storyboard".
- files with paths like ".*/[Ee]xamples/.*".
- files with paths like ".*[.]plist".
- files with paths like ".*[.]xib".
- files with paths like ".*[.]txt".
- 232 files match defined criteria (11,717 lines of code, 38.2% vs. main code):
- 22 *.md files (3,576 lines of code)
- 20 *.storyboard files (3,574 lines of code)
- 56 *.json files (1,786 lines of code)
- 55 *.plist files (1,377 lines of code)
- 28 *.m files (558 lines of code)
- 26 *.swift files (377 lines of code)
- 6 *.xib files (372 lines of code)
- 19 *.h files (97 lines of code)
- " *.md" is biggest, containing 30.52% of code.
- " *.h" is smallest, containing 0.83% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.bzl 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
- *.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
2022-02-03 05:30