microsoft / docker
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
spec
vim
txt
dockerignore
plist
nanorc
fish
  • 17 extensions are included in analyses: go, md, sh, svg, json, c, Dockerfile, spec, vim, gitignore, txt, dockerignore, psm1, xml, plist, nanorc, fish
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (8 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (199 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) (1 file).
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.

main65090 LOC (48%) 700 files
test54847 LOC (40%) 287 files
generated0 LOC (0%) 0 files
build and deployment2745 LOC (2%) 27 files
other12327 LOC (9%) 119 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
fish
nanorc
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 700 files match defined criteria (65,090 lines of code, 100.0% vs. main code):
    • 693 *.go files (64,437 lines of code)
    • 1 *.fish files (356 lines of code)
    • 1 *.psm1 files (156 lines of code)
    • 4 *.c files (123 lines of code)
    • 1 *.nanorc files (18 lines of code)
  • " *.go" is biggest, containing 99% of code.
  • " *.nanorc" is smallest, containing 0.03% of code.


*.go64437 LOC (98%) 693 files
*.fish356 LOC (<1%) 1 files
*.psm1156 LOC (<1%) 1 files
*.c123 LOC (<1%) 4 files
*.nanorc18 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 any line of content like ".*/simpletest/.*".
  • 287 files match defined criteria (54,847 lines of code, 84.3% vs. main code). All matches are in *.go files.


*.go54847 LOC (100%) 287 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
  • 27 files match defined criteria (2,745 lines of code, 4.2% vs. main code). All matches are in *.sh files.


*.sh2745 LOC (100%) 27 files
Other Code
vim
plist
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]dockerignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]plist".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]vim".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*/[Mm]an/.*".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 119 files match defined criteria (12,327 lines of code, 18.9% vs. main code):
    • 106 *.md files (10,316 lines of code)
    • 8 *.json files (1,894 lines of code)
    • 1 *.xml files (62 lines of code)
    • 2 *.vim files (23 lines of code)
    • 1 *.plist files (16 lines of code)
    • 1 *.sh files (16 lines of code)
  • " *.md" is biggest, containing 83.69% of code.
  • " *.sh" is smallest, containing 0.13% of code.


*.md10316 LOC (83%) 106 files
*.json1894 LOC (15%) 8 files
*.xml62 LOC (<1%) 1 files
*.vim23 LOC (<1%) 2 files
*.plist16 LOC (<1%) 1 files
*.sh16 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
  • *.fish 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
  • *.psm1 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
  • *.c files are analyzed with CStyleAnalyzer:
    • 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
  • *.nanorc 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-01-30 09:29