epam / hub-extensionsSource Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope

Files includes and excluded from analyses

bats

txt

editorconfig

gitmodules

9 extensions are included in analyses: md, bats, json, js, txt, gitignore, editorconfig, gitmodules, yaml
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (5 files).
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) (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.

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.

Explore: circles | sunburst

2 files match defined criteria (142 LOC, 100.0% vs. main code). All matches are in *.js files.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

bats

Explore: circles | sunburst

6 files match defined criteria (469 LOC, 330.3% vs. main code). All matches are in *.bats files.

Generated Code

Automatically generated files, not manually changed after generation.

Explore: circles | sunburst

1 file matches defined criteria (2,996 LOC, 2109.9% vs. main code). All matches are in *.json files.

Other Code

Explore: circles | sunburst