epam / hubctlSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

mod

txt

editorconfig

10 extensions are included in analyses: go, json, yaml, sh, md, mod, gitignore, dockerignore, txt, editorconfig
4 criteria are used to exclude files from analysis:

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

The source code folder contains 234 files:

194 files are included in analyses.
40 files are excluded from analyses:

Explore all 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.

149 files

17 files

28 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

The following criteria are used to filter files:

files with paths like ".*".

149 files match defined criteria (22,325 LOC, 100.0% vs. main code):

148 *.go files (22,271 LOC)
1 *.yaml files (54 LOC)

" *.go" is biggest, containing 99.76% of LOC.
" *.yaml" is smallest, containing 0.24% of LOC.

Test Code

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

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*_test[.].*".
files with paths like ".*/[Tt]est/.*".

17 files match defined criteria (2,332 LOC, 10.4% vs. main code):

12 *.go files (1,976 LOC)
5 *.yaml files (356 LOC)

" *.go" is biggest, containing 84.73% of LOC.
" *.yaml" is smallest, containing 15.27% of LOC.

Other Code

mod

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]json".
files with paths like ".*/go[.]mod".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*[.]editorconfig".
files with paths like ".*/[.]dockerignore".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*[.]txt".

28 files match defined criteria (2,105 LOC, 9.4% vs. main code):

14 *.json files (1,110 LOC)
3 *.yaml files (546 LOC)
3 *.md files (291 LOC)
1 *.mod files (111 LOC)
7 *.sh files (47 LOC)

" *.json" is biggest, containing 52.73% of LOC.
" *.sh" is smallest, containing 2.23% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.go files are analyzed with GoLangAnalyzer:

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

*.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

2025-01-10 14:08