microsoft / lsif-node
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
txt
eslintignore
npmignore
  • 9 extensions are included in analyses: json, ts, txt, js, eslintignore, npmignore, md, yml, gitignore
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (41 files).
    • exclude files with path like ".*/bin/.*" (Binaries for distribution) (5 files).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (2 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) (4 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.

  • 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.

main11983 LOC (34%) 49 files
test1979 LOC (5%) 7 files
generated9814 LOC (28%) 10 files
build and deployment0 LOC (0%) 0 files
other10844 LOC (31%) 94 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 ".*".
  • 49 files match defined criteria (11,983 lines of code, 100.0% vs. main code):
    • 44 *.ts files (11,869 lines of code)
    • 5 *.yml files (114 lines of code)
  • " *.ts" is biggest, containing 99.05% of code.
  • " *.yml" is smallest, containing 0.95% of code.


*.ts11869 LOC (99%) 44 files
*.yml114 LOC (<1%) 5 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 ".*[-]tests/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 7 files match defined criteria (1,979 lines of code, 16.5% vs. main code). All matches are in *.ts files.


*.ts1979 LOC (100%) 7 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/package[-]lock[.]json".
  • 10 files match defined criteria (9,814 lines of code, 81.9% vs. main code). All matches are in *.json files.


*.json9814 LOC (100%) 10 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]npmignore".
    • files with paths like ".*/[Ss]amples/.*".
  • 94 files match defined criteria (10,844 lines of code, 90.5% vs. main code):
    • 77 *.json files (10,707 lines of code)
    • 5 *.md files (100 lines of code)
    • 10 *.ts files (32 lines of code)
    • 2 *.js files (5 lines of code)
  • " *.json" is biggest, containing 98.74% of code.
  • " *.js" is smallest, containing 0.05% of code.


*.json10707 LOC (98%) 77 files
*.md100 LOC (<1%) 5 files
*.ts32 LOC (<1%) 10 files
*.js5 LOC (<1%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.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 22:30