Source Code Analysis Scope
Files includes and excluded from analyses
gitmodules

scoping details...
  • 8 extensions are included in analyses: hpp, py, txt, cpp, sh, gitignore, md, gitmodules
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
    • 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) (1 file).
    • 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 ".*/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.
main6763 LOC (76%) 69 files
test1644 LOC (18%) 10 files
generated0 LOC (0%) 0 files
build and deployment184 LOC (2%) 5 files
other273 LOC (3%) 2 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

hpp5115 LOC (75%) 47 files
py1573 LOC (23%) 20 files
cpp75 LOC (1%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 69 files match defined criteria (6,763 LOC, 100.0% vs. main code):
    • 47 hpp files (5,115 LOC)
    • 20 py files (1,573 LOC)
    • 2 cpp files (75 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

py1644 LOC (100%) 10 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/testing[.].*".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*/test_.*".
  • 10 files match defined criteria (1,644 LOC, 24.3% vs. main code). All matches are in py files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
gitmodules
Explore:   circles  |  sunburst

py141 LOC (76%) 1 file
sh22 LOC (11%) 2 files
gitignore15 LOC (8%) 1 file
gitmodules6 LOC (3%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/CMakeLists[.]txt".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitmodules".
    • files with paths like ".*/setup[.]py".
    • files with paths like ".*/[.]gitignore".
  • 5 files match defined criteria (184 LOC, 2.7% vs. main code):
    • 1 py files (141 LOC)
    • 2 sh files (22 LOC)
    • 1 gitignore files (15 LOC)
    • 1 gitmodules files (6 LOC)
Other Code
Explore:   circles  |  sunburst

md222 LOC (81%) 1 file
txt51 LOC (18%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 2 files match defined criteria (273 LOC, 4.0% vs. main code):
    • 1 md files (222 LOC)
    • 1 txt files (51 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...
  • *.hpp 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
  • *.cpp 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