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

cmd

props

txt

csproj

gitattributes

plist

editorconfig

18 extensions are included in analyses: cs, ps1, yaml, md, json, js, cmd, props, txt, csproj, css, gitattributes, plist, psm1, sh, editorconfig, svg, gitignore
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (8 files).
exclude files with path like ".*/docs/.*" (Documentation) (1 file).
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).

The source code folder contains 473 files:

361 files are included in analyses.
112 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.

282 files

36 files

2 files

41 files

Main Code

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

props

cmd

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

282 files match defined criteria (23,224 LOC, 100.0% vs. main code):

104 *.ps1 files (15,296 LOC)
168 *.cs files (7,048 LOC)
3 *.js files (283 LOC)
1 *.psm1 files (263 LOC)
1 *.css files (247 LOC)
2 *.props files (51 LOC)
3 *.cmd files (36 LOC)

" *.ps1" is biggest, containing 65.86% of LOC.
" *.cmd" is smallest, containing 0.16% of LOC.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

csproj

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]ests/.*".
files with paths like ".*[.][Tt]ests[.].*".
files with paths like ".*[-]test[-].*".
files with paths like ".*[.]tests[.].*".

36 files match defined criteria (3,345 LOC, 14.4% vs. main code):

32 *.cs files (2,771 LOC)
3 *.ps1 files (539 LOC)
1 *.csproj files (35 LOC)

" *.cs" is biggest, containing 82.84% of LOC.
" *.csproj" is smallest, containing 1.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 ".*/package[-]lock[.]json".

2 files match defined criteria (2,805 LOC, 12.1% vs. main code). All matches are in *.json 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 ".*/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".

2 files match defined criteria (105 LOC, 0.5% vs. main code):

1 *.csproj files (81 LOC)
1 *.sh files (24 LOC)

" *.csproj" is biggest, containing 77.14% of LOC.
" *.sh" is smallest, containing 22.86% of LOC.

Other Code

plist

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

41 files match defined criteria (6,179 LOC, 26.6% vs. main code):

16 *.json files (3,048 LOC)
22 *.md files (3,042 LOC)
1 *.svg files (76 LOC)
1 *.plist files (12 LOC)
1 *.txt files (1 LOC)

" *.json" is biggest, containing 49.33% 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

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

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

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

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

*.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 23:27