awslabs / aws-greengrass-labs-local-web-server
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
txt
dockerignore
  • 12 extensions are included in analyses: js, py, md, json, txt, css, gitignore, yaml, dockerignore, sh, xml, html
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (3 files).
    • 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) (0 files).
    • exclude files with path like ".*[.]txt" (Text files) (2 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
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.

  • 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.

main388 LOC (50%) 9 files
test81 LOC (10%) 5 files
generated0 LOC (0%) 0 files
build and deployment42 LOC (5%) 2 files
other264 LOC (34%) 7 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
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 9 files match defined criteria (388 lines of code, 100.0% vs. main code):
    • 4 *.js files (164 lines of code)
    • 1 *.py files (114 lines of code)
    • 1 *.yaml files (62 lines of code)
    • 2 *.css files (31 lines of code)
    • 1 *.html files (17 lines of code)
  • " *.js" is biggest, containing 42.27% of code.
  • " *.html" is smallest, containing 4.38% of code.


*.js164 LOC (42%) 4 files
*.py114 LOC (29%) 1 files
*.yaml62 LOC (15%) 1 files
*.css31 LOC (7%) 2 files
*.html17 LOC (4%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 5 files match defined criteria (81 lines of code, 20.9% vs. main code):
    • 4 *.py files (76 lines of code)
    • 1 *.js files (5 lines of code)
  • " *.py" is biggest, containing 93.83% of code.
  • " *.js" is smallest, containing 6.17% of code.


*.py76 LOC (93%) 4 files
*.js5 LOC (6%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/package[.]json".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/docker[-]compose[.]yaml".
    • files with paths like ".*[.]sh".
  • 2 files match defined criteria (42 lines of code, 10.8% vs. main code):
    • 1 *.yaml files (23 lines of code)
    • 1 *.sh files (19 lines of code)
  • " *.yaml" is biggest, containing 54.76% of code.
  • " *.sh" is smallest, containing 45.24% of code.


*.yaml23 LOC (54%) 1 files
*.sh19 LOC (45%) 1 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]dockerignore".
  • 7 files match defined criteria (264 lines of code, 68.0% vs. main code):
    • 4 *.md files (192 lines of code)
    • 3 *.json files (72 lines of code)
  • " *.md" is biggest, containing 72.73% of code.
  • " *.json" is smallest, containing 27.27% of code.


*.md192 LOC (72%) 4 files
*.json72 LOC (27%) 3 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.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
  • *.yaml files are analyzed with YamlAnalyzer:
    • 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
  • *.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
  • *.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


2022-01-31 22:41