Source Code Analysis Scope
Files includes and excluded from analyses
asc
patch

scoping details...
  • 9 extensions are included in analyses: asc, sh, h, patch, py, cpp, gitignore, md, hpp
  • 4 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
    • exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
    • 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_.*?[.]json" (Sokrates conventions and configurations) (0 files).
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.
main6614 LOC (75%) 7 files
test803 LOC (9%) 10 files
generated0 LOC (0%) 0 files
build and deployment286 LOC (3%) 5 files
other1066 LOC (12%) 4 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Explore:   circles  |  sunburst

h6315 LOC (95%) 5 files
py299 LOC (4%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 7 files match defined criteria (6,614 LOC, 100.0% vs. main code):
    • 5 h files (6,315 LOC)
    • 2 py files (299 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
asc
Explore:   circles  |  sunburst

hpp448 LOC (55%) 1 file
asc282 LOC (35%) 6 files
py38 LOC (4%) 1 file
cpp32 LOC (3%) 1 file
sh3 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*/test[.].*".
  • 10 files match defined criteria (803 LOC, 12.1% vs. main code):
    • 1 hpp files (448 LOC)
    • 6 asc files (282 LOC)
    • 1 py files (38 LOC)
    • 1 cpp files (32 LOC)
    • 1 sh files (3 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

sh279 LOC (97%) 4 files
gitignore7 LOC (2%) 1 file

scope details...
  • 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".
  • 5 files match defined criteria (286 LOC, 4.3% vs. main code):
    • 4 sh files (279 LOC)
    • 1 gitignore files (7 LOC)
Other Code
patch
Explore:   circles  |  sunburst

patch1032 LOC (96%) 3 files
md34 LOC (3%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]patch".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 4 files match defined criteria (1,066 LOC, 16.1% vs. main code):
    • 3 patch files (1,032 LOC)
    • 1 md files (34 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.

learn more about used code analyzers...
  • *.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
  • *.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