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

scoping details...
  • 15 extensions are included in analyses: kt, graphql, gradle, yml, md, graphqls, java, txt, xml, py, properties, gitignore, kts, bat, editorconfig
  • 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.
main20419 LOC (49%) 612 files
test20016 LOC (48%) 70 files
generated0 LOC (0%) 0 files
build and deployment429 LOC (1%) 15 files
other242 LOC (<1%) 10 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

kt19536 LOC (95%) 538 files
graphql633 LOC (3%) 64 files
py164 LOC (<1%) 2 files
xml31 LOC (<1%) 2 files
yaml30 LOC (<1%) 4 files
kts15 LOC (<1%) 1 file
java10 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 612 files match defined criteria (20,419 LOC, 100.0% vs. main code):
    • 538 kt files (19,536 LOC)
    • 64 graphql files (633 LOC)
    • 2 py files (164 LOC)
    • 2 xml files (31 LOC)
    • 4 yaml files (30 LOC)
    • 1 kts files (15 LOC)
    • 1 java files (10 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

kt19375 LOC (96%) 44 files
graphqls297 LOC (1%) 5 files
gradle243 LOC (1%) 17 files
java101 LOC (<1%) 4 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
  • 70 files match defined criteria (20,016 LOC, 98.0% vs. main code):
    • 44 kt files (19,375 LOC)
    • 5 graphqls files (297 LOC)
    • 17 gradle files (243 LOC)
    • 4 java files (101 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
editorconfig
Explore:   circles  |  sunburst

yaml174 LOC (40%) 5 files
gradle153 LOC (35%) 5 files
bat72 LOC (16%) 1 file
gitignore13 LOC (3%) 1 file
xml13 LOC (3%) 2 files
editorconfig4 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]gradle".
    • files with paths like ".*[.]editorconfig".
    • files with paths like "(.*/)?[.]editorconfig".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/requirements[a-zA-Z0-9._-]*[.]txt".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*[.]bat".
    • files with paths like "(.*/)?[.](idea|vscode|vs|gradle|mvn|settings|metadata|circleci)/.*".
  • 15 files match defined criteria (429 LOC, 2.1% vs. main code):
    • 5 yaml files (174 LOC)
    • 5 gradle files (153 LOC)
    • 1 bat files (72 LOC)
    • 1 gitignore files (13 LOC)
    • 2 xml files (13 LOC)
    • 1 editorconfig files (4 LOC)
Other Code
properties
Explore:   circles  |  sunburst

md238 LOC (98%) 8 files
txt2 LOC (<1%) 1 file
properties2 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]txt".
  • 10 files match defined criteria (242 LOC, 1.2% vs. main code):
    • 8 md files (238 LOC)
    • 1 txt files (2 LOC)
    • 1 properties files (2 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)
  • *.graphql 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
  • *.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
  • *.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
  • *.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)
  • *.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)