fbsamples / fblogin-sample
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
ejs
txt
pug
  • 9 extensions are included in analyses: json, js, md, ejs, svg, txt, css, pug, yaml
  • 4 criteria are used to exclude files from analysis:
    • 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 ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (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.

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

main2834 LOC (29%) 19 files
test0 LOC (0%) 0 files
generated2442 LOC (25%) 3 files
build and deployment0 LOC (0%) 0 files
other4228 LOC (44%) 32 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
ejs
pug
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 19 files match defined criteria (2,834 lines of code, 100.0% vs. main code):
    • 14 *.js files (1,803 lines of code)
    • 1 *.yaml files (872 lines of code)
    • 3 *.ejs files (117 lines of code)
    • 1 *.pug files (42 lines of code)
  • " *.js" is biggest, containing 63.62% of code.
  • " *.pug" is smallest, containing 1.48% of code.


*.js1803 LOC (63%) 14 files
*.yaml872 LOC (30%) 1 files
*.ejs117 LOC (4%) 3 files
*.pug42 LOC (1%) 1 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 ".*/npm[-]shrinkwrap[.]json".
    • files with paths like ".*/package[-]lock[.]json".
  • 3 files match defined criteria (2,442 lines of code, 86.2% vs. main code). All matches are in *.json files.


*.json2442 LOC (100%) 3 files
Other Code
Explore:   circles  |  sunburst
  • 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 ".*[.]json".
    • files with paths like ".*[.]txt".
  • 32 files match defined criteria (4,228 lines of code, 149.2% vs. main code):
    • 22 *.json files (3,768 lines of code)
    • 10 *.md files (460 lines of code)
  • " *.json" is biggest, containing 89.12% of code.
  • " *.md" is smallest, containing 10.88% of code.


*.json3768 LOC (89%) 22 files
*.md460 LOC (10%) 10 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.yaml 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
  • *.ejs files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.pug files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-01-26 09:36