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: js, md, graphql, rs, json, toml, snap, txt, css, yml, svg, gitignore, htm, py, gitattributes, watchmanconfig, sh, yaml, babelrc, eslintignore
- 4 criteria are used to exclude files from analysis:
- exclude files with path like ".*/docs/.*" (Documentation) (95 files).
- exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (13 files).
- exclude files with path like ".*/react(-[^.]*)?\.js" (React) (142 files).
- exclude files with path like ".*/flow-typed/.*\.js" (flow-typed) (3 files).
- The source code folder contains 5,456 files:
- 4,119 files are included in analyses.
- 1,337 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 ".*".
- 492 files match defined criteria (83,545 lines of code, 100.0% vs. main code):
- 309 *.rs files (60,445 lines of code)
- 142 *.js files (20,178 lines of code)
- 5 *.css files (1,963 lines of code)
- 32 *.toml files (694 lines of code)
- 2 *.graphql files (199 lines of code)
- 1 *.yaml files (48 lines of code)
- 1 *.py files (18 lines of code)
- " *.rs" is biggest, containing 72.35% of code.
- " *.py" is smallest, containing 0.02% 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 ".*[.]tests[.].*".
- files with paths like ".*/__mocks?__/.*".
- files with paths like ".*__tests__.*".
- files with paths like ".*_test[.].*".
- files with paths like ".*[.]snap".
- files with paths like ".*[-]test[-].*".
- files with paths like ".*/[Tt]ests/.*".
- files with paths like ".*/test_.*".
- files with paths like ".*_tests[.].*".
- files with paths like ".*[-]tests/.*".
- 1357 files match defined criteria (99,688 lines of code, 119.3% vs. main code):
- 186 *.js files (67,042 lines of code)
- 977 *.graphql files (18,661 lines of code)
- 173 *.rs files (10,124 lines of code)
- 18 *.snap files (3,814 lines of code)
- 3 *.toml files (47 lines of code)
- " *.js" is biggest, containing 67.25% of code.
- " *.toml" is smallest, containing 0.05% of code.
Generated Code
Automatically generated files, not manually changed after generation.
- The following criteria are used to filter files:
- files with paths like ".*/__generated__/.*".
- 1021 files match defined criteria (94,270 lines of code, 112.8% vs. main code). All matches are in *.js files.
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 ".*/package[.]json".
- files with paths like ".*[.]sh".
- files with paths like ".*/[.]gitattributes".
- 1 file matches defined criteria (3 lines of code, 0.0% vs. main code). All matches are in *.sh files.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]json".
- files with paths like ".*[.]md".
- files with paths like ".*/README[.][a-z0-9]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]svg".
- files with paths like ".*[.]txt".
- files with paths like ".*/[.]eslintignore".
- files with paths like ".*/[Ee]xamples/.*".
- 1248 files match defined criteria (154,459 lines of code, 184.9% vs. main code):
- 1,194 *.md files (148,862 lines of code)
- 40 *.json files (5,355 lines of code)
- 9 *.txt files (127 lines of code)
- 2 *.rs files (65 lines of code)
- 3 *.svg files (50 lines of code)
- " *.md" is biggest, containing 96.38% of code.
- " *.svg" is smallest, containing 0.03% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.rs 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
- *.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
- *.css files are analyzed with CssAnalyzer:
- 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
- *.toml 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
- *.graphql 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
- *.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
- *.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-04-14 23:04