Netflix/vmaf
Code Volume
Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
pkl
mat
in
ini
gitmodules
gitattributes

scoping details...
  • 24 extensions are included in analyses: py, c, m, h, json, pkl, md, gitignore, txt, cu, yml, mat, in, ini, cuh, asm, dockerignore, pyx, cpp, gitmodules, gitattributes, rst, sh, toml
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (5 files).
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (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.
main81725 LOC (75%) 466 files
test24411 LOC (22%) 127 files
generated0 LOC (0%) 0 files
build and deployment577 LOC (<1%) 22 files
other2002 LOC (1%) 34 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
pkl
in
mat
Explore:   circles  |  sunburst

c37075 LOC (45%) 103 files
py25336 LOC (31%) 88 files
m7411 LOC (9%) 133 files
h3663 LOC (4%) 101 files
cpp2677 LOC (3%) 1 file
pkl1841 LOC (2%) 21 files
asm1772 LOC (2%) 2 files
cu1594 LOC (1%) 7 files
cuh209 LOC (<1%) 2 files
pyx90 LOC (<1%) 1 file
in41 LOC (<1%) 3 files
mat10 LOC (<1%) 3 files
yaml6 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 466 files match defined criteria (81,725 LOC, 100.0% vs. main code):
    • 103 c files (37,075 LOC)
    • 88 py files (25,336 LOC)
    • 133 m files (7,411 LOC)
    • 101 h files (3,663 LOC)
    • 1 cpp files (2,677 LOC)
    • 21 pkl files (1,841 LOC)
    • 2 asm files (1,772 LOC)
    • 7 cu files (1,594 LOC)
    • 2 cuh files (209 LOC)
    • 1 pyx files (90 LOC)
    • 3 in files (41 LOC)
    • 3 mat files (10 LOC)
    • 1 yaml files (6 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
pkl
Explore:   circles  |  sunburst

py16476 LOC (67%) 81 files
c7141 LOC (29%) 37 files
pkl746 LOC (3%) 7 files
sh28 LOC (<1%) 1 file
h20 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 ".*/test_.*".
    • files with paths like ".*/test[.].*".
  • 127 files match defined criteria (24,411 LOC, 29.9% vs. main code):
    • 81 py files (16,476 LOC)
    • 37 c files (7,141 LOC)
    • 7 pkl files (746 LOC)
    • 1 sh files (28 LOC)
    • 1 h files (20 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
gitattributes
gitmodules
Explore:   circles  |  sunburst

yaml429 LOC (74%) 5 files
py67 LOC (11%) 1 file
gitignore63 LOC (10%) 12 files
dockerignore8 LOC (1%) 1 file
gitattributes5 LOC (<1%) 1 file
gitmodules3 LOC (<1%) 1 file
toml2 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/requirements[a-zA-Z0-9._-]*[.]txt".
    • files with paths like ".*/pyproject[.]toml".
    • files with paths like ".*/setup[.]py".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitmodules".
    • files with paths like ".*/[.]dockerignore".
    • files with paths like "(.*/)?[.]dockerignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*/[.]gitattributes".
  • 22 files match defined criteria (577 LOC, 0.7% vs. main code):
    • 5 yaml files (429 LOC)
    • 1 py files (67 LOC)
    • 12 gitignore files (63 LOC)
    • 1 dockerignore files (8 LOC)
    • 1 gitattributes files (5 LOC)
    • 1 gitmodules files (3 LOC)
    • 1 toml files (2 LOC)
Other Code
ini
Explore:   circles  |  sunburst

md1820 LOC (90%) 26 files
txt98 LOC (4%) 4 files
ini73 LOC (3%) 3 files
rst11 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]ini".
    • files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 34 files match defined criteria (2,002 LOC, 2.4% vs. main code):
    • 26 md files (1,820 LOC)
    • 4 txt files (98 LOC)
    • 3 ini files (73 LOC)
    • 1 rst files (11 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...
  • *.c files are analyzed with CStyleAnalyzer:
    • 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
  • *.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
  • *.m files are analyzed with CppAnalyzer:
    • 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
  • *.h files are analyzed with CppAnalyzer:
    • 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
  • *.cpp files are analyzed with CppAnalyzer:
    • 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
  • *.pkl 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
  • *.asm 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
  • *.cu 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
  • *.cuh 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
  • *.pyx 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
  • *.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
  • *.mat 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
  • *.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