epam / epam-graphqlSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

csproj

txt

props

editorconfig

targets

11 extensions are included in analyses: cs, md, csproj, txt, yaml, xml, gitignore, props, json, editorconfig, targets
5 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 ".*/docs/.*" (Documentation) (15 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (7 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 614 files:

577 files are included in analyses.
37 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.

404 files

131 files

5 files

37 files

Main Code

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

props

targets

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

404 files match defined criteria (28,212 LOC, 100.0% vs. main code):

402 *.cs files (28,160 LOC)
1 *.props files (35 LOC)
1 *.targets files (17 LOC)

" *.cs" is biggest, containing 99.82% of LOC.
" *.targets" is smallest, containing 0.06% of LOC.

Test Code

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

csproj

props

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]ests/.*".
files with paths like ".*[.][Tt]ests/.*".
files with paths like ".*[.][Tt]ests[.].*".
files with paths like ".*/TestData/.*".

131 files match defined criteria (48,296 LOC, 171.2% vs. main code):

126 *.cs files (48,171 LOC)
4 *.csproj files (104 LOC)
1 *.props files (21 LOC)

" *.cs" is biggest, containing 99.74% of LOC.
" *.props" is smallest, containing 0.04% of LOC.

Build and Deployment Code

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

csproj

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]csproj".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

5 files match defined criteria (82 LOC, 0.3% vs. main code). All matches are in *.csproj files.

Other Code

txt

csproj

Explore: circles | sunburst

The following criteria are used to filter files:

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

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

25 *.cs files (2,684 LOC)
5 *.txt files (97 LOC)
2 *.md files (71 LOC)
4 *.csproj files (55 LOC)
1 *.json files (23 LOC)

" *.cs" is biggest, containing 91.6% of LOC.
" *.json" is smallest, containing 0.78% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.cs files are analyzed with CSharpAnalyzer:

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 namespace heuristics)

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

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

2025-01-10 14:20