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

clang-format

pyi

ini

gitmodules

22 extensions are included in analyses: html, js, h, py, css, java, txt, md, svg, json, cpp, rst, gitignore, clang-format, pyi, sh, xml, yaml, in, ini, toml, gitmodules
6 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 ".*/docs/.*" (Documentation) (86 files).
exclude files with path like ".*/skeleton[.](css|less|scss|styl)" (Skeleton css) (0 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 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 267 files:

71 files are included in analyses.
196 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.

42 files

14 files

1 file

2 files

12 files

Main Code

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

pyi

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

42 files match defined criteria (6,895 LOC, 100.0% vs. main code):

21 *.h files (3,878 LOC)
2 *.cpp files (1,626 LOC)
9 *.py files (666 LOC)
7 *.java files (505 LOC)
1 *.pyi files (208 LOC)
1 *.toml files (8 LOC)
1 *.in files (4 LOC)

" *.h" is biggest, containing 56.24% of LOC.
" *.in" is smallest, containing 0.06% 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 ".*/test_.*".
files with paths like ".*/[Tt]est/.*".

14 files match defined criteria (1,783 LOC, 25.9% vs. main code):

6 *.py files (882 LOC)
5 *.java files (701 LOC)
3 *.cpp files (200 LOC)

" *.py" is biggest, containing 49.47% of LOC.
" *.cpp" is smallest, containing 11.22% 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 ".*[.]h" AND any line of content like ".* DO NOT EDIT THIS FILE [-] it is machine generated .*".
files with any line of content like "\<\!\-\-[ ]*Generated by .*".
files with paths like ".*[.](html|html|xhtml)" AND any line of content like "[ ]*[<]meta name[=]"generator" .*".

1 file matches defined criteria (84 LOC, 1.2% vs. main code). All matches are in *.h files.

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 ".*/pom[.]xml".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitmodules".
files with paths like ".*/[.]gitignore".

2 files match defined criteria (204 LOC, 3.0% vs. main code):

1 *.xml files (203 LOC)
1 *.sh files (1 LOC)

" *.xml" is biggest, containing 99.51% of LOC.
" *.sh" is smallest, containing 0.49% of LOC.

Other Code

txt

ini

Explore: circles | sunburst

The following criteria are used to filter files:

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

12 files match defined criteria (437 LOC, 6.3% vs. main code):

4 *.md files (303 LOC)
6 *.txt files (71 LOC)
1 *.ini files (43 LOC)
1 *.json files (20 LOC)

" *.md" is biggest, containing 69.34% of LOC.
" *.json" is smallest, containing 4.58% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.h files are analyzed with CppAnalyzer:

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

*.cpp files are analyzed with CppAnalyzer:

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

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

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

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

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

2025-01-17 11:39