Netflix/metaflow
Code Volume
Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
rd
svelte
rmd
cfg
in
ini
eslintignore

scoping details...
  • 23 extensions are included in analyses: py, r, rd, md, json, svelte, sh, txt, yml, ts, rmd, yaml, css, js, ipynb, html, cfg, in, ini, gitignore, cjs, svg, eslintignore
  • 8 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (4 files).
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (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.
main86890 LOC (68%) 480 files
test21423 LOC (16%) 302 files
generated6942 LOC (5%) 2 files
build and deployment1462 LOC (1%) 24 files
other10983 LOC (8%) 83 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
svelte
in
Explore:   circles  |  sunburst

py82255 LOC (94%) 415 files
svelte2681 LOC (3%) 34 files
ipynb634 LOC (<1%) 6 files
ts599 LOC (<1%) 8 files
html312 LOC (<1%) 1 file
yaml244 LOC (<1%) 6 files
css144 LOC (<1%) 3 files
in10 LOC (<1%) 2 files
js7 LOC (<1%) 4 files
cjs4 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 480 files match defined criteria (86,890 LOC, 100.0% vs. main code):
    • 415 py files (82,255 LOC)
    • 34 svelte files (2,681 LOC)
    • 6 ipynb files (634 LOC)
    • 8 ts files (599 LOC)
    • 1 html files (312 LOC)
    • 6 yaml files (244 LOC)
    • 3 css files (144 LOC)
    • 2 in files (10 LOC)
    • 4 js files (7 LOC)
    • 1 cjs files (4 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
cfg
Explore:   circles  |  sunburst

py20305 LOC (94%) 295 files
yaml1110 LOC (5%) 5 files
cfg5 LOC (<1%) 1 file
sh3 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*_tests[.].*".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/test[.].*".
    • files with paths like ".*[-]tests/.*".
    • files with paths like ".*/testing[.].*".
  • 302 files match defined criteria (21,423 LOC, 24.7% vs. main code):
    • 295 py files (20,305 LOC)
    • 5 yaml files (1,110 LOC)
    • 1 cfg files (5 LOC)
    • 1 sh files (3 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst

json6740 LOC (97%) 1 file
html202 LOC (2%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.](html|htm|xhtml)" AND any line of content like "[ ]*[<]meta name[=]"generator" .*".
    • files with paths like ".*/package[-]lock[.]json".
  • 2 files match defined criteria (6,942 LOC, 8.0% vs. main code):
    • 1 json files (6,740 LOC)
    • 1 html files (202 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
cfg
eslintignore
Explore:   circles  |  sunburst

yaml595 LOC (40%) 6 files
gitignore497 LOC (33%) 2 files
sh223 LOC (15%) 11 files
py111 LOC (7%) 2 files
cjs33 LOC (2%) 1 file
cfg2 LOC (<1%) 1 file
eslintignore1 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/setup[.]cfg".
    • files with paths like ".*/setup[.]py".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/requirements[a-zA-Z0-9._-]*[.]txt".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*/[.]github/actions/.*[.]ya?ml".
    • files with paths like ".*/action[.]ya?ml".
    • files with paths like "(.*/)?[.]eslintrc([.].*)?".
    • files with paths like ".*/package[-]lock[.]json".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like "(.*/)?[.]eslintignore".
  • 24 files match defined criteria (1,462 LOC, 1.7% vs. main code):
    • 6 yaml files (595 LOC)
    • 2 gitignore files (497 LOC)
    • 11 sh files (223 LOC)
    • 2 py files (111 LOC)
    • 1 cjs files (33 LOC)
    • 1 cfg files (2 LOC)
    • 1 eslintignore files (1 LOC)
Other Code
ini
Explore:   circles  |  sunburst

json9237 LOC (84%) 36 files
md1630 LOC (14%) 36 files
txt45 LOC (<1%) 8 files
ini38 LOC (<1%) 2 files
html33 LOC (<1%) 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 ".*[.]json".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]ini".
    • files with paths like ".*/[Dd]emos?/.*".
  • 83 files match defined criteria (10,983 LOC, 12.6% vs. main code):
    • 36 json files (9,237 LOC)
    • 36 md files (1,630 LOC)
    • 8 txt files (45 LOC)
    • 2 ini files (38 LOC)
    • 1 html files (33 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...
  • *.py files are analyzed with PythonAnalyzer:
    • 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
    • Basic heuristic dependency analysis
  • *.svelte 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
  • *.ipynb 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
  • *.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
  • *.html 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
  • *.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
  • *.css files are analyzed with CssAnalyzer:
    • 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
  • *.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
  • *.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
  • *.cjs 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