spotify / klioSource 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

tpl

ini

cfg

proto

18 extensions are included in analyses: py, rst, yaml, txt, in, tpl, md, svg, css, ini, cfg, dockerignore, sh, json, js, html, gitignore, proto
7 criteria are used to exclude files from analysis:

exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (13 files).
exclude files with path like ".*/docs/.*" (Documentation) (130 files).
exclude files with path like ".*[.]min[.]js" (Minimized JS library) (1 file).
exclude files with path like ".*/bootstrap[.](js|css|less|scss|styl)" (Bootstrap) (1 file).
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 564 files:

365 files are included in analyses.
199 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.

175 files

117 files

3 files

70 files

Main Code

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

tpl

proto

cfg

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

175 files match defined criteria (12,585 LOC, 100.0% vs. main code):

130 *.py files (11,466 LOC)
11 *.tpl files (364 LOC)
2 *.css files (202 LOC)
6 *.yaml files (188 LOC)
1 *.proto files (102 LOC)
1 *.html files (102 LOC)
18 *.in files (92 LOC)
6 *.cfg files (69 LOC)

" *.py" is biggest, containing 91.11% of LOC.
" *.cfg" is smallest, containing 0.55% of LOC.

Test Code

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

tpl

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]ests/.*".
files with paths like ".*/test_.*".
files with paths like ".*_test[.].*".
files with paths like ".*/test[.].*".

117 files match defined criteria (13,437 LOC, 106.8% vs. main code):

108 *.py files (13,199 LOC)
7 *.yaml files (218 LOC)
1 *.tpl files (19 LOC)
1 *.in files (1 LOC)

" *.py" is biggest, containing 98.23% of LOC.
" *.in" is smallest, containing 0.01% 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 ".*[.]sh".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

3 files match defined criteria (44 LOC, 0.3% vs. main code). All matches are in *.sh files.

Other Code

txt

ini

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]json".
files with paths like ".*[.]ini".
files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*[.]txt".
files with paths like ".*[.]md".
files with paths like ".*/[.]dockerignore".
files with paths like ".*[.]svg".
files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*/[.]gitignore".

70 files match defined criteria (4,699 LOC, 37.3% vs. main code):

22 *.txt files (1,702 LOC)
13 *.rst files (977 LOC)
3 *.json files (878 LOC)
7 *.ini files (471 LOC)
9 *.py files (415 LOC)
9 *.md files (139 LOC)
3 *.svg files (82 LOC)
1 *.yaml files (24 LOC)
3 *.in files (11 LOC)

" *.txt" is biggest, containing 36.22% of LOC.
" *.in" is smallest, containing 0.23% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

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

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

*.in files are analyzed with RustAnalyzer:

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

*.cfg files are analyzed with CfgAnalyzer:

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

2025-01-17 11:39