Source Code Analysis Scope
Files includes and excluded from analyses

scoping details...
  • 6 extensions are included in analyses: txt, sh, md, yaml, json, gitignore
  • 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.
main0 LOC (0%) 0 files
test65 LOC (16%) 3 files
generated0 LOC (0%) 0 files
build and deployment205 LOC (53%) 4 files
other116 LOC (30%) 5 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

yaml47 LOC (72%) 1 file
sh18 LOC (27%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test[.].*".
  • 3 files match defined criteria (65 LOC, 0.0% vs. main code):
    • 1 yaml files (47 LOC)
    • 2 sh files (18 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

sh105 LOC (51%) 1 file
yaml76 LOC (37%) 2 files
gitignore24 LOC (11%) 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".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
  • 4 files match defined criteria (205 LOC, 0.0% vs. main code):
    • 1 sh files (105 LOC)
    • 2 yaml files (76 LOC)
    • 1 gitignore files (24 LOC)
Other Code
Explore:   circles  |  sunburst

md88 LOC (75%) 3 files
json28 LOC (24%) 2 files

scope details...
  • 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 ".*[.]txt".
  • 5 files match defined criteria (116 LOC, 0.0% vs. main code):
    • 3 md files (88 LOC)
    • 2 json files (28 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...