openai / transformer-debugger
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
ini
cfg
  • 15 extensions are included in analyses: py, ts, tsx, md, json, css, ini, gitignore, txt, cfg, js, toml, sh, html, yaml
  • 3 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 ".*\.d\.ts" (Typescript definition files) (1 file).
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.

main26327 LOC (83%) 208 files
test4274 LOC (13%) 23 files
generated0 LOC (0%) 0 files
build and deployment223 LOC (<1%) 5 files
other684 LOC (2%) 12 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cfg
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 208 files match defined criteria (26,327 LOC, 100.0% vs. main code):
    • 73 *.py files (19,844 LOC)
    • 39 *.tsx files (4,106 LOC)
    • 90 *.ts files (2,303 LOC)
    • 1 *.js files (18 LOC)
    • 2 *.css files (17 LOC)
    • 1 *.yaml files (17 LOC)
    • 1 *.html files (16 LOC)
    • 1 *.cfg files (6 LOC)
  • " *.py" is biggest, containing 75.38% of LOC.
  • " *.cfg" is smallest, containing 0.02% of LOC.


*.py19844 LOC (75%) 73 files
*.tsx4106 LOC (15%) 39 files
*.ts2303 LOC (8%) 90 files
*.js18 LOC (<1%) 1 file
*.css17 LOC (<1%) 2 files
*.yaml17 LOC (<1%) 1 file
*.html16 LOC (<1%) 1 file
*.cfg6 LOC (<1%) 1 file
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 ".*/test_.*".
    • files with paths like ".*/[Tt]ests/.*".
  • 23 files match defined criteria (4,274 LOC, 16.2% vs. main code). All matches are in *.py files.


*.py4274 LOC (100%) 23 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*[.]sh".
    • files with paths like ".*/setup[.]py".
    • files with paths like ".*/pyproject[.]toml".
  • 5 files match defined criteria (223 LOC, 0.8% vs. main code):
    • 2 *.gitignore files (135 LOC)
    • 1 *.toml files (51 LOC)
    • 1 *.py files (29 LOC)
    • 1 *.sh files (8 LOC)
  • " *.gitignore" is biggest, containing 60.54% of LOC.
  • " *.sh" is smallest, containing 3.59% of LOC.


*.gitignore135 LOC (60%) 2 files
*.toml51 LOC (22%) 1 file
*.py29 LOC (13%) 1 file
*.sh8 LOC (3%) 1 file
Other Code
ini
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]ini".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]json".
  • 12 files match defined criteria (684 LOC, 2.6% vs. main code):
    • 6 *.md files (452 LOC)
    • 3 *.json files (201 LOC)
    • 2 *.ini files (28 LOC)
    • 1 *.txt files (3 LOC)
  • " *.md" is biggest, containing 66.08% of LOC.
  • " *.txt" is smallest, containing 0.44% of LOC.


*.md452 LOC (66%) 6 files
*.json201 LOC (29%) 3 files
*.ini28 LOC (4%) 2 files
*.txt3 LOC (<1%) 1 file
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.tsx 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
  • *.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
  • *.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
  • *.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
  • *.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
  • *.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
  • *.cfg files are analyzed with CfgAnalyzer:
    • 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

2026-06-24 10:35