aws-samples / aws-microservices-deploy-options
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
libsonnet
txt
tpl
adoc
  • 12 extensions are included in analyses: yaml, json, yml, md, libsonnet, jsonnet, sh, gitignore, js, txt, tpl, adoc
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 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) (1 file).
    • 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.

main5570 LOC (83%) 60 files
test0 LOC (0%) 0 files
generated0 LOC (0%) 0 files
build and deployment48 LOC (<1%) 4 files
other1047 LOC (15%) 20 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
adoc
tpl
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 60 files match defined criteria (5,570 lines of code, 100.0% vs. main code):
    • 46 *.yaml files (4,391 lines of code)
    • 1 *.adoc files (755 lines of code)
    • 7 *.yml files (279 lines of code)
    • 3 *.jsonnet files (80 lines of code)
    • 2 *.js files (56 lines of code)
    • 1 *.tpl files (9 lines of code)
  • " *.yaml" is biggest, containing 78.83% of code.
  • " *.tpl" is smallest, containing 0.16% of code.


*.yaml4391 LOC (78%) 46 files
*.adoc755 LOC (13%) 1 files
*.yml279 LOC (5%) 7 files
*.jsonnet80 LOC (1%) 3 files
*.js56 LOC (1%) 2 files
*.tpl9 LOC (<1%) 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 ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/docker[-]compose[.]yaml".
  • 4 files match defined criteria (48 lines of code, 0.9% vs. main code):
    • 3 *.sh files (24 lines of code)
    • 1 *.yaml files (24 lines of code)
  • " *.sh" is biggest, containing 50% of code.
  • " *.yaml" is smallest, containing 50% of code.


*.sh24 LOC (50%) 3 files
*.yaml24 LOC (50%) 1 files
Other Code
libsonnet
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]libsonnet".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 20 files match defined criteria (1,047 lines of code, 18.8% vs. main code):
    • 4 *.md files (546 lines of code)
    • 13 *.json files (394 lines of code)
    • 3 *.libsonnet files (107 lines of code)
  • " *.md" is biggest, containing 52.15% of code.
  • " *.libsonnet" is smallest, containing 10.22% of code.


*.md546 LOC (52%) 4 files
*.json394 LOC (37%) 13 files
*.libsonnet107 LOC (10%) 3 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.adoc 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
  • *.jsonnet 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
  • *.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
  • *.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


2022-01-31 15:42