apache / plc4x-extras - Source Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

properties

txt

mod

cmd

20 extensions are included in analyses: java, xml, go, yaml, properties, tsx, txt, ts, md, json, c, gitignore, css, adoc, html, svg, mod, kt, cjs, cmd
6 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 ".*/mvnw\.cmd" (Maven) (1 file).
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 ".*\.d\.ts" (Typescript definition files) (1 file).
exclude files with path like ".*/bin/.*" (Binaries for distribution) (0 files).

The source code folder contains 332 files:

288 files are included in analyses.
44 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.

1 file

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

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

65 *.java files (5,076 LOC)
34 *.go files (3,871 LOC)
11 *.tsx files (610 LOC)
4 *.ts files (89 LOC)
2 *.css files (69 LOC)
2 *.html files (31 LOC)
2 *.xml files (29 LOC)

" *.java" is biggest, containing 51.93% of LOC.
" *.xml" is smallest, containing 0.3% 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 ".*_test[.].*".
files with paths like ".*/[Tt]est/.*".

24 files match defined criteria (2,117 LOC, 21.7% vs. main code):

19 *.java files (1,508 LOC)
1 *.go files (549 LOC)
4 *.xml files (60 LOC)

" *.java" is biggest, containing 71.23% of LOC.
" *.xml" is smallest, containing 2.83% 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 ".*/generated/.*".

1 file matches defined criteria (128 LOC, 1.3% vs. main code). All matches are in *.ts 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 ".*/pom[.]xml".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/package[.]json".

17 files match defined criteria (2,368 LOC, 24.2% vs. main code). All matches are in *.xml files.

Other Code

properties

txt

mod

Explore: circles | sunburst

The following criteria are used to filter files:

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

126 files match defined criteria (7,660 LOC, 78.4% vs. main code):

48 *.java files (3,475 LOC)
31 *.xml files (1,128 LOC)
4 *.c files (972 LOC)
11 *.go files (642 LOC)
12 *.properties files (478 LOC)
5 *.md files (420 LOC)
7 *.txt files (265 LOC)
4 *.json files (108 LOC)
1 *.mod files (87 LOC)
2 *.adoc files (46 LOC)
1 *.kt files (39 LOC)

" *.java" is biggest, containing 45.37% of LOC.
" *.kt" is smallest, containing 0.51% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

*.tsx files are analyzed with TypeScriptAnalyzer:

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

*.ts files are analyzed with TypeScriptAnalyzer:

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

*.css files are analyzed with CssAnalyzer:

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

*.html files are analyzed with HtmlAnalyzer:

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

*.xml files are analyzed with XmlAnalyzer:

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

2025-05-07 20:58