Source Code Analysis Scope
Files includes and excluded from analyses
tpl
editorconfig
eslintignore
jshintrc

scoping details...
  • 11 extensions are included in analyses: js, scss, html, json, md, txt, gitignore, tpl, editorconfig, eslintignore, jshintrc
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (3 files).
    • 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.
main3719 LOC (23%) 56 files
test0 LOC (0%) 0 files
generated5968 LOC (37%) 1 file
build and deployment33 LOC (<1%) 4 files
other6070 LOC (38%) 6 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
tpl
Explore:   circles  |  sunburst

js1832 LOC (49%) 26 files
scss1582 LOC (42%) 24 files
html223 LOC (5%) 5 files
tpl82 LOC (2%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 56 files match defined criteria (3,719 LOC, 100.0% vs. main code):
    • 26 js files (1,832 LOC)
    • 24 scss files (1,582 LOC)
    • 5 html files (223 LOC)
    • 1 tpl files (82 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst

json5968 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/package[-]lock[.]json".
  • 1 file matches defined criteria (5,968 LOC, 160.5% vs. main code). All matches are in json files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
editorconfig
jshintrc
eslintignore
Explore:   circles  |  sunburst

gitignore11 LOC (33%) 1 file
editorconfig11 LOC (33%) 1 file
jshintrc10 LOC (30%) 1 file
eslintignore1 LOC (3%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like "(.*/)?[.]jshintrc".
    • 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 ".*/package[-]lock[.]json".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like "(.*/)?[.]eslintignore".
    • files with paths like "(.*/)?[.]eslintrc([.].*)?".
  • 4 files match defined criteria (33 LOC, 0.9% vs. main code):
    • 1 gitignore files (11 LOC)
    • 1 editorconfig files (11 LOC)
    • 1 jshintrc files (10 LOC)
    • 1 eslintignore files (1 LOC)
Other Code
Explore:   circles  |  sunburst

json6066 LOC (99%) 5 files
md4 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
  • 6 files match defined criteria (6,070 LOC, 163.2% vs. main code):
    • 5 json files (6,066 LOC)
    • 1 md files (4 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...
  • *.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
  • *.scss files are analyzed with ScssAnalyzer:
    • 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
  • *.html files are analyzed with HtmlAnalyzer:
    • 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
  • *.tpl 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