bazelbuild / rules_python
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
in
txt
mod
patch
  • 13 extensions are included in analyses: py, in, md, yaml, bzl, go, txt, gitignore, json, sh, yml, mod, patch
  • 8 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (4 files).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (15 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (3 files).
    • exclude files with path like ".*/testdata/.*" (Test data) (244 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) (9 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.

main5070 LOC (67%) 54 files
test953 LOC (12%) 17 files
generated0 LOC (0%) 0 files
build and deployment5 LOC (<1%) 1 files
other1437 LOC (19%) 35 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 ".*".
  • 54 files match defined criteria (5,070 lines of code, 100.0% vs. main code):
    • 21 *.bzl files (1,950 lines of code)
    • 13 *.go files (1,580 lines of code)
    • 20 *.py files (1,540 lines of code)
  • " *.bzl" is biggest, containing 38.46% of code.
  • " *.py" is smallest, containing 30.37% of code.


*.bzl1950 LOC (38%) 21 files
*.go1580 LOC (31%) 13 files
*.py1540 LOC (30%) 20 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 ".*/[Tt]ests/.*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*__test__.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 17 files match defined criteria (953 lines of code, 18.8% vs. main code):
    • 11 *.py files (547 lines of code)
    • 3 *.go files (291 lines of code)
    • 2 *.bzl files (113 lines of code)
    • 1 *.sh files (2 lines of code)
  • " *.py" is biggest, containing 57.4% of code.
  • " *.sh" is smallest, containing 0.21% of code.


*.py547 LOC (57%) 11 files
*.go291 LOC (30%) 3 files
*.bzl113 LOC (11%) 2 files
*.sh2 LOC (<1%) 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".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
  • 1 file matches defined criteria (5 lines of code, 0.1% vs. main code). All matches are in *.sh files.


*.sh5 LOC (100%) 1 files
Other Code
patch
mod
in
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 ".*/go[.]mod".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]patch".
  • 35 files match defined criteria (1,437 lines of code, 28.3% vs. main code):
    • 12 *.md files (708 lines of code)
    • 17 *.py files (563 lines of code)
    • 1 *.yaml files (125 lines of code)
    • 1 *.patch files (16 lines of code)
    • 1 *.mod files (12 lines of code)
    • 2 *.in files (8 lines of code)
    • 1 *.json files (5 lines of code)
  • " *.md" is biggest, containing 49.27% of code.
  • " *.json" is smallest, containing 0.35% of code.


*.md708 LOC (49%) 12 files
*.py563 LOC (39%) 17 files
*.yaml125 LOC (8%) 1 files
*.patch16 LOC (1%) 1 files
*.mod12 LOC (<1%) 1 files
*.in8 LOC (<1%) 2 files
*.json5 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.bzl 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
  • *.go files are analyzed with GoLangAnalyzer:
    • 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
  • *.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


2022-02-03 05:31