apache / skywalking-pythonSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

ini

cfg

txt

gitmodules

13 extensions are included in analyses: py, yml, yaml, md, sh, toml, json, ini, cfg, gitignore, dockerignore, txt, gitmodules
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (10 files).
exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/docs/.*" (Documentation) (24 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 431 files:

385 files are included in analyses.
46 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.

115 files

259 files

11 files

Main Code

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

cfg

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

115 files match defined criteria (5,972 LOC, 100.0% vs. main code):

112 *.py files (5,789 LOC)
2 *.toml files (159 LOC)
1 *.cfg files (24 LOC)

" *.py" is biggest, containing 96.94% of LOC.
" *.cfg" is smallest, containing 0.4% 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 ".*/e2e/.*".
files with paths like ".*[-]test[-].*".

259 files match defined criteria (6,996 LOC, 117.1% vs. main code):

71 *.yml files (4,473 LOC)
157 *.py files (1,737 LOC)
26 *.yaml files (753 LOC)
5 *.sh files (33 LOC)

" *.yml" is biggest, containing 63.94% of LOC.
" *.sh" is smallest, containing 0.47% of LOC.

Other Code

ini

Explore: circles | sunburst

The following criteria are used to filter files:

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

11 files match defined criteria (442 LOC, 7.4% vs. main code):

4 *.md files (276 LOC)
1 *.yaml files (81 LOC)
5 *.py files (65 LOC)
1 *.ini files (20 LOC)

" *.md" is biggest, containing 62.44% of LOC.
" *.ini" is smallest, containing 4.52% 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

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

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

2023-08-11 01:45