azure / Azure-Landing-Zones-Library

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

Source Code Analysis Scope

Files includes and excluded from analyses

txt

webmanifest

editorconfig

15 extensions are included in analyses: json, js, html, md, yaml, txt, css, svg, ps1, gitignore, sh, toml, webmanifest, xml, editorconfig
6 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (5 files).
exclude files with path like ".*/docs/.*" (Documentation) (118 files).
exclude files with path like ".*/docs?/_?(build|themes?|templates?|static)/.*" (Sphinx) (0 files).
exclude files with path like ".*[.]min[.]js" (Minimized JS library) (0 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).

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.

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

6 files match defined criteria (634 LOC, 100.0% vs. main code). All matches are in *.ps1 files.

Build and Deployment Code

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

Explore: circles | sunburst

3 files match defined criteria (42 LOC, 6.6% vs. main code). All matches are in *.sh files.

Other Code

Explore: circles | sunburst

446 files match defined criteria (96,716 LOC, 15254.9% vs. main code):