openai / openai-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
- 8 extensions are included in analyses: py, md, yaml, json, gitignore, txt, sh, toml
- 1 criterion is used to exclude files from analysis:
- exclude files with path like ".*/extern(al)?/.*" (Dependencies) (1 file).
- The source code folder contains 1,490 files:
- 1,449 files are included in analyses.
- 41 files are excluded from analyses:
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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*".
- 1251 files match defined criteria (67,039 LOC, 100.0% vs. main code). All matches are in *.py files.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Build and Deployment Code
Source code used to configure or support build and deployment process.
- The following criteria are used to filter files:
- files with paths like ".*[.]sh".
- files with paths like ".*/pyproject[.]toml".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like "(.*/)?[.](idea|vscode|vs|gradle|mvn|settings|metadata|circleci)/.*".
- 3 files match defined criteria (294 LOC, 0.4% vs. main code):
- 1 *.toml files (260 LOC)
- 1 *.sh files (20 LOC)
- 1 *.gitignore files (14 LOC)
- " *.toml" is biggest, containing 88.44% of LOC.
- " *.gitignore" is smallest, containing 4.76% of LOC.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]md".
- files with paths like ".*/[Ee]xamples/.*".
- files with paths like ".*[.]json".
- files with paths like ".*[.]txt".
- files with paths like ".*/README[.][a-z0-9]+".
- 51 files match defined criteria (6,329 LOC, 9.4% vs. main code):
- 11 *.md files (4,679 LOC)
- 33 *.py files (1,530 LOC)
- 5 *.json files (113 LOC)
- 1 *.sh files (6 LOC)
- 1 *.txt files (1 LOC)
- " *.md" is biggest, containing 73.93% of LOC.
- " *.txt" is smallest, containing 0.02% of LOC.
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
2026-06-24 10:33