tensorflow / fold
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
proto
txt
gitmodules
  • 12 extensions are included in analyses: py, h, cc, md, sh, proto, bzl, ipynb, inc, txt, json, gitmodules
  • 5 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) (1 file).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (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.

main11194 LOC (48%) 69 files
test4984 LOC (21%) 26 files
generated0 LOC (0%) 0 files
build and deployment185 LOC (<1%) 3 files
other6508 LOC (28%) 31 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
proto
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 69 files match defined criteria (11,194 lines of code, 100.0% vs. main code):
    • 21 *.py files (4,331 lines of code)
    • 14 *.cc files (3,215 lines of code)
    • 26 *.h files (3,166 lines of code)
    • 4 *.proto files (221 lines of code)
    • 2 *.bzl files (216 lines of code)
    • 2 *.inc files (45 lines of code)
  • " *.py" is biggest, containing 38.69% of code.
  • " *.inc" is smallest, containing 0.4% of code.


*.py4331 LOC (38%) 21 files
*.cc3215 LOC (28%) 14 files
*.h3166 LOC (28%) 26 files
*.proto221 LOC (1%) 4 files
*.bzl216 LOC (1%) 2 files
*.inc45 LOC (<1%) 2 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 ".*_test[.].*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 26 files match defined criteria (4,984 lines of code, 44.5% vs. main code):
    • 13 *.py files (3,037 lines of code)
    • 3 *.h files (1,438 lines of code)
    • 10 *.cc files (509 lines of code)
  • " *.py" is biggest, containing 60.93% of code.
  • " *.cc" is smallest, containing 10.21% of code.


*.py3037 LOC (60%) 13 files
*.h1438 LOC (28%) 3 files
*.cc509 LOC (10%) 10 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitmodules".
  • 3 files match defined criteria (185 lines of code, 1.7% vs. main code). All matches are in *.sh files.


*.sh185 LOC (100%) 3 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 31 files match defined criteria (6,508 lines of code, 58.1% vs. main code):
    • 14 *.md files (3,186 lines of code)
    • 2 *.ipynb files (1,997 lines of code)
    • 10 *.py files (983 lines of code)
    • 2 *.cc files (260 lines of code)
    • 1 *.h files (73 lines of code)
    • 2 *.sh files (9 lines of code)
  • " *.md" is biggest, containing 48.96% of code.
  • " *.sh" is smallest, containing 0.14% of code.


*.md3186 LOC (48%) 14 files
*.ipynb1997 LOC (30%) 2 files
*.py983 LOC (15%) 10 files
*.cc260 LOC (3%) 2 files
*.h73 LOC (1%) 1 files
*.sh9 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
  • *.cc files are analyzed with CppAnalyzer:
    • 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
  • *.h files are analyzed with CppAnalyzer:
    • 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
  • *.proto 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
  • *.bzl 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
  • *.inc files are analyzed with PhpAnalyzer:
    • 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


2022-02-03 07:59