JetBrains / resharper-cyclomatic-complexity Source Code Overview

Source Code Analysis Scope

Files includes and excluded from analyses

csproj

properties

props

xaml

gitattributes

dotsettings

txt

20 extensions are included in analyses: cs, xml, js, ts, ps1, md, kt, kts, csproj, properties, json, cpp, props, xaml, gitattributes, bat, dotsettings, gitignore, toml, txt
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (16 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 122 files:

65 files are included in analyses.
57 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.

28 files

27 files

1 file

3 files

6 files

Main Code

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

xaml

props

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

28 files match defined criteria (1,075 LOC, 100.0% vs. main code):

12 *.cs files (508 LOC)
3 *.kts files (240 LOC)
4 *.ps1 files (125 LOC)
1 *.xaml files (67 LOC)
3 *.kt files (54 LOC)
2 *.props files (45 LOC)
2 *.xml files (28 LOC)
1 *.toml files (8 LOC)

" *.cs" is biggest, containing 47.26% of LOC.
" *.toml" is smallest, containing 0.74% 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 ".*/[Tt]est/.*".

27 files match defined criteria (1,300 LOC, 120.9% vs. main code):

10 *.cs files (639 LOC)
8 *.js files (302 LOC)
6 *.ts files (226 LOC)
2 *.cpp files (108 LOC)
1 *.csproj files (25 LOC)

" *.cs" is biggest, containing 49.15% of LOC.
" *.csproj" is smallest, containing 1.92% 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 ".*[.]cs" AND any line of content like "[/][/][ ]*".

1 file matches defined criteria (7,549 LOC, 702.2% vs. main code). All matches are in *.cs 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 ".*[.]bat".

files with paths like ".*[.]git[a-z]+".

files with paths like ".*/[.]gitignore".

files with paths like ".*/[.]gitattributes".

3 files match defined criteria (188 LOC, 17.5% vs. main code):

1 *.bat files (122 LOC)

2 *.csproj files (66 LOC)

" *.bat" is biggest, containing 64.89% of LOC.

" *.csproj" is smallest, containing 35.11% of LOC.

Other Code

properties

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 ".*[.]properties".

files with paths like ".*/[.]gitignore".

files with paths like ".*[.]txt".

6 files match defined criteria (101 LOC, 9.4% vs. main code):

2 *.md files (71 LOC)

2 *.properties files (22 LOC)

2 *.json files (8 LOC)

" *.md" is biggest, containing 70.3% of LOC.

" *.json" is smallest, containing 7.92% 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)

*.kts files are analyzed with KotlinAnalyzer:

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

Basic heuristic dependency analysis (based on imports and package statements)

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

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

*.kt files are analyzed with KotlinAnalyzer:

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

Basic heuristic dependency analysis (based on imports and package statements)

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

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

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

2026-01-18 16:44