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

scoping details...
  • 11 extensions are included in analyses: html, xsd, json, js, scss, xml, txt, svg, gitignore, babelrc, md
  • 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 ".*/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.
main7106 LOC (87%) 34 files
test0 LOC (0%) 0 files
generated0 LOC (0%) 0 files
build and deployment34 LOC (<1%) 3 files
other997 LOC (12%) 10 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
xsd
Explore:   circles  |  sunburst

xsd3104 LOC (43%) 11 files
xml2026 LOC (28%) 5 files
html906 LOC (12%) 7 files
js686 LOC (9%) 6 files
scss384 LOC (5%) 5 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 34 files match defined criteria (7,106 LOC, 100.0% vs. main code):
    • 11 xsd files (3,104 LOC)
    • 5 xml files (2,026 LOC)
    • 7 html files (906 LOC)
    • 6 js files (686 LOC)
    • 5 scss files (384 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
babelrc
Explore:   circles  |  sunburst

babelrc26 LOC (76%) 1 file
gitignore8 LOC (23%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like "(.*/)?[.]babelrc([.].*)?".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[.]json".
  • 3 files match defined criteria (34 LOC, 0.5% vs. main code):
    • 1 babelrc files (26 LOC)
    • 2 gitignore files (8 LOC)
Other Code
Explore:   circles  |  sunburst

svg617 LOC (61%) 2 files
json203 LOC (20%) 5 files
md94 LOC (9%) 1 file
txt83 LOC (8%) 2 files

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".
  • 10 files match defined criteria (997 LOC, 14.0% vs. main code):
    • 2 svg files (617 LOC)
    • 5 json files (203 LOC)
    • 1 md files (94 LOC)
    • 2 txt files (83 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...
  • *.xsd files are analyzed with XmlAnalyzer:
    • 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
  • *.xml files are analyzed with XmlAnalyzer:
    • 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
  • *.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