Source Code Analysis Scope
Files includes and excluded from analyses
hbs

scoping details...
  • 9 extensions are included in analyses: rs, txt, yaml, md, sh, gitignore, hbs, json, toml
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
    • 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) (1 file).
    • exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
    • exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
    • exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (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.
main841 LOC (75%) 8 files
test0 LOC (0%) 0 files
generated0 LOC (0%) 0 files
build and deployment137 LOC (12%) 6 files
other143 LOC (12%) 3 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
hbs
Explore:   circles  |  sunburst

rs591 LOC (70%) 7 files
hbs250 LOC (29%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 8 files match defined criteria (841 LOC, 100.0% vs. main code):
    • 7 rs files (591 LOC)
    • 1 hbs files (250 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

yaml80 LOC (58%) 3 files
toml29 LOC (21%) 1 file
sh25 LOC (18%) 1 file
gitignore3 LOC (2%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/Cargo[.]toml".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like "(.*/)?[.](idea|vscode|vs|gradle|mvn|settings|metadata|circleci)/.*".
  • 6 files match defined criteria (137 LOC, 16.3% vs. main code):
    • 3 yaml files (80 LOC)
    • 1 toml files (29 LOC)
    • 1 sh files (25 LOC)
    • 1 gitignore files (3 LOC)
Other Code
Explore:   circles  |  sunburst

md135 LOC (94%) 2 files
json8 LOC (5%) 1 file

scope details...
  • 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 ".*[.]txt".
    • files with paths like ".*[.]json".
  • 3 files match defined criteria (143 LOC, 17.0% vs. main code):
    • 2 md files (135 LOC)
    • 1 json files (8 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.

learn more about used code analyzers...
  • *.rs files are analyzed with RustAnalyzer:
    • 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
  • *.hbs files are analyzed with HtmlAnalyzer:
    • 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