Source Code Analysis Scope
Files includes and excluded from analyses
sass
babelrc

scoping details...
  • 11 extensions are included in analyses: js, scss, html, json, md, py, css, txt, sass, gitignore, babelrc
  • 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 ".*/docs/.*" (Documentation) (4 files).
    • 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.
main5398 LOC (92%) 76 files
test0 LOC (0%) 0 files
generated3 LOC (<1%) 1 file
build and deployment63 LOC (1%) 2 files
other344 LOC (5%) 11 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
sass
Explore:   circles  |  sunburst

js2350 LOC (43%) 27 files
scss2334 LOC (43%) 30 files
html375 LOC (6%) 12 files
py201 LOC (3%) 5 files
sass138 LOC (2%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 76 files match defined criteria (5,398 LOC, 100.0% vs. main code):
    • 27 js files (2,350 LOC)
    • 30 scss files (2,334 LOC)
    • 12 html files (375 LOC)
    • 5 py files (201 LOC)
    • 2 sass files (138 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst

json3 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 (3 LOC, 0.1% vs. main code). All matches are in json files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
babelrc
Explore:   circles  |  sunburst

babelrc62 LOC (98%) 1 file
gitignore1 LOC (1%) 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 ".*/package[-]lock[.]json".
    • files with paths like ".*/package[.]json".
    • files with paths like "(.*/)?[.]babelrc([.].*)?".
  • 2 files match defined criteria (63 LOC, 1.2% vs. main code):
    • 1 babelrc files (62 LOC)
    • 1 gitignore files (1 LOC)
Other Code
Explore:   circles  |  sunburst

md186 LOC (54%) 2 files
json158 LOC (45%) 9 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 11 files match defined criteria (344 LOC, 6.4% vs. main code):
    • 2 md files (186 LOC)
    • 9 json files (158 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
  • *.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
  • *.sass files are analyzed with SassAnalyzer:
    • 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