azure / azure-sdk - 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

cmd

gitattributes

17 extensions are included in analyses: md, yaml, ps1, html, json, css, js, ts, svg, txt, cmd, xml, gitignore, py, gitattributes, psm1, sh
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (12 files).
exclude files with path like ".*[.]min[.]js" (Minimized JS library) (1 file).
exclude files with path like ".*/normalize[.](css|less|scss|styl)" (Normalize css) (1 file).
exclude files with path like ".*/docs/.*" (Documentation) (77 files).

The source code folder contains 1,521 files:

959 files are included in analyses.
562 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.

180 files

3 files

2 files

1 file

775 files

Main Code

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

cmd

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

180 files match defined criteria (29,070 LOC, 100.0% vs. main code):

102 *.ps1 files (17,799 LOC)
10 *.css files (8,525 LOC)
44 *.html files (937 LOC)
8 *.ts files (790 LOC)
6 *.js files (496 LOC)
1 *.psm1 files (263 LOC)
4 *.yaml files (172 LOC)
2 *.xml files (52 LOC)
3 *.cmd files (36 LOC)

" *.ps1" is biggest, containing 61.23% of LOC.
" *.cmd" is smallest, containing 0.12% of LOC.

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 ".*[-]test[-].*".
files with paths like ".*[.][Tt]ests[.].*".
files with paths like ".*[.]tests[.].*".

3 files match defined criteria (544 LOC, 1.9% vs. main code). All matches are in *.ps1 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".

2 files match defined criteria (3,578 LOC, 12.3% vs. main code). All matches are in *.json 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 ".*/package[-]lock[.]json".
files with paths like ".*/package[.]json".
files with paths like ".*[.]sh".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitattributes".

1 file matches defined criteria (24 LOC, 0.1% vs. main code). All matches are in *.sh files.

Other Code

txt

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 ".*[.]svg".
files with paths like ".*/[.]gitignore".

775 files match defined criteria (35,857 LOC, 123.3% vs. main code):

754 *.md files (26,879 LOC)
15 *.json files (6,204 LOC)
3 *.svg files (2,766 LOC)
3 *.txt files (8 LOC)

" *.md" is biggest, containing 74.96% of LOC.
" *.txt" is smallest, containing 0.02% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

*.css files are analyzed with CssAnalyzer:

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

*.html files are analyzed with HtmlAnalyzer:

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

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

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

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

*.yaml files are analyzed with YamlAnalyzer:

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

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

2025-05-06 21:39