aws-samples / amazon-documentdb-samples
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
npmignore
  • 14 extensions are included in analyses: md, sh, json, js, yml, py, java, txt, ts, npmignore, gitignore, rb, xml, php
  • 6 criteria are used to exclude files from analysis:
    • 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 ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*/bin/.*" (Binaries for distribution) (1 file).
    • 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.

main976 LOC (<1%) 8 files
test0 LOC (0%) 0 files
generated2656 LOC (<1%) 1 files
build and deployment188 LOC (<1%) 9 files
other327419 LOC (98%) 40 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 ".*".
  • 8 files match defined criteria (976 lines of code, 100.0% vs. main code):
    • 6 *.js files (484 lines of code)
    • 1 *.yml files (295 lines of code)
    • 1 *.ts files (197 lines of code)
  • " *.js" is biggest, containing 49.59% of code.
  • " *.ts" is smallest, containing 20.18% of code.


*.js484 LOC (49%) 6 files
*.yml295 LOC (30%) 1 files
*.ts197 LOC (20%) 1 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/package[-]lock[.]json".
  • 1 file matches defined criteria (2,656 lines of code, 272.1% vs. main code). All matches are in *.json files.


*.json2656 LOC (100%) 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 ".*/docker[-]compose[.]yml".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[-]lock[.]json".
    • files with paths like ".*/pom[.]xml".
  • 9 files match defined criteria (188 lines of code, 19.3% vs. main code):
    • 8 *.sh files (126 lines of code)
    • 1 *.yml files (62 lines of code)
  • " *.sh" is biggest, containing 67.02% of code.
  • " *.yml" is smallest, containing 32.98% of code.


*.sh126 LOC (67%) 8 files
*.yml62 LOC (32%) 1 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]npmignore".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[Ss]amples/.*".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 40 files match defined criteria (327,419 lines of code, 33547.0% vs. main code):
    • 7 *.json files (324,827 lines of code)
    • 3 *.yml files (1,006 lines of code)
    • 4 *.py files (503 lines of code)
    • 16 *.md files (452 lines of code)
    • 3 *.java files (287 lines of code)
    • 3 *.sh files (203 lines of code)
    • 1 *.xml files (43 lines of code)
    • 1 *.rb files (38 lines of code)
    • 1 *.js files (35 lines of code)
    • 1 *.php files (25 lines of code)
  • " *.json" is biggest, containing 99.21% of code.
  • " *.php" is smallest, containing 0.01% of code.


*.json324827 LOC (99%) 7 files
*.yml1006 LOC (<1%) 3 files
*.py503 LOC (<1%) 4 files
*.md452 LOC (<1%) 16 files
*.java287 LOC (<1%) 3 files
*.sh203 LOC (<1%) 3 files
*.xml43 LOC (<1%) 1 files
*.rb38 LOC (<1%) 1 files
*.js35 LOC (<1%) 1 files
*.php25 LOC (<1%) 1 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
  • *.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
  • *.ts files are analyzed with TypeScriptAnalyzer:
    • 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


2022-01-31 16:28