JetBrains / intellij-deps-kotlinx.coroutines 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

pro

properties

cfg

15 extensions are included in analyses: kt, md, kts, txt, java, pro, properties, xml, bat, gitignore, py, sh, json, yaml, cfg
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (2 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (13 files).
exclude files with path like ".*/docs/.*" (Documentation) (30 files).
exclude files with path like ".*/testdata/.*" (Test data) (3 files).

The source code folder contains 1,329 files:

1,191 files are included in analyses.
138 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.

466 files

642 files

3 files

80 files

Main Code

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

pro

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

466 files match defined criteria (30,407 LOC, 100.0% vs. main code):

397 *.kt files (27,724 LOC)
40 *.kts files (1,705 LOC)
20 *.java files (796 LOC)
8 *.pro files (119 LOC)
1 *.py files (63 LOC)

" *.kt" is biggest, containing 91.18% of LOC.
" *.py" is smallest, containing 0.21% 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]est/.*".
files with paths like ".*/test[-]resources/.*".
files with paths like ".*[-]tests/.*".
files with paths like ".*/[Tt]ests/.*".
files with paths like ".*[-]test[-].*".

642 files match defined criteria (53,301 LOC, 175.3% vs. main code):

640 *.kt files (53,280 LOC)
1 *.xml files (11 LOC)
1 *.kts files (10 LOC)

" *.kt" is biggest, containing 99.96% of LOC.
" *.kts" is smallest, containing 0.02% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/package[.]json".
files with paths like ".*[.]bat".
files with paths like ".*[.]sh".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

3 files match defined criteria (224 LOC, 0.7% vs. main code):

2 *.bat files (146 LOC)
1 *.sh files (78 LOC)

" *.bat" is biggest, containing 65.18% of LOC.
" *.sh" is smallest, containing 34.82% of LOC.

Other Code

txt

properties

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 ".*[.]properties".
files with paths like ".*[.]json".
files with paths like ".*[.]txt".
files with paths like ".*/LICENSE[.][a-z0-9]+".
files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*/[.]gitignore".

80 files match defined criteria (5,161 LOC, 17.0% vs. main code):

34 *.md files (4,182 LOC)
28 *.txt files (468 LOC)
11 *.kt files (417 LOC)
6 *.properties files (71 LOC)
1 *.json files (23 LOC)

" *.md" is biggest, containing 81.03% of LOC.
" *.json" is smallest, containing 0.45% 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)

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

*.java files are analyzed with JavaAnalyzer:

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 package names)

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

*.py files are analyzed with PythonAnalyzer:

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

2026-01-18 17:31