aws / aws-xray-sdk-dotnet - 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

csproj

txt

proj

gitattributes

props

nuspec

12 extensions are included in analyses: cs, json, csproj, md, yaml, txt, gitignore, proj, gitattributes, props, ps1, nuspec
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (9 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (3 files).
exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (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 239 files:

206 files are included in analyses.
33 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.

118 files

52 files

8 files

28 files

Main Code

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

proj

props

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

118 files match defined criteria (8,494 LOC, 100.0% vs. main code):

115 *.cs files (8,336 LOC)
1 *.ps1 files (101 LOC)
1 *.proj files (44 LOC)
1 *.props files (13 LOC)

" *.cs" is biggest, containing 98.14% of LOC.
" *.props" is smallest, containing 0.15% 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]est/.*".
files with paths like ".*/UnitTests?/.*".
files with paths like ".*UnitTests[.][a-zA-Z0-9_]+".
files with paths like ".*/IntegrationTests?/.*".

52 files match defined criteria (7,176 LOC, 84.5% vs. main code):

49 *.cs files (6,990 LOC)
3 *.csproj files (186 LOC)

" *.cs" is biggest, containing 97.41% of LOC.
" *.csproj" is smallest, containing 2.59% 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 ".*[.]nuspec".
files with paths like ".*[.]csproj".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitattributes".

8 files match defined criteria (337 LOC, 4.0% vs. main code):

7 *.csproj files (270 LOC)
1 *.nuspec files (67 LOC)

" *.csproj" is biggest, containing 80.12% of LOC.
" *.nuspec" is smallest, containing 19.88% 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 ".*/README[.][a-z0-9]+".
files with paths like ".*[.]json".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]txt".

28 files match defined criteria (3,206 LOC, 37.7% vs. main code):

22 *.json files (1,893 LOC)
5 *.md files (1,270 LOC)
1 *.txt files (43 LOC)

" *.json" is biggest, containing 59.05% of LOC.
" *.txt" is smallest, containing 1.34% 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)

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

*.proj 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-03 22:09