Source Code Analysis Scope
Files includes and excluded from analyses
babelrc
jade
editorconfig
eslintignore

scoping details...
  • 11 extensions are included in analyses: less, js, vue, txt, babelrc, gitignore, jade, md, editorconfig, json, eslintignore
  • 7 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 ".*/normalize[.](css|less|scss|styl)" (Normalize css) (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.
main1491 LOC (81%) 23 files
test0 LOC (0%) 0 files
generated0 LOC (0%) 0 files
build and deployment203 LOC (11%) 6 files
other138 LOC (7%) 2 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
jade
Explore:   circles  |  sunburst

less903 LOC (60%) 15 files
js456 LOC (30%) 5 files
vue118 LOC (7%) 2 files
jade14 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 23 files match defined criteria (1,491 LOC, 100.0% vs. main code):
    • 15 less files (903 LOC)
    • 5 js files (456 LOC)
    • 2 vue files (118 LOC)
    • 1 jade files (14 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
babelrc
editorconfig
eslintignore
Explore:   circles  |  sunburst

js171 LOC (84%) 2 files
babelrc17 LOC (8%) 1 file
editorconfig9 LOC (4%) 1 file
gitignore4 LOC (1%) 1 file
eslintignore2 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like "(.*/)?[.]babelrc([.].*)?".
    • files with paths like ".*([.]|/)webpack([.]|/).*".
    • 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[.]json".
    • files with paths like "(.*/)?[.]eslintrc([.].*)?".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like "(.*/)?[.]eslintignore".
  • 6 files match defined criteria (203 LOC, 13.6% vs. main code):
    • 2 js files (171 LOC)
    • 1 babelrc files (17 LOC)
    • 1 editorconfig files (9 LOC)
    • 1 gitignore files (4 LOC)
    • 1 eslintignore files (2 LOC)
Other Code
Explore:   circles  |  sunburst

md74 LOC (53%) 1 file
json64 LOC (46%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]txt".
  • 2 files match defined criteria (138 LOC, 9.3% vs. main code):
    • 1 md files (74 LOC)
    • 1 json files (64 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...
  • *.less files are analyzed with LessAnalyzer:
    • 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
  • *.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
  • *.vue 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
  • *.jade 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