aws-samples / aws-iot-core-lorawan
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
  • 10 extensions are included in analyses: py, md, json, txt, js, yaml, sh, gitignore, yml, bat
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 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) (15 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.

main5823 LOC (66%) 64 files
test237 LOC (2%) 6 files
generated13 LOC (<1%) 1 files
build and deployment36 LOC (<1%) 6 files
other2612 LOC (29%) 34 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 ".*".
  • 64 files match defined criteria (5,823 lines of code, 100.0% vs. main code):
    • 47 *.py files (3,510 lines of code)
    • 9 *.yaml files (1,785 lines of code)
    • 7 *.js files (482 lines of code)
    • 1 *.yml files (46 lines of code)
  • " *.py" is biggest, containing 60.28% of code.
  • " *.yml" is smallest, containing 0.79% of code.


*.py3510 LOC (60%) 47 files
*.yaml1785 LOC (30%) 9 files
*.js482 LOC (8%) 7 files
*.yml46 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 ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 6 files match defined criteria (237 lines of code, 4.1% vs. main code):
    • 4 *.js files (234 lines of code)
    • 2 *.sh files (3 lines of code)
  • " *.js" is biggest, containing 98.73% of code.
  • " *.sh" is smallest, containing 1.27% of code.


*.js234 LOC (98%) 4 files
*.sh3 LOC (1%) 2 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 (13 lines of code, 0.2% vs. main code). All matches are in *.json files.


*.json13 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 ".*[.]bat".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*/package[-]lock[.]json".
  • 6 files match defined criteria (36 lines of code, 0.6% vs. main code):
    • 5 *.sh files (25 lines of code)
    • 1 *.bat files (11 lines of code)
  • " *.sh" is biggest, containing 69.44% of code.
  • " *.bat" is smallest, containing 30.56% of code.


*.sh25 LOC (69%) 5 files
*.bat11 LOC (30%) 1 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 ".*[.]txt".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
  • 34 files match defined criteria (2,612 lines of code, 44.9% vs. main code):
    • 18 *.md files (2,353 lines of code)
    • 16 *.json files (259 lines of code)
  • " *.md" is biggest, containing 90.08% of code.
  • " *.json" is smallest, containing 9.92% of code.


*.md2353 LOC (90%) 18 files
*.json259 LOC (9%) 16 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
  • *.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


2022-01-31 16:48