golang / text
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
cfg
gitattributes
  • 9 extensions are included in analyses: go, txt, json, xml, md, mod, cfg, gitignore, gitattributes
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*/testdata/.*" (Test data) (27 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) (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.

main543571 LOC (87%) 282 files
test72069 LOC (11%) 162 files
generated960 LOC (<1%) 6 files
build and deployment0 LOC (0%) 0 files
other1357 LOC (<1%) 20 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cfg
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 282 files match defined criteria (543,571 lines of code, 100.0% vs. main code):
    • 281 *.go files (543,570 lines of code)
    • 1 *.cfg files (1 lines of code)
  • " *.go" is biggest, containing 100% of code.
  • " *.cfg" is smallest, containing 0% of code.


*.go543570 LOC (99%) 281 files
*.cfg1 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 any line of content like ".*/simpletest/.*".
  • 162 files match defined criteria (72,069 lines of code, 13.3% vs. main code). All matches are in *.go files.


*.go72069 LOC (100%) 162 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/gen/.*[.]go".
  • 6 files match defined criteria (960 lines of code, 0.2% vs. main code). All matches are in *.go files.


*.go960 LOC (100%) 6 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 ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]json".
    • files with paths like ".*/go[.]mod".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 20 files match defined criteria (1,357 lines of code, 0.2% vs. main code):
    • 10 *.json files (1,051 lines of code)
    • 7 *.go files (215 lines of code)
    • 2 *.md files (83 lines of code)
    • 1 *.mod files (8 lines of code)
  • " *.json" is biggest, containing 77.45% of code.
  • " *.mod" is smallest, containing 0.59% of code.


*.json1051 LOC (77%) 10 files
*.go215 LOC (15%) 7 files
*.md83 LOC (6%) 2 files
*.mod8 LOC (<1%) 1 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
  • *.cfg files are analyzed with CfgAnalyzer:
    • 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


2022-02-03 01:44