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

scoping details...
  • 16 extensions are included in analyses: kt, java, kts, md, yml, py, json, cjs, txt, properties, gitattributes, pro, toml, gitignore, jsonl, bat
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (7 files).
    • 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.
main49226 LOC (5%) 335 files
test51506 LOC (5%) 186 files
generated872895 LOC (88%) 3,719 files
build and deployment1547 LOC (<1%) 12 files
other5704 LOC (<1%) 20 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
pro
jsonl
Explore:   circles  |  sunburst

kt44017 LOC (89%) 229 files
java2533 LOC (5%) 64 files
py1385 LOC (2%) 3 files
kts1062 LOC (2%) 29 files
cjs130 LOC (<1%) 4 files
yaml56 LOC (<1%) 2 files
pro34 LOC (<1%) 1 file
toml7 LOC (<1%) 2 files
jsonl2 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 335 files match defined criteria (49,226 LOC, 100.0% vs. main code):
    • 229 kt files (44,017 LOC)
    • 64 java files (2,533 LOC)
    • 3 py files (1,385 LOC)
    • 29 kts files (1,062 LOC)
    • 4 cjs files (130 LOC)
    • 2 yaml files (56 LOC)
    • 1 pro files (34 LOC)
    • 2 toml files (7 LOC)
    • 1 jsonl files (2 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
pro
Explore:   circles  |  sunburst

kt49829 LOC (96%) 179 files
py1494 LOC (2%) 4 files
cjs176 LOC (<1%) 2 files
pro7 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test[.].*".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with paths like ".*/test_.*".
  • 186 files match defined criteria (51,506 LOC, 104.6% vs. main code):
    • 179 kt files (49,829 LOC)
    • 4 py files (1,494 LOC)
    • 2 cjs files (176 LOC)
    • 1 pro files (7 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst

kt872895 LOC (100%) 3,719 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.](kts?|java|go|py|cs)" AND any line of content like "[/][/][ ]*File generated from .*".
  • 3719 files match defined criteria (872,895 LOC, 1773.2% vs. main code). All matches are in kt files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
gitattributes
Explore:   circles  |  sunburst

yaml1459 LOC (94%) 8 files
bat73 LOC (4%) 1 file
gitignore9 LOC (<1%) 1 file
gitattributes6 LOC (<1%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*[.]bat".
  • 12 files match defined criteria (1,547 LOC, 3.1% vs. main code):
    • 8 yaml files (1,459 LOC)
    • 1 bat files (73 LOC)
    • 1 gitignore files (9 LOC)
    • 2 gitattributes files (6 LOC)
Other Code
properties
Explore:   circles  |  sunburst

md4317 LOC (75%) 8 files
txt689 LOC (12%) 3 files
json661 LOC (11%) 7 files
properties37 LOC (<1%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
  • 20 files match defined criteria (5,704 LOC, 11.6% vs. main code):
    • 8 md files (4,317 LOC)
    • 3 txt files (689 LOC)
    • 7 json files (661 LOC)
    • 2 properties files (37 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)
  • *.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
  • *.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)
  • *.cjs 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
  • *.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
  • *.pro 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
  • *.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
  • *.jsonl files are analyzed with JsonAnalyzer:
    • 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