microsoft / mariadb-connector-j
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
creole
properties
txt
gitattributes
policy
  • 14 extensions are included in analyses: java, creole, yml, sh, xml, md, properties, sql, txt, gitignore, gitattributes, bat, json, policy
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (13 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.

main35766 LOC (53%) 208 files
test28872 LOC (42%) 106 files
generated0 LOC (0%) 0 files
build and deployment11 LOC (<1%) 1 files
other2774 LOC (4%) 19 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 ".*".
  • 208 files match defined criteria (35,766 lines of code, 100.0% vs. main code):
    • 205 *.java files (35,530 lines of code)
    • 3 *.yml files (236 lines of code)
  • " *.java" is biggest, containing 99.34% of code.
  • " *.yml" is smallest, containing 0.66% of code.


*.java35530 LOC (99%) 205 files
*.yml236 LOC (<1%) 3 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 ".*/[Tt]est/.*".
    • files with paths like ".*[-]test[-].*".
    • files with any line of content like ".*/simpletest/.*".
  • 106 files match defined criteria (28,872 lines of code, 80.7% vs. main code). All matches are in *.java files.


*.java28872 LOC (100%) 106 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 ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*/docker[-]compose[.]yml".
    • files with paths like ".*[.]bat".
    • files with paths like ".*/build[.]xml".
    • files with paths like ".*/pom[.]xml".
  • 1 file matches defined criteria (11 lines of code, 0.0% vs. main code). All matches are in *.bat files.


*.bat11 LOC (100%) 1 files
Other Code
creole
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[Dd]ocumentation/.*".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 19 files match defined criteria (2,774 lines of code, 7.8% vs. main code):
    • 3 *.md files (852 lines of code)
    • 7 *.creole files (848 lines of code)
    • 5 *.xml files (548 lines of code)
    • 1 *.sql files (445 lines of code)
    • 3 *.properties files (81 lines of code)
  • " *.md" is biggest, containing 30.71% of code.
  • " *.properties" is smallest, containing 2.92% of code.


*.md852 LOC (30%) 3 files
*.creole848 LOC (30%) 7 files
*.xml548 LOC (19%) 5 files
*.sql445 LOC (16%) 1 files
*.properties81 LOC (2%) 3 files
Analyzers
Info about analyzers used for source code examinations.
  • *.java files are analyzed with JavaAnalyzer:
    • 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 (based on package names)
  • *.yml 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


2022-01-30 23:54