kubernetes / cloud-provider-vsphere
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
mod
mk
dockerignore
tpl
proto
  • 14 extensions are included in analyses: go, yaml, md, sh, txt, gitignore, mod, yml, mk, dockerignore, toml, tpl, proto, json
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (12 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (18 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 ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (7 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.

main15727 LOC (60%) 175 files
test8815 LOC (33%) 55 files
generated0 LOC (0%) 0 files
build and deployment564 LOC (2%) 17 files
other853 LOC (3%) 13 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
proto
tpl
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 175 files match defined criteria (15,727 lines of code, 100.0% vs. main code):
    • 148 *.go files (13,405 lines of code)
    • 24 *.yaml files (2,200 lines of code)
    • 1 *.proto files (51 lines of code)
    • 1 *.tpl files (50 lines of code)
    • 1 *.toml files (21 lines of code)
  • " *.go" is biggest, containing 85.24% of code.
  • " *.toml" is smallest, containing 0.13% of code.


*.go13405 LOC (85%) 148 files
*.yaml2200 LOC (13%) 24 files
*.proto51 LOC (<1%) 1 files
*.tpl50 LOC (<1%) 1 files
*.toml21 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 ".*[-]test[-].*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/e2e/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 55 files match defined criteria (8,815 lines of code, 56.1% vs. main code):
    • 47 *.go files (8,535 lines of code)
    • 4 *.yaml files (231 lines of code)
    • 4 *.sh files (49 lines of code)
  • " *.go" is biggest, containing 96.82% of code.
  • " *.sh" is smallest, containing 0.56% of code.


*.go8535 LOC (96%) 47 files
*.yaml231 LOC (2%) 4 files
*.sh49 LOC (<1%) 4 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
mk
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 ".*/[.]gitignore".
    • files with paths like ".*[.]mk".
  • 17 files match defined criteria (564 lines of code, 3.6% vs. main code):
    • 15 *.sh files (505 lines of code)
    • 2 *.mk files (59 lines of code)
  • " *.sh" is biggest, containing 89.54% of code.
  • " *.mk" is smallest, containing 10.46% of code.


*.sh505 LOC (89%) 15 files
*.mk59 LOC (10%) 2 files
Other Code
mod
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 ".*[.]json".
    • files with paths like ".*/go[.]mod".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]dockerignore".
    • files with paths like ".*[.]txt".
  • 13 files match defined criteria (853 lines of code, 5.4% vs. main code):
    • 11 *.md files (685 lines of code)
    • 2 *.mod files (168 lines of code)
  • " *.md" is biggest, containing 80.3% of code.
  • " *.mod" is smallest, containing 19.7% of code.


*.md685 LOC (80%) 11 files
*.mod168 LOC (19%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.go files are analyzed with GoLangAnalyzer:
    • 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
  • *.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
  • *.tpl 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
  • *.toml 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


2022-02-03 09:21