JetBrains / sdk
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
targets
props
resx
txt
cmd
proj
fs
patch
vbproj
fsproj
gitattributes
editorconfig
shproj
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.

main20380 LOC (30%) 260 files
test22345 LOC (33%) 196 files
generated39 LOC (<1%) 1 file
build and deployment2519 LOC (3%) 75 files
other22062 LOC (32%) 44 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
targets
props
cmd
proj
fsproj
fs
shproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 260 files match defined criteria (20,380 LOC, 100.0% vs. main code):
    • 156 *.cs files (9,717 LOC)
    • 13 *.xlf files (5,538 LOC)
    • 35 *.targets files (2,936 LOC)
    • 10 *.ps1 files (969 LOC)
    • 1 *.psm1 files (307 LOC)
    • 12 *.props files (276 LOC)
    • 3 *.cmake files (194 LOC)
    • 1 *.groovy files (135 LOC)
    • 7 *.cmd files (89 LOC)
    • 4 *.proj files (84 LOC)
    • 8 *.xml files (51 LOC)
    • 3 *.fsproj files (32 LOC)
    • 3 *.vb files (24 LOC)
    • 3 *.fs files (15 LOC)
    • 1 *.shproj files (13 LOC)
  • " *.cs" is biggest, containing 47.68% of LOC.
  • " *.shproj" is smallest, containing 0.06% of LOC.


*.cs9717 LOC (47%) 156 files
*.xlf5538 LOC (27%) 13 files
*.targets2936 LOC (14%) 35 files
*.ps1969 LOC (4%) 10 files
*.psm1307 LOC (1%) 1 file
*.props276 LOC (1%) 12 files
*.cmake194 LOC (<1%) 3 files
*.groovy135 LOC (<1%) 1 file
*.cmd89 LOC (<1%) 7 files
*.proj84 LOC (<1%) 4 files
*.xml51 LOC (<1%) 8 files
*.fsproj32 LOC (<1%) 3 files
*.vb24 LOC (<1%) 3 files
*.fs15 LOC (<1%) 3 files
*.shproj13 LOC (<1%) 1 file
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
csproj
targets
props
cmd
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/test[.].*".
    • files with paths like ".*[.]UnitTests/.*".
    • files with paths like ".*UnitTests[.][a-zA-Z0-9_]+".
    • files with paths like ".*/[Mm]ocks/.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*[.][Tt]ests/.*".
    • files with paths like ".*[.][Tt]ests[.].*".
  • 196 files match defined criteria (22,345 LOC, 109.6% vs. main code):
    • 176 *.cs files (21,876 LOC)
    • 13 *.csproj files (381 LOC)
    • 3 *.targets files (62 LOC)
    • 2 *.props files (15 LOC)
    • 1 *.sh files (8 LOC)
    • 1 *.cmd files (3 LOC)
  • " *.cs" is biggest, containing 97.9% of LOC.
  • " *.cmd" is smallest, containing 0.01% of LOC.


*.cs21876 LOC (97%) 176 files
*.csproj381 LOC (1%) 13 files
*.targets62 LOC (<1%) 3 files
*.props15 LOC (<1%) 2 files
*.sh8 LOC (<1%) 1 file
*.cmd3 LOC (<1%) 1 file
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 (39 LOC, 0.2% vs. main code). All matches are in *.cs files.


*.cs39 LOC (100%) 1 file
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
vbproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]csproj".
    • files with paths like ".*[.]vbproj".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitattributes".
  • 75 files match defined criteria (2,519 LOC, 12.4% vs. main code):
    • 19 *.sh files (1,517 LOC)
    • 53 *.csproj files (973 LOC)
    • 3 *.vbproj files (29 LOC)
  • " *.sh" is biggest, containing 60.22% of LOC.
  • " *.vbproj" is smallest, containing 1.15% of LOC.


*.sh1517 LOC (60%) 19 files
*.csproj973 LOC (38%) 53 files
*.vbproj29 LOC (1%) 3 files
Other Code
patch
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 ".*[.]editorconfig".
    • files with paths like ".*[.]patch".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]gitignore".
  • 44 files match defined criteria (22,062 LOC, 108.3% vs. main code):
    • 21 *.json files (21,828 LOC)
    • 3 *.patch files (178 LOC)
    • 2 *.md files (38 LOC)
    • 18 *.txt files (18 LOC)
  • " *.json" is biggest, containing 98.94% of LOC.
  • " *.txt" is smallest, containing 0.08% of LOC.


*.json21828 LOC (98%) 21 files
*.patch178 LOC (<1%) 3 files
*.md38 LOC (<1%) 2 files
*.txt18 LOC (<1%) 18 files
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)
  • *.xlf 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
  • *.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
  • *.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
  • *.psm1 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
  • *.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
  • *.groovy files are analyzed with GroovyAnalyzer:
    • 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
  • *.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
  • *.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
  • *.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
  • *.fsproj 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
  • *.vb files are analyzed with VisualBasicAnalyzer:
    • 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
  • *.fs 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
  • *.shproj 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

2026-01-18 17:04