JetBrains / koog 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

properties

txt

editorconfig

gitattributes

plist

pro

23 extensions are included in analyses: kt, md, kts, properties, yaml, java, xml, ipynb, bat, toml, gitignore, json, txt, html, sh, py, editorconfig, css, gitattributes, plist, swift, svg, pro
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (14 files).
exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (12 files).
exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (1 file).
exclude files with path like ".*/cache/.*" (Caches) (10 files).
exclude files with path like ".*/docs/.*" (Documentation) (87 files).

The source code folder contains 1,858 files:

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

1,105 files

75 files

4 files

422 files

Main Code

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

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

1105 files match defined criteria (119,939 LOC, 100.0% vs. main code):

1,017 *.kt files (116,046 LOC)
77 *.kts files (3,172 LOC)
5 *.java files (330 LOC)
2 *.py files (226 LOC)
2 *.toml files (143 LOC)
2 *.xml files (22 LOC)

" *.kt" is biggest, containing 96.75% of LOC.
" *.xml" is smallest, containing 0.02% 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]ests/.*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*/mock[a-zA-Z0-9_\- ]+/.*".
files with paths like ".*/[Mm]ocks/.*".
files with paths like ".*[-]tests/.*".
files with paths like ".*[-]test[-].*".
files with paths like ".*/testing[.].*".

75 files match defined criteria (10,665 LOC, 8.9% vs. main code):

72 *.kt files (10,559 LOC)
2 *.kts files (96 LOC)
1 *.xml files (10 LOC)

" *.kt" is biggest, containing 99.01% of LOC.
" *.xml" is smallest, containing 0.09% 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 ".*[.]bat".
files with paths like ".*/AndroidManifest[.]xml".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/docker[-]compose[.]yaml".
files with paths like ".*/[.]gitattributes".
files with paths like ".*/pom[.]xml".
files with paths like ".*[.]sh".

4 files match defined criteria (106 LOC, 0.1% vs. main code):

1 *.bat files (73 LOC)
3 *.sh files (33 LOC)

" *.bat" is biggest, containing 68.87% of LOC.
" *.sh" is smallest, containing 31.13% of LOC.

Other Code

txt

properties

plist

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

422 files match defined criteria (29,073 LOC, 24.2% vs. main code):

182 *.kt files (12,950 LOC)
106 *.md files (8,775 LOC)
12 *.ipynb files (3,800 LOC)
11 *.bat files (795 LOC)
18 *.java files (775 LOC)
28 *.kts files (726 LOC)
16 *.xml files (426 LOC)
8 *.toml files (180 LOC)
6 *.json files (180 LOC)
3 *.txt files (177 LOC)
24 *.properties files (160 LOC)
2 *.html files (52 LOC)
4 *.yaml files (52 LOC)
1 *.swift files (17 LOC)
1 *.plist files (8 LOC)

" *.kt" is biggest, containing 44.54% of LOC.
" *.plist" is smallest, containing 0.03% 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)

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

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

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

2026-01-18 17:37