awslabs / aws-htc-grid
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
tpl
dockerignore
gitmodules
  • 17 extensions are included in analyses: md, yaml, py, tf, html, txt, tpl, css, json, sh, js, yml, dockerignore, cpp, gitignore, toml, gitmodules
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (5 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (73 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) (13 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.

main9215 LOC (47%) 123 files
test410 LOC (2%) 3 files
generated0 LOC (0%) 0 files
build and deployment150 LOC (<1%) 5 files
other9581 LOC (49%) 32 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
tpl
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 123 files match defined criteria (9,215 lines of code, 100.0% vs. main code):
    • 41 *.tf files (3,470 lines of code)
    • 46 *.yaml files (2,816 lines of code)
    • 31 *.py files (2,602 lines of code)
    • 4 *.tpl files (288 lines of code)
    • 1 *.yml files (39 lines of code)
  • " *.tf" is biggest, containing 37.66% of code.
  • " *.yml" is smallest, containing 0.42% of code.


*.tf3470 LOC (37%) 41 files
*.yaml2816 LOC (30%) 46 files
*.py2602 LOC (28%) 31 files
*.tpl288 LOC (3%) 4 files
*.yml39 LOC (<1%) 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 any line of content like ".*/simpletest/.*".
  • 3 files match defined criteria (410 lines of code, 4.4% vs. main code):
    • 2 *.py files (355 lines of code)
    • 1 *.yaml files (55 lines of code)
  • " *.py" is biggest, containing 86.59% of code.
  • " *.yaml" is smallest, containing 13.41% of code.


*.py355 LOC (86%) 2 files
*.yaml55 LOC (13%) 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 ".*/docker[-]compose[.]yml".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitmodules".
    • files with paths like ".*[.]sh".
    • files with paths like ".*/[.]gitignore".
  • 5 files match defined criteria (150 lines of code, 1.6% vs. main code). All matches are in *.sh files.


*.sh150 LOC (100%) 5 files
Other Code
tpl
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 ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]dockerignore".
  • 32 files match defined criteria (9,581 lines of code, 104.0% vs. main code):
    • 5 *.json files (8,329 lines of code)
    • 9 *.py files (531 lines of code)
    • 8 *.tpl files (349 lines of code)
    • 9 *.md files (330 lines of code)
    • 1 *.cpp files (42 lines of code)
  • " *.json" is biggest, containing 86.93% of code.
  • " *.cpp" is smallest, containing 0.44% of code.


*.json8329 LOC (86%) 5 files
*.py531 LOC (5%) 9 files
*.tpl349 LOC (3%) 8 files
*.md330 LOC (3%) 9 files
*.cpp42 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.tf 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
  • *.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
  • *.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
  • *.tpl files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.yml 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


2022-01-31 22:38