epam / edp-ddm-form-submission-validation
Source 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
gitattributes
tpl
editorconfig
npmrc
properties
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.

main9174 LOC (87%) 42 files
test1061 LOC (10%) 5 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other286 LOC (2%) 6 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
tpl
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 42 files match defined criteria (9,174 LOC, 100.0% vs. main code):
    • 31 *.ts files (8,904 LOC)
    • 7 *.yaml files (207 LOC)
    • 1 *.tpl files (57 LOC)
    • 3 *.groovy files (6 LOC)
  • " *.ts" is biggest, containing 97.06% of LOC.
  • " *.groovy" is smallest, containing 0.07% of LOC.


*.ts8904 LOC (97%) 31 files
*.yaml207 LOC (2%) 7 files
*.tpl57 LOC (<1%) 1 file
*.groovy6 LOC (<1%) 3 files
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 ".*/jest[.][a-zA-Z0-9\.]+".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
  • 5 files match defined criteria (1,061 LOC, 11.6% vs. main code):
    • 4 *.ts files (1,046 LOC)
    • 1 *.yaml files (15 LOC)
  • " *.ts" is biggest, containing 98.59% of LOC.
  • " *.yaml" is smallest, containing 1.41% of LOC.


*.ts1046 LOC (98%) 4 files
*.yaml15 LOC (1%) 1 file
Other Code
txt
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]npmrc".
    • files with paths like ".*[.]editorconfig".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
  • 6 files match defined criteria (286 LOC, 3.1% vs. main code):
    • 1 *.txt files (169 LOC)
    • 3 *.json files (95 LOC)
    • 1 *.properties files (19 LOC)
    • 1 *.md files (3 LOC)
  • " *.txt" is biggest, containing 59.09% of LOC.
  • " *.md" is smallest, containing 1.05% of LOC.


*.txt169 LOC (59%) 1 file
*.json95 LOC (33%) 3 files
*.properties19 LOC (6%) 1 file
*.md3 LOC (1%) 1 file
Analyzers
Info about analyzers used for source code examinations.

2025-01-10 14:22