JetBrains / aspire-plugin Source Code Overview

Source Code Analysis Scope

Files includes and excluded from analyses

csproj

razor

xaml

properties

http

plist

props

txt

gitattributes

dotsettings

proto

cmd

25 extensions are included in analyses: kt, cs, json, css, csproj, razor, js, svg, xml, kts, yaml, xaml, properties, md, http, plist, gitignore, props, txt, gitattributes, bat, dotsettings, toml, proto, cmd
4 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) (13 files).
exclude files with path like ".*/dist/.*" (Distributions) (27 files).
exclude files with path like ".*/bootstrap[.](js|css|less|scss|styl)" (Bootstrap) (0 files).

The source code folder contains 649 files:

455 files are included in analyses.
194 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.

7 files

Main Code

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

razor

xaml

proto

cmd

props

http

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

308 files match defined criteria (15,455 LOC, 100.0% vs. main code):

167 *.kt files (9,873 LOC)
78 *.cs files (2,786 LOC)
27 *.razor files (510 LOC)
6 *.css files (489 LOC)
6 *.xaml files (482 LOC)
8 *.kts files (445 LOC)
1 *.proto files (364 LOC)
7 *.xml files (249 LOC)
1 *.cmd files (178 LOC)
2 *.props files (34 LOC)
1 *.toml files (25 LOC)
4 *.http files (20 LOC)

" *.kt" is biggest, containing 63.88% of LOC.
" *.http" is smallest, containing 0.13% 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 ".*/UnitTests?/.*".
files with paths like ".*/[Tt]est/.*".

13 files match defined criteria (786 LOC, 5.1% vs. main code):

8 *.kt files (590 LOC)
3 *.cs files (144 LOC)
2 *.csproj files (52 LOC)

" *.kt" is biggest, containing 75.06% of LOC.
" *.csproj" is smallest, containing 6.62% 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 ".*/generated/.*".
files with paths like ".*[.]cs" AND any line of content like "[/][/][ ]*".

files with any line of content like "//[ ]*Generated by .*".

7 files match defined criteria (4,837 LOC, 31.3% vs. main code):

4 *.cs files (2,981 LOC)

3 *.kt files (1,856 LOC)

" *.cs" is biggest, containing 61.63% of LOC.

" *.kt" is smallest, containing 38.37% of LOC.

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 ".*[.]git[a-z]+".

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

files with paths like ".*/AndroidManifest[.]xml".

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

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

29 files match defined criteria (431 LOC, 2.8% vs. main code):

27 *.csproj files (353 LOC)

1 *.bat files (72 LOC)

1 *.xml files (6 LOC)

" *.csproj" is biggest, containing 81.9% of LOC.

" *.xml" is smallest, containing 1.39% of LOC.

Other Code

properties
plist
txt

Explore: circles | sunburst

The following criteria are used to filter files:

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

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

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

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

files with paths like ".*/README[.][a-z0-9]+".

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

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

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

98 files match defined criteria (1,711 LOC, 11.1% vs. main code):

70 *.json files (845 LOC)

5 *.md files (562 LOC)

5 *.properties files (140 LOC)

14 *.svg files (80 LOC)

3 *.plist files (73 LOC)

1 *.txt files (11 LOC)

" *.json" is biggest, containing 49.39% of LOC.

" *.txt" is smallest, containing 0.64% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

*.razor files are analyzed with HtmlAnalyzer:

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

*.css files are analyzed with CssAnalyzer:

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

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

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

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

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

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

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

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

*.http 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 17:31