JetBrains / go-code-samples 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

mod

txt

http

12 extensions are included in analyses: go, js, xml, mod, sql, json, md, html, gitignore, txt, http, yaml
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/testdata/.*" (Test data) (2 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (20 files).
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 172 files:

123 files are included in analyses.
49 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.

68 files

16 files

1 file

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

68 files match defined criteria (3,227 LOC, 100.0% vs. main code):

36 *.go files (2,287 LOC)
17 *.js files (718 LOC)
7 *.html files (134 LOC)
7 *.sql files (81 LOC)
1 *.yaml files (7 LOC)

" *.go" is biggest, containing 70.87% of LOC.
" *.yaml" is smallest, containing 0.22% of LOC.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

http

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*_test[.].*".
files with paths like ".*/mock[a-zA-Z0-9_\- ]+/.*".

16 files match defined criteria (904 LOC, 28.0% vs. main code):

13 *.go files (698 LOC)
3 *.http files (206 LOC)

" *.go" is biggest, containing 77.21% of LOC.
" *.http" is smallest, containing 22.79% 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 ".*/package[-]lock[.]json".

1 file matches defined criteria (102 LOC, 3.2% vs. main code). All matches are in *.json files.

Other Code

mod

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 ".*/go[.]mod".
files with paths like ".*[.]json".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*[.]txt".

39 files match defined criteria (916 LOC, 28.4% vs. main code):

7 *.go files (374 LOC)
6 *.json files (240 LOC)
11 *.mod files (207 LOC)
9 *.md files (48 LOC)
3 *.sql files (34 LOC)
1 *.yaml files (7 LOC)
2 *.txt files (6 LOC)

" *.go" is biggest, containing 40.83% of LOC.
" *.txt" is smallest, containing 0.66% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.go files are analyzed with GoLangAnalyzer:

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

*.js files are analyzed with JavaScriptAnalyzer:

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

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

*.sql files are analyzed with SqlAnalyzer:

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

*.yaml files are analyzed with YamlAnalyzer:

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:26