openai/openai-dotnet
Code Volume Analysis scope, overview of main, test, generated, deployment, build, and other code. |
Source Code Analysis Scope
Files includes and excluded from analyses
scoping details...
- 15 extensions are included in analyses: cs, json, md, yml, ps1, csproj, targets, yaml, txt, props, gitignore, gitattributes, jsonl, ts, editorconfig
- 6 criteria are used to exclude files from analysis:
- exclude files with path like ".*/docs/.*" (Documentation) (39 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).
- The source code folder contains 4,470 files:
- 4,034 files are included in analyses.
- 436 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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*/[Tt]ests/.*".
- files with paths like ".*[.][Tt]ests[.].*".
- files with paths like ".*UnitTests[.][a-zA-Z0-9_]+".
- files with paths like ".*/[Tt]est/.*".
- files with paths like ".*/TestData/.*".
- files with paths like ".*[-]tests/.*".
- 106 files match defined criteria (27,604 LOC, 98.9% vs. main code):
- 100 cs files (27,490 LOC)
- 3 csproj files (93 LOC)
- 2 jsonl files (14 LOC)
- 1 targets files (7 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*[.]cs" AND any line of content like "[/][/][ ]*
- files with paths like ".*/package[-]lock[.]json".
- 2441 files match defined criteria (244,053 LOC, 874.5% vs. main code):
- 2,440 cs files (240,081 LOC)
- 1 json files (3,972 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*[.]targets".
- files with paths like ".*[.]props".
- files with paths like ".*[.]csproj".
- files with paths like ".*/package[.]json".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*/[.]gitattributes".
- files with paths like ".*[.]editorconfig".
- files with paths like "(.*/)?[.]editorconfig".
- files with paths like ".*/package[-]lock[.]json".
- files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
- files with paths like ".*/[.]github/actions/.*[.]ya?ml".
- files with paths like ".*/action[.]ya?ml".
- 22 files match defined criteria (1,334 LOC, 4.8% vs. main code):
- 8 yaml files (780 LOC)
- 2 gitignore files (162 LOC)
- 1 editorconfig files (156 LOC)
- 3 props files (120 LOC)
- 4 targets files (63 LOC)
- 2 csproj files (51 LOC)
- 2 gitattributes files (2 LOC)
Other Code
scope details...
- 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 ".*/[Ee]xamples/.*".
- files with paths like ".*[.]txt".
- 503 files match defined criteria (123,297 LOC, 441.8% vs. main code):
- 394 json files (115,199 LOC)
- 84 cs files (4,592 LOC)
- 21 md files (3,465 LOC)
- 2 csproj files (33 LOC)
- 1 targets files (7 LOC)
- 1 txt files (1 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...
- *.cs files are analyzed with CSharpAnalyzer:
- 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 (based on namespace heuristics)
- *.ps1 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
- *.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