epam / TimebaseWSSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

txt

editorconfig

properties

jshintrc

babelrc

http

22 extensions are included in analyses: ts, java, js, scss, html, json, md, xml, gradle, yaml, sh, py, svg, txt, editorconfig, gitignore, properties, css, bat, jshintrc, babelrc, http
7 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 ".*\.d\.ts" (Typescript definition files) (408 files).
exclude files with path like ".*/dist/.*" (Distributions) (43 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 files).
exclude files with path like ".*/docs/.*" (Documentation) (6 files).
exclude files with path like ".*/cache/.*" (Caches) (4 files).
exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).

The source code folder contains 2,339 files:

1,785 files are included in analyses.
554 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.

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

The following criteria are used to filter files:

files with paths like ".*".

1528 files match defined criteria (121,191 LOC, 100.0% vs. main code):

735 *.java files (38,619 LOC)
434 *.ts files (37,515 LOC)
89 *.js files (29,616 LOC)
136 *.scss files (7,355 LOC)
113 *.html files (4,830 LOC)
20 *.xml files (3,201 LOC)
1 *.yaml files (55 LOC)

" *.java" is biggest, containing 31.87% of LOC.
" *.yaml" is smallest, containing 0.05% 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 ".*[.][Tt]ests[.].*".
files with paths like ".*[.]tests[.].*".
files with paths like ".*/[Tt]ests/.*".
files with paths like ".*/e2e/.*".
files with paths like ".*/protractor[.]conf[.]js".
files with paths like ".*[.]spec[.]ts".
files with paths like ".*/test[.].*".
files with paths like ".*/karma[.]conf[.]js".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*[-]tests/.*".
files with paths like ".*_test[.].*".

82 files match defined criteria (7,829 LOC, 6.5% vs. main code):

60 *.java files (6,989 LOC)
6 *.yaml files (443 LOC)
12 *.ts files (183 LOC)
1 *.py files (136 LOC)
3 *.js files (78 LOC)

" *.java" is biggest, containing 89.27% of LOC.
" *.js" is smallest, containing 1% of LOC.

Generated Code

Automatically generated files, not manually changed after generation.

Explore: circles | sunburst

The following criteria are used to filter files:

files with any line of content like "\<\!\-\-[ ]*Generated by .*".
files with paths like ".*[.](html|html|xhtml)" AND any line of content like "[ ]*[<]meta name[=]"generator" .*".

1 file matches defined criteria (183 LOC, 0.2% vs. main code). All matches are in *.md files.

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 ".*/package[.]json".
files with paths like ".*([.]|/)webpack([.]|/).*".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]gradle".
files with paths like ".*[.]sh".
files with paths like ".*[.]bat".

18 files match defined criteria (1,034 LOC, 0.9% vs. main code):

15 *.gradle files (869 LOC)
2 *.js files (97 LOC)
1 *.bat files (68 LOC)

" *.gradle" is biggest, containing 84.04% of LOC.
" *.bat" is smallest, containing 6.58% of LOC.

Other Code

txt

properties

Explore: circles | sunburst

The following criteria are used to filter files:

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

157 files match defined criteria (8,683 LOC, 7.2% vs. main code):

101 *.json files (6,069 LOC)
27 *.md files (1,778 LOC)
13 *.js files (395 LOC)
3 *.txt files (153 LOC)
4 *.py files (117 LOC)
1 *.svg files (114 LOC)
7 *.sh files (50 LOC)
1 *.properties files (7 LOC)

" *.json" is biggest, containing 69.9% of LOC.
" *.properties" is smallest, containing 0.08% 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)

*.ts files are analyzed with TypeScriptAnalyzer:

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

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

*.html files are analyzed with HtmlAnalyzer:

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

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

2025-01-10 14:19