aws-solutions / maintaining-personalized-experiences-with-machine-learning
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
properties
ini
  • 11 extensions are included in analyses: py, txt, md, java, gradle, json, properties, ini, sh, gitignore, toml
  • 6 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 ".*/gradle/wrapper/.*" (Gradle) (2 files).
    • exclude files with path like ".*[.]txt" (Text files) (14 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.

main9104 LOC (65%) 188 files
test3718 LOC (26%) 60 files
generated0 LOC (0%) 0 files
build and deployment81 LOC (<1%) 3 files
other1007 LOC (7%) 11 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 ".*".
  • 188 files match defined criteria (9,104 lines of code, 100.0% vs. main code):
    • 185 *.py files (9,031 lines of code)
    • 3 *.java files (73 lines of code)
  • " *.py" is biggest, containing 99.2% of code.
  • " *.java" is smallest, containing 0.8% of code.


*.py9031 LOC (99%) 185 files
*.java73 LOC (<1%) 3 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 paths like ".*/[Tt]est/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 60 files match defined criteria (3,718 lines of code, 40.8% vs. main code):
    • 53 *.py files (3,576 lines of code)
    • 4 *.java files (88 lines of code)
    • 2 *.gradle files (42 lines of code)
    • 1 *.toml files (12 lines of code)
  • " *.py" is biggest, containing 96.18% of code.
  • " *.toml" is smallest, containing 0.32% of code.


*.py3576 LOC (96%) 53 files
*.java88 LOC (2%) 4 files
*.gradle42 LOC (1%) 2 files
*.toml12 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 ".*[.]gradle".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
  • 3 files match defined criteria (81 lines of code, 0.9% vs. main code):
    • 2 *.gradle files (50 lines of code)
    • 1 *.sh files (31 lines of code)
  • " *.gradle" is biggest, containing 61.73% of code.
  • " *.sh" is smallest, containing 38.27% of code.


*.gradle50 LOC (61%) 2 files
*.sh31 LOC (38%) 1 files
Other Code
ini
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 ".*[.]properties".
    • files with paths like ".*[.]ini".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
  • 11 files match defined criteria (1,007 lines of code, 11.1% vs. main code):
    • 8 *.md files (781 lines of code)
    • 2 *.json files (210 lines of code)
    • 1 *.ini files (16 lines of code)
  • " *.md" is biggest, containing 77.56% of code.
  • " *.ini" is smallest, containing 1.59% of code.


*.md781 LOC (77%) 8 files
*.json210 LOC (20%) 2 files
*.ini16 LOC (1%) 1 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
  • *.java files are analyzed with JavaAnalyzer:
    • 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
    • Advanced heuristic dependency analysis (based on package names)


2022-02-01 01:24