epam / eco-schema-catalogSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

properties

gitattributes

ejs

txt

editorconfig

cmd

17 extensions are included in analyses: java, js, scss, json, avsc, svg, xml, properties, md, yaml, gitignore, dockerignore, gitattributes, ejs, txt, editorconfig, cmd
7 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (8 files).
exclude files with path like ".*/controls\.js" (Prototype) (1 file).
exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/mvnw\.cmd" (Maven) (1 file).
exclude files with path like ".*/testdata/.*" (Test data) (2 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).

The source code folder contains 606 files:

574 files are included in analyses.
32 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.

421 files

95 files

8 files

50 files

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

ejs

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

421 files match defined criteria (23,586 LOC, 100.0% vs. main code):

156 *.java files (12,660 LOC)
163 *.js files (7,310 LOC)
71 *.scss files (2,451 LOC)
21 *.avsc files (642 LOC)
7 *.xml files (358 LOC)
2 *.yaml files (128 LOC)
1 *.ejs files (37 LOC)

" *.java" is biggest, containing 53.68% of LOC.
" *.ejs" is smallest, containing 0.16% 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 ".*/__mock[a-zA-Z0-9_\- ]+/.*".
files with paths like ".*/jest[.][a-zA-Z0-9\.]+".
files with paths like ".*[.]spec[.]js".
files with paths like ".*[.][Tt]est[.].*".
files with paths like ".*[.]test[.].*".
files with paths like ".*/[Tt]est/.*".

95 files match defined criteria (8,997 LOC, 38.1% vs. main code):

67 *.java files (6,013 LOC)
28 *.js files (2,984 LOC)

" *.java" is biggest, containing 66.83% of LOC.
" *.js" is smallest, containing 33.17% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*([.]|/)webpack([.]|/).*".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/package[.]json".
files with paths like ".*/docker[-]compose[.]yaml".
files with paths like ".*/pom[.]xml".
files with paths like ".*/[.]gitattributes".

8 files match defined criteria (1,096 LOC, 4.6% vs. main code):

6 *.xml files (949 LOC)
1 *.js files (121 LOC)
1 *.yaml files (26 LOC)

" *.xml" is biggest, containing 86.59% of LOC.
" *.yaml" is smallest, containing 2.37% of LOC.

Other Code

properties

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]editorconfig".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]json".
files with paths like ".*[.]svg".
files with paths like ".*[.]properties".
files with paths like ".*/[.]dockerignore".
files with paths like ".*[.]txt".

50 files match defined criteria (1,078 LOC, 4.6% vs. main code):

24 *.json files (432 LOC)
8 *.md files (423 LOC)
8 *.svg files (174 LOC)
10 *.properties files (49 LOC)

" *.json" is biggest, containing 40.07% of LOC.
" *.properties" is smallest, containing 4.55% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.java files are analyzed with JavaAnalyzer:

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 (based on package names)

*.js files are analyzed with JavaScriptAnalyzer:

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

No dependency analysis

*.scss files are analyzed with ScssAnalyzer:

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

*.avsc files are analyzed with JsonAnalyzer:

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

*.xml files are analyzed with XmlAnalyzer:

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

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

*.ejs files are analyzed with DefaultLanguageAnalyzer:

All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)

Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)

No unit size analysis

No conditional complexity analysis

No dependency analysis

2025-01-10 14:09