Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 19 extensions are included in analyses: json, py, txt, css, js, rst, html, yml, md, sh, tex, xml, ipynb, yaml, svg, jl, bat, gitignore, h
- 11 criteria are used to exclude files from analysis:
- exclude files with path like ".*/extern(al)?/.*" (Dependencies) (4 files).
- exclude files with path like ".*/dist/.*" (Distributions) (531 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 ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
- exclude files with path like ".*/docs/.*" (Documentation) (30 files).
- exclude files with path like ".*/docs?/_?(build|themes?|templates?|static)/.*" (Sphinx) (0 files).
- exclude files with path like "(?i).*/jquery.*[.]js" (jQuery files) (0 files).
- exclude files with path like ".*/underscore\.js" (Underscore.js) (0 files).
- exclude files with path like ".*[.]txt" (Text files) (13 files).
- exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
- The source code folder contains 1,189 files:
- 311 files are included in analyses.
- 878 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 ".*".
- 286 files match defined criteria (43,753 lines of code, 100.0% vs. main code):
- 285 *.py files (43,740 lines of code)
- 1 *.yaml files (13 lines of code)
- " *.py" is biggest, containing 99.97% of code.
- " *.yaml" is smallest, containing 0.03% 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 ".*/[Tt]ests/.*".
- files with paths like ".*/test_.*".
- files with paths like ".*_test[.].*".
- files with any line of content like ".*/simpletest/.*".
- 10 files match defined criteria (391 lines of code, 0.9% vs. main code):
- 9 *.py files (364 lines of code)
- 1 *.jl files (27 lines of code)
- " *.py" is biggest, containing 93.09% of code.
- " *.jl" is smallest, containing 6.91% 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 ".*[.]sh".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]bat".
- 3 files match defined criteria (209 lines of code, 0.5% vs. main code). All matches are in *.sh files.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]md".
- files with paths like ".*[.]txt".
- files with paths like ".*/LICENSE[.][a-z0-9]+".
- files with paths like ".*[.]json".
- files with paths like ".*/README[.][a-z0-9]+".
- files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]svg".
- files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
- 12 files match defined criteria (1,995 lines of code, 4.6% vs. main code):
- 1 *.ipynb files (1,238 lines of code)
- 4 *.md files (396 lines of code)
- 2 *.rst files (279 lines of code)
- 3 *.json files (54 lines of code)
- 2 *.xml files (28 lines of code)
- " *.ipynb" is biggest, containing 62.06% of code.
- " *.xml" is smallest, containing 1.4% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.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
- *.yaml 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-31 16:27