Source Code Analysis Scope
Files includes and excluded from analyses
prettierignore

scoping details...
  • 14 extensions are included in analyses: jsx, js, json, ts, txt, css, svg, scss, html, gitignore, md, tsx, yml, prettierignore
  • 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 ".*/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 ".*\.d\.ts" (Typescript definition files) (3 files).
    • 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.
main12192 LOC (62%) 122 files
test128 LOC (<1%) 2 files
generated0 LOC (0%) 0 files
build and deployment56 LOC (<1%) 3 files
other7046 LOC (36%) 17 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

jsx7352 LOC (60%) 82 files
js4317 LOC (35%) 28 files
scss230 LOC (1%) 2 files
tsx153 LOC (1%) 1 file
css66 LOC (<1%) 2 files
ts49 LOC (<1%) 5 files
html25 LOC (<1%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 122 files match defined criteria (12,192 LOC, 100.0% vs. main code):
    • 82 jsx files (7,352 LOC)
    • 28 js files (4,317 LOC)
    • 2 scss files (230 LOC)
    • 1 tsx files (153 LOC)
    • 2 css files (66 LOC)
    • 5 ts files (49 LOC)
    • 2 html files (25 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

js128 LOC (100%) 2 files

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

yaml35 LOC (62%) 1 file
gitignore20 LOC (35%) 1 file
prettierignore1 LOC (1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[.]prettierignore".
    • files with paths like "(.*/)?[.]prettierignore".
    • files with paths like "(.*/)?[.]prettierrc([.].*)?".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
  • 3 files match defined criteria (56 LOC, 0.5% vs. main code):
    • 1 yaml files (35 LOC)
    • 1 gitignore files (20 LOC)
    • 1 prettierignore files (1 LOC)
Other Code
Explore:   circles  |  sunburst

json6961 LOC (98%) 14 files
svg52 LOC (<1%) 1 file
md30 LOC (<1%) 1 file
txt3 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".
    • files with paths like ".*[.]svg".
  • 17 files match defined criteria (7,046 LOC, 57.8% vs. main code):
    • 14 json files (6,961 LOC)
    • 1 svg files (52 LOC)
    • 1 md files (30 LOC)
    • 1 txt files (3 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...
  • *.jsx 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
  • *.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
  • *.tsx files are analyzed with TypeScriptAnalyzer:
    • 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
  • *.css files are analyzed with CssAnalyzer:
    • 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
  • *.ts files are analyzed with TypeScriptAnalyzer:
    • 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
  • *.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