Uber / neuropodSource Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope

Files includes and excluded from analyses

patch

txt

gitattributes

clang-format

clang-tidy

21 extensions are included in analyses: cc, py, hh, h, sh, java, json, md, bzl, pt, yml, pb, patch, txt, dockerignore, gitattributes, c, gitignore, dockerfile, clang-format, clang-tidy
5 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) (10 files).
exclude files with path like ".*/docs/.*" (Documentation) (8 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 412 files:

325 files are included in analyses.
87 files are excluded from analyses:

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.

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

177 files match defined criteria (11,162 LOC, 100.0% vs. main code):

49 *.cc files (4,833 LOC)
48 *.hh files (2,686 LOC)
38 *.py files (1,779 LOC)
7 *.bzl files (729 LOC)
11 *.java files (602 LOC)
23 *.h files (497 LOC)
1 *.yml files (36 LOC)

" *.cc" is biggest, containing 43.3% of LOC.
" *.yml" is smallest, containing 0.32% 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_.*".
files with paths like ".*/[Tt]ests/.*".
files with paths like ".*[.][Tt]est[.].*".
files with paths like ".*[.]test[.].*".

97 files match defined criteria (5,092 LOC, 45.6% vs. main code):

33 *.cc files (1,860 LOC)
42 *.py files (1,491 LOC)
4 *.pb files (635 LOC)
10 *.java files (566 LOC)
1 *.yml files (165 LOC)
1 *.c files (155 LOC)
1 *.hh files (122 LOC)
4 *.pt files (58 LOC)
1 *.sh files (40 LOC)

" *.cc" is biggest, containing 36.53% of LOC.
" *.sh" is smallest, containing 0.79% 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".
files with paths like ".*/[.]gitattributes".
files with paths like ".*[.]dockerfile".

22 files match defined criteria (461 LOC, 4.1% vs. main code):

21 *.sh files (398 LOC)
1 *.dockerfile files (63 LOC)

" *.sh" is biggest, containing 86.33% of LOC.
" *.dockerfile" is smallest, containing 13.67% of LOC.

Other Code

patch

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]json".
files with paths like ".*[.]patch".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/[.]dockerignore".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]txt".

29 files match defined criteria (1,626 LOC, 14.6% vs. main code):

18 *.json files (1,228 LOC)
3 *.patch files (227 LOC)
7 *.md files (157 LOC)
1 *.txt files (14 LOC)

" *.json" is biggest, containing 75.52% of LOC.
" *.txt" is smallest, containing 0.86% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

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

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

2024-04-03 14:39