microsoft / vscode-azurearmtools
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
jsonc
vscodeignore
cmd
  • 14 extensions are included in analyses: json, ts, txt, jsonc, svg, yml, md, js, gitignore, ps1, vscodeignore, sh, html, cmd
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (15 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (3 files).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (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).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (57 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.

main15844 LOC (13%) 164 files
test26211 LOC (22%) 172 files
generated21890 LOC (18%) 1 files
build and deployment24 LOC (<1%) 2 files
other51505 LOC (44%) 355 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
jsonc
cmd
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 164 files match defined criteria (15,844 lines of code, 100.0% vs. main code):
    • 160 *.ts files (15,504 lines of code)
    • 1 *.jsonc files (187 lines of code)
    • 1 *.ps1 files (133 lines of code)
    • 1 *.js files (19 lines of code)
    • 1 *.cmd files (1 lines of code)
  • " *.ts" is biggest, containing 97.85% of code.
  • " *.cmd" is smallest, containing 0.01% of code.


*.ts15504 LOC (97%) 160 files
*.jsonc187 LOC (1%) 1 files
*.ps1133 LOC (<1%) 1 files
*.js19 LOC (<1%) 1 files
*.cmd1 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
jsonc
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 172 files match defined criteria (26,211 lines of code, 165.4% vs. main code):
    • 124 *.ts files (25,581 lines of code)
    • 48 *.jsonc files (630 lines of code)
  • " *.ts" is biggest, containing 97.6% of code.
  • " *.jsonc" is smallest, containing 2.4% of code.


*.ts25581 LOC (97%) 124 files
*.jsonc630 LOC (2%) 48 files
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 ".*/package[-]lock[.]json".
  • 1 file matches defined criteria (21,890 lines of code, 138.2% vs. main code). All matches are in *.json files.


*.json21890 LOC (100%) 1 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[-]lock[.]json".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*[.]sh".
    • files with paths like ".*([.]|/)webpack([.]|/).*".
  • 2 files match defined criteria (24 lines of code, 0.2% vs. main code):
    • 1 *.sh files (12 lines of code)
    • 1 *.js files (12 lines of code)
  • " *.sh" is biggest, containing 50% of code.
  • " *.js" is smallest, containing 50% of code.


*.sh12 LOC (50%) 1 files
*.js12 LOC (50%) 1 files
Other Code
jsonc
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]vscodeignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]svg".
  • 355 files match defined criteria (51,505 lines of code, 325.1% vs. main code):
    • 316 *.json files (50,247 lines of code)
    • 5 *.md files (736 lines of code)
    • 33 *.svg files (515 lines of code)
    • 1 *.jsonc files (7 lines of code)
  • " *.json" is biggest, containing 97.56% of code.
  • " *.jsonc" is smallest, containing 0.01% of code.


*.json50247 LOC (97%) 316 files
*.md736 LOC (1%) 5 files
*.svg515 LOC (<1%) 33 files
*.jsonc7 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.jsonc 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
  • *.ps1 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
  • *.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
  • *.cmd 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


2022-01-30 15:14