Pyro
Source Code Overview

Source Code Analysis Scope
Files includes and excluded from analyses
  • 2 extensions are included in analyses: py, ipynb
  • 2 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (1 file).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (0 files).
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.

main39139 LOC (59%) 350 files
test26592 LOC (40%) 195 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other0 LOC (0%) 0 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 350 files match defined criteria (39,139 lines of code, 100.0% vs. main code):
    • 333 *.py files (30,584 lines of code)
    • 17 *.ipynb files (8,555 lines of code)
  • " *.py" is biggest, containing 78.14% of code.
  • " *.ipynb" is smallest, containing 21.86% of code.


*.py30584 LOC (78%) 333 files
*.ipynb8555 LOC (21%) 17 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
  • The following criteria are used to filter files:
    • files with paths like ".*/tests/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*_test[.].*".
  • 195 files match defined criteria (26,592 lines of code, 67.9% vs. main code). All matches are in *.py files.


*.py26592 LOC (100%) 195 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
  • *.ipynb 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

2020-09-11 20:40