azure / azure-functions-java-worker

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

Source Code Analysis Scope

Files includes and excluded from analyses

proto

csproj

txt

nuspec

13 extensions are included in analyses: java, cs, md, yaml, json, xml, ps1, gitignore, bat, proto, csproj, txt, nuspec
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/cache/.*" (Caches) (2 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (5 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 241 files:

199 files are included in analyses.
42 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.

94 files

52 files

8 files

45 files

Main Code

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

proto

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

94 files match defined criteria (5,567 LOC, 100.0% vs. main code):

84 *.java files (4,483 LOC)
3 *.proto files (589 LOC)
5 *.ps1 files (463 LOC)
2 *.xml files (32 LOC)

" *.java" is biggest, containing 80.53% of LOC.
" *.xml" is smallest, containing 0.57% 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 ".*[-]tests[-].*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*/[Tt]ests/.*".

52 files match defined criteria (3,567 LOC, 64.1% vs. main code):

27 *.cs files (2,064 LOC)
22 *.java files (1,404 LOC)
1 *.ps1 files (50 LOC)
2 *.csproj files (49 LOC)

" *.cs" is biggest, containing 57.86% of LOC.
" *.csproj" is smallest, containing 1.37% of LOC.

Build and Deployment Code

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

nuspec

Explore: circles | sunburst

The following criteria are used to filter files:

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

8 files match defined criteria (828 LOC, 14.9% vs. main code):

4 *.xml files (802 LOC)
1 *.nuspec files (23 LOC)
3 *.bat files (3 LOC)

" *.xml" is biggest, containing 96.86% of LOC.
" *.bat" is smallest, containing 0.36% of LOC.

Other Code

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

45 files match defined criteria (1,741 LOC, 31.3% vs. main code):

12 *.md files (930 LOC)
19 *.java files (310 LOC)
3 *.xml files (305 LOC)
11 *.json files (196 LOC)

" *.md" is biggest, containing 53.42% of LOC.
" *.json" is smallest, containing 11.26% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.java files are analyzed with JavaAnalyzer:

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 package names)

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

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

2025-05-06 21:20