twitter / vireoSource 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

properties

15 extensions are included in analyses: h, cpp, scala, m4, sh, c, hpp, in, md, gitignore, txt, java, json, properties, mk
6 criteria are used to exclude files from analysis:

exclude files with path like ".*[.]m4" (stuff autogenerated by autoconf - still C deps) (14 files).
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) (5 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).
exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (13 files).

The source code folder contains 371 files:

297 files are included in analyses.
74 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.

286 files

2 files

6 files

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

286 files match defined criteria (34,568 LOC, 100.0% vs. main code):

111 *.cpp files (22,150 LOC)
120 *.h files (5,275 LOC)
5 *.in files (4,805 LOC)
43 *.scala files (1,976 LOC)
6 *.hpp files (352 LOC)
1 *.java files (10 LOC)

" *.cpp" is biggest, containing 64.08% of LOC.
" *.java" is smallest, containing 0.03% 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_.*".

2 files match defined criteria (90 LOC, 0.3% vs. main code):

1 *.cpp files (70 LOC)
1 *.h files (20 LOC)

" *.cpp" is biggest, containing 77.78% of LOC.
" *.h" is smallest, containing 22.22% 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 ".*[.]mk".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

6 files match defined criteria (130 LOC, 0.4% vs. main code):

5 *.sh files (105 LOC)
1 *.mk files (25 LOC)

" *.sh" is biggest, containing 80.77% of LOC.
" *.mk" is smallest, containing 19.23% of LOC.

Other Code

properties

Explore: circles | sunburst

The following criteria are used to filter files:

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

3 files match defined criteria (208 LOC, 0.6% vs. main code):

2 *.md files (207 LOC)
1 *.properties files (1 LOC)

" *.md" is biggest, containing 99.52% of LOC.
" *.properties" is smallest, containing 0.48% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

*.scala files are analyzed with ScalaAnalyzer:

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

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

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

2025-01-17 11:59