Source Code Analysis Scope
Files includes and excluded from analyses
properties

scoping details...
  • 10 extensions are included in analyses: xml, txt, sbt, scala, gitignore, sh, md, json, properties, yaml
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (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) (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.
main7 LOC (<1%) 1 file
test6 LOC (<1%) 1 file
generated0 LOC (0%) 0 files
build and deployment127 LOC (15%) 14 files
other695 LOC (83%) 4 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

scala7 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 1 file matches defined criteria (7 LOC, 100.0% vs. main code). All matches are in scala files.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

scala6 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
  • 1 file matches defined criteria (6 LOC, 85.7% vs. main code). All matches are in scala files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

xml73 LOC (57%) 8 files
yaml21 LOC (16%) 1 file
sbt11 LOC (8%) 2 files
sh11 LOC (8%) 1 file
gitignore11 LOC (8%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]sbt".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like "(.*/)?[.](idea|vscode|vs|gradle|mvn|settings|metadata|circleci)/.*".
  • 14 files match defined criteria (127 LOC, 1814.3% vs. main code):
    • 8 xml files (73 LOC)
    • 1 yaml files (21 LOC)
    • 2 sbt files (11 LOC)
    • 1 sh files (11 LOC)
    • 2 gitignore files (11 LOC)
Other Code
properties
Explore:   circles  |  sunburst

json679 LOC (97%) 1 file
md13 LOC (1%) 1 file
txt2 LOC (<1%) 1 file
properties1 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".
    • files with paths like ".*[.]json".
  • 4 files match defined criteria (695 LOC, 9928.6% vs. main code):
    • 1 json files (679 LOC)
    • 1 md files (13 LOC)
    • 1 txt files (2 LOC)
    • 1 properties files (1 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...
  • *.scala files are analyzed with ScalaAnalyzer:
    • 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