azure / azure-functions-dotnet-worker

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

Source Code Analysis Scope

Files includes and excluded from analyses

csproj

targets

props

proto

txt

editorconfig

nuspec

http

14 extensions are included in analyses: cs, yaml, csproj, md, json, targets, props, ps1, proto, gitignore, txt, editorconfig, nuspec, http
4 criteria are used to exclude files from analysis:

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

The source code folder contains 1,073 files:

929 files are included in analyses.
144 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.

Main Code

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

proto

targets

props

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

522 files match defined criteria (20,735 LOC, 100.0% vs. main code):

497 *.cs files (19,058 LOC)
4 *.proto files (699 LOC)
6 *.ps1 files (485 LOC)
8 *.targets files (382 LOC)
7 *.props files (111 LOC)

" *.cs" is biggest, containing 91.91% of LOC.
" *.props" is smallest, containing 0.54% 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 ".*/test[.].*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*[.][Tt]ests/.*".
files with paths like ".*[.][Tt]ests[.].*".

234 files match defined criteria (24,826 LOC, 119.7% vs. main code):

211 *.cs files (24,221 LOC)
23 *.csproj files (605 LOC)

" *.cs" is biggest, containing 97.56% of LOC.
" *.csproj" is smallest, containing 2.44% of LOC.

Build and Deployment Code

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

csproj

nuspec

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]csproj".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]nuspec".

32 files match defined criteria (765 LOC, 3.7% vs. main code):

31 *.csproj files (740 LOC)
1 *.nuspec files (25 LOC)

" *.csproj" is biggest, containing 96.73% of LOC.
" *.nuspec" is smallest, containing 3.27% of LOC.

Other Code

csproj

http

txt

props

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

141 files match defined criteria (3,234 LOC, 15.6% vs. main code):

58 *.cs files (2,121 LOC)
38 *.md files (548 LOC)
32 *.json files (368 LOC)
10 *.csproj files (162 LOC)
1 *.http files (15 LOC)
1 *.txt files (11 LOC)
1 *.props files (9 LOC)

" *.cs" is biggest, containing 65.58% of LOC.
" *.props" is smallest, containing 0.28% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

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

2025-05-06 22:04