openai / gpt-oss
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
metal
in
jsonl
  • 18 extensions are included in analyses: py, h, metal, cc, c, hpp, md, ts, txt, json, svg, toml, gitignore, yaml, in, m, jsonl, ipynb
  • 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.

main17308 LOC (46%) 110 files
test1668 LOC (4%) 16 files
generated3431 LOC (9%) 2 files
build and deployment163 LOC (<1%) 4 files
other14401 LOC (38%) 20 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
metal
jsonl
in
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 110 files match defined criteria (17,308 LOC, 100.0% vs. main code):
    • 53 *.py files (7,321 LOC)
    • 10 *.c files (3,909 LOC)
    • 14 *.metal files (2,232 LOC)
    • 16 *.h files (1,357 LOC)
    • 6 *.cc files (919 LOC)
    • 5 *.ts files (740 LOC)
    • 1 *.m files (423 LOC)
    • 3 *.hpp files (376 LOC)
    • 1 *.jsonl files (30 LOC)
    • 1 *.in files (1 LOC)
  • " *.py" is biggest, containing 42.3% of LOC.
  • " *.in" is smallest, containing 0.01% of LOC.


*.py7321 LOC (42%) 53 files
*.c3909 LOC (22%) 10 files
*.metal2232 LOC (12%) 14 files
*.h1357 LOC (7%) 16 files
*.cc919 LOC (5%) 6 files
*.ts740 LOC (4%) 5 files
*.m423 LOC (2%) 1 file
*.hpp376 LOC (2%) 3 files
*.jsonl30 LOC (<1%) 1 file
*.in1 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 ".*/[Tt]ests/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*/[Tt]est/.*".
  • 16 files match defined criteria (1,668 LOC, 9.6% vs. main code):
    • 5 *.hpp files (732 LOC)
    • 7 *.cc files (545 LOC)
    • 4 *.py files (391 LOC)
  • " *.hpp" is biggest, containing 43.88% of LOC.
  • " *.py" is smallest, containing 23.44% of LOC.


*.hpp732 LOC (43%) 5 files
*.cc545 LOC (32%) 7 files
*.py391 LOC (23%) 4 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/package[-]lock[.]json".
  • 2 files match defined criteria (3,431 LOC, 19.8% vs. main code). All matches are in *.json files.


*.json3431 LOC (100%) 2 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 ".*/pyproject[.]toml".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/CMakeLists[.]txt".
    • files with paths like ".*/package[-]lock[.]json".
    • files with paths like ".*/package[.]json".
  • 4 files match defined criteria (163 LOC, 0.9% vs. main code):
    • 2 *.gitignore files (111 LOC)
    • 2 *.toml files (52 LOC)
  • " *.gitignore" is biggest, containing 68.1% of LOC.
  • " *.toml" is smallest, containing 31.9% of LOC.


*.gitignore111 LOC (68%) 2 files
*.toml52 LOC (31%) 2 files
Other Code
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 ".*[.]txt".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]json".
  • 20 files match defined criteria (14,401 LOC, 83.2% vs. main code):
    • 1 *.ipynb files (9,407 LOC)
    • 4 *.json files (3,462 LOC)
    • 5 *.py files (661 LOC)
    • 6 *.md files (606 LOC)
    • 2 *.txt files (178 LOC)
    • 1 *.ts files (78 LOC)
    • 1 *.toml files (9 LOC)
  • " *.ipynb" is biggest, containing 65.32% of LOC.
  • " *.toml" is smallest, containing 0.06% of LOC.


*.ipynb9407 LOC (65%) 1 file
*.json3462 LOC (24%) 4 files
*.py661 LOC (4%) 5 files
*.md606 LOC (4%) 6 files
*.txt178 LOC (1%) 2 files
*.ts78 LOC (<1%) 1 file
*.toml9 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
  • *.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
  • *.metal 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
  • *.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
  • *.cc 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
  • *.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
  • *.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
  • *.hpp 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
  • *.jsonl files are analyzed with JsonAnalyzer:
    • 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

2026-06-24 10:39