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

scoping details...
  • 12 extensions are included in analyses: json, html, scss, js, py, babelrc, gitignore, kml, geojson, xml, md, sass
  • 4 criteria are used to exclude files from analysis:
    • 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 ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (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.
main1710 LOC (28%) 26 files
test0 LOC (0%) 0 files
generated1417 LOC (23%) 1 file
build and deployment37 LOC (<1%) 3 files
other2833 LOC (47%) 13 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
sass
geojson
kml
Explore:   circles  |  sunburst

js786 LOC (45%) 8 files
scss576 LOC (33%) 10 files
py160 LOC (9%) 3 files
html126 LOC (7%) 2 files
sass60 LOC (3%) 1 file
geojson1 LOC (<1%) 1 file
kml1 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 26 files match defined criteria (1,710 LOC, 100.0% vs. main code):
    • 8 js files (786 LOC)
    • 10 scss files (576 LOC)
    • 3 py files (160 LOC)
    • 2 html files (126 LOC)
    • 1 sass files (60 LOC)
    • 1 geojson files (1 LOC)
    • 1 kml files (1 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst

json1417 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 (1,417 LOC, 82.9% 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

babelrc26 LOC (70%) 1 file
gitignore11 LOC (29%) 2 files

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

json2760 LOC (97%) 12 files
md73 LOC (2%) 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]+".
  • 13 files match defined criteria (2,833 LOC, 165.7% vs. main code):
    • 12 json files (2,760 LOC)
    • 1 md files (73 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
  • *.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
  • *.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
  • *.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
  • *.geojson files are analyzed with JsonAnalyzer:
    • 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
  • *.kml 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