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

scoping details...
  • 9 extensions are included in analyses: clj, cljc, md, gradle, txt, yml, bat, gitignore, properties
  • 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.
main1793 LOC (56%) 27 files
test817 LOC (25%) 6 files
generated0 LOC (0%) 0 files
build and deployment499 LOC (15%) 8 files
other83 LOC (2%) 5 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cljc
Explore:   circles  |  sunburst

cljc1008 LOC (56%) 12 files
clj785 LOC (43%) 15 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 27 files match defined criteria (1,793 LOC, 100.0% vs. main code):
    • 12 cljc files (1,008 LOC)
    • 15 clj files (785 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

clj817 LOC (100%) 6 files

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

gradle161 LOC (32%) 3 files
gitignore148 LOC (29%) 1 file
yaml122 LOC (24%) 3 files
bat68 LOC (13%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*[.]bat".
  • 8 files match defined criteria (499 LOC, 27.8% vs. main code):
    • 3 gradle files (161 LOC)
    • 1 gitignore files (148 LOC)
    • 3 yaml files (122 LOC)
    • 1 bat files (68 LOC)
Other Code
Explore:   circles  |  sunburst

md83 LOC (100%) 5 files

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".
  • 5 files match defined criteria (83 LOC, 4.6% vs. main code). All matches are in md files.
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...
  • *.cljc files are analyzed with ClojureLangAnalyzer:
    • 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
  • *.clj files are analyzed with ClojureLangAnalyzer:
    • 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