epam / covid-resistance-mobileSource Code Overview

Source Code Analysis Scope

Files includes and excluded from analyses

xaml

csproj

txt

plist

xsd

gitattributes

storyboard

resx

props

editorconfig

16 extensions are included in analyses: cs, xaml, svg, xml, json, md, csproj, txt, plist, xsd, gitattributes, storyboard, resx, props, editorconfig, bash
6 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) (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).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
exclude files with path like ".*[.]resx" (The resx resource files) (1 file).

The source code folder contains 456 files:

434 files are included in analyses.
22 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.

377 files

24 files

6 files

27 files

Main Code

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

xaml

xsd

props

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

377 files match defined criteria (14,549 LOC, 100.0% vs. main code):

322 *.cs files (12,029 LOC)
41 *.xaml files (2,313 LOC)
11 *.xml files (128 LOC)
1 *.xsd files (63 LOC)
1 *.bash files (8 LOC)
1 *.props files (8 LOC)

" *.cs" is biggest, containing 82.68% of LOC.
" *.props" is smallest, containing 0.05% 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 paths like ".*[.]cs" AND any line of content like "[/][/][ ]*".

24 files match defined criteria (2,695 LOC, 18.5% vs. main code). All matches are in *.cs files.

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 ".*/AndroidManifest[.]xml".

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

files with paths like ".*/[.]gitattributes".

6 files match defined criteria (1,218 LOC, 8.4% vs. main code):

5 *.csproj files (1,192 LOC)

1 *.xml files (26 LOC)

" *.csproj" is biggest, containing 97.87% of LOC.

" *.xml" is smallest, containing 2.13% of LOC.

Other Code

plist
txt
storyboard

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]json".

files with paths like ".*[.]md".

files with paths like ".*/README[.][a-z0-9]+".

files with paths like ".*[.]txt".

files with paths like ".*[.]editorconfig".

files with paths like ".*[.]plist".

files with paths like ".*[.]storyboard".

files with paths like ".*[.]svg".

27 files match defined criteria (1,505 LOC, 10.3% vs. main code):

10 *.json files (1,047 LOC)

10 *.svg files (217 LOC)

3 *.plist files (92 LOC)

1 *.md files (57 LOC)

2 *.txt files (53 LOC)

1 *.storyboard files (39 LOC)

" *.json" is biggest, containing 69.57% of LOC.

" *.storyboard" is smallest, containing 2.59% 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)

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

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

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

*.bash files are analyzed with ShellAnalyzer:

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

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

2025-01-10 14:10