openai / symphony 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
- 11 extensions are included in analyses: ex, exs, md, txt, yaml, sh, css, gitignore, py, gitattributes, toml
- 3 criteria are used to exclude files from analysis:
- exclude files with path like ".*/docs/.*" (Documentation) (4 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).
- The source code folder contains 106 files:
- 88 files are included in analyses.
- 18 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 ".*".
- 43 files match defined criteria (9,360 LOC, 100.0% vs. main code):
- 37 *.ex files (8,303 LOC)
- 1 *.py files (536 LOC)
- 1 *.css files (406 LOC)
- 3 *.exs files (112 LOC)
- 1 *.toml files (3 LOC)
- " *.ex" is biggest, containing 88.71% of LOC.
- " *.toml" is smallest, containing 0.03% of LOC.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*/[Tt]est/.*".
- files with paths like ".*_test[.].*".
- files with paths like ".*/test_.*".
- files with paths like ".*[-]test[-].*".
- 20 files match defined criteria (8,764 LOC, 93.6% vs. main code):
- 19 *.exs files (8,756 LOC)
- 1 *.sh files (8 LOC)
- " *.exs" is biggest, containing 99.91% of LOC.
- " *.sh" is smallest, containing 0.09% of LOC.
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 ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitattributes".
- files with paths like ".*[.]sh".
- files with paths like ".*/[.]gitignore".
- 3 files match defined criteria (52 LOC, 0.6% vs. main code):
- 1 *.gitignore files (40 LOC)
- 1 *.sh files (11 LOC)
- 1 *.gitattributes files (1 LOC)
- " *.gitignore" is biggest, containing 76.92% of LOC.
- " *.gitattributes" is smallest, containing 1.92% of LOC.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]md".
- files with paths like ".*[.]txt".
- files with paths like ".*/README[.][a-z0-9]+".
- 22 files match defined criteria (3,274 LOC, 35.0% vs. main code):
- 17 *.md files (3,179 LOC)
- 5 *.txt files (95 LOC)
- " *.md" is biggest, containing 97.1% of LOC.
- " *.txt" is smallest, containing 2.9% of LOC.
Analyzers
Info about analyzers used for source code examinations.
- *.ex 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
- *.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
- *.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
- *.exs 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
- *.toml 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
2026-06-24 10:41