azure / azure-umqtt-c - 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

targets

nuspec

gitmodules

12 extensions are included in analyses: c, sh, txt, h, md, cmd, gitignore, targets, cmake, nuspec, gitmodules, yaml
3 criteria are used to exclude files from analysis:

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

50 files are included in analyses.
20 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.

14 files

7 files

12 files

17 files

Main Code

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

cmd

targets

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

14 files match defined criteria (3,307 LOC, 100.0% vs. main code):

3 *.c files (2,653 LOC)
5 *.cmd files (333 LOC)
4 *.h files (218 LOC)
1 *.targets files (98 LOC)
1 *.cmake files (5 LOC)

" *.c" is biggest, containing 80.22% of LOC.
" *.cmake" is smallest, containing 0.15% 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 ".*/[Tt]ests/.*".
files with paths like ".*_test[.].*".

7 files match defined criteria (3,965 LOC, 119.9% vs. main code):

6 *.c files (3,931 LOC)
1 *.sh files (34 LOC)

" *.c" is biggest, containing 99.14% of LOC.
" *.sh" is smallest, containing 0.86% 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 ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitmodules".
files with paths like ".*[.]sh".
files with paths like ".*[.]nuspec".

12 files match defined criteria (280 LOC, 8.5% vs. main code):

11 *.sh files (246 LOC)
1 *.nuspec files (34 LOC)

" *.sh" is biggest, containing 87.86% of LOC.
" *.nuspec" is smallest, containing 12.14% of LOC.

Other Code

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]md".
files with paths like ".*[.]txt".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[Ss]amples/.*".

17 files match defined criteria (877 LOC, 26.5% vs. main code):

4 *.md files (378 LOC)
9 *.txt files (286 LOC)
3 *.c files (203 LOC)
1 *.h files (10 LOC)

" *.md" is biggest, containing 43.1% of LOC.
" *.h" is smallest, containing 1.14% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.c files are analyzed with CStyleAnalyzer:

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

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

*.h files are analyzed with CppAnalyzer:

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

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

*.cmake 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:13