apache / skywalking-satelliteSource 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

mod

gitattributes

tpl

cmd

15 extensions are included in analyses: txt, go, md, yml, yaml, java, sh, xml, properties, mod, gitignore, gitattributes, tpl, json, cmd
7 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (11 files).
exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/bin/.*" (Binaries for distribution) (2 files).
exclude files with path like ".*/dist/.*" (Distributions) (217 files).
exclude files with path like ".*/docs/.*" (Documentation) (70 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 601 files:

286 files are included in analyses.
315 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.

161 files

109 files

3 files

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

161 files match defined criteria (9,914 LOC, 100.0% vs. main code):

160 *.go files (9,505 LOC)
1 *.yaml files (409 LOC)

" *.go" is biggest, containing 95.87% of LOC.
" *.yaml" is smallest, containing 4.13% 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 ".*/e2e/.*".
files with paths like ".*_test[.].*".

109 files match defined criteria (5,049 LOC, 50.9% vs. main code):

35 *.go files (3,030 LOC)
41 *.yml files (883 LOC)
8 *.yaml files (533 LOC)
5 *.xml files (298 LOC)
13 *.java files (236 LOC)
7 *.sh files (69 LOC)

" *.go" is biggest, containing 60.01% of LOC.
" *.sh" is smallest, containing 1.37% 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 ".*/docker[-]compose[.]yml".
files with paths like ".*/pom[.]xml".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitattributes".

3 files match defined criteria (118 LOC, 1.2% vs. main code):

2 *.sh files (72 LOC)
1 *.yml files (46 LOC)

" *.sh" is biggest, containing 61.02% of LOC.
" *.yml" is smallest, containing 38.98% of LOC.

Other Code

mod

properties

txt

Explore: circles | sunburst

The following criteria are used to filter files:

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

13 files match defined criteria (343 LOC, 3.5% vs. main code):

10 *.md files (196 LOC)
1 *.mod files (105 LOC)
1 *.properties files (25 LOC)
1 *.txt files (17 LOC)

" *.md" is biggest, containing 57.14% of LOC.
" *.txt" is smallest, containing 4.96% 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

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

2023-08-11 02:04