Source Code Analysis Scope
Files includes and excluded from analyses
mdx
mjs
prettierignore

scoping details...
  • 14 extensions are included in analyses: json, ts, md, mdx, txt, yml, gitignore, js, yaml, css, svg, mjs, tsx, prettierignore
  • 8 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (15 files).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (3 files).
    • 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.
main329 LOC (4%) 5 files
test182 LOC (2%) 1 file
generated0 LOC (0%) 0 files
build and deployment6741 LOC (88%) 7 files
other387 LOC (5%) 12 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

ts203 LOC (61%) 3 files
tsx90 LOC (27%) 1 file
js36 LOC (10%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 5 files match defined criteria (329 LOC, 100.0% vs. main code):
    • 3 ts files (203 LOC)
    • 1 tsx files (90 LOC)
    • 1 js files (36 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

ts182 LOC (100%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
  • 1 file matches defined criteria (182 LOC, 55.3% vs. main code). All matches are in ts files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
prettierignore
Explore:   circles  |  sunburst

yaml6730 LOC (99%) 5 files
gitignore8 LOC (<1%) 1 file
prettierignore3 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/pnpm.*[.]ya?ml".
    • files with paths like ".*/[.]prettierignore".
    • files with paths like "(.*/)?[.]prettierignore".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[.]json".
    • files with paths like "(.*/)?[.](idea|vscode|vs|gradle|mvn|settings|metadata|circleci)/.*".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
  • 7 files match defined criteria (6,741 LOC, 2048.9% vs. main code):
    • 5 yaml files (6,730 LOC)
    • 1 gitignore files (8 LOC)
    • 1 prettierignore files (3 LOC)
Other Code
Explore:   circles  |  sunburst

md228 LOC (58%) 6 files
json159 LOC (41%) 6 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]mdx".
    • files with paths like ".*[.]txt".
  • 12 files match defined criteria (387 LOC, 117.6% vs. main code):
    • 6 md files (228 LOC)
    • 6 json files (159 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...
  • *.ts files are analyzed with TypeScriptAnalyzer:
    • 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
  • *.tsx files are analyzed with TypeScriptAnalyzer:
    • 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
  • *.js files are analyzed with JavaScriptAnalyzer:
    • 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