Source Code Analysis Scope
Files includes and excluded from analyses

scoping details...
  • 3 extensions are included in analyses: yaml, txt, md
  • 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.
main8 LOC (8%) 1 file
test21 LOC (23%) 1 file
generated0 LOC (0%) 0 files
build and deployment45 LOC (49%) 1 file
other17 LOC (18%) 1 file
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

yaml8 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 1 file matches defined criteria (8 LOC, 100.0% vs. main code). All matches are in yaml files.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

yaml21 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/test[.].*".
  • 1 file matches defined criteria (21 LOC, 262.5% vs. main code). All matches are in yaml files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

yaml45 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/action[.]ya?ml".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
  • 1 file matches defined criteria (45 LOC, 562.5% vs. main code). All matches are in yaml files.
Other Code
Explore:   circles  |  sunburst

md17 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
  • 1 file matches defined criteria (17 LOC, 212.5% vs. main code). All matches are in md files.
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...
  • *.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