awslabs / aws-emr-launch
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
in
ini
cfg
  • 16 extensions are included in analyses: py, sh, md, json, tf, hql, txt, gitignore, yaml, in, css, ini, cfg, toml, tfvars, yml
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (10 files).
    • exclude files with path like ".*/bin/.*" (Binaries for distribution) (1 file).
    • exclude files with path like ".*/docs/.*" (Documentation) (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) (0 files).
    • exclude files with path like ".*[.]txt" (Text files) (8 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.

main4712 LOC (44%) 58 files
test1516 LOC (14%) 21 files
generated0 LOC (0%) 0 files
build and deployment8 LOC (<1%) 2 files
other4442 LOC (41%) 123 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
in
cfg
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 58 files match defined criteria (4,712 lines of code, 100.0% vs. main code):
    • 51 *.py files (4,516 lines of code)
    • 3 *.yaml files (74 lines of code)
    • 2 *.in files (65 lines of code)
    • 1 *.toml files (31 lines of code)
    • 1 *.cfg files (26 lines of code)
  • " *.py" is biggest, containing 95.84% of code.
  • " *.cfg" is smallest, containing 0.55% of code.


*.py4516 LOC (95%) 51 files
*.yaml74 LOC (1%) 3 files
*.in65 LOC (1%) 2 files
*.toml31 LOC (<1%) 1 files
*.cfg26 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/.*".
  • 21 files match defined criteria (1,516 lines of code, 32.2% vs. main code). All matches are in *.py files.


*.py1516 LOC (100%) 21 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".
  • 2 files match defined criteria (8 lines of code, 0.2% vs. main code). All matches are in *.sh files.


*.sh8 LOC (100%) 2 files
Other Code
ini
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]ini".
  • 123 files match defined criteria (4,442 lines of code, 94.3% vs. main code):
    • 53 *.py files (2,400 lines of code)
    • 14 *.json files (704 lines of code)
    • 12 *.md files (633 lines of code)
    • 13 *.tf files (556 lines of code)
    • 17 *.sh files (62 lines of code)
    • 1 *.css files (32 lines of code)
    • 1 *.tfvars files (25 lines of code)
    • 1 *.ini files (19 lines of code)
    • 11 *.hql files (11 lines of code)
  • " *.py" is biggest, containing 54.03% of code.
  • " *.hql" is smallest, containing 0.25% of code.


*.py2400 LOC (54%) 53 files
*.json704 LOC (15%) 14 files
*.md633 LOC (14%) 12 files
*.tf556 LOC (12%) 13 files
*.sh62 LOC (1%) 17 files
*.css32 LOC (<1%) 1 files
*.tfvars25 LOC (<1%) 1 files
*.ini19 LOC (<1%) 1 files
*.hql11 LOC (<1%) 11 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.in files are analyzed with RustAnalyzer:
    • 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
  • *.toml 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
  • *.cfg files are analyzed with CfgAnalyzer:
    • 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 19:27