Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 12 extensions are included in analyses: js, html, ts, svg, css, txt, json, md, gitignore, yml, nuspec, eslintignore
- 7 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 ".*/dist/.*" (Distributions) (1 file).
- exclude files with path like ".*\.d\.ts" (Typescript definition files) (0 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) (4 files).
- The source code folder contains 183 files:
- 161 files are included in analyses.
- 22 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 ".*".
- 25 files match defined criteria (2,655 lines of code, 100.0% vs. main code):
- 24 *.ts files (2,446 lines of code)
- 1 *.js files (209 lines of code)
- " *.ts" is biggest, containing 92.13% of code.
- " *.js" is smallest, containing 7.87% 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 ".*/karma[.]conf[.]js".
- files with paths like ".*/[Tt]est/.*".
- files with paths like ".*[.]spec[.]ts".
- files with paths like ".*[.][Tt]est[.].*".
- files with paths like ".*[.]test[.].*".
- files with any line of content like ".*/simpletest/.*".
- 16 files match defined criteria (5,290 lines of code, 199.2% vs. main code):
- 13 *.ts files (5,192 lines of code)
- 2 *.js files (87 lines of code)
- 1 *.html files (11 lines of code)
- " *.ts" is biggest, containing 98.15% of code.
- " *.html" is smallest, containing 0.21% 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 ".*[.]nuspec".
- files with paths like ".*/package[.]json".
- files with paths like ".*([.]|/)webpack([.]|/).*".
- 2 files match defined criteria (47 lines of code, 1.8% vs. main code):
- 1 *.js files (25 lines of code)
- 1 *.nuspec files (22 lines of code)
- " *.js" is biggest, containing 53.19% of code.
- " *.nuspec" is smallest, containing 46.81% of code.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]json".
- files with paths like ".*/[.]eslintignore".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]md".
- files with paths like ".*[.]txt".
- files with paths like ".*/LICENSE[.][a-z0-9]+".
- files with paths like ".*/README[.][a-z0-9]+".
- files with paths like ".*/[Dd]emos?/.*".
- files with paths like ".*[.]svg".
- 118 files match defined criteria (14,446 lines of code, 544.1% vs. main code):
- 35 *.js files (8,250 lines of code)
- 9 *.css files (3,247 lines of code)
- 44 *.html files (2,309 lines of code)
- 23 *.svg files (339 lines of code)
- 4 *.json files (167 lines of code)
- 3 *.md files (134 lines of code)
- " *.js" is biggest, containing 57.11% of code.
- " *.md" is smallest, containing 0.93% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.ts files are analyzed with TypeScriptAnalyzer:
- 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
- *.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-01-30 11:10