Source Code Analysis Scope
Files includes and excluded from analyses
properties
gitattributes
editorconfig

scoping details...
  • 19 extensions are included in analyses: kt, java, kts, graphqls, md, yml, json, txt, js, xml, gitignore, py, properties, gitattributes, bat, editorconfig, html, graphql, gradle
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (1 file).
    • exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
    • exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
    • exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (0 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.
main12468 LOC (42%) 304 files
test15909 LOC (53%) 142 files
generated0 LOC (0%) 0 files
build and deployment494 LOC (1%) 18 files
other667 LOC (2%) 24 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

kt9260 LOC (74%) 173 files
java2042 LOC (16%) 85 files
kts543 LOC (4%) 27 files
graphqls299 LOC (2%) 8 files
py224 LOC (1%) 2 files
yaml45 LOC (<1%) 6 files
js37 LOC (<1%) 2 files
xml18 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 304 files match defined criteria (12,468 LOC, 100.0% vs. main code):
    • 173 kt files (9,260 LOC)
    • 85 java files (2,042 LOC)
    • 27 kts files (543 LOC)
    • 8 graphqls files (299 LOC)
    • 2 py files (224 LOC)
    • 6 yaml files (45 LOC)
    • 2 js files (37 LOC)
    • 1 xml files (18 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

kt14118 LOC (88%) 84 files
java1701 LOC (10%) 48 files
graphqls87 LOC (<1%) 9 files
graphql3 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
  • 142 files match defined criteria (15,909 LOC, 127.6% vs. main code):
    • 84 kt files (14,118 LOC)
    • 48 java files (1,701 LOC)
    • 9 graphqls files (87 LOC)
    • 1 graphql files (3 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
editorconfig
gitattributes
Explore:   circles  |  sunburst

yaml190 LOC (38%) 6 files
gitignore154 LOC (31%) 4 files
bat64 LOC (12%) 1 file
xml51 LOC (10%) 4 files
gradle20 LOC (4%) 1 file
editorconfig14 LOC (2%) 1 file
gitattributes1 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]gradle".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]editorconfig".
    • files with paths like "(.*/)?[.]editorconfig".
    • files with paths like ".*/requirements[a-zA-Z0-9._-]*[.]txt".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*[.]bat".
    • files with paths like "(.*/)?[.](idea|vscode|vs|gradle|mvn|settings|metadata|circleci)/.*".
  • 18 files match defined criteria (494 LOC, 4.0% vs. main code):
    • 6 yaml files (190 LOC)
    • 4 gitignore files (154 LOC)
    • 1 bat files (64 LOC)
    • 4 xml files (51 LOC)
    • 1 gradle files (20 LOC)
    • 1 editorconfig files (14 LOC)
    • 1 gitattributes files (1 LOC)
Other Code
properties
Explore:   circles  |  sunburst

json291 LOC (43%) 6 files
md265 LOC (39%) 14 files
txt88 LOC (13%) 3 files
properties23 LOC (3%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]properties".
  • 24 files match defined criteria (667 LOC, 5.3% vs. main code):
    • 6 json files (291 LOC)
    • 14 md files (265 LOC)
    • 3 txt files (88 LOC)
    • 1 properties files (23 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.

learn more about used code analyzers...
  • *.kt files are analyzed with KotlinAnalyzer:
    • 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 (based on imports and package statements)
  • *.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)
  • *.kts files are analyzed with KotlinAnalyzer:
    • 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 (based on imports and package statements)
  • *.graphqls 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
  • *.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
  • *.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
  • *.js files are analyzed with JavaScriptAnalyzer:
    • 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
  • *.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