azure / azure-schema-registry-for-kafka
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
properties
csproj
gitattributes
txt
cmd
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.

main2193 LOC (37%) 24 files
test447 LOC (7%) 12 files
generated93 LOC (1%) 1 file
build and deployment341 LOC (5%) 6 files
other2736 LOC (47%) 51 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 ".*".
  • 24 files match defined criteria (2,193 LOC, 100.0% vs. main code):
    • 18 *.java files (1,886 LOC)
    • 6 *.cs files (307 LOC)
  • " *.java" is biggest, containing 86% of LOC.
  • " *.cs" is smallest, containing 14% of LOC.


*.java1886 LOC (86%) 18 files
*.cs307 LOC (13%) 6 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 ".*_tests[.].*".
  • 12 files match defined criteria (447 LOC, 20.4% vs. main code):
    • 10 *.java files (443 LOC)
    • 2 *.sh files (4 LOC)
  • " *.java" is biggest, containing 99.11% of LOC.
  • " *.sh" is smallest, containing 0.89% of LOC.


*.java443 LOC (99%) 10 files
*.sh4 LOC (<1%) 2 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with any line of content like "//[ ]*Generated by .*".
    • files with paths like ".*[.]cs" AND any line of content like "[/][/][ ]*".
  • 1 file matches defined criteria (93 LOC, 4.2% vs. main code). All matches are in *.cs files.


*.cs93 LOC (100%) 1 file
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/pom[.]xml".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]csproj".
  • 6 files match defined criteria (341 LOC, 15.5% vs. main code):
    • 4 *.xml files (315 LOC)
    • 2 *.csproj files (26 LOC)
  • " *.xml" is biggest, containing 92.38% of LOC.
  • " *.csproj" is smallest, containing 7.62% of LOC.


*.xml315 LOC (92%) 4 files
*.csproj26 LOC (7%) 2 files
Other Code
properties
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/checkstyle[.]xml".
    • files with paths like ".*/checkstyle.*".
    • files with paths like ".*/[Ss]amples/.*".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
  • 51 files match defined criteria (2,736 LOC, 124.8% vs. main code):
    • 23 *.java files (1,462 LOC)
    • 6 *.xml files (555 LOC)
    • 6 *.cs files (357 LOC)
    • 6 *.md files (201 LOC)
    • 5 *.properties files (72 LOC)
    • 3 *.avsc files (50 LOC)
    • 2 *.csproj files (39 LOC)
  • " *.java" is biggest, containing 53.44% of LOC.
  • " *.csproj" is smallest, containing 1.43% of LOC.


*.java1462 LOC (53%) 23 files
*.xml555 LOC (20%) 6 files
*.cs357 LOC (13%) 6 files
*.md201 LOC (7%) 6 files
*.properties72 LOC (2%) 5 files
*.avsc50 LOC (1%) 3 files
*.csproj39 LOC (1%) 2 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)
  • *.cs files are analyzed with CSharpAnalyzer:
    • 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 namespace heuristics)


2025-05-06 22:02