facebookincubator / fbc_owrt_feed
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
patch
lua
in
txt
  • 8 extensions are included in analyses: patch, md, lua, json, htm, in, txt, sh
  • 2 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).
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.

main162 LOC (3%) 4 files
test0 LOC (0%) 0 files
generated0 LOC (0%) 0 files
build and deployment1 LOC (<1%) 1 files
other4675 LOC (96%) 14 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
lua
in
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 4 files match defined criteria (162 lines of code, 100.0% vs. main code):
    • 2 *.lua files (114 lines of code)
    • 1 *.in files (35 lines of code)
    • 1 *.htm files (13 lines of code)
  • " *.lua" is biggest, containing 70.37% of code.
  • " *.htm" is smallest, containing 8.02% of code.


*.lua114 LOC (70%) 2 files
*.in35 LOC (21%) 1 files
*.htm13 LOC (8%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]sh".
  • 1 file matches defined criteria (1 lines of code, 0.6% vs. main code). All matches are in *.sh files.


*.sh1 LOC (100%) 1 files
Other Code
patch
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 ".*[.]patch".
    • files with paths like ".*[.]txt".
  • 14 files match defined criteria (4,675 lines of code, 2885.8% vs. main code):
    • 7 *.patch files (4,502 lines of code)
    • 5 *.md files (93 lines of code)
    • 2 *.json files (80 lines of code)
  • " *.patch" is biggest, containing 96.3% of code.
  • " *.json" is smallest, containing 1.71% of code.


*.patch4502 LOC (96%) 7 files
*.md93 LOC (1%) 5 files
*.json80 LOC (1%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.lua files are analyzed with LuaAnalyzer:
    • 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
  • *.in 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
  • *.htm 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


2022-04-15 05:05