azure / webhook-tls-manager
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
s
txt
editorconfig
gitattributes
mod
cfg
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.

main1267 LOC (30%) 21 files
test1425 LOC (33%) 14 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other1531 LOC (36%) 14 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 ".*".
  • 21 files match defined criteria (1,267 LOC, 100.0% vs. main code). All matches are in *.go files.


*.go1267 LOC (100%) 21 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 ".*/mock[a-zA-Z0-9_\- ]+/.*".
    • files with paths like ".*/[Mm]ocks/.*".
    • files with paths like ".*/test[.].*".
  • 14 files match defined criteria (1,425 LOC, 112.5% vs. main code). All matches are in *.go files.


*.go1425 LOC (100%) 14 files
Other Code
mod
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/vendor/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*[.]editorconfig".
    • files with paths like ".*[.]json".
    • files with paths like ".*/go[.]mod".
  • 14 files match defined criteria (1,531 LOC, 120.8% vs. main code):
    • 9 *.yaml files (1,367 LOC)
    • 4 *.md files (84 LOC)
    • 1 *.mod files (80 LOC)
  • " *.yaml" is biggest, containing 89.29% of LOC.
  • " *.mod" is smallest, containing 5.23% of LOC.


*.yaml1367 LOC (89%) 9 files
*.md84 LOC (5%) 4 files
*.mod80 LOC (5%) 1 file
Analyzers
Info about analyzers used for source code examinations.

2025-05-06 23:03