aws / aws-codedeploy-agent
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
feature
txt
  • 11 extensions are included in analyses: rb, bat, sh, yml, md, feature, json, gitignore, txt, gemspec, yaml
  • 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) (0 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.

main5384 LOC (39%) 58 files
test5988 LOC (43%) 26 files
generated0 LOC (0%) 0 files
build and deployment57 LOC (<1%) 38 files
other2224 LOC (16%) 4 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 ".*".
  • 58 files match defined criteria (5,384 lines of code, 100.0% vs. main code):
    • 49 *.rb files (5,219 lines of code)
    • 7 *.yml files (118 lines of code)
    • 1 *.gemspec files (26 lines of code)
    • 1 *.yaml files (21 lines of code)
  • " *.rb" is biggest, containing 96.94% of code.
  • " *.yaml" is smallest, containing 0.39% of code.


*.rb5219 LOC (96%) 49 files
*.yml118 LOC (2%) 7 files
*.gemspec26 LOC (<1%) 1 files
*.yaml21 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
feature
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*[.]feature".
    • files with any line of content like ".*/simpletest/.*".
  • 26 files match defined criteria (5,988 lines of code, 111.2% vs. main code):
    • 24 *.rb files (5,874 lines of code)
    • 2 *.feature files (114 lines of code)
  • " *.rb" is biggest, containing 98.1% of code.
  • " *.feature" is smallest, containing 1.9% of code.


*.rb5874 LOC (98%) 24 files
*.feature114 LOC (1%) 2 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]bat".
  • 38 files match defined criteria (57 lines of code, 1.1% vs. main code):
    • 19 *.sh files (38 lines of code)
    • 19 *.bat files (19 lines of code)
  • " *.sh" is biggest, containing 66.67% of code.
  • " *.bat" is smallest, containing 33.33% of code.


*.sh38 LOC (66%) 19 files
*.bat19 LOC (33%) 19 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".
  • 4 files match defined criteria (2,224 lines of code, 41.3% vs. main code):
    • 1 *.json files (2,144 lines of code)
    • 3 *.md files (80 lines of code)
  • " *.json" is biggest, containing 96.4% of code.
  • " *.md" is smallest, containing 3.6% of code.


*.json2144 LOC (96%) 1 files
*.md80 LOC (3%) 3 files
Analyzers
Info about analyzers used for source code examinations.
  • *.rb files are analyzed with RubyAnalyzer:
    • 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
    • Basic heuristic 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
  • *.gemspec files are analyzed with RubyAnalyzer:
    • 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
    • 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


2022-01-30 22:22