pytorch / opacus
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
in
ini
ps1
  • 16 extensions are included in analyses: py, rst, md, svg, js, ipynb, css, sh, txt, json, yml, in, ini, gitignore, ps1, bat
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (2 files).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (10 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) (3 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.

main5464 LOC (41%) 69 files
test3252 LOC (24%) 38 files
generated0 LOC (0%) 0 files
build and deployment160 LOC (1%) 4 files
other4358 LOC (32%) 58 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
ps1
in
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 69 files match defined criteria (5,464 lines of code, 100.0% vs. main code):
    • 56 *.py files (3,462 lines of code)
    • 5 *.css files (1,413 lines of code)
    • 6 *.js files (567 lines of code)
    • 1 *.ps1 files (20 lines of code)
    • 1 *.in files (2 lines of code)
  • " *.py" is biggest, containing 63.36% of code.
  • " *.in" is smallest, containing 0.04% of code.


*.py3462 LOC (63%) 56 files
*.css1413 LOC (25%) 5 files
*.js567 LOC (10%) 6 files
*.ps120 LOC (<1%) 1 files
*.in2 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 ".*_test[.].*".
  • 38 files match defined criteria (3,252 lines of code, 59.5% vs. main code). All matches are in *.py files.


*.py3252 LOC (100%) 38 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 ".*/package[.]json".
    • files with paths like ".*[.]bat".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
  • 4 files match defined criteria (160 lines of code, 2.9% vs. main code):
    • 3 *.sh files (133 lines of code)
    • 1 *.bat files (27 lines of code)
  • " *.sh" is biggest, containing 83.12% of code.
  • " *.bat" is smallest, containing 16.88% of code.


*.sh133 LOC (83%) 3 files
*.bat27 LOC (16%) 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 ".*[.]svg".
    • files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]ini".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 58 files match defined criteria (4,358 lines of code, 79.8% vs. main code):
    • 8 *.py files (1,948 lines of code)
    • 3 *.ipynb files (1,446 lines of code)
    • 12 *.md files (631 lines of code)
    • 28 *.rst files (150 lines of code)
    • 2 *.sh files (107 lines of code)
    • 3 *.json files (62 lines of code)
    • 2 *.svg files (14 lines of code)
  • " *.py" is biggest, containing 44.7% of code.
  • " *.svg" is smallest, containing 0.32% of code.


*.py1948 LOC (44%) 8 files
*.ipynb1446 LOC (33%) 3 files
*.md631 LOC (14%) 12 files
*.rst150 LOC (3%) 28 files
*.sh107 LOC (2%) 2 files
*.json62 LOC (1%) 3 files
*.svg14 LOC (<1%) 2 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
  • *.css files are analyzed with CssAnalyzer:
    • 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
  • *.ps1 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
  • *.in files are analyzed with RustAnalyzer:
    • 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-24 14:34